Google Search Console (GSC) is the only place you see how Google itself understands your site. Analytics tells you what visitors did after they arrived; Search Console tells you what happened in the search results before they clicked — which queries you appeared for, how often, at what position, and which pages Google refused to index.
It is free, it has no meaningful competitor because nobody else has Google's data, and most sites use perhaps a fifth of it. This guide covers what each report is for and how to act on it.
Setting up: adding and verifying a property
A "property" is the site you want data for. You have two choices, and the difference matters more than people expect.
| Property type | Covers | Verification |
|---|---|---|
| Domain | Every subdomain and both http/https — example.com, www, blog.example.com, m.example.com | DNS TXT record only |
| URL prefix | Only the exact prefix you enter, e.g. https://www.example.com/ | HTML file, meta tag, Google Analytics, Tag Manager, or DNS |
Use a Domain property if you can add a DNS record. It captures everything, so you never discover months later that half your traffic was on a subdomain you were not tracking. Use URL prefix if you have no DNS access, or if you genuinely need to separate a subdirectory (say, a client microsite you manage but do not own).
Verification methods for URL prefix, roughly in order of durability:
- 1DNS TXT record — survives redesigns, CMS migrations and theme changes. The most robust option.
- 2HTML file upload — put a file Google gives you at the site root. Easy, but a migration usually deletes it and silently unverifies you.
- 3HTML meta tag — a single tag in the homepage <head>. Fine, but themes get replaced.
- 4Google Analytics or Tag Manager — quick if already installed, but breaks if you change analytics providers.
Do not skip this
Losing verification stops data collection silently — you will not get an email until Google has already stopped. If you verified with an HTML file years ago, add a DNS record as a second method now.
The Performance report
This is the report you will spend most of your time in. It has four metrics, and misreading the relationship between them is the most common mistake in SEO reporting.
| Metric | What it means | What a change usually indicates |
|---|---|---|
| Impressions | Your page appeared in results a user saw | Rising = more queries matched, or you gained visibility on existing ones |
| Clicks | Someone clicked through to your site | Falling while impressions rise = your title/description is not compelling, or you slipped below the fold |
| CTR | Clicks ÷ impressions | Position-dependent — compare against pages at similar positions, never against a flat benchmark |
| Average position | Mean position across all impressions | A blunt average; a page ranking #3 for one term and #60 for forty others shows a bad "average" |
Reading it properly
Average position is the metric that misleads people most. It is averaged across every query the page appeared for, so ranking newly for a hundred marginal long-tail terms will drag your "average position" down while your actual traffic goes up. That is a good outcome that looks like a bad chart. Always segment by query before drawing conclusions.
The most useful view is the Pages tab filtered to the last 28 days, compared against the previous 28. Sort by clicks lost. Anything that dropped sharply is worth investigating; anything that gained is worth understanding so you can repeat it.
The high-impressions, low-CTR opportunity
Filter queries to those with high impressions and a CTR well below what their position would normally earn. These are pages Google is already showing to people who then choose something else. Rewriting the title tag and meta description on those pages is among the highest-return work in SEO because the ranking is already won — only the click is being lost.
AI Overviews and AI Mode
Since 2026, Performance data includes impressions and clicks from AI Overviews and AI Mode alongside classic blue-link results. They are not broken out separately, so a page that is being cited in AI answers but rarely clicked will show as rising impressions with falling CTR. Interpret that pattern as visibility without traffic rather than a ranking problem.
The Page Indexing report
A page that is not indexed cannot rank, so this report outranks almost everything else in priority. It splits your URLs into indexed and not indexed, with a reason attached to each exclusion.
The reasons that usually need action:
- ●Crawled — currently not indexed: Google fetched the page and chose not to index it. Almost always a quality or duplication signal. Thin, templated or near-identical pages land here.
- ●Discovered — currently not indexed: Google knows the URL exists but has not crawled it. Common on large sites and usually a crawl-budget or internal-linking problem — the page is too deep or barely linked to.
- ●Duplicate without user-selected canonical: Google found several near-identical pages and picked one itself. Set canonicals explicitly rather than letting it guess.
- ●Soft 404: the page returns HTTP 200 but looks empty or error-like to Google. Frequent on out-of-stock product pages and empty category pages.
- ●Blocked by robots.txt: intentional or not, verify it is deliberate.
- ●Excluded by noindex tag: same — check it is on purpose.
Reasons that are usually fine and need no action: "Alternate page with proper canonical tag", "Page with redirect", and "Duplicate, Google chose different canonical than user" when your canonical logic is deliberately loose.
Sitemaps
A sitemap does not make Google index a page. It helps Google discover URLs, which matters on large sites, new sites with few backlinks, and sites with poor internal linking. On a well-linked 30-page site it changes almost nothing.
- ●Include only canonical, indexable, HTTP 200 URLs. Listing redirects or noindexed pages wastes crawl signals and dilutes trust in the file.
- ●Keep <lastmod> honest. Sitemaps that claim every page changed today get ignored.
- ●Split files above 50,000 URLs or 50 MB uncompressed, and reference them from a sitemap index.
- ●The Sitemaps report shows discovered vs indexed counts. A large gap points at a quality problem, not a sitemap problem.
URL Inspection
Paste any URL on your property to see exactly what Google knows about it: whether it is indexed, when it was last crawled, which canonical Google selected versus which you declared, and whether it is mobile-usable.
The part most people miss is "Test Live URL", which fetches the page right now rather than showing the cached crawl. Use it after fixing something to confirm the fix is actually visible to Googlebot — particularly on JavaScript-rendered sites, where the rendered HTML can differ from what you see in your browser.
"Request Indexing" submits the URL for priority crawling. It is genuinely useful for a handful of important updates. It is not a bulk tool and will not rescue a site with systemic quality issues.
Experience, Enhancements and Links
Core Web Vitals
Reports field data from real Chrome users, grouped into URLs with similar templates. Because it needs enough real traffic to report, low-traffic pages may show no data at all. This is real-world data, which makes it more trustworthy — and slower to react — than a lab test like PageSpeed Insights.
Enhancements / structured data
If you have valid schema markup, GSC reports on it here — FAQ, Breadcrumb, Product, Review and so on — with errors and warnings. Errors block rich results; warnings mean a recommended field is missing but the markup still qualifies.
Links
Shows top linking sites, most linked pages and anchor text. It is a reasonable sanity check but it is not a backlink analysis tool: the data is sampled, delayed and gives you no quality signal about the linking domains.
A workable review routine
| Frequency | What to check | Looking for |
|---|---|---|
| Weekly | Performance, last 28 days vs previous 28, Pages tab | Sudden click losses on important pages |
| Weekly | Page Indexing — not indexed count | New exclusion reasons appearing |
| Monthly | Queries with high impressions and low CTR | Title/description rewrite candidates |
| Monthly | Core Web Vitals + Enhancements | Templates slipping out of "Good"; schema errors |
| After any launch or migration | URL Inspection on key templates, Sitemaps, Page Indexing | Accidental noindex, broken canonicals, dropped verification |
The point of a routine is catching problems while they are small. A noindex tag shipped by accident costs very little if you find it in a week and a great deal if you find it in a quarter.
Common mistakes
- ●Treating average position as a ranking report. It is an average across all queries and hides more than it shows.
- ●Comparing CTR against a universal benchmark. CTR is a function of position, intent and SERP features — compare like with like.
- ●Ignoring the 16-month data limit. GSC keeps 16 months; export regularly if you need year-over-year comparisons beyond that.
- ●Assuming filtered totals add up. GSC anonymises rare queries, so the sum of your query rows will be lower than your reported total. That gap is expected.
- ●Requesting indexing repeatedly instead of fixing the underlying reason a page was not indexed.
Connecting Search Console to Flux N Pro
Flux N Pro reads your Search Console data through Google's official API — queries, pages, clicks, impressions, CTR and average position — and joins it to your keyword tracking, audits and content so you are not exporting CSVs to compare things by hand. Access is read-only; nothing in your Search Console configuration is modified.
Connect it under Settings → Integrations → Google Search Console. Everything above still applies — the reports are the same, they are just sitting next to the rest of your data.
Frequently asked questions
Is Google Search Console free?
Yes, entirely free with no paid tier. You only need a Google account and the ability to verify ownership of the site.
How long does Search Console data take to appear?
Performance data typically appears within 1–2 days. A brand-new property starts collecting from the verification date — it does not backfill history from before you verified.
Why do my Search Console clicks not match Google Analytics?
They measure different things. Search Console counts clicks on a search result; Analytics counts sessions that loaded your tracking code. Clicks that bounce before the page loads, ad blockers, and consent-mode settings all create a gap. A difference of 5–20% is normal.
How far back does Search Console data go?
16 months. If you need longer history, export the data periodically or connect it to a tool that stores it for you.
What is the difference between a Domain and URL prefix property?
A Domain property covers every subdomain and protocol and requires DNS verification. A URL prefix property covers only the exact prefix entered and supports several verification methods. Domain properties give the more complete picture.
Try the Site Audit
Run the checks described in this guide against your own site — free, no account needed.
Open Site Audit →Get new guides by email
Occasional, practical SEO writing. No sequences, no upsells.