Where is the best place to host your AMP pages: subdomain, subdirectory, or parameter?

Why does Google remain neutral on the URL structure of AMP pages?

Mueller's statement reflects a technical reality: Google crawls and indexes AMP pages regardless of their location within the site's hierarchy. The algorithm does not give any ranking bonus to one method over another.

This neutrality aligns with AMP's technical philosophy: the format itself matters more than its location. HTML AMP validation and compliance with specifications are the real criteria for eligibility in the mobile carousel, not the chosen URL architecture.

What are the technical differences among these three approaches?

The subdomain (amp.site.com) completely isolates the AMP environment. This separation makes managing distinct infrastructures easier but fragments authority signals: Google technically treats the subdomain as a partially separate entity.

The subdirectory (/amp/article.html) centralizes everything under the main domain. All backlinks, history, and authority remain consolidated. This is the preferred structure when maximizing signal consistency is the goal.

URL parameters (?amp=1) generate an alternative version without changing the path. While technically simple, this method complicates canonical management and can create duplicates if parameters are not properly configured in Search Console.

Does this flexibility hide strategic implications?

Google's stated neutrality does not mean that all choices are equally valid for your ecosystem. The URL structure directly influences how you handle redirects, canonicals, and the distribution of ranking signals.

A site with strong domain authority should keep its AMP in a subdirectory to capitalize on that authority. Conversely, an isolated project with a dedicated technical team may justify a subdomain to simplify deployments.

• No direct SEO impact between subdomain, subdirectory, or parameter according to Google
• The choice depends on your technical constraints (infrastructure, teams, CMS)
• Authority signals consolidate better in a subdirectory than in a subdomain
• URL parameters require a rigorous configuration in Search Console to avoid duplicates
• The coherence of the canonical structure outweighs the type of URL chosen

Is this neutrality consistent with real-world observations?

In practice, sites that have migrated their AMP from a subdomain to a subdirectory often report a improvement in signal consolidation. Google theoretically treats subdomains as part of the main domain, but reality shows a less fluid distribution of authority.

News sites that have adopted subdirectories find that their AMP articles inherit internal PageRank more quickly. [To be verified] Google has never published comparative data on the speed of PageRank propagation between these structures, but real-world experience suggests a measurable difference.

What risks does this statement downplay?

Mueller does not explicitly mention the configuration traps specific to each method. URL parameters, for example, often generate duplicate content if you forget to declare the parameter in Search Console or if your canonical points to the wrong version.

The subdomain creates additional complexity for analytics tracking and data consolidation. You need to set up cross-domain tracking, which opens the door to measurement errors and session losses in Google Analytics.

In what cases does this rule not fully apply?

If your main domain suffers from manual or algorithmic penalties, isolating your AMP on a subdomain could theoretically limit contamination. Google claims to treat subdomains as part of the domain, but this technical separation does exist.

For multilingual or multi-regional sites, the URL structure of AMP must align with your hreflang strategy. A parameter may complicate the declaration of alternative language versions, while a subdirectory aligns better with your existing hierarchy.

What structure should you choose for your site?

Prefer the subdirectory (/amp/) if you seek simplicity and maximum signal consolidation. It is the cleanest setup for maintaining domain authority and simplifying canonical management. Most modern CMSs support this structure natively.

Choose the subdomain (amp.site.com) only if you have a compelling technical reason: separate infrastructure, dedicated team, or need for complete isolation for testing. Accept the additional configuration cost (cross-domain, analytics, Search Console).

URL parameters (?amp=1) are suitable for small sites or environments where modifying the hierarchy is impossible. However, this solution demands absolute rigor in Search Console configuration and canonical management to avoid indexed duplicates.

How can you check that your current configuration is optimal?

Use the URL Inspection tool in Search Console to verify that Google correctly detects the relationship between your canonical page and its AMP version. The report should explicitly show the link between both versions without error.

Check your XML sitemap file: if you are using an AMP subdomain, create a dedicated sitemap on that subdomain and declare it separately in Search Console. For a subdirectory, integrate the AMP URLs into your main sitemap with a specific tag.

Analyze your server logs to identify any crawl anomalies. If Googlebot crawls your AMP and canonical pages at highly unbalanced frequencies, your structure may be generating inefficiencies that a migration could fix.

What errors should you absolutely avoid in implementation?

Never create redirect chains between your versions. If a user clicks on an AMP result, they should land directly on the AMP page, not on a canonical that then redirects to the AMP. These circular redirects degrade the experience and consume crawl budget.

Avoid changing your AMP URL structure without a rigorous migration plan. Previously generated AMP URLs remain cached in the Google ecosystem (carousels, saved results). A sudden migration creates 404s that can persist for several weeks.

If your technical choice proves to be complex to maintain or generates crawl inefficiencies, a migration to a more coherent architecture may be necessary. These technical decisions often require thorough analysis of your infrastructure and current SEO signals. For critical configurations or high-traffic sites, the support of an SEO agency specialized in AMP migrations can help you avoid costly errors and accelerate the stabilization of your performance.

• Check the consistency of canonical and amphtml tags across all your pages
• Correctly declare your AMP URLs in Search Console according to the chosen structure
• Set up cross-domain tracking if you are using an AMP subdomain
• Test the canonical/AMP relationship using the URL Inspection tool for each page template
• Audit your server logs to identify inefficient crawl patterns
• Document your technical choice to avoid arbitrary future changes