AMP markup: no ranking or feature benefit since July 2026

What it means

This page advertises an AMP variant via a <link rel="amphtml"> tag. On 1 July 2026, Google removed all AMP-related content from its Search developer documentation — AMP Viewer, AMP Cache, and Signed Exchange references are gone. AMP no longer carries any special treatment, ranking signal, or feature eligibility in Google Search. This check is HTML-level (a link tag), not JSON-LD.

Why it matters

AMP's relationship with Google Search ended gradually. Top Stories dropped its AMP requirement in 2021 when Core Web Vitals replaced AMP eligibility as the page-experience gate — from then on, any fast, well-structured page qualified. The 1 July 2026 documentation removal formalized what was already true: there is no Search advantage to serving AMP. Maintaining an AMP version carries real cost — a separate template to keep in sync, extra URLs for Googlebot to discover and compare, and content or structured-data inconsistencies between AMP and canonical that can confuse crawlers.

How to fix it

1. Remove the <link rel="amphtml" href="/amp/..."> tag from canonical pages.
2. Set up 301 redirects from all /amp/* URLs to their canonical equivalents to preserve links and consolidate signals.
3. Remove AMP-specific templates and build tooling once redirects are confirmed working.
4. If a CMS plugin generated the AMP pages (e.g. a WordPress AMP plugin), disable it and confirm the redirect rules are in place before removing it entirely.
5. Invest the freed effort in Core Web Vitals, which are the actual page-experience signals Google uses.

Example

<!-- canonical HTML page still advertises an AMP variant -->
<link rel="amphtml" href="https://example.com/article/amp">

<!-- remove the amphtml link; 301 the /amp/ URL to canonical -->
<!-- (no amphtml link) -->
# server: 301 https://example.com/article/amp -> https://example.com/article

Google removed AMP from Search on 1 Jul 2026. Delete the rel=amphtml link and 301-redirect /amp/ URLs to their canonical equivalents so crawl budget isn't wasted on dead variants.

When it's not a problem

AMP for Email is a separate specification unaffected by this deprecation and is not flagged. If leaving AMP pages in place is a deliberate choice — a content partnership or distribution channel that still consumes AMP — this notice can be suppressed for the affected URL patterns.

How Crawlinx detects it

At parse time we detect a <link rel="amphtml"> on the page. Since Google dropped AMP from Search in July 2026, advertising an AMP variant now earns no ranking or feature benefit — so we flag it as legacy markup.

How common is it?

156 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

FAQ

Is AMP dead for SEO?

For Google Search, effectively yes — AMP pages lost all ranking and feature preference on 1 Jul 2026. There's no Top Stories or search benefit to maintaining AMP versions anymore.

How do I remove AMP safely?

Drop the rel=amphtml link from your canonical pages, then 301-redirect the /amp/ URLs to their canonical equivalents so existing links and any lingering index entries consolidate cleanly.

Will removing AMP hurt my rankings?

No — the canonical HTML page is what ranks now. As long as it's fast and passes Core Web Vitals, retiring AMP removes maintenance overhead with no downside.

Related guides

• Google Search Updates 2025-2026: What Changed