In short
Google Search Console (GSC) is a free analysis and diagnostic tool from Google with which website operators can monitor how their pages appear in Google Search: which search queries bring clicks, which pages are indexed, where technical problems hinder crawling and whether manual actions have been taken against the website. It is the only source in which Google itself releases this data: every other SEO tool measures from the outside, Search Console measures at the source.
The tool launched in 2006 as "Google Webmaster Tools"; in 2015, Google renamed it Search Console, partly to signal that the target group had long since grown beyond classic webmasters: shop operators, marketing teams, developers and agencies all work with it. Use is free of charge and only requires a Google account and proof that you control the website in question. You get started at search.google.com/search-console.
What Google Search Console can do
Search Console bundles several reports that together give a complete picture of a website's organic presence. The most important at a glance:
| Report | What it shows | Typical use |
|---|---|---|
| Performance | Clicks, impressions, click-through rate and position per search query, page, country and device | Keyword and content analysis, measuring success |
| Page indexing | Which URLs are in the index, and why others are not | Checking index coverage, finding errors such as soft 404 or "noindex" |
| URL inspection | Status of a single URL from Google's point of view, including a live test | Debugging individual pages, requesting indexing again |
| Sitemaps | Submitted XML sitemaps and their processing status | Telling Google about new or changed URLs |
| Core Web Vitals | Loading performance and stability based on real user data (CrUX) | Narrowing down performance problems by page group |
| Links | External and internal linking, top linking sites and anchor texts | Backlink overview without a third-party tool |
| Manual actions & security | Penalties by the spam team, malware findings | The report that hopefully always stays empty |
The performance report in detail
The most used report is the performance view. It stores up to 16 months of data and answers the questions on which all SEO work depends: via which search queries do visitors arrive? Which pages rank for what, in which position, with which click-through rate? The dimensions can be combined and filtered, for example all search queries for a single category page, mobile only, Germany only. Important for managing expectations: the data is not complete. Google filters out very rare search queries for privacy reasons, the user interface shows a maximum of 1,000 rows per table, and the figures arrive with a delay of one to two days. Anyone who needs more depth gets the data via the Search Console API or the bulk export to BigQuery.
Property types and set-up
Before data flows, ownership of the website must be confirmed. There are two property types for this, and the difference between them is often underestimated in practice. The domain property covers all subdomains and protocol variants of a domain (i.e. http, https, www, non-www, subdomains) and is verified via a DNS record: the cleanest variant, because nothing slips through the net. The URL prefix property only covers exactly the specified path including protocol, and in return offers more verification methods: an HTML file on the server, a meta tag in the source code, a Google Analytics or Tag Manager snippet.
For online shops with international subdomains or a staging system, the domain property is almost always worthwhile. In addition, a URL prefix property can make sense for individual areas, for example to look at the blog separately. Access can be delegated in a granular way: owners, users with full access, users with restricted access, so the agency gets insight without anyone having to hand over the DNS verification.
Why Search Console is indispensable for online shops
For a shop, Search Console is less a reporting tool than an early warning system. Indexing problems show up here weeks before they become visible in revenue: a growing number of 404 errors after a deployment, soft 404 messages caused by emptied category pages, a "noindex" from the staging environment that accidentally went live; all of this appears first in the indexing reports, long before a ranking tool or the revenue curve raises the alarm.
Search Console shows its full weight during a shop migration. A real scenario from practice: a retailer moves from Magento to Shopware 6, the domain stays the same, the URL structures change. Before go-live, the existing property is used to complete the URL inventory: the performance report also shows ranking URLs that have long since ceased to be linked internally. On launch day, the new XML sitemap is submitted, plus temporarily a sitemap with the old URLs so that Google finds and processes the 301 redirects more quickly. In the weeks that follow, the team monitors the indexing reports for increases in 404s and soft 404s and compares in the performance report whether the new URLs take over the clicks of the old ones. If a domain change is also involved, two properties run in parallel (the old one shows the decline, the new one the build-up), and the move is additionally registered via Search Console's change of address tool. Without these instruments, a migration flies blind.
A typical working rhythm in day-to-day shop operations
What does working with Search Console look like in concrete terms when there is no migration on the agenda? A three-tier rhythm has proven itself. Weekly: a quick look at the performance curve and the indexing reports: are there kinks, new error types, conspicuous increases in 404s? Monthly: an analysis of search queries with high impressions and a weak click-through rate, because that is where pages rank but their snippet does not convince; often a better title or a more precise meta description is enough to get more clicks out of existing visibility. Quarterly: a comparison of the top pages with the business goals. Are the pages that bring margin ranking, or only the advice content? This routine costs a few hours a month and does not replace a specialised SEO tool, but it catches the problems that become expensive.
API and bulk export for larger set-ups
Above a certain shop size, the user interface reaches its limits. There are two ways out: the Search Console API delivers performance data programmatically and with far more than 1,000 rows, so that you can build your own dashboards, alerting workflows or regular exports to a data warehouse. Since 2023, there has also been the daily bulk export to Google BigQuery, which continuously writes the unfiltered performance data into your own database: the basis if a company wants to combine search data with revenue or merchandise management data. For a mid-sized shop with 5,000 products, this is rarely necessary; for platforms with six-figure URL inventories, it is the only way to reliable statements.
Limits and common misconceptions
As central as the tool is, its limits are just as clear. Search Console is not a web analytics tool: it ends with the click on the search result. What visitors do in the shop afterwards (conversions, revenue, abandonment) belongs in web analytics, not in GSC. Nor is it a lever for improving rankings directly: using it is not a ranking factor in itself, and requesting indexing via URL inspection only speeds up crawling, not assessment.
Three misconceptions are particularly persistent:
- "What GSC doesn't show doesn't exist." The data is filtered and capped. Long-tail queries with few impressions are partly missing, which is why the sum of the table rows is often smaller than the total shown.
- "Average position 8 means we're in 8th place." The position is an average across all impressions, devices and locations. A page that sometimes appears at 3 and sometimes at 13 reports an 8 that nobody has ever seen.
- "Once it's set up, nobody needs to look at it again." Google does send critical messages such as manual actions or security problems by email, but not creeping losses in indexing. A fixed weekly look at index coverage and the performance curve is part of the operating routine of every website that takes organic traffic seriously.
Finally, it is worth mentioning that the range of reports changes constantly: Google discontinued the mobile usability report in 2023, while reports on rich results, shopping features and the bulk export to BigQuery were added in the meantime. The documentation in the Search Console Help is accordingly the most reliable source for the current status.
Context: Search Console in the age of AI search
With AI Overviews and AI Mode, Google Search has changed noticeably since 2025, and Search Console only partly keeps up. Impressions and clicks from AI Overviews do flow into the performance report, but they are not shown there as a separate category; a separate evaluation of "classic search versus AI answer" is not possible with the built-in tools. This makes interpreting the curves more demanding: a stable number of impressions with a falling click-through rate can simply mean that your page is cited but the user finds their answer directly in the AI overview. Anyone who wants to assess the development of their organic channel has to take this shift into account instead of reading every drop in CTR as a ranking problem. Nothing changes about the basic function: an AI answer can also only cite what has been crawled and indexed, and that is exactly what Search Console makes visible.
Frequently asked questions about Google Search Console
What does Google Search Console cost?
Nothing. Search Console is completely free, without premium tiers or limits based on website size. All you need is a Google account and verification of ownership via a DNS record, HTML file, meta tag or an existing Analytics or Tag Manager set-up.
How does Search Console differ from Google Analytics?
Search Console shows what happens before the click: search queries, impressions, positions, indexing and crawling status. Google Analytics (or any web analytics tool) shows what happens after the click: behaviour, conversions, revenue. The two complement each other and do not replace one another.
How long does it take for data to appear in Search Console?
After initial verification, the first data usually arrives within a few days. In ongoing operation, performance data appears with a delay of around one to two days. Historical data from before the set-up is not available retrospectively, which is one reason to create the property early and not only when the first problem arises.
Which property should I create: domain or URL prefix?
If in doubt, the domain property. It covers all subdomains and protocol variants and prevents the classic measurement gap in which www and non-www traffic end up in separate properties. The URL prefix property is the right choice if there is no access to the DNS settings or if only a sub-area is to be looked at deliberately.
Does Search Console help directly with ranking?
No. It does not improve any ranking but makes visible what is holding it back: technical errors, missing indexing, weak click-through rates. The leverage comes from what you do with this information, not from the tool itself.