Mobile Sitemap: How Google Handles Sitemaps on Mobile
Search for "mobile sitemap" and you will find a lot of outdated advice — articles that recommend building a separate XML sitemap just for your mobile pages, or that warn you to "annotate" every URL with a mobile tag. Most of that guidance is no longer relevant. Google switched to mobile-first indexing years ago and simplified the rules significantly. This guide explains what a mobile sitemap actually is, when you need one, and what the only real requirement is under modern SEO.
What Is a Mobile Sitemap?
A "mobile sitemap" is not an official Google product or a distinct sitemap format. The term refers to how a standard XML sitemap handles URLs that are served to mobile devices. In the early days of mobile SEO — roughly 2010 to 2016 — Google supported a dedicated mobile sitemap schema that used the <mobile:mobile/> tag to mark URLs as mobile-only. That format was designed for feature phones and WAP-era content.
Google deprecated that schema entirely. Today, the XML sitemap specification does not have a mobile-specific tag. There is no such thing as a mobile sitemap format that you need to implement. What you do need is a standard XML sitemap whose URLs are accessible and functional on mobile devices — because that is how Google crawls and indexes the entire web now.
How Mobile-First Indexing Changed Sitemap Strategy
Mobile-first indexing means Google primarily uses its smartphone Googlebot to crawl and index pages. This is not a ranking signal in isolation — it is an infrastructure change. The same Googlebot that builds Google's index now identifies itself as a mobile browser (specifically, Chrome on Android) when fetching URLs.
The sitemap implication is direct: every URL you list in your sitemap needs to work when fetched by mobile Googlebot. If a URL returns a 200 status on desktop but redirects mobile users to a different page, or if the page is blocked behind a login that triggers on mobile user-agents, Google will see that problem and it will affect indexing.
The practical takeaway is that your sitemap is now implicitly a mobile sitemap. You are not listing desktop pages and mobile pages separately. You are listing pages, and Google visits them as a mobile browser. This makes the sitemap cleaner — not more complex.
Mobile URLs in Sitemaps: Three URL Structures
How you handle mobile URLs in your sitemap depends entirely on how your site is structured. There are three patterns:
Responsive design (recommended). The same URL serves the same HTML regardless of device. CSS and JavaScript adapt the layout for screen size. In this case, your sitemap does not change at all — list every URL once, as normal. No annotations, no extra tags, no second sitemap. This is the structure Google recommends and the one that requires the least sitemap maintenance.
Dynamic serving (same URL, different HTML). The URL is identical for desktop and mobile, but the server detects the user-agent and sends different HTML. Your sitemap still lists each URL once. However, you should implement the Vary: User-Agent HTTP header so that Googlebot understands the content differs by device. No sitemap change is needed, but verify that the Vary header is present.
Separate mobile subdomain (m-dot sites). Mobile users are redirected to m.example.com/page/ while desktop users see example.com/page/. This is the one case where your sitemap strategy requires extra work. Both subdomains are distinct properties in Google Search Console, and each needs its own sitemap submitted. The m-dot subdomain needs its own XML sitemap listing all mobile URLs, and the desktop domain needs its sitemap listing desktop URLs.
The m-dot Site Sitemap Pattern
If you operate an m-dot site, you need to do two things at the sitemap level. First, submit a sitemap for m.example.com in Google Search Console under the separate mobile property. Second, use rel="alternate" and rel="canonical" annotations in your HTML to tell Google which desktop URL corresponds to which mobile URL, and vice versa. The sitemap itself is standard XML — there is no special mobile syntax.
Here is what a sitemap for the m-dot subdomain looks like:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://m.example.com/</loc>
<lastmod>2026-04-15</lastmod>
<changefreq>daily</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>https://m.example.com/products/</loc>
<lastmod>2026-04-10</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://m.example.com/products/blue-widget/</loc>
<lastmod>2026-03-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.6</priority>
</url>
</urlset>Each mobile URL listed in this sitemap should have a corresponding <link rel="canonical" href="https://example.com/products/blue-widget/"> in the mobile page's <head>, pointing back to the canonical desktop version. The desktop page should have a <link rel="alternate" media="only screen and (max-width: 640px)" href="https://m.example.com/products/blue-widget/"> pointing to the mobile version.
AMP URLs and Sitemaps
Accelerated Mobile Pages (AMP) introduced another layer of mobile URL complexity that has since been significantly reduced. Google removed AMP as a requirement for Top Stories in 2021, and AMP adoption has declined. But if you still run AMP pages, here is how they relate to sitemaps.
AMP pages should not be listed as standalone URLs in your main sitemap unless the AMP URL is the canonical version of the page. In most cases, the canonical is the standard HTML page. The AMP page is an alternate representation. Declare the relationship in the HTML: the canonical page gets <link rel="amphtml" href="https://example.com/page/amp/">, and the AMP page gets <link rel="canonical" href="https://example.com/page/">. You do not need to list AMP URLs in your sitemap separately — Google discovers them through the amphtml link.
The exception: if you maintain a dedicated AMP sitemap for discovery purposes (common on large news sites), keep it in a sitemap index file and submit it alongside your main sitemap. This is optional and useful only if your AMP pages are not well-linked.
How to Verify Mobile Googlebot Can Access Your Sitemap URLs
Google Search Console gives you two tools that directly tell you whether your sitemap URLs are accessible to mobile Googlebot:
URL Inspection tool. Enter any URL from your sitemap and click "Test Live URL." GSC fetches the page as mobile Googlebot and reports what it sees — including any blocked resources, redirect chains, and rendering errors. If the fetch fails for mobile but not desktop, you have a mobile accessibility problem that will affect indexing.
Mobile Usability report. Found under Experience in GSC, this report lists pages that have mobile usability errors — clickable elements too close together, text too small to read, content wider than screen. These are not sitemap errors, but they affect how well Google can index and rank pages that appear in your sitemap.
For a faster check across your whole sitemap, use a tool like SitemapFixer, which fetches every URL in your sitemap and reports on HTTP status, redirect chains, and accessibility. It cannot replicate the full mobile rendering test, but it will immediately show you which sitemap URLs return non-200 responses or redirect mobile users to different pages.
Common Mobile Sitemap Mistakes
Even though the rules are simpler than they used to be, several mistakes appear repeatedly in mobile sitemap audits:
Blocking mobile Googlebot in robots.txt. The most damaging mistake. If your robots.txt has a rule that blocks the Googlebot-Mobile user-agent, or if you use a middleware layer that returns 403 for mobile user-agents, your entire site can become invisible to mobile-first indexing. Always verify your robots.txt does not contain user-agent-specific blocks for mobile crawlers.
m-dot pages missing from sitemap. Running an m-dot site and only submitting a sitemap for the desktop domain is extremely common. Google may still find mobile URLs through links, but without an explicit sitemap, coverage gaps appear — especially for newer pages that have few internal links.
Mobile-only pages absent from the main sitemap. Some sites serve unique content only on mobile — a stripped-down version of a page, or a mobile-specific landing page — that is never listed in any sitemap. If the page is not linked from anywhere visible to desktop Googlebot, it may never be indexed.
Using deprecated mobile sitemap extensions. The old xmlns:mobile namespace and <mobile:mobile/> tag in XML sitemaps are ignored by Google. If you inherited a sitemap that uses this syntax, it is harmless but useless. Remove it to clean up your sitemap, but it is not causing any active harm.
The Full XML Sitemap Under Mobile-First Indexing
To make the picture concrete, here is what a standard well-formed XML sitemap looks like under mobile-first indexing — which is simply a normal XML sitemap with no mobile-specific additions:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-04-28</lastmod>
<priority>1.0</priority>
</url>
<url>
<loc>https://example.com/products/</loc>
<lastmod>2026-04-20</lastmod>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/blog/mobile-seo-guide/</loc>
<lastmod>2026-04-15</lastmod>
<priority>0.6</priority>
</url>
</urlset>No mobile namespace. No <mobile:mobile/> tags. No separate file for mobile. Google visits each of these URLs as a mobile browser and indexes whatever it finds. The sitemap's job is simply to declare that these URLs exist and when they were last updated — the rest is handled at the page level through responsive design and proper HTML canonicalization.
What Actually Matters for Mobile SEO and Sitemaps
After stripping away the outdated advice, the real mobile sitemap requirements reduce to three points:
Responsive design means no extra work. If your site uses responsive design, your existing sitemap is already your mobile sitemap. Confirm that mobile Googlebot can access every URL via the GSC URL Inspection tool, and you are done.
m-dot sites need explicit sitemaps per subdomain. Submit a sitemap for m.yourdomain.com in GSC under the mobile subdomain property. Keep it updated whenever new mobile pages are created. Use canonical and alternate annotations in HTML to link the desktop and mobile versions of each page.
The sitemap must list only 200-status URLs. Whether mobile or desktop, any URL in your sitemap that returns a redirect, a 404, or a 5xx error is a wasted entry. Regularly audit your sitemap with a tool that checks live HTTP status codes to keep it clean. A sitemap with non-200 URLs sends Google confusing signals regardless of mobile-first indexing.
Mobile SEO is not a separate discipline from sitemap management — it is the same discipline applied consistently. Keep your sitemap clean, ensure your URLs are accessible to a smartphone user-agent, and Google will handle the rest.