Google Search Console is Google’s free service for monitoring how a website performs in Google Search and for diagnosing problems that affect crawling, indexing and presentation in results. It is the only source of first-party Google data on queries, impressions, clicks and average position, which makes it the reference dataset for SEO measurement.
The tool began as Google Webmaster Tools and was renamed in 2015. It does not change rankings directly; it reports what Google sees and gives site owners controls such as sitemap submission, indexing requests and temporary removals.
How Search Console collects and reports data
Search Console data comes from Google’s own logs of search activity and crawling, not from tracking code on the site. A visit is not required for data to appear: every time a page is shown in results, Google records an impression, and every click to the site is recorded as a click.
Access starts with verifying ownership of a property. The choice of property type determines what the reports cover, so it should be made deliberately.
| Property type | Scope | Verification |
|---|---|---|
| Domain property | All subdomains and both HTTP and HTTPS | DNS TXT record only |
| URL-prefix property | Only URLs under the exact prefix | HTML file, meta tag, analytics, tag manager or DNS |
A domain property is the recommended default, because it captures traffic that a single URL-prefix property misses, such as a forgotten subdomain or the non-www version. URL-prefix properties remain useful for isolating a subfolder, for example one language section.
The performance report and its four core metrics
The Performance report shows how often a site appears in Google results and how users respond. It keeps 16 months of data and can be segmented by query, page, country, device, search appearance and date, with separate views for web, image, video and news search.
| Metric | Definition | Interpretation note |
|---|---|---|
| Clicks | Clicks from a Google result to the site | Close to, but never equal to, analytics sessions |
| Impressions | Times a link to the site appeared in results | Counted when the result loads, even if unscrolled |
| CTR | Clicks divided by impressions | Strongly shaped by position and result features |
| Average position | Mean of the topmost position per impression | An average across many queries hides wide spreads |
Average position is the metric most often misread. A page shown at position 2 for one query and position 40 for another with equal impressions reports an average of 21, which describes neither situation. Filtering by a single query and country gives a much more meaningful number.
The interface displays at most 1,000 rows per table, and Google omits anonymized queries that too few users searched. For full analysis, teams use the Search Console API or the bulk data export to BigQuery, which removes the row limit for new data going forward.
Indexing, experience and security reports
Beyond performance, Search Console contains diagnostic reports that explain why pages are missing or underperforming. Each answers a specific technical question.
| Report or tool | Question it answers | Typical action |
|---|---|---|
| Page indexing | Which URLs are indexed and why others are not | Fix noindex, redirects, duplicates or soft 404s |
| URL Inspection | How Google sees one specific URL | Run a live test, then request indexing |
| Sitemaps | Whether submitted sitemaps were processed | Resubmit after fixing fetch or parsing errors |
| Core Web Vitals | Whether real users get good loading and responsiveness | Improve LCP, INP or CLS on flagged URL groups |
| Manual actions | Whether a reviewer applied a penalty | Fix the violation and file a reconsideration request |
| Security issues | Whether hacking or malware was detected | Clean the site and request a review |
| Links | Top linking sites, linked pages and anchor text | Audit the backlink profile and internal linking |
The Core Web Vitals report uses field data at the 75th percentile. A URL group is rated good when LCP is at most 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1.
Search Console compared with web analytics
Search Console and web analytics measure different events from different vantage points, so their numbers should be compared for trends, not matched exactly.
| Aspect | Search Console | Web analytics |
|---|---|---|
| Data source | Google search logs | Tracking code in the browser |
| Covers | Activity before and at the click | Behavior after the visit starts |
| Query data | Yes, with anonymized queries omitted | Almost none for organic search |
| Affected by consent or blockers | No | Yes, often significantly |
| Data retention in interface | 16 months | Depends on product settings |
Clicks and organic sessions diverge because of consent banners, ad blockers, redirects and session timeouts. A gap of 10 to 30 percent is common and is not, by itself, a tracking error.
Common mistakes when using Search Console
Most errors come from reading aggregate data as if it were precise or from treating every report warning as urgent.
- Treating every excluded URL as a problem: many URLs are correctly excluded, such as redirects, canonicalized duplicates and filtered parameters.
- Requesting indexing repeatedly: it does not speed up a page that Google has chosen not to index for quality reasons.
- Comparing short periods: weekday patterns and the roughly two-day reporting delay distort comparisons shorter than four weeks.
- Ignoring user permissions: former agencies and employees often keep owner access long after they leave.
Put simply
Google Search Console is a dashboard Google gives website owners for free. It shows which searches made your site appear, how many people saw it and how many clicked.
It also works like a service report from a mechanic. It points out pages Google could not add to its index, slow pages and security problems, so you know what to fix before it costs you visitors.
In practice
An online retailer of outdoor gear notices that organic revenue has fallen for six weeks. The Performance report shows that clicks dropped by about 25 percent while impressions stayed almost flat, and filtering by page reveals that the decline is concentrated on category pages.
The Page indexing report then shows roughly 3,400 URLs, including many core category pages, moved to the status in which Google chose a different canonical than the one declared, starting the week a new faceted navigation went live. URL Inspection confirms the cause: every filtered parameter URL carries a self-referencing canonical tag, so Google treats the filtered versions as the main pages.
The team points the canonical tags of filtered URLs to their main category, blocks crawl-wasting filter combinations and resubmits the sitemap. Within five weeks most category pages return to the index and clicks recover to their earlier level, a fix found entirely through first-party Search Console data.