How to Use Google Search Console for SEO

Search Console is Google’s own record of how it crawls, indexes and shows your site, and its value comes from running repeatable routines on a handful of reports. The routine is short: mine the Performance report for pages close to earning more clicks, read the Page indexing report by its exact reasons and validate fixes, inspect the URLs that matter, and keep an eye on Manual Actions and Security Issues. Each routine depends on reading the report without being misled by it.

Performance report: find the opportunities, and read the numbers correctly

The Performance report groups clicks, impressions, CTR and position by the dimension you choose: queries, pages, countries, devices, search appearance or dates. Three routines pay for the time:

Queries just off the first page. Filter to queries where your average position sits roughly between 5 and 15. The range is a working rule, not a Google threshold. These pages already rank; targeted improvements to the page that answers the query can cost less than a new page.
High impressions, low CTR. A page with high impressions and a low CTR at a stable position is a candidate for a better title and description, or a sign the results page answers the query on its own.
Impressions and clicks together. Impressions steady while clicks fall can point to a change in the results page, such as new features above your listing, rather than lost rankings. Both falling together points to lost rankings or lower demand; the position column helps tell them apart.

Before acting, know three things about the data:

Totals can disagree. The report says data grouped by queries, countries, devices or dates is aggregated by property, while data grouped by pages or search appearance is aggregated by page. So the chart totals can differ from the table totals. That is aggregation, not an error.
Your own search isn’t the report. Google notes that a query can appear in your list and still not show your site when you search it yourself, because results depend on the time, place, device and recent history of the person searching.
Search type matters. Web results are one type among several, and the search type filter has a “Web: multimodal” option for web results where an image was part of the search. Compare like with like.

Page indexing report: read the reasons, not the count

The Page indexing report shows which of your pages are indexed and why the others aren’t. Its value is in the reasons. Several reasons describe choices you made, and those need no action if they match your intent: a noindex rule, an alternate page with a proper canonical, a redirect. The ones to work on are pages you expect in the index that aren’t there.

Two reasons are easy to misread, and Google’s Page indexing report help defines both:

“Discovered – currently not indexed”: known to Google but not crawled yet. The help page says the typical cause is load: crawling it was expected to overload the site.
“Crawled – currently not indexed”: Google crawled the page and didn’t index it. Its future is open: the help page says it may or may not be indexed later, and that resubmitting isn’t needed.

The help page’s names for reasons can differ slightly from the labels in your account, so match on meaning when you compare.

After you fix a cause, use Validate fix. The help page says Search Console immediately checks a few pages, and that validation typically takes up to about two weeks but can take much longer. It also asks you not to click Validate fix again until the validation has succeeded or failed.

URL Inspection: one URL at a time

The URL Inspection tool answers what Google knows about one exact URL. Two limits keep it in proportion:

The default view isn’t live. It shows the most recently indexed version. Run a live test to see how the current page fetches and renders.
“URL is on Google” isn’t a ranking promise. Google says that status doesn’t guarantee the page appears in search results, because the tool doesn’t account for every requirement.

Request indexing asks Google to crawl a URL, and each property has a daily limit on inspection requests. Use it after a meaningful fix on an important page, not as a bulk tool.

The rest of the routine

Sitemaps report. Shows whether Google could read the sitemaps you submitted. Combined with the Page indexing report’s sitemap filter, it shows how many submitted URLs are indexed.
Links report. Shows top linking sites, top linked pages and top linking text, from a sample of links.
Core Web Vitals report. Groups URLs by their field performance on LCP, INP and CLS. web.dev’s thresholds for good are 2.5 seconds, 200 milliseconds and 0.1, measured at the 75th percentile of page loads.
Crawl Stats. Available for root-level properties. Shows host health, response times and crawl purpose.

Two reports are for checking on sight, because a problem there outranks the rest of the routine:

Manual Actions: a human reviewer found pages that don’t comply with Google’s spam policies.
Security Issues: hacked content, malware and unwanted software, or social engineering.

A monthly rhythm

Monthly: pull the queries just off the first page and the high-impression, low-CTR pages, and queue the page work they imply. Scan the Page indexing report for new or growing reasons, and validate what you have fixed.
Weekly, or on alert: check Manual Actions and Security Issues.
After a significant release: inspect the key URLs with a live test.

For analysis beyond the interface, export the data or use the Search Console API, which lets you query your search analytics programmatically and keep your own history.

Frequently asked questions

Where should I start for quick wins?

In the Performance report. Filter to queries with average positions around 5 to 15, and to pages with high impressions and a low CTR. Improve the pages that answer those queries.

Does Request indexing get my page indexed?

It asks Google to crawl the URL. It doesn’t promise indexing, and each property has a daily limit on inspection requests. Use it after a real fix on an important page.

Why don’t my Performance chart and table totals match?

Because they are aggregated differently. Google says data grouped by queries is aggregated by property, while data grouped by pages is aggregated by page, so the totals can differ.