TL;DR
For each important page, compare the URL your navigation uses, the final destination, the canonical tag and the sitemap entry. Resolve conflicts against an agreed preferred address. A sitemap helps discovery; a canonical expresses a preference among duplicate or very similar pages. Neither guarantees indexing.
Audit the addresses your site actually publishes
Start with an existing page whose purpose and preferred public address are already agreed. This audit checks whether the website consistently expresses that decision. Choosing which overlapping articles to merge is a separate editorial task.
A redesign or template change can leave a link, redirect, canonical or sitemap pointing somewhere different from the intended page. Inspect the values the public site serves instead of relying on the settings displayed in the CMS.
Google describes redirects and canonical annotations as stronger canonicalization signals than sitemap inclusion. These methods communicate preferences; Google still selects the canonical it uses. Google’s canonical URL guidance also warns against specifying conflicting preferred URLs.
Capture the page in four places
| Check | Record the actual value | Question to resolve |
|---|---|---|
| Internal link | Address linked from the service menu or another relevant page | Are visitors sent to the preferred version? |
| Final destination | Address after redirects finish | Is there an unnecessary detour or wrong page? |
| Canonical | Page’s declared preferred URL | Does it describe this content on the intended public domain? |
| Sitemap | Listed URL, if present | Is this the intended discoverable version? |
Repeat the comparison for the homepage, a priority service page, location pages and appointment information. Record the source of each value and the inspection date. If several pages disagree in the same way, ask the developer whether a shared template or setting supplies the incorrect value.
Do not force different offices to share a canonical merely to make a spreadsheet look consistent. Consistency means that each page’s signals match its intended identity, not that every page points to the same URL.
Turn a mismatch into a bounded repair request
Use the observed mismatch to identify what needs investigation:
| Observed mismatch | Decision or repair evidence to request |
|---|---|
| Navigation links to a preview domain | Verify the production destination and correct the component generating the link |
| Menu link reaches the right page through an old path | Confirm the preferred direct link and whether the old redirect remains necessary for existing bookmarks |
| Rendered canonical names another domain or unrelated page | Inspect the template or plugin supplying the value against the approved page identity |
| Sitemap still lists a retired route | Confirm the intended replacement and update the source that generates the sitemap |
| Page has no sitemap entry | Check whether inclusion is intended; absence alone does not prove the page cannot be discovered |
These are investigation prompts, not instructions to remove redirects or change canonicals automatically. Give the implementer the exact source URL, observed value, intended value and affected component. Avoid broad replacements that might change unrelated pages.
Keep discovery evidence in perspective
A submitted sitemap helps Google discover URLs but does not guarantee that every entry will be crawled or indexed. Google’s sitemap overview explains that limit. A successful submission does not verify the page’s content or settle a conflicting canonical.
Keep protected previews and patient portals out of the public editorial sitemap. Review the generated file when pages are added, moved or retired, and check that its host and paths match the intended public site.
If the preferred page itself is undecided, return that decision to the editorial owner. Do not let a technical cleanup silently decide which useful content should disappear.
Verify the repaired values together
After the change, follow the same referring link and capture the final URL, rendered canonical and sitemap entry again. Check an affected neighboring page when the repair changes a shared component. Record anything still outside the practice’s control.
Retain the before-and-after values with the change ticket. The acceptance evidence is a coherent public implementation of the approved address; it is not a promise about Google’s eventual selection or search traffic.
Frequently asked questions
Does every discoverable page need a sitemap entry?
No. Google can discover properly linked pages without one. Decide which preferred public URLs belong in your sitemap and investigate missing entries in that context.
If all the values agree, is the page guaranteed to be indexed?
No. The audit resolves conflicting URL signals. Google still makes its crawling, canonicalization and indexing decisions, so investigate any remaining issue separately.