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

Read saved Indexing Evidence for a Site

Indexing Evidence is a dated Search Engine observation. It is not a permanent URL verdict.

Before you start

Use a key with indexing:read and an authorized Site. The main path below only reads saved data. Start with the hosted client.

Read the Site view

const overview = await client.getSiteIndexing({
  params: { siteId },
  query: { days: 28 },
})
console.log(overview.data.summary, overview.data.trend)

The summary includes URL counts and observation dates. Check oldestCheck and newestCheck before using a trend. The hosted HTTP reference defines the full response.

List URLs and diagnostics

const urls = await client.listSiteIndexingUrls({
  params: { siteId },
  query: { limit: 100, offset: 0 },
})
const diagnostics = await client.getSiteIndexingDiagnostics({
  params: { siteId },
  query: {},
})
console.log(urls.data.urls, urls.data.pagination)
console.log(diagnostics.data.issues)

listSiteIndexingUrls reads saved observations. Page through pagination when hasMore is true. getSiteIndexingDiagnostics groups missing or uncertain evidence. Keep each observation date next to its URL. If no observation exists, show that gap.

Request a fresh inspection if needed

Keep the page edit date separate from its inspection date and Google's last crawl. Google Search processing timelines explains waiting after a change. Those observations do not define SDK request duration or gscdump's inspection schedule.

inspectSiteUrls starts a new inspection and requires indexing:write. It is a mutation. A network timeout leaves its outcome uncertain, so read saved state before sending it again. Errors and retry covers this case.

Choose another source

Hosted sitemaps answers whether an exact URL appears in a saved sitemap generation. That is separate evidence. To call Bing directly, switch to Direct Bing.