URL in Multiple XML Sitemaps: How to Fix It

What "URL in Multiple XML Sitemaps" means

This audit flag means that one or more of your URLs are listed in two or more of your XML sitemap files at the same time. Large sites usually split their sitemaps into several files, often grouped under a single sitemap index. That is completely normal and expected once a sitemap reaches the format limit of 50,000 URLs or 50MB uncompressed. The flag is not about having multiple sitemaps. It is about the same address being repeated across those sitemaps instead of living in just one of them.

In practice, the crawler reads every sitemap your site references, builds a combined list of URLs, and notices that certain entries show up in more than one file. Each duplicated URL is what triggers this hint.

Why duplicate listing is suboptimal

Reporting clarity

Google has stated that listing a URL in more than one sitemap is not harmful to indexing on its own. The real cost is to your own visibility. When you open the Sitemaps report in Google Search Console, that tool reports submitted and indexed counts per sitemap file. If the same URLs appear in several files, the per-file numbers overlap and stop adding up cleanly, which makes it much harder to tell which sitemap is actually doing its job and which URLs are genuinely missing. Google's own guidance notes that overlapping URLs can obscure the insight you would otherwise get from that report.

Redundancy and hidden mistakes

Duplication is also a symptom worth reading. When URLs land in multiple sitemaps it often signals a configuration mistake, and the same misconfiguration that double-lists some pages can quietly leave other pages out of every sitemap. Redundant entries add no value, they make the files larger than they need to be, and they make routine maintenance harder because you now have to keep the same URL correct in more than one place.

Common causes

Almost every instance of this issue traces back to overlapping sitemap configurations rather than a deliberate choice. The usual culprits are:

Overlapping sitemap index entries. A sitemap index file points to several child sitemaps, but the rules that decide which URLs go into each child overlap. For example, one child sitemap covers "all posts" while another covers "a category" that contains some of those same posts, so the shared posts appear in both.

A plugin sitemap plus a manual sitemap. An SEO plugin generates its own sitemap set automatically, and at some point a separate hand-built or legacy sitemap was also left in place and submitted. Both describe the same site, so the same URLs get listed twice across the two systems.

Multiple plugins or generators. Two tools that both produce sitemaps are active at once, each generating a full set, which guarantees broad overlap.

How to diagnose

Start at your sitemap index, usually found at /sitemap.xml or /sitemap_index.xml, and list every child sitemap it references. Then crawl the full sitemap set with a tool such as Screaming Frog or Sitebulb in list or sitemap mode and have it report which sitemap each URL came from. A URL that reports more than one source sitemap is a confirmed duplicate.

You can also spot the pattern by hand. Pull each sitemap and compare the URL lists for overlap:

# Extract URLs from two sitemaps and show any that appear in both
curl -s https://example.com/post-sitemap.xml | grep -oE '<loc>[^<]+</loc>' | sort > a.txt
curl -s https://example.com/category-sitemap.xml | grep -oE '<loc>[^<]+</loc>' | sort > b.txt
comm -12 a.txt b.txt   # lines printed here are duplicated across both files

Cross-check the Sitemaps report in Google Search Console too. If you see more sitemap files submitted than you expect, or an old standalone sitemap sitting alongside your plugin set, that mismatch points straight at the cause.

How to fix

The goal is simple: one URL, one sitemap, across the whole set. Work toward a clean sitemap configuration in this order.

Pick a single source of truth. Decide which system owns your sitemaps, normally your SEO plugin, and disable or delete every competing generator and every leftover manual sitemap. If an old sitemap is still submitted in Search Console, remove the submission and let the stale file 404 or redirect to the live one.

Make the grouping rules mutually exclusive. If your sitemap index splits by type, ensure each URL qualifies for exactly one child sitemap. Group by a non-overlapping dimension such as content type (posts, pages, products) rather than by overlapping taxonomies like categories or tags, which naturally share the same URLs.

Re-crawl and confirm. After the change, crawl the sitemap set again and verify that no URL reports more than one source file. Then resubmit only the corrected sitemap index in Search Console.

Best practice

Keep one canonical sitemap setup, ideally a single sitemap index that references child sitemaps with no overlap, and list each indexable URL exactly once. Fill each sitemap toward the 50,000 URL limit before starting another, group by a clean non-overlapping dimension, and submit only the index file. Done this way, your Search Console Sitemaps report stays readable, your files stay lean, and missing pages become obvious instead of being masked by duplicates.

FAQ