Documentation menu

Search Console: Indexing

Describes GLLmolfar 0.9.22current release 0.9.23 · checked 1 Nov 2026

Google's own answer for each page of the site, from Search Console's URL Inspection: whether the page is in the index and, if not, why; when Google last crawled it; which canonical Google chose; and which rich results it found. Pages are asked in portions, and every answer is kept on this computer.

Where
GSC › Indexing
Mode
Simple and Pro
Built from
Search Console's URL Inspection, asked page by page; the crawl's indexable pages
Changes
When you press Inspect, a portion at a time

On the screen

Under the shared head (see Performance): the lead, the button with the day's allowance, four counts, the reasons in Google's words, and one row per page asked.

The Indexing report of the GSC section in GLLmolfar for getlooploop.com, fifteen pages inspected
real screenshotProject getlooploop.com. Other sites and brands on screen are replaced with neutral names.

  1. What it asks. In the index or not and why, when Google last fetched the page, which canonical it chose. Every answer is kept on this computer.

  2. Inspect N pages. Asks Google about the next portion: up to 200 pages not yet asked or older than 14 days.

  3. Allowance. {left} of {daily} inspections left today, and how many pages are not yet asked or older than 14 days.

  4. Counts. indexed, not indexed or excluded, Google chose another canonical, not asked yet.

  5. By Google's reason. The pages asked, grouped by the reason Search Console gives, in its own words.

  6. In the index. Indexed, Not indexed, Excluded, or No answer.

  7. Canonical. as declared, or Google chose {address} in red when Google picked another page.

How pages are asked

  • The pages asked about are the open crawl's indexable HTML pages that answered 200. Without a crawl, the pages Search Console lists for the period.
  • Inspect {n} pages takes up to 200 of them at a press: pages never asked, or asked more than 14 days ago.
  • Google is asked four pages at a time. While it runs, the wait bar reads “Asking Google about page {n} of {total}” beside Stop; what was learnt before Stop is kept.
  • Search Console allows 2,000 page inspections a day per site; that is Google's limit, not the app's. The app counts the day's use and stops when it is used up.
  • Each answer is saved on this computer with its date, so the report is there offline and signed out. Asking again needs the account.

The table

ColumnWhat it shows
AddressThe page asked about. Pages not in the index come first, then those with no answer, then indexed pages. Up to 500 rows, with Showing N of M.
In the indexGoogle's verdict: Indexed, Not indexed, Excluded (neither), or No answer when the question failed.
Google's reasonThe coverage state as Search Console states it, such as “Submitted and indexed”.
Last crawled by GoogleWhen Google last fetched the page, or a dash.
Canonicalas declared when Google kept the page's own canonical; Google chose {address} when it picked another.
Rich resultsThe rich result types Google detected, such as Breadcrumbs, or a dash.

States and messages

Nothing askedNo page has been inspected yet. Inspect a portion to see which pages Google indexed and why the others are out.

Shown in place of the counts.

RunningAsking Google about page {n} of {total}

With Stop.

Allowance usedGoogle's daily allowance of inspections for this site is used up; it renews tomorrow.

The answers so far are kept.

Related pages

Search Console: PerformanceGSC › Performance: Google clicks, impressions, CTR and position read-only, kept on this computer and shown with their date when you are offline or signed out.Search Console: SitemapsGSC › Sitemaps: the sitemaps submitted to Search Console, their URLs, errors and warnings, when Google last read them, beside the URLs the crawl found.Search Console: PagesGSC › Pages: each page's Google clicks, impressions, CTR and position, its top query, its state in the crawl, and crawled pages Google never showed.IssuesThe Issues tab: every check that failed in the crawl, by importance and type, with why it matters, how to fix it and the URLs behind it.URL auditSite › URL audit: one page checked without a crawl — status, speed, JavaScript, page map, failed checks, accessibility, robots.txt, headers and screenshots.