Greg Ichshenko

Calgary SEO expert and digital marketing specialist,
developing advertising strategies for businesses of all sizes

(403) 308-5949

greg@to-the-top.ca
1509 14 Ave SW, Calgary,
AB T3C 0W4

    Submit your request or question, and I will get back
    to you shortly

    What Is AMP in SEO?

    AMP is an open-source HTML framework, originally named Accelerated Mobile Pages, that Google launched with publishers in 2015 to make pages load fast on phones. In SEO terms, an AMP page is a stripped-down, validated version of a page that once earned special treatment in Google’s mobile results. That treatment ended in 2021, when Google opened its Top Stories carousel to non-AMP pages and dropped the AMP badge. Then on 1 July 2026 Google stopped serving AMP results from its own cache and began sending searchers straight to the publisher’s page. Today Google says AMP content ranks like any other page, so AMP is one way to build a fast page rather than an SEO advantage in itself.

    The letters AMP with a lightning bolt, introducing what AMP means in SEO

    What AMP stands for, and why the name changed

    AMP originally stood for Accelerated Mobile Pages, which is why “what does AMP stand for in SEO” is still a common search. The project was announced on 7 October 2015 by Google together with news publishers and technology partners such as Twitter, Pinterest, LinkedIn and WordPress. Its idea was simple: limit what a page is allowed to contain, so that it cannot be slowed down by heavy scripts, oversized styles or layout surprises. The project moved to open governance in 2018 and has been part of the OpenJS Foundation since 2019, so it is no longer a Google product in the formal sense, even though Google remains its best-known supporter.

    Over time the project dropped the long form of the name. Google’s current documentation and the project’s own site, amp.dev, simply say “AMP”, and Google’s FAQ answers “Are AMP pages mobile-only?” with a plain no, because AMP pages work on desktop and tablets as well. That matters for the SEO meaning of the term. AMP is a way of building pages, and it was always one possible tool for mobile SEO rather than mobile SEO itself, which is about how a whole site works for people on phones.

    Timeline graphic showing the rise of AMP in 2015 and its decline after 2021

    Why AMP mattered for SEO, and what changed in 2021

    AMP became an SEO topic because of where Google showed it. From February 2016, Google began showing AMP versions of pages in mobile search results, first in the Top Stories section and then in the main results, marked with a small lightning bolt icon. For news publishers, Top Stories was the prize, and AMP was effectively the entry ticket, so many sites built AMP versions of every article. Plugins, agencies and whole publishing workflows grew up around that one requirement. The framework also drew criticism, because publishers gave up design control and many felt that Google gained too much say over how the open web was built.

    The turning point was the page experience update. In a Search Central blog post dated 19 April 2021, Google said that Top Stories would include all news content that meets the Google News policies, that the AMP format was no longer required, and that it would stop showing the AMP badge. The rollout began in mid-June 2021. From then on, a regular page and an AMP page competed on the same terms, and page experience signals such as Core Web Vitals, which apply to any page, replaced the framework as the speed factor Google looked at. Some large platforms later moved away from AMP, and the reason to build it for search largely went with them.

    Diagram of a canonical page linked to its AMP version with rel="amphtml" and rel="canonical" tags

    How an AMP page works now

    Most AMP setups pair two versions of the same content. The regular page, which is the canonical version, carries a <link rel="amphtml"> tag pointing to its AMP twin, and the AMP page carries a <link rel="canonical"> tag pointing back. Google requires that every AMP page link to a canonical page, which can also be the AMP page itself on a site built entirely in AMP. Google also asks that visitors can see the same content and complete the same actions on both versions where possible, and that both versions use the same structured data.

    AMP HTML looks like ordinary HTML with rules attached. The page loads the AMP JavaScript library, replaces some standard elements with AMP components such as amp-img, and keeps all of its own styles under 75,000 bytes, which is a validation error if exceeded. Custom JavaScript can only run through the amp-script component, inside a Web Worker and with restrictions. Every page has to pass validation against the AMP specification. Search Console’s AMP status report lists the problems Google finds, and Google states that an AMP page with a critical issue is invalid and cannot be shown on Google, which is why a stray inline style from a theme update can quietly take a page out of AMP features.

    The biggest recent change is how searchers reach the page. For years, tapping an AMP result opened a copy that Google had stored in its Google AMP Cache, shown inside Google’s AMP viewer, and publishers had to set up signed exchanges if they wanted their own address to appear. On 1 July 2026 Google announced that Google Search “will now take users directly to the publisher’s AMP host pages”, and it removed the AMP viewer, AMP Cache and signed exchange references from its documentation. An AMP page in Google Search now loads from the publisher’s own server, like any other page, so its speed depends on that server and on how the page is built.

    Search results on a phone, illustrating whether AMP still helps rankings in 2026

    Does AMP help rankings in 2026?

    Not directly. Google’s documentation says that Google Search indexes AMP pages just like other web pages and applies the same standard to all pages, regardless of the technology used to build them, and its July 2026 note repeats that AMP content will continue to rank like any other web page. There is no AMP ranking bonus, no reserved carousel and, since 2021, no badge that might lift clicks. Since July 2026 there is also no cache delivery that once made AMP results open almost instantly from Google’s own servers.

    What AMP can still do is help a page be fast, and speed is part of page experience. Google’s page experience guidance says that Core Web Vitals are used by its ranking systems, but also that good scores do not guarantee top rankings and that relevance comes first. A slow page that becomes fast may see some benefit, whatever technology made it fast. A well-built regular page can reach the same result, so a pitch that presents AMP as an SEO boost in 2026 is describing the search results of 2018. Relevance and the quality of the content still matter far more than the framework a page is built with.

    Comparison graphic of AMP and the three Core Web Vitals metrics

    AMP and Core Web Vitals are different things

    The two are often mixed up, but one is a tool and the other is a measurement. Core Web Vitals are Google’s real-user measures of loading, responsiveness and visual stability: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Google’s documentation recommends an LCP within 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1, and Search Console’s Core Web Vitals report groups pages by those field results. AMP is one way to build a page that has a good chance of meeting those targets, because its rules prevent many of the usual causes of slowness and layout shift, though it does not guarantee them.

    The framework does not guarantee the scores, though. An AMP page loaded with heavy ad units or large images can still miss the targets, while a regular page with compressed images, a lean theme, few scripts and decent hosting can meet them too, as long as field data confirms it. Since the July 2026 change, Google Search opens both kinds of page from the publisher’s own host rather than from a Google cache, so neither gets a delivery advantage from Google. The useful target is therefore the measurement itself, and the article on how Core Web Vitals affect rankings explains what those scores do and do not change.

    Illustration of the design and maintenance tradeoffs of AMP pages

    What AMP costs a site to run

    AMP’s speed comes from restriction, and the restrictions are where the cost lies. Custom scripts have to be replaced with AMP components, rewritten for amp-script or embedded in a restricted iframe, which affects things such as calculators, booking widgets, chat tools and complex forms. Styles have to fit inside the 75,000-byte limit. Third-party tools need an AMP-compatible component or a workaround, and some features cannot be reproduced on the AMP page without changing how they work.

    A paired setup also means two versions of every page to keep in step. Google wants the AMP page to match the canonical page in content, actions and structured data, so every edit, plugin update or theme change has to work on both. When the two drift apart, the usual symptoms are missing content on the AMP side, broken canonical tags, or validation errors that remove the AMP version from AMP features. None of this is a reason to panic about an existing setup, but it is a real, ongoing workload that a regular, well-built page does not carry.

    WordPress dashboard settings illustrating AMP setup on a small business site

    AMP on WordPress and small business sites

    On WordPress, AMP usually comes from a plugin. The official AMP plugin, which its WordPress.org listing describes as supported by the AMP team, offers three template modes: Standard, where the whole site is AMP; Transitional, where one theme serves both an AMP and a non-AMP version; and Reader, where a separate simplified theme serves the AMP version. As of November 2026, its WordPress.org listing shows more than 300,000 active installations, a last update about two years ago, and a warning that it has not been tested with the latest three major WordPress releases. Anyone considering a new AMP setup should weigh that maintenance picture, because an add-on that touches every page needs to keep up with WordPress itself.

    For most small and mid-sized business sites, such as a Calgary contractor, a clinic, a law office or an Edmonton retailer, the case for adding AMP now is weak. These sites do not compete for Top Stories, their pages often rely on forms, booking tools and tracking scripts that AMP restricts, and the speed AMP once gained from Google’s cache no longer exists in Search. The same effort spent on the regular site usually goes further.

    Common causes of slow small business sites include oversized images, too many plugins and scripts, a heavy page builder or slow hosting, and the usual speed fixes address those directly on the pages people already use. A website audit is a sensible first move before any rebuild, because it shows which pages are slow, why, and whether the problem is the page, the theme or the host.

    Decision chart showing when AMP is worth it and when it is not

    When AMP is worth it, and when it is not

    The answer depends mostly on whether a site already runs AMP and what kind of site it is. The table below sums up the decision as a practitioner would make it today, based on Google’s current documentation.

    Situation Suggested approach Why
    Small business site with no AMP Do not add it; improve the regular pages No ranking bonus, no cache delivery in Search since July 2026, and restrictions on forms and scripts
    News or content publisher with a working, valid AMP setup Keep it while it stays valid and maintained, and judge it by Core Web Vitals Google indexes and ranks valid AMP like any other page; removing it is a project of its own
    Any site running an outdated or broken AMP plugin Plan to remove AMP, or fix the plugin, after checking the AMP status report Invalid AMP pages cannot be shown on Google, and an unmaintained plugin is a maintenance risk
    Site built entirely in AMP (AMP is the canonical page) Treat it as the site’s normal code and maintain it There is no second version to drop; the pages are the site

    For a site that decides to drop AMP and keep its regular pages, Google documents the safe route: remove the rel="amphtml" link from each canonical page, then make the old AMP URL return a 301 or 302 redirect to its canonical page. The companion article on what AMP still does to a site that already has it covers how to find leftover AMP pages and what to check before and after removal.

    AMP was a smart answer to a real problem in 2015, when mobile pages were slow and Google rewarded the format with visibility. In 2026 it is a valid but niche way to build fast pages, and for most businesses the better investment is a fast, well-structured regular site with content that answers what people search for. SEO Company To-The-TOP! is a Calgary-based SEO company founded in 2007, and a conversation with To-The-TOP! can help sort out whether an AMP setup, a speed problem or something else is holding a site back.

    Contact Calgary SEO Company To-The-TOP!

    Questions about anything in this article, or about your own rankings? Talk to a Calgary SEO specialist directly.

    Phone: (403) 308-5949
    Address: 1509 14 Ave SW, Calgary, AB T3C 0W4

    Hours:
    Monday to Friday: 10:00 am – 7:00 pm
    Saturday: 12:00 pm – 4:00 pm
    Sunday: closed