Google Search Console is a free Google service that shows how the search engine sees your website: which queries bring people to it, which pages made it into the index and which did not, and what exactly is getting in the way. To get real value from it you need three things: verify ownership, open two reports once a week (Performance and Page indexing), and read the numbers correctly, because there are a few traps. Below we walk through every section of the interface in business-owner language and finish with a six-point weekly checklist.

Analytics counts what happened after the click: how many people arrived, what they did, whether they bought. Search Console shows what happened before the click: how many times your site appeared in results, at which position and for which query. It is the only source of search query data that comes straight from Google rather than from a third-party estimate. It is also where the messages about manual penalties, security problems and mass indexing errors land. The service is free, and signing up at search.google.com/search-console takes a few minutes.
Google has to make sure the site is yours. The method depends on what you have access to. At Query we recommend adding a Domain property through DNS: it covers every subdomain, http and https at once, and it survives a redesign.
| Method | What you need | When it fits |
|---|---|---|
| DNS record | TXT record at the registrar | Main option: all subdomains and protocols |
| HTML file | File in the site root | File access, no DNS access |
| HTML tag | meta in the homepage head | CMS with a header code field |
| Google Analytics | "Edit" rights in GA | Analytics already installed |
| Google Tag Manager | "Publish" rights in GTM | Tags managed via GTM |
With the file and tag options, verification only covers one specific prefix, say https://example.com/. If part of your traffic lands on www or on http, those addresses will not show up in the reports. After verification the data starts from zero, there is no history from before you connected, so it pays to connect on day one of a site's life.
This is the main report and the one you open first. The four metrics at the top mean the following:
The power of the report is in its filters. The Queries tab answers "which words do people use to find us", the Pages tab answers "which pages earn the traffic". Click a specific page in the list and the query table rebuilds for that page alone, which shows exactly what a product page or an article ranks for. A "Query contains" filter with your brand name separates branded traffic from generic search, and the Compare toggle puts two periods side by side. The most useful combination for a weekly review is a page filter plus a comparison of the last 28 days against the previous 28.

The report splits every address Google knows about into two groups: indexed and not indexed. The mere fact that some pages are out of the index is not a problem: pagination, filter pages and service URLs should not be there anyway. The problem is when pages that make money end up in the "not indexed" list. The most common reasons and what they mean:
Clicking a reason opens the list of specific URLs, and the Validate fix button asks Google to re-check them after you make changes. A large share of these errors gets closed during technical SEO optimization, when the site is cleaned of duplicates and the indexing rules are set properly.
The Experience section shows whether the site meets three speed and stability metrics based on real visitor data: LCP, INP and CLS. What matters here is not the raw numbers but the groups of "poor" mobile URLs: if a category or product page template falls into one, hundreds of pages suffer at once. We explained what the metrics mean and how to fix them in a separate article on Core Web Vitals.
This report shows which sites link to yours, to which pages and with what anchor text. The list is incomplete compared with paid tools, but it comes straight from Google. Checking it once a month is enough: a sudden jump in linking domains from odd sites deserves attention, and your most-linked pages hint at which content is worth developing.
The search bar at the top of the interface accepts any address on your site and tells you whether it is indexed, when Google last crawled it, which canonical version it chose and whether the page passes the mobile usability check. The Test live URL button checks the page right now, and Request indexing puts it in the queue. This works for new or updated pages, but it does not perform miracles: if Google has already rejected a page as low value, asking again changes nothing.
Submit your sitemap.xml in the Sitemaps section. Once added, Search Console shows how many URLs it read and whether there were errors. The gap between the number of addresses in the sitemap and the number of indexed pages is a useful metric in its own right: if the map lists 5,000 URLs and the index holds 900, something is wrong with the site.
One session of 15-20 minutes. Doing it more often makes little sense, because the data updates with a delay and day after day you will be looking at the same chart.
| Step | Where to look | Signal |
|---|---|---|
| 1. Clicks and impressions, 7 days | Performance, compare | Drop beyond seasonal swings |
| 2. New indexing errors | Page indexing | 404 or 5xx on pages with traffic |
| 3. High impressions, low CTR | Performance, Queries | Position 3-10, CTR below neighbours |
| 4. Lost positions | Performance, Pages | Minus 3 or more positions |
| 5. Messages and manual actions | Bell, Security | Any new notice |
| 6. Core Web Vitals | Experience | URL group moved to "needs improvement" |

Average position is not a position. If a site ranks 2nd for one query and 40th for another, Console shows 21. A single page can have position 1.3 in Ukraine and 45 worldwide. Look at position only for a specific query and country, otherwise the number means nothing.
A 2-3 day lag. Today's figures in Performance are incomplete, so the last few days on the chart always look like a slump. Compare periods that ended at least three days ago.
Impressions without clicks are not always bad. A query like "instagram login" that your blog accidentally ranks for will produce a million impressions and zero clicks. CTR in such cases says nothing about page quality.
The query total is smaller than the overall total. Console hides part of the rare and anonymized queries, so the query table covers only a portion of the clicks. That is normal.
Only 16 months of data. There is no longer history in the interface. If you need year-over-year trends, export the reports or set up the BigQuery export in advance.
The wrong property. Accounts often hold two properties: https://example.com/ and the domain. Their figures differ because the first one sees a single prefix only. Work with the Domain property.