You publish a new product guide and it opens in a browser, but its URL isn't in your XML sitemap. Before resubmitting anything, find out whether the sitemap omitted the page, listed another version, or simply hasn't reached production yet.
Compare the final public URL with the sitemap served by your site. Then trace the missing entry back to the generator, deployment, or URL-selection rule that produced it. Check indexing separately in Search Console.
Is it really missing from the sitemap Google sees?
- Open the production page in a signed-out browser. Copy the final address after any redirect and check the canonical declared in the HTML.
- Open the submitted sitemap URL. If it's a sitemap index, open the child file that should contain this type of page. Search for the exact URL inside its
<loc>entries. - Check whether a different hostname, path, or trailing-slash variant appears. If both addresses serve the same content, investigate which address the site declares and links to before changing the generator.
Google's sitemap guidance recommends listing preferred canonical URLs that you want to appear in search results. If Google selected a different address, use our canonical troubleshooting guide before deciding which URL to add.
Where did the entry disappear?
Compare the CMS record with the sitemap generator's inputs. A page can be available on the site while excluded from a separate export by content type, publication status or host. If the intended record was missing at build time, find out whether the sitemap ran before the content change reached the generator. If the generated output contains the URL but the public file doesn't, check the deployed artifact and the caching rules for that file.
Here's a fictional example. A SaaS team ships a new guide at /docs/export-roles. The documentation page goes live immediately, but the sitemap is produced in the marketing build. The previous build couldn't see the new record. The team regenerates the production sitemap through its normal release path and checks that the next newly published guide also appears. Hand-editing the XML might add one URL today and lose it again on the next build.
When is leaving a URL out the right decision?
If the missing URL redirects, list the intended final page when it is eligible. If the page is a duplicate, keep the preferred version in the sitemap. If the URL is an intentionally excluded preview, keep its exclusion and access controls in place. Write down the decision so it won't be treated as an error in the next audit.
If the generator writes lastmod, use a verified date for a meaningful page change. Google's sitemap documentation says it uses the field when it is consistently accurate. The time the XML file was rebuilt is a poor substitute for the time the page changed.
How do you verify the repair?
Open the public sitemap again and confirm that it contains the preferred URL once. Check one different entry and one intentionally excluded URL to catch unintended changes. In the Search Console Sitemaps report, check when Google last read the file and investigate processing errors if it couldn't read it. Then inspect the individual URL if you need to know what Google recorded for that page.
Record the public sitemap URL, child file if applicable, expected page address, and what changed. A sitemap makes a URL easier to discover. Inclusion or successful processing alone doesn't show that the page is indexed.
Use a small sample when the omission affects a section. Check a recently published page, an older page on the same template, and an intentionally excluded page. If only the new page is missing, look at publication timing or the record's state. If the entire section is missing, investigate the selection rule and the child sitemap registration. Those are different fixes, and the sample helps you make the narrower one.



