
Google Search Console is the only tool that shows you how Google itself sees your site: which queries you appear for, which pages are indexed, and which ones Google quietly decided to skip. It holds 16 months of search performance data, it is free, and most teams use maybe a fifth of what it offers. This guide walks through the reports that matter for SEO work, plus the filtering and export tricks that turn raw numbers into decisions.
What the Data in Search Console Actually Represents
Search Console reports on Google Search results only: clicks from organic listings, impressions, click-through rate and average position. It does not track on-site behaviour, so the numbers will never match an analytics platform exactly, and that is normal rather than a tracking bug.
Clicks are counted when someone leaves the search results page for your site, while an analytics tool counts a session once a page loads and a tag fires. Ad blockers, bounced loads and redirects routinely create a 5 to 15 percent gap between the two. Treat Search Console as the demand-side view and your analytics as the behaviour-side view.
Property Types and Verification Choices That Affect Your Data
Before you read a single report, pick the right property type, because this decision changes what you can see for the next 16 months. A Domain property rolls up every subdomain and both HTTP and HTTPS versions under one roof, while a URL-prefix property tracks only the exact protocol and subdomain you enter.
- DNS TXT record: required for Domain properties, usually live within an hour, sometimes up to 48 hours depending on your registrar.
- HTML file upload: fastest for URL-prefix properties if you have FTP or file manager access.
- HTML meta tag: paste one line into the head section; fine for WordPress, Shopify and Webflow.
- Google Tag or Google Analytics: works if the tag already sits on the homepage and you have edit permissions.
Set up a Domain property as your primary view, then add URL-prefix properties for subfolders you care about, such as /blog/ or /products/. Google’s own Search Central documentation confirms that subfolder properties get their own full set of reports, which is the cleanest way to track a content hub separately from commercial pages.
Submit an XML sitemap on day one under Indexing then Sitemaps. A sitemap does not force indexing, but it gives Google a canonical list of URLs with lastmod dates, which speeds up discovery on sites with weak internal linking.
Reading the Performance Report Without Fooling Yourself
Average position is the single most misread metric in the console. It is an impression-weighted average across every query and every device, so a page ranking second for a tiny query and fortieth for a big one can show an unhelpful average of twenty-one.
Three habits make the performance report far more honest:
- Compare like-for-like date ranges. Use 28 days versus the previous 28 days, not month-to-month, so you avoid comparing a four-weekend month against a five-weekend one.
- Split branded from non-branded queries. Brand searches mask whether your SEO work is winning new demand.
- Filter to one page at a time when diagnosing a drop, because site-wide averages hide the handful of URLs doing the damage.
Remember that Google anonymises rare queries for privacy, so the query table will always total fewer clicks than the top-line chart. On smaller sites the gap can reach 30 percent, and that hidden long tail is often where new topic ideas live.
Regex Filters and Striking-Distance Queries
The custom regex filter is where this tool stops being a dashboard and starts being an SEO research platform. Switch the query filter to “Custom (regex)” and you can slice 16 months of real search demand in seconds.
- Question queries: ^(who|what|why|how|when|where|is|can|does) surfaces the informational gaps your FAQ sections should answer.
- Brand exclusion: use “Doesn’t match regex” with your brand variants to see pure non-branded performance.
- Buying intent: (near me|cost|price|quote|best|vs) isolates the queries most likely to convert.
Then hunt for striking-distance terms: queries sitting between positions 8 and 20 with at least a few hundred impressions. These pages already have relevance signals, so a sharper title tag, a stronger intro and two internal links from related posts often move them several positions within a month.
Filtering by page also exposes keyword cannibalisation. If three URLs trade impressions for the same query across different weeks, consolidate them or re-point the weaker ones, a fix that pairs well with a proper content gap analysis against your competitors.
Fixing Indexing Problems in the Page Indexing Report
The Page Indexing report splits your URLs into indexed and not indexed, and the “not indexed” reasons deserve weekly attention. Four statuses account for most real problems:
- Crawled, currently not indexed: Google saw the page and judged it not worth storing, usually a quality or duplication signal.
- Discovered, currently not indexed: often a crawl budget or server speed issue on larger sites.
- Duplicate without user-selected canonical: Google picked a different URL than you intended.
- Soft 404: thin pages, empty category results or JavaScript that renders nothing useful.
Use the URL Inspection tool to check any single page: it shows last crawl date, the canonical Google chose, the rendered HTML and mobile usability status. The “Request indexing” button is capped at roughly ten submissions per property per day, so save it for genuinely important updates rather than every blog post.
How to Make Google Crawl Your Site Faster
Crawl speed is mostly earned, not requested. Open Settings then Crawl stats and look at average response time: sites answering in under 300 milliseconds typically see noticeably more pages crawled per day than sites sitting above a second.
Practical levers that shift crawl behaviour include accurate lastmod dates in your sitemap, removing crawl traps like faceted URL parameters, returning clean 410s for deleted pages, and adding internal links from pages Google already crawls daily. Page speed feeds into this too, which is why site speed matters well beyond conversion rates.
Core Web Vitals, Structured Data and Shopping Reports
The Core Web Vitals report uses field data from the Chrome User Experience Report on a rolling 28-day window, so fixes take about a month to show fully. Current thresholds are an LCP under 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1 for 75 percent of visits, as documented by Google’s web.dev team.
Below that, the Enhancements section validates your structured data: FAQ, product, review snippet, breadcrumb and merchant listing markup each get their own report with errors and warnings. Ecommerce sites should cross-check these against their feed work, since the same product data issues tend to show up when you optimise a Google Merchant Center feed.
Local businesses should read the performance report with a geography filter applied, comparing organic query patterns against paid reach from Google local campaigns that drive foot traffic. The overlap usually reveals which service terms deserve a dedicated landing page.
Exporting Past the 1,000-Row Limit
The interface caps exports at 1,000 rows, which is the point where most SEOs assume they have seen everything. They have not. The Search Console API returns up to 25,000 rows per request, and the Bulk Data Export pipes daily query and URL data straight into BigQuery with no row sampling at all.
For teams without engineering support, a Looker Studio connection to the same data set gives unlimited row access in a shareable report, and tools like SEOTesting layer annotation and split-test analysis on top. Set the bulk export up early: it only collects data from the day you enable it forward, never retroactively.
A Monthly Routine That Keeps the Console Useful
- Week one: review 28-day performance versus the prior period, branded and non-branded separately.
- Week two: work a striking-distance list of 10 queries in positions 8 to 20.
- Week three: clear new entries in the Page Indexing report and validate fixes.
- Week four: check Core Web Vitals, structured data errors and any manual action or security notices.
Four hours a month on that loop beats a six-hour audit once a quarter, mainly because validation cycles in Search Console take days to complete and you want them running continuously.
Frequently Asked Questions
How Long Does It Take for Google to Index a New Website?
Most new sites get their first pages indexed within 3 to 14 days, and full indexing of a small site typically settles within four to eight weeks. Submitting a sitemap and earning a few external links from already-crawled sites shortens that window considerably.
Is Google Search Console Free?
Yes, it is completely free with no paid tier, and there is no limit on the number of properties you can verify. The only cost appears if you pipe bulk data into BigQuery, where storage and query charges usually run a few dollars a month for a mid-sized site.
Why Do Search Console Clicks Not Match Google Analytics Sessions?
Gaps of 5 to 15 percent are standard because the two tools count different events: one counts clicks leaving the search results, the other counts tagged page loads. Larger gaps usually point to missing tags, redirect chains or heavy bot filtering.
Is There an Official Google Search Console Course?
Google publishes free training through Search Central, including documentation, video walkthroughs and the Search Console Training series on YouTube. Third-party platforms also run paid courses, though the official material covers every report in the tool.
How Far Back Does Search Console Data Go?
The performance report stores 16 months of data, and anything older is permanently deleted. If you want multi-year trend analysis, export monthly snapshots or enable the BigQuery bulk export before that rolling window erases what you need.
Get Help Turning Search Console Data Into Rankings
If your reports are full of “crawled, currently not indexed” URLs or flat impressions you cannot explain, a second pair of eyes usually finds the pattern in an hour. SEO Quirk audits Search Console properties and builds the fix list, and you can read more about working with a local agency before you decide.