A sitemap should list the canonical public pages intended for search discovery. For a 100-page library, a generated XML sitemap is usually easier to maintain than a manually edited list.
Decide which URLs belong in the public library
Create an inventory of the site's intended canonical pages before writing the sitemap generator. Include useful service explanations, articles, category pages and a public contact page where appropriate. Exclude form submission endpoints, internal dashboards, unpublished drafts and confirmation screens whose only purpose is acknowledging an inquiry.
Use one canonical address per content item. If a guide loads under multiple paths, choose the preferred public version and align links with it. A sitemap that lists all duplicate versions expresses a different preference from the page's canonical annotation.
Generate the sitemap from the publishing source
For a hundred-page library, build the sitemap from the same approved records that generate the article routes. This reduces the chance that an editor publishes a page but forgets the discovery list. Use full public URLs, ensure valid XML and check that encoded characters remain valid.
Google describes sitemap submission as a way to help discovery, without guaranteeing indexing. Treat the sitemap as a reliable inventory, not a ranking accelerator. Set modification dates from substantive published changes when used; resetting every date on every deployment obscures what actually changed.
Test three failure modes after deployment
A sitemap can appear correct locally while failing on the public site. Open the production address and inspect its actual response. Then select a recent article, an older article and a service page from it and open each in a fresh browser session.
A small deployment check that compares the published route inventory against sitemap entries is more useful than manually clicking one hundred links every morning.
- The sitemap must return XML rather than the application's generic HTML shell.
- Listed public pages should load successfully at the canonical address.
- Removed or redirected content should not remain listed as a current canonical page.
Make removal and consolidation predictable
Suppose two articles separately discuss appointment cost but answer the same question. Consolidate the useful parts into the stronger destination and decide how the old address should resolve. Update internal links and the sitemap together. Otherwise, an editorial cleanup leaves readers and crawlers pointed at contradictory versions.
Keep a change log with the removed address, destination, reason and date. Distinguish a permanent consolidation from a temporary publishing mistake. Restore an accidentally missing guide rather than redirecting all errors to the homepage, which leaves visitors without the answer they requested.
Review discovery alongside usefulness
Submit the sitemap to Google Search Console and Bing Webmaster Tools, then review each platform's reported processing state. If a group of pages is missing from search, inspect representative examples instead of repeatedly submitting the same list. Look for access, canonical and editorial issues.
For an illustrative hundred-page launch, divide the inventory into five topic groups and review two URLs from each. Record whether each guide has a distinct reader task, meaningful internal links and current sources. A technically perfect sitemap cannot compensate for fifty near-identical articles. Maintaining both the discovery inventory and the content map makes future daily publishing easier to audit.
Questions agents ask
Should a sitemap contain contact pages?
It can contain a useful public contact page intended for search. Exclude form-processing endpoints, private inboxes and thank-you routes that do not help searchers.
Sources & further reading
Primary references for the rules and platform mechanics discussed here. Templates and recommendations are Medicare Marketing’s planning guidance. Examples are illustrative unless explicitly sourced.
Turn the idea into a next step.
Use the free toolkit to check your local foundation, build a content rhythm, or plan a webinar.
Explore the tools →