My sitemap has more pages than the indexing report. Which count is current?

Put dates beside the counts

Fictional release timeline, not a report from a real site:

Compare the same intended URL population: property, sitemap/child scope, canonical policy and report filters matter. Do not subtract an older property-wide indexed count from today’s sitemap total and label the difference “new pages rejected.” Those counts can describe different dates and URL sets.

Google’s Sitemaps report defines Last read as its fetch time and Success as successful loading/processing. Parsed URLs are not guaranteed to be crawled or indexed. Page indexing is a different report; an individual URL still needs its own evidence.

Separate the observations

Inspect the actual affected URL when needed. Do not apply one inspected page’s result to every new article.

A sitemap can have a Last read timestamp and still report parsing errors. Record its status separately and review the reported errors; a fetch timestamp alone does not approve the sitemap contents or prove any listed page is indexed.

Prioritize concrete defects

Check whether the new pages return successful public responses, have appropriate canonical URLs and are linked from useful public hubs. Fix an observed block or broken destination. “Discovered, not indexed” is not itself proof of a broken model feature or a robots error. Read the specific state and dates. For a sampled URL distinguish stored inspection from a live test using the indexing-evidence diagnostic; a live fetch cannot represent the whole batch’s index state.

Do not remove intentional private-route protections merely to increase an index count. Expected excluded pages and relevant public pages have different purposes.

Follow up without repeated blind submission

Keep the sitemap accurate and allow the actual reports to update. Use individual inspection for meaningful examples rather than repeatedly submitting the same unchanged inventory. Monitor indexed status and search performance separately. A successful notification or sitemap read is not proof of ranking or traffic growth. Record the next evidence checkpoint in your review notes without inventing a completed result.