Does an Aged Domain’s Old AMP Pages Cause Problems Today?

Q: How do I check if an aged domain has indexed AMP pages?

Run a site search using site:domain.com inurl:amp in Google to see if AMP URLs are still indexed separately from the main pages.

Rarely, but they’re worth cleaning up — Google retired AMP’s special search treatment (the lightning-bolt carousel and mobile ranking boost) between 2021 and 2024, so an aged domain’s leftover AMP pages are now just ordinary duplicate-content risks rather than the ranking advantage they once represented, and the fix is standard canonicalization or removal, not urgent damage control.

Last updated: September 2026.

What AMP Used to Do, and What Changed

Accelerated Mobile Pages launched in 2015 as a stripped-down HTML format that loaded near-instantly on mobile and, for years, was rewarded with a dedicated carousel placement in mobile search results for news content. Google began phasing out AMP’s special treatment as Core Web Vitals became the primary page-experience signal, and by 2024 AMP no longer carried any unique ranking benefit — any page meeting Core Web Vitals thresholds, AMP or not, is eligible for the same search features.

What Leftover AMP Pages Can Actually Cause

Duplicate content without canonical tags. If an aged domain’s AMP pages (at /amp/ or on an amp. subdomain) don’t correctly canonicalize to the main version, Google may treat them as separate, competing pages.
Indexed AMP URLs outranking the main page. In some legacy setups, the AMP version accumulated its own backlinks and indexing signals separately from the main URL, which can fragment authority that should be consolidated on one canonical version.
Broken AMP-specific markup. Old AMP pages sometimes reference deprecated AMP components or scripts that throw console errors — cosmetically irrelevant to rankings now, but worth cleaning up if you’re auditing technical debt.

How to Handle Legacy AMP Pages on an Aged Domain

Check whether AMP URLs are still live and indexed via a site: search for inurl:amp on the domain.
If AMP pages are still indexed separately, add or fix the canonical tag pointing to the main non-AMP URL, or 301 redirect the AMP version entirely if you’re not maintaining an AMP setup going forward.
Remove any AMP-specific structured data or <link rel="amphtml"> tags from the main pages if you’re fully discontinuing AMP, since referencing a redirected or removed AMP URL serves no purpose.
Prioritize Core Web Vitals on the main page instead — that’s the actual page-experience signal Google evaluates today, AMP or not.

Frequently Asked Questions

Do old AMP pages still help an aged domain rank in Google?

No. Google retired AMP’s special search treatment and ranking benefits between 2021 and 2024. Any current ranking advantage comes from meeting Core Web Vitals thresholds, which applies equally to AMP and non-AMP pages.

Can leftover AMP pages hurt an aged domain’s SEO?

They can create duplicate content issues if not properly canonicalized to the main page, potentially fragmenting backlink and indexing signals — but this is a technical cleanup issue, not a penalty or trust problem.

Should I keep or remove AMP pages on an aged domain I just bought?

Most sites benefit from removing or redirecting AMP pages today, since AMP no longer provides a ranking advantage and maintaining a separate page format adds technical overhead with no upside.