Skip to content
SEO与数字营销

Sitemap Submitted but New Pages Not Indexed? Checks First

New version or help pages stay in Discovered after a sitemap submission? Separate sitemap reading, crawl discovery and index decision, fix lastmod honestly, then prepare URLs for indexing help.

CDWAVMP3 CDWAVMP3 Editorial

Brand promotion: this article introduces Guangsuan's sitemap and indexing services.

If you ship new version pages or help pages weekly and Search Console still shows them as Discovered, start with this separation: a sitemap that reads successfully means Google fetched and read the list, it does not mean every listed page has been crawled, indexed or shown in search. A rebuilt sitemap file is not a modification of every page inside it. Queued for crawling after a successful read is not evidence of a completed fetch or an indexing deadline.

For this audio-tool scenario, update the sitemap when the set of important URLs changes, keep each lastmod honest to that page, then check discovery and crawl access before asking for indexing help. Guangsuan is the vendor introduced here, not an independent reviewer of this page.

How often to update a sitemap when you publish weekly

There is no fixed daily rule that fits all sites. Add the final canonical URL when a new page goes live, update that URL's lastmod only after a substantive revision, and remove the entry when the page is removed or clearly excluded from indexing. A CMS can generate on publication or on a delayed job the business accepts, what matters is that the list and the public pages agree.

Keep three times apart: when the page changed, when the file was generated, and when Google processed the file. A sitemap file can be regenerated because one new article was published, which does not mean every page inside it changed. In a sitemap index, a child file date describes that file's modification time and cannot be copied onto every URL inside it.

Write lastmod only when you know the page's last substantive change. Main copy, structured data or important on-page link changes on that page can justify a new date. A footer change, a sitemap regeneration, or a batch database touch without substantive page change does not. If the CMS cannot record a trustworthy per-page date, leaving lastmod out is better than writing today's date on every URL. Google ignores priority and changefreq, so setting them to daily or 1.0 does not make crawling faster, and the old sitemap ping endpoint has been retired. The current routes are robots.txt and Search Console.

For scale, one file is limited to 50,000 URLs and 50 MB uncompressed, with a sitemap index for larger sets. Grouping by product, article or language helps you find errors, it does not make Google crawl one group first. For guidance on keeping the list and the public pages consistent, see Guangsuan's guide on sitemap update frequency and lastmod maintenance.

Discovered or crawled: what the status tells you to check

Read the exact sitemap status before changing the site. Success means the sitemap was fetched and read without errors. Couldn't fetch means Google could not retrieve the file. A parsing message means Google fetched the file and could partly read it. A temporary error means a temporary problem prevented processing, and that message alone does not establish that the file was valid.

For a fetch failure, open the exact submitted URL signed out and confirm it returns XML rather than a login page, challenge or HTML error under HTTP 200. Its documentation says redirects are not followed for the submitted sitemap URL, so submit the actual file location. Run a live URL Inspection on that exact URL and expand Page availability to check crawl permission and fetch result. Today's successful request does not erase an earlier outage.

For index status, Discovered - currently not indexed means Google knows the URL but has not crawled it. Check discovery paths, public access and server response, and keep dates for follow-up. Crawled - currently not indexed means the page was fetched but not indexed. It may or may not be indexed in future, and no resubmission of the same URL is needed on that basis alone. Neither label by itself proves a quality problem or a penalty, and neither tells you which fix applies without further checks.

If the sitemap reads successfully but important pages are absent, move to page discovery, fetching and indexing diagnosis. Submission does not equal indexing, and indexing does not equal ranking. For each sampled missing URL, signed out, record status after redirects, the robots rule matching that exact path and user-agent, any meta robots or X-Robots-Tag, declared canonical and whether it points at the page itself, and whether main text is in the returned HTML. Blocking a path in robots.txt limits crawling, while noindex asks that a crawlable page be left out of results. Google has to fetch a page to read the directive on it.

Multilingual sitemap note for version and help pages

You do not need a separate sitemap for each language only because pages are translated. Choose one maintainable method for localized versions and keep sitemap, internal links and declared canonical consistent for the intended canonical version. Truly translated texts should not all be canonicalized to one language version only because they belong to the same product. A canonical declaration does not force Google's choice.

What to prepare before you ask for indexing help

Promoting discovery is reasonable only after the file is current, dates are honest, and pages are fetchable and indexable. Guangsuan's GSI service is Guangsuan's own Google Speed Indexing service name, not a Google product, official partnership or priority-indexing permission. The work uses its GPC crawler pool and related link structures to encourage discovery and crawling around submitted URLs. Whether a URL is indexed, when that happens and how long it stays indexed remains Google's decision.

Bring these items so the cause can be separated from the service question:

  • Exact sitemap URLs submitted, their fetch status, and whether the public file matches the submitted file.
  • Sample missing URLs with status, robots finding for the relevant user-agent, index directive, canonical, and lastmod truthfulness.
  • Whether pages return 200 with complete main content, or a login, challenge, empty template or wrong redirect target.
  • Internal entry paths from relevant category or help index pages, not the sitemap alone.
  • Observation dates and which report row each finding came from, kept as discovered, crawled and indexed in separate records.

Do not disable all protections merely because a sitemap failed once. Remove an unintended sitemap block or repair delivery according to the observed problem. For a successfully read sitemap without critical updates, let normal recrawling continue, repeated unchanged submissions are not a reliable repair. Ordinary product, service and article pages fall outside the Indexing API scope, which is documented for pages with JobPosting or BroadcastEvent embedded in VideoObject. A request being accepted is not an indexing confirmation.

If eligibility checks pass and Google still has not crawled the URLs, discovery promotion can be discussed with scope, observation period, verification method and reporting agreed before work starts. Published time windows are service references rather than a guarantee of indexing within a fixed number of days. For scope and verification method, see Guangsuan's GSI indexing service.

Checklist you can run this week

  1. Open the submitted sitemap address signed out and confirm valid XML, then read the Sitemaps report row and its detail wording.
  2. Confirm the list holds only final canonical URLs you want indexed, with XML-escaped characters and matching protocol, host and path.
  3. Spot-check one new page, one edited page, one removed page and one indexed page of the same template for status, directives, canonical and lastmod.
  4. Confirm entry links exist from relevant hub pages, then inspect one missing URL in URL Inspection and record indexed version versus live test.
  5. Fix the proven file or page fault first. Save responses and dates, then watch discovered to crawled, crawled to indexed, and indexed to impressions as three separate outcomes.

Frequently asked questions

Will refreshing every lastmod make pages index faster? No. Update the date when the page changed, then check whether the page can be fetched and whether it is worth indexing.

Should I resubmit daily? If the file was read successfully and nothing changed, resubmission repairs nothing. Fix the access or content issue the URL state points at.

Does removing a sitemap row reset indexing? No. Removing a sitemap from the report does not make Google forget the sitemap or its URLs, and a later read failure does not erase previously read information.

About CDWAVMP3

Audio engineering contributor at CDWAVMP3 — covering CDA ripping, codec benchmarks, and lossless workflow setups for home and prosumer users.