Blog / Technical SEO /

What a sitemap can tell you about site ownership and maintenance

Open a sitemap and it looks like a boring technical file. Look a bit longer and it starts asking awkward questions. Who owns half of these URLs? Why did this section stop updating two years ago? Is this file even generated from the live site?

An XML sitemap is a list of URLs a site owner wants search engines to consider. It doesn’t guarantee indexing, and it doesn’t replace internal links. But it does show how an organisation thinks about its website. Which content types are in? Which are missing? Are retired pages still hanging around? Those are maintenance questions as much as SEO questions.

First check that it is the sitemap you think it is

Start with the sitemap index, if one exists. Larger content systems often divide URLs into several files by content type or date. A sitemap index can help you see whether the site produces separate lists for products, pages, articles, images or other resources. Open each child file and check that it loads, contains valid URLs and belongs to the correct host.

Don’t trust a filename. A file called page-sitemap.xml could hold archive pages, landing pages or something else entirely, so I always open it and compare the URLs with the CMS. If the sitemap is generated by a plugin or platform, note which system controls it and who can change its settings. A file can be technically valid and still reflect a configuration no one intended.

Check whether the listed URLs use the preferred protocol and hostname. A sitemap full of redirected URLs, non-canonical versions or blocked pages tells you the publishing system and the indexation rules are out of step. A few exceptions may be deliberate. A repeated pattern deserves a proper look.

Read the URL patterns as an organisational map

Group the entries by path. You might see /products/, /collections/, /blog/, /author/ or old campaign paths. The groups show the shape of the site. They also expose content nobody owns any more. A section with live pages and no known editor tends to collect outdated claims, broken links and abandoned calls to action.

Ask who is accountable for each kind of page. A product manager may own product facts, while an editor owns buying guides and a developer owns platform-generated utility pages. SEO can help decide whether URLs should be discoverable, but I don’t think SEO should become the default owner of every page. The sitemap is a good excuse to have that ownership conversation.

Look for duplicate paths, date-based archives, parameter variants or pages that appear to have been created by an old campaign. A sitemap should generally list the canonical URL intended for search, not every URL that can be produced by the application. If old versions are still present, trace them back to the publishing process. Removing the URLs from the file without fixing the source can make them reappear next week.

Last-modified dates need a real meaning

Many sitemap entries include a lastmod value. It can be useful when it reflects a meaningful update to the page. It’s much less useful when the value changes every time the sitemap runs, even though the page hasn’t. Search engines decide how to use it, so don’t treat it as a request to crawl everything now.

Ask how the date is generated. Is it the last real content change, any database save, a theme update or the sitemap rebuild time? If nobody knows, the field may be feeding search engines noise. A system that reports dates accurately is better than one that presents every URL as freshly edited.

This is also an ownership clue. If editorial teams are expected to keep pages current, they need a clear update process. A date field alone does not establish that anyone checked the information. For pages with a genuine review cycle, record the responsible person or team in the CMS, or in a separate content inventory, and define what should trigger a review.

Compare the sitemap with other evidence

A sitemap is only one view of the site. Compare it with a crawl, the CMS content list, internal links and Search Console. The CMS may show published pages absent from the sitemap. A crawl may find orphaned URLs that are linked internally but not listed. Search Console may surface URLs Google knows about through links or previous crawls, even if they are not currently in the file.

These differences are useful when interpreted carefully. A page missing from a sitemap may be intentionally noindex or canonicalised elsewhere. A URL in Search Console but not in the current sitemap may be old, externally linked or redirected. Avoid treating every discrepancy as a defect; ask what purpose the URL serves and what action is intended.

For a practical review, sample by section. Check a few current pages, a recently updated page and one older URL. Confirm the response status, canonical, robots directives, page content and internal links. Then investigate patterns. A sitemap can identify a group to inspect, but it cannot confirm that the pages are useful or technically healthy on its own.

Turn findings into maintenance work

Create a short list with three categories: pages to keep and maintain, pages to correct, and pages that may need consolidation or removal. For each item, write the reason, the owner and the next decision. I’d rather not delete a URL just because it looks old. It may still answer a useful question, attract the right visits or earn links. But keeping everything because it exists isn’t a strategy either.

When a page is retired, decide whether it should redirect to a genuinely relevant alternative, return a not-found status or remain accessible without search visibility. The appropriate action depends on the page and its replacement. A blanket redirect to the homepage often creates a poor experience and hides the fact that the original resource is gone.

Review sitemap generation after major changes: a migration, CMS change, plugin replacement, product taxonomy redesign or large content cleanup. Add the check to the release process. After deployment, someone should verify the sitemap index, a few child files and the submitted property.

Treat it as evidence, not a report card

A large sitemap does not mean a healthy site, and a small one does not mean a broken one. What matters is whether the listed URLs match the site’s purpose, are accessible and have someone responsible for them. A technically clean file can still contain pages no customer needs. A useful content inventory may contain valuable pages that should not be indexed.

Open your sitemap index and pick one URL group nobody has reviewed lately. Can you name the person or team responsible for those pages, and say what would get them updated or removed? If not, your next SEO task may be an ownership conversation rather than another crawl.