Should you really exclude mobile URLs from XML sitemaps?

Why does Google emphasize canonical URLs in sitemaps?

When you maintain two distinct versions of your site (desktop and mobile on separate URLs), Google does not want you to submit the same content twice. The sitemap should reflect your canonical structure, not all of your technical URLs.

Submitting mobile URLs alongside desktop URLs creates confusion in the crawling process. Google then has to spend extra crawl budget to understand that these URLs point to the same content. The engine prefers that you clearly indicate which version holds authority.

What exactly does “correct annotations” mean?

This part of the statement is crucial. Google requires a complete two-way annotation: each desktop page must have a link rel="alternate" media="only screen and (max-width: 640px)" tag pointing to its mobile version.

Conversely, each mobile page must have a link rel="canonical" tag pointing to the desktop version. This symmetry allows Google to understand the relationship between the URLs and to choose the correct version based on the search context.

Is this approach still relevant with mobile-first indexing?

The shift to mobile-first indexing complicates matters. Officially, Google is now indexing the mobile version of your pages primarily, even for desktop results. Still, the recommendation regarding sitemaps remains unchanged.

In this context, the canonical URL remains that of the desktop in 90% of cases, but Google evaluates the content of the mobile version. The annotation remains the technical pivot that ensures the engine understands your architecture.

• Include only canonical URLs (typically desktop) in your XML sitemaps
• Each desktop page must point to its mobile version through rel="alternate"
• Each mobile page must point to its desktop version through rel="canonical"
• Mobile-first indexing does not change the logic of two-way annotations
• Separate mobile URLs (m.example.com) must have their own robots.txt but not their own sitemap

Is this recommendation consistent with observed practices?

Google's recommendation makes theoretical sense but presents a practical contradiction. With mobile-first indexing, Google claims to prioritize indexing the mobile version, yet it asks for desktop URLs to be submitted in sitemaps. This is counterintuitive for a bot.

In reality, tests show that Google first follows the URLs in the sitemap, then discovers mobile versions through annotations. The crawl remains driven by canonical URLs, even though content evaluation occurs on the mobile version. This method works but introduces unnecessary complexity.

What situations cause issues with this rule?

Sites with high editorial velocity face challenges. If you first publish on mobile (which is becoming common), waiting for the desktop version to be ready before submitting the URL to the sitemap delays indexing. Some publishers have circumvented this by submitting mobile URLs anyway.

Google generally turns a blind eye to this practice as long as the annotations are correct. [To be verified] No official documentation confirms that submitting both versions truly penalizes, but it uses up crawl budget without added value.

What should you do if your annotations are incomplete or broken?

This is the real risk. An incomplete two-way annotation (for example, the alternate tag present on desktop but no canonical on mobile) creates content duplication. Google may then index both versions as distinct pages.

Field audits show that 30 to 40% of sites with separate versions have defective annotations on at least 10% of their pages. Common causes: different templates between mobile and desktop, dynamic tag management failing on certain pages, or temporary 302 redirects breaking the annotation chain.

How to audit your two-way annotations?

Start with a full crawl of both versions (desktop and mobile) using Screaming Frog or Oncrawl. Export the link rel="alternate" and rel="canonical" tags for each URL. Create a matching matrix: each desktop URL must point to exactly one mobile URL, and vice versa.

Common errors to track: mobile URLs pointing to themselves as canonical (instead of pointing to desktop), alternate tags with 404 URLs, or worse, redirection chains between the versions. A tool like OnCrawl automatically detects these inconsistencies in its technical audit module.

What to do if you have already submitted mobile URLs in your sitemaps?

No need to panic. Google will not penalize you overnight. Gradually clean up your sitemaps: create a new version containing only canonical URLs, submit it in Search Console, and let Google recrawl over several weeks.

Monitor your server logs during this period. If you see Googlebot continuing to crawl the mobile URLs even though they are no longer in the sitemap, that's a good sign: your annotations work correctly. The bot discovers them through the alternate tags.

What critical mistakes should you absolutely avoid?

Never confuse canonical and alternate. The canonical tag on a mobile page must point to the desktop version (unless there are specific cases like AMP). The alternate tag on a desktop page must point to the mobile version. Reversing these two tags is a catastrophic mistake that can demote your site within days.

Another pitfall: URL parameters. If your mobile version uses tracking parameters (?utm_source, etc.), make sure your annotations point to clean URLs without parameters. Otherwise, Google may create dozens of indexed variations for the same page.

• Audit your two-way annotations with a technical crawler
• Remove mobile URLs from your XML sitemaps (keep only the canonicals)
• Ensure each desktop page has an alternate tag to mobile
• Confirm that each mobile page has a canonical tag to desktop
• Monitor your logs for crawl errors post-cleanup
• Manually test 10-20 strategic pages with the URL inspector in Search Console