XML sitemaps: give search engines a useful URL inventory

1. Start with the pages you actually want found

Create a short inventory by page type: services, products, articles, and other useful destinations. Select the preferred version of each page rather than adding every parameter variation. For example, an advertising campaign URL should not become a second sitemap entry just because it loads the same service page with tracking attached. Review retired pages, temporary landing pages, and translated content deliberately. This exercise often reveals publishing decisions that a file generator cannot make for you, especially when several teams contribute content.

2. Find the existing source of truth

Check your CMS or publishing system before creating another sitemap. Maintaining two competing inventories can leave one outdated. Open the published file and confirm that it contains real sitemap data rather than a login screen or an HTML error page. Use complete URLs, including the correct protocol and host. If a sitemap becomes large, the standard limits are 50,000 URLs or 50 MB uncompressed per file; split larger inventories and use an index. Choose a structure your team can maintain reliably.

3. Keep updates meaningful and automatic

Prefer a generation process connected to publication, retirement, and meaningful content edits. A maintenance checklist might ask: did the new page enter the inventory, did the retired URL leave it, and does the preferred address match the website's links? If you provide lastmod dates, make them reflect significant page changes rather than the moment someone regenerated the file. Assign an owner for exceptions. An automatically produced sitemap still needs periodic sampling, because a template mistake can quietly affect many entries at once.

4. Separate submission from indexing

Make the sitemap discoverable through a robots.txt reference or submit it in Search Console. Then read the result carefully: a successful sitemap fetch means the file was read, not that every listed page entered the index. Google does not guarantee crawling or indexing because a URL appears in a sitemap. Pick a few important entries and investigate them individually when visibility is missing. A sitemap problem, a page access problem, and a content evaluation problem require different fixes.

5. Turn a scan finding into a maintenance task

If Suprara does not find a sitemap signal, first locate the file through your CMS and confirm its public address. A missing signal in one check does not prove that no sitemap exists. Use the personalized PDF to record the finding, identify who can change the generator, and define a small verification sample. After publication, rescan the public site and compare the relevant evidence. Keep Search Console checks alongside this process so a clean inventory is not mistaken for confirmed indexing.

Frequently asked questions