A mobile sitemap is an XML sitemap built for mobile-only content, either the old feature-phone annotation or, informally, a set of alternate-URL tags for a separate m.example.com domain. Most sites in 2026 do not need one: if your site is responsive, your regular XML sitemap already covers every device, and Google has run mobile-first indexing across the entire web since July 2024. The cases where a mobile sitemap (or something like it) still matters are narrower than most guides on this topic admit, and this one walks through exactly which situation you are in.
We built this guide because the existing pages on "mobile sitemap" mostly repeat a definition from a decade ago without saying whether it still applies to you. It usually does not. Below you get the real history of the feature, a clear decision path for your own site, the correct way to handle separate mobile URLs if you genuinely have them, and what to do with any leftover mobile sitemap tags you find in an old file.
<mobile:mobile/> tag targeted feature phones running WAP, XHTML Mobile Profile, or cHTML browsers. Google retired feature-phone crawling and indexing support in November 2016.rel="alternate" annotation added to your existing sitemap entries.A mobile sitemap is one of two things: the old <mobile:mobile/> annotation that told Google a page was formatted for a feature phone, or an informal shorthand for adding alternate-URL annotations to a sitemap when a site runs a separate mobile domain. Neither one is a distinct file format. It is always the same XML sitemap protocol, just with an extra tag on specific entries.
The first meaning is mostly historical. In the mid-2000s and early 2010s, plenty of sites served a stripped-down version of their pages to feature phones using WAP, XHTML Mobile Profile, or cHTML markup, languages built for browsers that could not render a normal webpage. The Sitemaps protocol added a <mobile:mobile/> tag so crawlers could tell those pages apart from the desktop version.
The second meaning shows up today when someone still runs a separate mobile subdomain, most often a legacy m.example.com setup that predates responsive design. In that case, "building a mobile sitemap" really means adding a rel="alternate" annotation with a CSS media query to the desktop URL's existing sitemap entry, not creating a second file.
No, unless you still serve dedicated feature-phone pages or maintain a separate m. subdomain, both of which are rare in 2026. If your site uses responsive design, meaning the same URL and HTML adapt to any screen size through CSS, one standard XML sitemap is enough. Google has run mobile-first indexing, evaluating the mobile version of your pages for ranking, across the entire web since July 2024.
That timeline matters because it shows how long this has been settled. Google first told site owners not to bother building a mobile sitemap for mobile-friendly sites years before mobile-first indexing even existed, then spent nearly a decade migrating the rest of the web onto it.
The practical upshot is that a mobile sitemap cannot help a site Google already treats as mobile-first by default. If your goal is better mobile visibility, that budget is almost always better spent on mobile SEO strategy work like page speed and usability rather than sitemap tags nobody reads anymore.
Whether you need anything beyond a normal sitemap depends entirely on how your site serves mobile visitors. There are three real setups, and Google recommends a different answer for each.
| Setup | How it works | Mobile sitemap needed? | What to do instead |
|---|---|---|---|
| Responsive design | Same URL and HTML for every device; CSS adapts the layout | No | Nothing. One ordinary sitemap covers everything. |
| Dynamic serving | Same URL, but the server sends different HTML based on the user-agent | No | Add a Vary: User-Agent HTTP header so Google and CDNs cache each version correctly. |
| Separate mobile URLs | A distinct URL for mobile (often m.example.com), linked with rel=canonical | Rare, only as an annotation | Add a rel="alternate" media annotation to the existing sitemap entry. |
| Feature-phone pages | Legacy WAP, XHTML Mobile Profile, or cHTML markup | No, retired | Remove any leftover <mobile:mobile/> tags; they are not read anymore. |
Most sites built in the last several years fall into the first row without ever deciding to. If your theme or CMS handles layout with CSS breakpoints, you are already responsive and this entire topic is a non-issue for you.
Vary: User-Agent header is present.<mobile:mobile/> tags, or a plugin still labeled "mobile sitemap," it is safe to remove. Google stopped using it in 2016.If step three above applies to you, do not build a second sitemap. Add an xhtml:link annotation to the existing entry for the desktop URL, pointing at its mobile counterpart with a CSS media query. Here is a minimal, valid example:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://example.com/shoes</loc>
<xhtml:link rel="alternate"
media="only screen and (max-width: 640px)"
href="https://m.example.com/shoes" />
</url>
</urlset>Three rules keep this working. The mobile URL still needs its own rel="canonical" tag pointing back to the desktop version. The redirect behavior between the two URLs has to match what the annotation says, so Google is not sent to a page different from what it expects. And you list only the desktop (or canonical) URL as the primary <loc>, never both as separate top-level entries for the same content.
Google's own sitemap documentation puts it plainly: if you have different URLs for mobile and desktop versions of a page, point to only one version in your sitemap, and annotate the URL if you want to reference both. There is no dedicated "mobile sitemap" endpoint to submit separately in Search Console; it is the same file you already have, generated the same way our free XML sitemap generator builds one for any site. If you have not built your base sitemap yet, start with our guide on how to make a sitemap before adding any mobile-specific annotation on top of it.
It was a Sitemaps protocol extension for feature phones running WAP, XHTML Mobile Profile, or cHTML browsers, and Google retired feature-phone crawling and indexing support in November 2016. Search Console no longer reads the tag, so leaving it in a sitemap today does nothing, good or bad.
The tag existed because those old browsers could not render a normal webpage, so sites served a separate, stripped-down version and needed a way to tell Googlebot which URLs were built for that audience. Once smartphones with full browsers became the default and responsive design became the standard build pattern, the entire category of problem it solved mostly stopped existing.
If your CMS or an old SEO plugin still generates a file with this tag, it is not causing harm, but it is also not doing anything useful. Cleaning it out is a five-minute task worth doing the next time you touch your robots.txt sitemap directive or run a broader sitemap best practices pass.
Fixing all five usually takes less time than researching whether you need a mobile sitemap in the first place, which is exactly why so many sites still have leftover tags nobody has looked at since 2016. If mobile rendering itself is the real concern, our AMP mobile SEO guide covers the related question of whether that older mobile framework is still worth using.
Do I need a mobile sitemap for a responsive website? No. A responsive site serves one URL and one set of HTML to every device, so your normal XML sitemap already covers it. Google's own guidance is that mobile-friendly sites should not build a separate mobile sitemap at all.
What was the mobile:mobile tag used for? It flagged sitemap entries built for feature phones running WAP, XHTML Mobile Profile, or cHTML browsers. Google retired feature-phone crawling and indexing support in November 2016, so the tag has no effect on modern crawling.
Is a mobile sitemap different from a regular XML sitemap? Not structurally. It is the same XML sitemap format, either with the old feature-phone annotation or, for separate mobile URLs, a rel=alternate media annotation added to an existing url entry. There is no separate mobile sitemap file format.
Do I need to list my m.example.com pages separately in my sitemap? Only if you still run a genuinely separate mobile domain. Add an xhtml:link rel=alternate annotation to the desktop URL's entry pointing to the mobile version, rather than listing the mobile URLs as their own entries.
Does mobile-first indexing change what I put in my sitemap? No. Mobile-first indexing changed which version of a page Google evaluates for ranking, the mobile version, not the sitemap format. You still list one canonical URL per page.
Can one sitemap cover both my desktop and mobile URLs? Yes, and that is what Google recommends. If your desktop and mobile content live at different URLs, point the sitemap at the canonical version and add an alternate annotation for the mobile counterpart.
Will Google still read old mobile sitemap tags if I leave them in? No. Search Console and Googlebot stopped processing feature-phone sitemap extensions after 2016, so old mobile:mobile tags sit inertly in the file without causing errors or bringing any benefit.
How do I check which mobile setup my site actually uses? Compare the URL you see on a phone and on a desktop browser. If it is identical, you are responsive or use dynamic serving. If it changes to a subdomain or a /mobile/ path, you are on separate URLs and need the rel=alternate annotation.
Does having a mobile sitemap improve mobile rankings? No. A sitemap only helps discovery and crawling, it carries no ranking weight of its own. Google's documentation is explicit that submitting a sitemap does not guarantee higher positions, mobile or otherwise.
What should I do with an old mobile sitemap file I find on my server? Keep any entries that still point to real, live URLs in your main sitemap, then delete the file or plugin generating the separate mobile-only sitemap. Google does not read it, and it is one more file you would otherwise have to maintain.
Check which of the three setups your site actually uses before you touch anything. If you are responsive, which is most sites in 2026, you already have everything you need and can stop here. If you run separate mobile URLs, add the rel=alternate annotation to your existing sitemap rather than building a second file. Either way, run your sitemap through our free XML sitemap generator to confirm it is clean, then move on to the technical checks that actually move rankings. If you want a second pair of eyes on your crawlability and mobile setup together, request a free SEO audit from Rankite.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.