You open a sitemap and see links to other XML files instead of articles. That can be correct: a sitemap index points to individual sitemaps, and those files list page URLs. An article does not have to appear directly in the first file you open.

Check the correct level

  1. Check the root element: sitemapindex links to sitemaps; urlset contains page URLs.
  2. Open the child file actually listed there.
  3. Search that file for the complete article URL.

Filenames such as “posts” or “products” may be outdated after a platform change.

Fictional example: /sitemap.xml lists /articles-2.xml. That second file contains /insights/image-sizes/. Searching only the index would produce a false report that the article is missing.

When a child file fails

Check its response separately. A working index can still point to a file that no longer exists. Record which file failed and whether it should contain articles, products or another page type. This gives the person maintaining the generator a useful starting point.

A sitemap helps search engines discover URLs; it does not guarantee indexing. Once the article appears in the correct child file, investigate its accessibility and indexing rules separately. Adding every page URL directly to the index would mix up the two document types.

Related check: Remove redirects from a sitemap.

If ownership of sitemap generation is unclear, the Technology and stack review can help assess the application’s structure and deployment.

Sources