What Are AMP Pages? Do You Still Need Them?
AMP is an open-source HTML framework for stripped-down, fast mobile pages. Since Google removed the AMP requirement for Top Stories in 2021, it is optional: plain fast pages compete equally.
Explain It Like I'm 5
AMP was a special fast-lane format Google promoted for mobile news: strip the page to essentials and it loads instantly. Then Google made regular pages eligible for the same perks, so most sites dropped the extra workload. AMP is still around, but the VIP pass it offered is gone.
Understanding AMP
The Accelerated Mobile Pages project launched in 2015 as a Google-backed open-source framework: restricted components, cached delivery, and near-instant loads. Its heyday ran through the late 2010s, when AMP format was the entry ticket to Google's Top Stories carousel on mobile.
The turning point was the Page Experience update era: with the June 2021 rollout, Google removed the AMP requirement for Top Stories eligibility, opening the carousel to any page meeting news content and experience criteria. Publisher adoption has declined steadily since, and the framework's momentum has largely wound down.
AMP's technical constraints (validated components, no custom JS, cached versions served from Google's cache) traded flexibility for speed. Modern performance practice achieves comparable results with standard HTML plus performance discipline: no framework lock-in, no dual-maintenance of AMP and canonical pages, no cache intermediaries.
Who still uses AMP: some news publishers with existing pipelines, regions where the cache economics still help, and edge cases with extreme bandwidth constraints. For new sites in 2024, the default answer is standard fast pages with Core Web Vitals discipline.
Types of AMP Pages
AMP News Carousel Era (2015-2021)
AMP format as the ticket to Top Stories.
Example: A news publisher maintaining AMP versions solely for carousel eligibility.
Post-2021 Equality
Any fast page competing for the same placements.
Example: A standard page with strong vitals ranking in Top Stories without AMP.
Why AMP Barely Matters Now
AMP's ranking privileges are gone; speed is achievable without its constraints. The decision is now infrastructure economics, not SEO advantage.
Best Practices
Default to Standard Fast Pages
Core Web Vitals discipline on your own stack beats maintaining parallel AMP versions for zero privilege.
Audit Legacy AMP Installations
If AMP exists on your site, verify canonicalization, structured data parity, and whether removing it simplifies without loss.
Invest in Performance Fundamentals
The benefits AMP promised are delivered today by image optimization, CDN, minimal JS, and measurement.
Match Metrics, Not Formats
The goal is LCP/INP/CLS performance. Any format achieving it competes fully.
Common Mistakes
Building new AMP pipelines in the 2020s
Fix: The privilege that justified AMP is gone. New builds inherit constraints without advantage.
Assuming AMP means fast
Fix: AMP guarantees its framework's constraints, not your field-data vitals. Standard pages routinely outperform it.
Ignoring canonical/duplicate signals when AMP exists
Fix: Parallel versions demand meticulous canonical and linking hygiene, which is exactly the maintenance burden worth ending.
WPLink and Page Speed
WPLink runs locally on your machine and writes plain HTML links into content, adding nothing to page weight. The fastest page is the one carrying no extra framework at all.
Frequently Asked Questions
Related Articles
Ready to optimize your internal links?
Get started with WPLink today and see the difference.
Download WPLink