Is it really sufficient to include only one version, mobile or desktop, in your XML sitemap?

Why does Google allow only submitting one version of the URL?

When a site maintains distinct URLs for mobile and desktop, Google relies primarily on the HTML annotations to understand the relationship between these versions. The rel="alternate" media="only screen and (max-width: 640px)" tags on the desktop side and rel="canonical" on the mobile side explicitly indicate to the crawler which version to serve based on the context.

If these annotations are present and consistent, Googlebot can discover all URL pairs by crawling only one version. The sitemap then becomes redundant for this specific function — it is merely used to speed up initial discovery or signal deep pages.

What constitutes a correct bidirectional annotation?

The bidirectional annotation requires that each URL points to its counterpart and vice versa. On the desktop version https://example.com/page, there should be a link to https://m.example.com/page with rel="alternate" and the appropriate media attribute. On the mobile version, a rel="canonical" must point back to the desktop version.

This symmetry allows Google to automatically map all pairs without needing a comprehensive inventory in the sitemap. But beware: a missing, malformed, or inconsistent annotation breaks this logic and can leave orphan pages or create canonicalization conflicts.

In what context does this practice still apply?

This setup primarily concerns sites that have chosen to maintain separate mobile/desktop URLs rather than adopt a responsive design with unique URLs. This architectural choice has become a minority since the widespread adoption of responsive design and mobile-first indexing.

The sites still affected are often historical platforms (legacy e-commerce, complex media portals) where a complete redesign is postponed for budgetary or technical reasons. For these sites, managing annotations and sitemaps remains critical, as an error can fragment indexing between the two versions.

• A sitemap can contain only one version (mobile OR desktop) if the HTML annotations are perfectly implemented.
• Bidirectional annotations (rel="alternate" + rel="canonical") must cover 100% of URL pairs without exception.
• This approach pertains to sites with separate URLs, a minority configuration compared to responsive design.
• The sitemap remains useful for rapid discovery and managing deep pages, even with correct annotations.
• Google uses HTML annotations as the primary source for mapping mobile/desktop relationships.

Is this statement consistent with real-world observations?

On paper, Google's logic is perfectly defensible. HTML annotations are indeed more reliable than a sitemap for defining canonical relationships, as they are directly attached to each resource. In theory, a crawler can rebuild the entire tree by following these links.

However — and here lies the problem — in practice, annotations are rarely perfect across an entire site. Field audits regularly reveal inconsistencies: orphan pages without rel="canonical", asymmetric annotations (present in one direction but not the other), miscalibrated media attributes, or worse, conflicts where multiple mobile pages point to the same desktop page with different canonicals. [To be verified] to what extent Googlebot tolerates these partial errors without degrading indexing.

What risks does this minimalist approach entail?

Including just one version in the sitemap creates a total dependency on the quality of the annotations. If an annotation is missing or erroneous in one part of the site, Google may never discover the counterpart mobile (or desktop) pages. The risk is particularly high on large sites with dynamically generated content.

Some practitioners prefer a defensive approach: submit both versions in the sitemap, even if annotations are present. This redundancy provides an extra layer of security and speeds up discovery, especially after a massive deployment or update. Google does not penalize this practice — it simply ignores detected duplicates.

Should we still care about this configuration in a mobile-first indexing environment?

Since the widespread shift to mobile-first indexing, Google crawls and indexes the mobile version primarily. For a site with separate URLs, this means the mobile URL effectively becomes the canonical reference — even if the rel="canonical" technically points to the desktop.

This inversion sometimes creates confusion: SEO professionals observe that Google indexes the mobile version while displaying the desktop URL in the SERP, thanks to the annotations. As a result, the mobile sitemap becomes more critical than the desktop. If you could submit only one version, favor the mobile — this is what Googlebot crawls first and what serves as the basis for content evaluation.

What steps should be taken on a site with separate URLs?

Start with a complete audit of bidirectional annotations. Export all mobile/desktop URL pairs from your CMS or database, then check that each desktop page contains a rel="alternate" pointing to its mobile version, and vice versa a rel="canonical" from the mobile to the desktop. Tools like Screaming Frog or OnCrawl can automate this verification on scale.

If the annotations are solid and comprehensive, you can technically submit only one sitemap — favor the mobile sitemap, as this is the version that Googlebot crawls first since the mobile-first indexing. But monitor coverage in Search Console: any absent or excluded page should trigger an immediate check of the corresponding annotations.

What mistakes to avoid in this configuration?

The classic mistake is to correct annotations on only part of the site, creating an inconsistency between sections. For example, new pages follow best practices, but the old catalog remains orphaned. Google may then index partially, with mobile or desktop versions missing based on section.

Another pitfall: changing URLs (structure change, moving from /m/ to m.example.com) without updating existing annotations. Old pages continue pointing to outdated URLs, breaking bidirectionality. An incomplete sitemap then hides these errors until they translate to traffic drops.

How to check if the configuration is working correctly?

Use Search Console to compare submitted URLs and indexed URLs. If you submitted only the mobile sitemap, check that desktop versions correctly appear in the coverage reports with a status of "Alternative page with proper canonical tag". If desktop pages are indexed when you intended to prioritize mobile, this is a signal of faulty annotations.

Also test using the URL inspection tool: enter a mobile URL and check that Google correctly recognizes the canonical pointing to the desktop (and vice versa). The inspection report explicitly displays the declared canonical and the one Google has selected — any discrepancies warrant investigation.

• Audit the completeness and symmetry of rel="alternate" and rel="canonical" annotations across the site.
• Favor the mobile sitemap if you submit only one version, as Google crawls in mobile-first.
• Monitor Search Console coverage reports to detect orphan pages or canonicalization conflicts.
• Set up automated annotation monitoring with every deployment of new pages.
• Regularly test with the URL inspection tool to validate that Google correctly interprets mobile/desktop relationships.
• Document the sitemap strategy to avoid regressions during team or vendor changes.