AMP for SEO: Pros, Cons, Measurement and When to Use

Quick conclusion: AMP is not an independent ranking factor and is no longer required for a page to be eligible to appear in Top Stories. If your website already achieves good Core Web Vitals using conventional HTML, CSS and JavaScript, you generally do not need to create AMP pages as well. Conversely, AMP may be worth testing for a publishing website with substantial mobile traffic that is experiencing performance problems that are difficult to resolve in the short term.

This article explains how AMP works, identifies the costs and limitations of implementation, covers the necessary technical signals, and shows how to measure results to decide whether to continue, test or remove AMP.

Should you implement AMP?

Situation	Recommendation
The website already has good LCP, INP and CLS, with complete design and functionality	No need to add AMP for SEO alone.
The website publishes articles, has substantial mobile traffic, and the canonical version remains slow	Consider testing AMP on a representative group of URLs.
The website depends on payments, personalisation, web applications or complex JavaScript	Prioritise optimising the canonical version; AMP may increase costs and limit functionality.
The website is already using AMP reliably	There is no need to remove it immediately. Compare the data before migrating.

The decision should be based on actual performance, visibility, engagement rate, conversions and maintenance costs—not merely on whether a URL has an AMP icon or format.

What is AMP?

AMP (Accelerated Mobile Pages) is an HTML format with strict rules governing HTML, CSS, JavaScript and resource loading. Its aim is to produce pages with predictable performance by restricting arbitrary JavaScript, managing resources through AMP elements and defining the dimensions of certain resources before they are displayed (according to the AMP HTML Specification).

AMP can be used in two models:

Paired AMP: the website maintains a canonical HTML page and a corresponding AMP page.
Canonical AMP: the AMP page itself is the primary version, with no separate HTML version maintained for the same content.

Google Search indexes AMP in much the same way as other web pages. Using AMP does not automatically improve a page’s ranking; visibility still depends on content quality, query relevance, crawlability, page experience and many other signals (according to About AMP on Google Search).

How does the AMP Cache work?

A valid AMP document may be stored by a supporting system in an AMP Cache. This proxy-based distribution mechanism can apply optimisations such as compression, image optimisation or resource preloading. However, not every AMP visit goes through Google AMP Cache. Speed also depends on the origin server, network, device, browser and how the platform distributes the URL (according to How AMP pages are cached).

AMP is therefore not magic that automatically makes every website faster. Its main benefits come from constraints on resources and loading order, validation, and—in some contexts—cache-based distribution.

Advantages of AMP for SEO

It can improve performance when the canonical version has problems

AMP limits many common causes of slow pages, such as arbitrary JavaScript, resources without declared dimensions or poorly prioritised loading. As a result, AMP can help teams create a lighter, more controllable version, particularly for article pages or landing pages with limited interaction.

To assess the outcome, monitor Core Web Vitals using real-user data:

LCP: Largest Contentful Paint; the good threshold is no more than 2.5 seconds.
INP: interaction responsiveness; the good threshold is below 200 milliseconds.
CLS: unexpected layout movement; the good threshold is below 0.1.

These thresholds are assessed at the 75th percentile of relevant user data. Good Core Web Vitals do not guarantee high rankings, but they help you evaluate real-world experience and identify performance problems (according to Understanding Core Web Vitals and Google search results).

It can make performance rules easier to validate

AMP has a validator and a clearly defined set of rules. Teams can incorporate validation into the development workflow to detect invalid tags, attributes or components before release. This is a control benefit, not a guarantee that every AMP page will be faster than its canonical version.

No longer required for Top Stories

Google has removed the AMP requirement from the eligibility criteria for appearing in Top Stories. Pages that do not use AMP may still be considered if they meet the relevant content and search-experience requirements (according to Evaluating page experience for a better web).

AMP should therefore not be implemented solely to qualify for Top Stories, rich results or prominent placement. Structured data can help Google understand content and assess eligibility for certain enhanced results, but it does not guarantee that they will be displayed.

Drawbacks and costs to consider first

Development and design constraints

You cannot use arbitrary JavaScript as you can on a conventional HTML page; many functions must be implemented through the corresponding AMP element.
Some interactive interfaces, personalisation, login flows or complex web applications are difficult to reproduce in full.
Teams may need to learn additional AMP components, rules and validation procedures.

Higher maintenance costs when there are two versions

If a website maintains both a canonical version and an AMP version, every significant change—content, internal links, advertising, forms, structured data, hreflang and conversion tracking—can diverge between the two versions. This creates significant technical debt if the publishing workflow is not well automated.

Advertising and measurement can become more complex

AMP has its own rules for advertising and interactive components. Publishers need to check ad formats, placement, revenue, viewability and separate AMP reporting when necessary (according to Google Ad Manager Help).

If users move between AMP and non-AMP pages, inconsistent analytics configuration can create duplicate sessions, lose traffic-source data or undercount events. AMP should therefore not be judged effective solely on the basis of views or time on page for one version.

Non-equivalent content can cause SEO problems

The AMP version must provide content and essential functionality equivalent to the canonical version. Do not create an AMP version that contains only an introduction and forces users to click again to read the main content. Check the menu, forms, videos, ads, related content, internal links and conversion actions on both versions.

How to implement AMP correctly

1. Choose a URL structure

You can use a parameter, subfolder, subdomain or separate URL suffix, provided the structure is consistent and the relationship to the canonical URL is clear. For example: /bai-viet/amp/ or /bai-viet.amp.html. Avoid creating multiple AMP URLs for the same content.

2. Set up bidirectional links

When an AMP version serves as an alternative, the canonical page should link to the AMP version:

<link rel="amphtml" href="https://example.com/bai-viet/amp/">

The AMP page should link back to the canonical URL:

<link rel="canonical" href="https://example.com/bai-viet/">

Bidirectional links help systems understand the relationship between two representations of the same content (see Making your page discoverable). If AMP is the only canonical page, the canonical tag is still required and may point to the same URL.

3. Keep content, titles and SEO data consistent

Keep the main content, title, headings and description equivalent.
Maintain appropriate internal links, hreflang annotations and image alt text.
Apply the correct structured data for the content type to both the AMP and canonical versions.
Ensure that images and videos have the required dimensions or attributes to reduce layout shift.
Check monetization components, forms and analytics events.

4. Validate before release

You can check directly in a browser by adding #development=1 to the AMP URL and then reviewing errors in Developer Tools. For automated workflows, use the AMP Validator in the web interface or install the command-line tool:

npm install -g amphtml-validator
amphtml-validator https://example.com/bai-viet/amp/

The expected result is PASS. If errors occur, fix the validation errors before assessing visibility or performance. AMP documentation also supports integrating the validator into CI/CD workflows (see Validate AMP pages).

How to measure AMP’s impact

Measure AMP using an experimental design rather than comparing it with the entire website. Select comparable URLs, segment the data by device and traffic source, and track the data over the same period.

Step 1: Record pre-implementation data

Core Web Vitals from Search Console or real-user data.
Impressions, clicks, click-through rate (CTR) and average position in Search Console.
Engagement rate, conversions, revenue per session and functional errors.
Server response time, page size and render-blocking resources.

Step 2: Check validity and indexability

Use AMP Validator to check syntax, URL Inspection to see what Google knows about the URL, and the Core Web Vitals report to monitor real-user data. Rich Results Test checks only whether structured data is eligible; it does not guarantee that the page will appear as a rich result.

Step 3: Compare business metrics

Compare AMP with the corresponding canonical pages by device, traffic source, landing-page group and content type. Check important events separately, such as form submissions, logins, add-to-cart actions, payments or newsletter sign-ups.

AMP is worth maintaining only if the observed benefits—such as improved performance or conversions—are large enough to offset the costs of building, testing, monitoring and maintaining two versions.

When should you implement, retain or remove AMP?

Consider implementing AMP when

The website primarily publishes articles or relatively simple landing pages.
Mobile users account for a significant share of traffic.
The canonical version has clear performance problems and the team cannot address them quickly through conventional optimization.
You can automate content synchronization, canonicalization, measurement and validation.
A controlled experiment shows sufficiently large benefits.

AMP is generally unnecessary when

The canonical version already has good Core Web Vitals.
AMP cannot provide essential functionality in full.
The team lacks the resources to maintain two versions.
The only reason is the expectation that AMP will automatically improve rankings or enable inclusion in Top Stories.

If you currently use AMP

Do not remove it in bulk simply because AMP is no longer required. First measure the share of AMP traffic, check traffic sources and conversions, assess the performance of the canonical version, and then test migrating a small group of URLs. If you remove AMP, create a redirect map, keep canonicalization consistent, check internal links, update the sitemap and monitor crawl errors after release.

In conclusion

AMP is an HTML format that can help standardize the creation and validation of lightweight pages, but it is not an independent ranking signal. Google no longer requires AMP for Top Stories, while Core Web Vitals and page experience can be improved through AMP or conventional web techniques.

Prioritize optimizing the canonical version first: remove unnecessary JavaScript, optimize images, improve server response times, use caching, specify resource dimensions and limit layout shift. Implement AMP only when testing shows that the practical benefits outweigh the operating costs, while ensuring that content, functionality, canonicalization and measurement remain synchronized.

Decision checklist:

Performance problems have been identified using real-user data.
The cost of AMP has been compared with the cost of optimizing the canonical version.
Equivalent content and functionality have been verified.
Canonical and rel="amphtml" have been configured correctly.
AMP Validator has been integrated into the testing workflow.
Performance, visibility and conversions have been monitored after implementation.

AMP for SEO: Pros, Cons and When to Implement