Index of every page on this site: llms.txt
Skip to content

Check URL Indexing Evidence and sitemaps

Indexing Evidence is a dated observation, not a guarantee that a page will appear in search. Keep inspection, sitemap membership, and change notifications separate.

Build a URL list

Save one absolute URL per line in urls.txt, or pass URLs directly. Use only URLs within the selected Site. For hosted sitemap membership, use the sitemaps membership command in Hosted mode. The commands reference lists the sitemap operations.

Inspect Google evidence

gscdump inspect --site example.com --file urls.txt --json

For one page, run gscdump inspect https://example.com/blog/post --site example.com --json. Results can include Google's verdict, last crawl, chosen canonical URL, and rich-result details. Some fields may be absent. Google URL Inspection has quotas; the CLI saves each completed result and reports remaining URLs after a quota stop.

Read saved observations

gscdump entities show https://example.com/blog/post --site example.com

Compare the observation date with the traffic period. A saved record can be stale. Hosted mode also offers gscdump indexing urls --site example.com --status not_indexed for saved hosted results. That listing spends no inspection quota. A Local mode inspect call does.

To refresh hosted results, run:

gscdump indexing inspect https://example.com/page --site example.com --yes --json

Pass up to 10 unique URLs. The platform reserves its shared daily quota before calling Google. The command sends one request and never retries it automatically. If the API returns 429, wait for the reported reset. If results are partial, read errors and skipped. This refreshes Google's indexed-page verdict. It does not test the live page or request indexing.

Read the coverage ladder (hosted)

gscdump indexing summary --site example.com --json

Each day in trend has coverageStates. A counted day holds one URL count per coverage state. Read the four ladder states in order: unknown_to_google, discovered_not_indexed, crawled_not_indexed, and indexed. A not_counted day was stored before gscdump counted coverage states. A newer host can add states. Read a missing state as 0, and read a state you do not know as its own state.

capture says when gscdump counted the saved verdicts and how old they are. capture.source is stored for counts gscdump saved on its daily run and live for counts made during the request. olderThan7d and olderThan30d count verdicts inspected more than 7 times 24 hours and 30 times 24 hours before capturedAt, not calendar days. Quote capturedAt and the freshness percents with each count. capture.scope is sitemap_members when every counted URL is in a live sitemap. The counts come from saved URL Inspection results. They are not Google's live index, and they can differ from the Search Console Page indexing report.

If URLs unknown to Google are already in a sitemap, adding them to the sitemap again changes nothing.

Watch URLs (hosted)

gscdump indexing watch add --site example.com https://example.com/guide
gscdump indexing watch list --site example.com --json

A Site can hold 50 Watched URLs. gscdump inspects each one every 7 days, before other scheduled URLs, and never backs off. Each inspection spends the Site's daily URL Inspection budget and the URL Inspections meter. Each scheduled inspection stores one Watched URL inspection. Compare Watched URL inspections by date to see when a URL moves up the ladder.

add and remove send 50 URLs per request, so a longer list works. Every URL must be absolute; a relative URL fails before any request. If a Site has URL Inspection off, add skips each URL with inspection_disabled, because gscdump never inspects that Site. Turn on URL Inspection in the Site settings first.

Check sitemap membership

gscdump sitemaps list --site example.com
gscdump sitemaps membership --site example.com \
  --urls https://example.com/blog/post --json

Use the hosted membership command only in Hosted mode. For local inspection of URLs in a sitemap, pipe gscdump sitemaps urls https://example.com/sitemap.xml to gscdump inspect --site example.com. A submitted sitemap is a discovery signal, not an indexing verdict. Missing membership in an incomplete sitemap observation is unknown, not absent.

Choose the next action

Check the live page before deciding to wait. Google's recrawl guidance allows days to weeks and guarantees no inclusion.

An October 2026 report describes internal Google observations presented by Gary Illyes:

Google processReported typicalReported slow cases
New URL discoveryAbout 20 hoursWeeks or never
Known URL refreshAbout 30 daysWeeks or never
Sitemap processingAbout 24 hoursUp to 14 days, or never
Canonical change1 to 3 weeksMonths with conflicting signals

These observations set no deadline for a URL. Gary described an audience exercise using internal numbers. The reporting gives no sample size or measurement method.

Earlier stages can add to the wait. The seven-day Watched URL inspection schedule cannot measure precise Google processing times. See Google Search processing timelines for the wider context.

ObservationNext check
URL absent from the intended sitemapFix the sitemap and submit it if needed.
URL in the sitemap and still unknown to GoogleCheck that Google downloaded the sitemap, then link to the URL from indexed pages.
Google selected a different canonicalCheck page canonicals and internal links.
Evidence is oldInspect again after a meaningful change and allow crawl time.
Bing differsCompare Google and Bing.

Google's Indexing API accepts change notifications only for eligible JobPosting or livestream pages with BroadcastEvent inside VideoObject. The Site must meet Google's prerequisites, and the API needs local Google credentials with the required scope.

gscdump indexing submit https://example.com/jobs/frontend-engineer --mode local
gscdump indexing status https://example.com/jobs/frontend-engineer --mode local

indexing status reads notification metadata. It does not prove indexing. Use inspect for dated Indexing Evidence. More URL checks: Check visibility.

Run this with an agent

Install the gscdump agent skill, then adapt this prompt to your Site.

Use the installed gscdump skill. Ask for one page URL and Site. Inspect dated Google Indexing Evidence. Check sitemap membership if Hosted mode supports it. Keep indexing notifications separate.