🗺️ Why This Discrepancy Happens
When Site Audit reports that a page is missing from your XML sitemap, but you can see the page listed in your live sitemap, the most common cause is a data freshness issue. Site Audit captures a snapshot of your site at the time the crawl runs. If your sitemap was updated after the crawl began — or after the last completed crawl — the audit results will not reflect those changes until the next crawl is processed.
Other frequent causes include:
- Sitemap caching: Your server or CDN may serve a cached version of the sitemap to crawlers. The cached copy Site Audit fetched may have been outdated at crawl time, even if your live sitemap is now correct.
- Multiple sitemap files: If your site uses a sitemap index file pointing to several child sitemaps, Site Audit may have successfully fetched some child sitemaps but not others due to a temporary fetch error or timeout.
- Conditional serving: Some sitemap plugins or CMS configurations serve different sitemap content based on the requesting user-agent or IP address. The crawler may receive a different response than a browser does.
- Redirect chains on the sitemap URL: If the sitemap URL itself redirects before returning XML content, the crawler may not follow all redirect hops, resulting in an incomplete or empty sitemap read.
- Recently added pages: Pages added to your sitemap shortly before or during an active crawl may fall outside the crawl window and only appear in the next scheduled audit.
🛠️ How to Troubleshoot the Discrepancy
- Re-run the Site Audit crawl. Navigate to your Site Audit dashboard and trigger a fresh crawl. Once the crawl completes, check whether the page is still flagged as missing. This is the quickest way to rule out a stale-data issue.
- Verify the sitemap URL used by Site Audit. Open your Site Audit project settings and confirm the sitemap URL entered matches your actual live sitemap URL exactly, including the protocol (https://) and any subdirectory path. A mismatch here means the tool is checking a different file than the one you are viewing in your browser.
- Fetch the sitemap URL directly. Paste your sitemap URL into a browser or a tool like Google Search Console's Sitemap report. Confirm the page in question is listed and that the sitemap returns a valid HTTP 200 status with correct XML markup.
- Check for sitemap caching. Add a cache-busting query string (e.g., ?nocache=1) to your sitemap URL in a browser to see if you get a fresher version with more entries. If the cached and uncached versions differ, work with your hosting provider or CDN to reduce the sitemap cache TTL.
- Inspect child sitemaps in a sitemap index. If you use a sitemap index, open each child sitemap URL individually and confirm the page appears in the correct child file. If a child sitemap returns an error or is empty, that file needs to be fixed at the CMS or plugin level.
- Review the page's canonical tag and index status. Occasionally, Site Audit flags a page as missing from the sitemap because the page itself contains a noindex directive or a canonical tag pointing to a different URL. Site Audit may exclude noindexed URLs from sitemap coverage checks by design. Confirm the page is indexable before expecting it to appear as covered.
- Check for redirect chains on the page URL. If the URL listed in your sitemap redirects to another URL, Site Audit may record the final destination URL as the canonical version. Compare the URL in your sitemap against the URL Site Audit tracked after following redirects.
📋 Best Practices to Prevent Future Discrepancies
- Keep your sitemap URL stable and ensure it returns a 200 OK status at all times.
- Avoid making large sitemap changes while a crawl is actively running.
- Set your CDN or server cache TTL for sitemap files to 1 hour or less so crawlers always receive a near-current version.
- Use a single, authoritative sitemap index file rather than submitting multiple disconnected sitemap URLs.
- After publishing new pages, allow at least one full audit cycle before expecting them to appear as covered in Site Audit reports.
💡 Understanding the Audit Timestamp
Every Site Audit report displays a last crawled timestamp at the top of the dashboard. Always compare this timestamp against the date you last updated your sitemap. If your sitemap was modified after the crawl timestamp, the current report cannot reflect those changes. Re-running the crawl will bring the report up to date.
🙋 Still Seeing the Discrepancy?
If you have re-run the crawl and verified all the steps above but the page is still showing as missing, there may be a crawl configuration or account-level issue that requires investigation. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.
Additional Notes
Step 2: Clear Your Browser Cache and Reload — A cached version of the Site Audit dashboard can display outdated results even after a new crawl has completed. Clear cached images/files and cookies (Ctrl+Shift+Delete / Cmd+Shift+Delete), set time range to All time, then reopen browser and log back in.