Search Engines & SEO

Google Search Console

Definition

Search Console is a dashboard fed by Google's own crawling and serving data, available once you have proved you control the address. Verification is done with a DNS TXT record, an HTML file uploaded to the site root, a meta tag in the homepage head, or a linked Google Analytics account. Four parts do most of the work: the Performance report, which lists real queries with clicks, impressions, average position and click-through rate; the Pages report, which groups every known URL as indexed or not indexed with a reason attached; the URL Inspection tool, which says what Google currently knows about one specific address; and sitemap submission. The data is Google's alone and says nothing about Bing, which runs its own equivalent. Figures lag by two to three days, and queries with very few impressions are withheld to protect searchers.

Why It Matters

Without it you are guessing. Analytics tells you someone arrived; only this tells you what they typed, which is where most realistic content ideas come from — the queries where you already sit at position 11 to 20 are usually one edit away from page one. The Pages report is the only authoritative answer to why a page is missing from search, and it separates cases that look identical from the outside: crawled but not indexed, blocked by robots.txt, marked noindex, or folded into another URL as a duplicate. It is also the only channel through which Google sends manual actions and security warnings, so an unverified site simply never hears about them.

How It Works

You add a property — either a domain property covering every subdomain and protocol, or a URL-prefix property covering one exact origin — then verify ownership. Google backfills up to sixteen months of Performance data and keeps it updated from there. Submitting a sitemap.xml gives the crawler a list of addresses to check, though submission is a hint and not a promise of indexing. The URL Inspection tool fetches the live page on request, shows the rendered HTML Google would see after scripts run, names the canonical it has chosen, and offers a Request Indexing button that queues a recrawl. Coverage problems appear in the Pages report as they are found, usually several days after the change that caused them.

Real-World Example

Someone publishing a static site at field-notes.99helpers.site verifies a URL-prefix property for that exact address and submits a sitemap. Three weeks later the Pages report shows eight pages indexed and four listed as Discovered — currently not indexed, all four being pages nothing on the site links to. Adding those four to the navigation clears the problem at the next crawl. The Performance report also shows the site picking up impressions for a phrase the author never targeted, which becomes the subject of the next page.

Common Mistakes

  • Verifying only the www version and then wondering why the reports look empty — a URL-prefix property covers one exact origin, protocol and subdomain included
  • Reading Request Indexing as a command — it queues a recrawl and nothing more, and pressing it repeatedly speeds up nothing
  • Comparing its click totals with an analytics tool and assuming one is broken — they count different events, and a ten to twenty per cent gap is normal

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →