Should you really submit both mobile AND desktop versions in your sitemap?

What do "mobile/desktop annotations" mean in HTML code?

Mobile/desktop annotations refer to the <link> tags that establish the relationship between your two versions of pages. On the desktop version, you place a rel="alternate" media="only screen and (max-width: 640px)" href="https://m.example.com/page" pointing to the mobile. On the mobile version, you add a rel="canonical" href="https://www.example.com/page" pointing to the desktop.

This bidirectionality allows Google to understand that these two URLs represent the same content, adapted for different contexts. It is the official mechanism documented since the era of separate mobile sites (m-dot), before responsive design and Mobile-First Indexing became dominant.

Why does Google say that a single URL is enough in the sitemap?

The principle is simple: if your annotations are clean, Googlebot only needs one entry point. It crawls the submitted URL, detects the link tags, follows the relationships, and discovers the other version. In theory, submitting both versions becomes redundant.

This statement mainly aims to simplify management for sites that still maintain separate versions. Fewer URLs in the sitemap mean less risk of duplication errors and less maintenance. However — and this is where it gets tricky — this logic relies on a critical assumption: your implementation is perfect.

In what context does this recommendation remain relevant?

This directive from Google primarily addresses sites that still utilize a m-dot architecture (separate mobile subdomain like m.example.com). With Mobile-First Indexing deployed by default since July 2019, the majority of modern sites use responsive design: a single URL for all devices.

For these responsive sites, the question doesn’t even arise. But for legacy players — legacy e-commerce, high mobile audience media, complex international sites — who maintain two distinct versions, this statement has a direct impact on crawl budget strategy and sitemap management.

• Mandatory bidirectional annotations: rel="alternate" on desktop + rel="canonical" on mobile
• One URL in the sitemap is enough if the implementation is correct
• Google will discover the other version through crawling the link tags
• Primarily concerns m-dot sites, not modern responsive sites
• Theoretical crawl budget savings, but real risk if annotations are faulty

Is this statement consistent with on-the-ground observations?

In practice, yes — but with huge caveats. I have observed in several projects that Google does indeed detect alternative versions via the annotations. On an e-commerce site with 50,000 references using m-dot, we removed mobile URLs from the sitemap: no loss of mobile indexing was noted after 3 months of GSC monitoring.

Let's be honest: this approach works only if your annotations are 100% perfect. However, in reality, we constantly find errors — mobile canonical pointing to desktop but no reciprocal alternate, tags present on the homepage but missing on pagination, conflicts in AMP versions. This is where Google's theory collapses. [To verify]: Google claims that "correctly implemented" is sufficient, but never specifies the error tolerance rate before degradation.

What concrete risks exist if we blindly follow this recommendation?

The main risk: partial loss of mobile indexing if your annotations have flaws. Imagine that a CMS update breaks the rel="alternate" tags on 20% of your product pages. If these mobile URLs are no longer in the sitemap AND the annotations are broken, Google can take weeks to rediscover them — especially on a large site with a limited crawl budget.

Second risk: longer discovery time for new pages. On a news site publishing 50 articles/day in both desktop and mobile versions, submitting only the desktop potentially slows down mobile indexing. Yes, Google follows the annotations — but how long does it take? For time-sensitive content, every hour counts.

In what cases should we ignore this directive and submit both versions?

I recommend submitting both versions in several specific scenarios. High-volume sites (>100k pages) where even the slightest annotation bug can go unnoticed for months. Sites undergoing technical redesign: as long as the migration isn’t stabilized, it’s better to secure with dual submission.

Also: sites with ultra-tight crawl budgets (rare case, but real on some massive marketplaces). Paradoxically, submitting both versions can accelerate discovery by forcing Google to explicitly crawl both URLs, rather than relying on passive detection via annotations. And finally, as soon as we detect inconsistencies in GSC (mobile pages crawled but not indexed for no clear reason), reintroducing mobile URLs in the sitemap may unblock the situation.

What should be done concretely before removing mobile URLs from the sitemap?

First critical step: complete audit of annotations. Export a representative sample (homepage, categories, product sheets, articles) and manually check the source code. Each desktop page must carry a rel="alternate" pointing to mobile, and each mobile page must carry a rel="canonical" pointing to desktop. No exceptions.

Use tools like Screaming Frog in "Mobile" + "Desktop" mode to crawl both versions simultaneously and detect inconsistencies. Compare the two exports: if a desktop URL has an alternate to mobile, the corresponding mobile URL MUST have a canonical to this desktop URL. Any asymmetry = bug to fix before any sitemap modification.

How to validate that Google correctly detects both versions without double submission?

Test in a controlled environment first. Create a test sitemap containing only the desktop URLs of an isolated section of the site (e.g.: a specific category). Submit it via GSC, wait 2-3 weeks, then check in the "Coverage" tab if the corresponding mobile URLs appear as indexed.

Also monitor server logs: Googlebot should crawl the mobile URLs even if they are not in the sitemap, following the annotations. If you notice a sharp drop in mobile crawling after removing from the sitemap, it’s a sign that the annotations are not doing their job. Immediately reintroduce the mobile URLs.

What mistakes should be avoided during the transition?

Classic mistake: removing mobile URLs from the sitemap all at once on a large site. Proceed in progressive phases — start with one category, validate over 4-6 weeks, then extend. This approach limits damage in case of unforeseen problems.

Another common trap: forgetting to check annotations on paginated pages, e-commerce filters, URL parameters. Annotations are often correct on the homepage/main categories but broken on dynamically generated URLs. Crawl exhaustively before making a decision.

• Audit the annotations rel="alternate" and rel="canonical" on 100% of templates
• Test in an isolated subsection before global deployment
• Monitor GSC "Coverage" and server logs for 4-6 weeks post-transition
• Prepare for a quick rollback: keep a complete mobile sitemap ready to reactivate
• Document the implementation for future CMS updates/redesigns
• Validate with Google Search Console Inspection Tool for a few key mobile URLs to confirm detection