Technical
Warning

Sitemap index has broken children

This error appears when your website has a sitemap index and one or more of the sitemaps it groups can't be opened. Here's what it means and how to find the ones that fail so you can fix them.

What this error means

A sitemap index is a file that lists other sitemaps instead of listing pages. It's the usual setup in WordPress, where plugins like Yoast or Rank Math create a sitemap_index.xml with one child sitemap for posts, another for pages, another for categories and so on for each content type. When checking your index, Ruk Audit opened the child sitemaps one by one and at least one can't be read. The server responds with an error, such as a page not found (404) or a server failure (500), or it keeps loading without ever responding. The URLs in that child stop reaching Google through that route. Your pages still exist and Google can discover them by following links, but the sitemap no longer tells it about the pages in that part of the website. It's different from an empty or badly written sitemap, where the main file fails. Here the index opens fine and the sitemaps it lists are what fail. It's usually caused by a WordPress setting that needs to be saved again, by the hosting configuration or by a cache that keeps showing an old version.

Why fixing broken child sitemaps in the sitemap index matters

Each broken child leaves out of the sitemap the URLs it listed, which may be all your posts or part of your products.

Impact on SEO rankings

New or updated pages in that part may take longer to appear on Google, especially if they have few internal links. The ones already in the results don't drop because of this.

Crawling and indexing obstacles

In the Sitemaps report in Search Console, that child usually shows up as "Couldn't fetch". Google tries again for a few days and, if it keeps failing, stops requesting it until you submit it again.

Negative signals for site quality

A sitemap that returns an error usually gives away a configuration problem, such as lost WordPress rules or an outdated cache. That same problem may be affecting other pages, so check whether your audit flags server errors on other URLs.

How to fix it step by step

If this error showed up in your audit, here are the steps to leave it behind.

Step 1

Identify which child sitemaps fail

Open your index in your browser, usually at yourdomain.com/sitemap_index.xml if you use Yoast or Rank Math, and go into each sitemap on the list. The ones that work show their URLs. The broken ones return an error page or keep loading without finishing.

Step 2

Fix each child according to the cause

In WordPress, the first thing to do is go to Settings > Permalinks and click Save Changes without changing anything. That way WordPress regenerates the rules that make the sitemaps work. Yoast and Rank Math recommend it as the first step. If it still fails, clear the cache of your caching plugin and, if you use a service like Cloudflare, its cache too. Then deactivate the plugins other than the SEO one, one at a time, and open the sitemap after each one. If it works again after removing one of them, reactivate the rest and contact that plugin's support. If the one failing is the categories, tags or another content type sitemap, check that it has something published, because that sitemap doesn't exist if it's empty. If you're not going to use it, exclude it from the sitemap in the plugin settings. On very large websites, a child with too many URLs can take so long that it never finishes loading. In Rank Math you can lower the Links Per Sitemap setting, which defaults to 200, for example to 100. If none of this works, write to your hosting provider and ask them to add the rewrite rules for your SEO plugin's sitemaps.

Step 3

Check that all children respond

Open the index again in an incognito window, so your browser cache doesn't fool you, and go into each child again. When they all show their list of URLs, run the audit in Ruk Audit again to confirm that the error has disappeared.

Step 4

Resubmit the index to Google Search Console

Open the Sitemaps report from the left-hand menu in Search Console and submit the index again. The status of each child updates when Google reads it again, and that can take a few days.

Does your site have this problem?

Audit your website for free and discover if this and other SEO errors are affecting your ranking.

Get a free audit. Over 3022 reports delivered.
Hey, wait a moment
To analyze a website, you first need to create an account in the application. Click the button below to go to the registration screen.
Create account