What is Google Search Console? A plain guide for site owners

Google Search Console is a free service from Google that shows how your website is doing in Google Search: which searches show your pages, how often people click, which pages Google has indexed, and what went wrong when it tried to crawl the rest. Your site can appear in Google without it, but without it you would be guessing at every one of those answers.

What does Search Console do?

Google's own summary of the service (About Search Console) lists five jobs:

• confirm that Google can find and crawl your site;
• fix indexing problems and ask Google to re-index new or updated content;
• show your Google Search traffic data;
• alert you when Google runs into indexing, spam or other issues on your site;
• show which sites link to yours.

Google also says who it is for: business owners who should at least know it exists, SEO specialists and marketers who watch traffic and rankings, site administrators who look after servers and security, and developers who fix markup problems. In practice the same property is usually shared between several of those people, which is why permissions matter (more on that below).

The reports you will open most

Search Console has many reports, but most weeks you will only need a handful. Each one answers a single question.

The Core Web Vitals report is built from real-world usage data and groups similar URLs as Poor, Need improvement or Good on three metrics: LCP, INP and CLS (Core Web Vitals report). The rest of this track concentrates on the first three reports, because they cover the questions you will ask most often.

What the Performance report shows, and where its data stops

The Performance report is the one you will live in. It reports four metrics (clicks, impressions, CTR and average position) and lets you slice them by six dimensions: queries, pages, countries, devices, search appearance and dates. You can switch the search type between web, image, video and news results; Discover and Google News have reports of their own.

Its data comes with limits that explain most of the "why don't these numbers match?" questions people ask:

• History. Search Console keeps the last 16 months of performance data, so anything older is gone unless you exported it.
• Delay. Google says collected data is usually available in 2 to 3 days, and the newest day can be preliminary and still change for a few hours (Troubleshooting data discrepancies).
• Time zone. Days are counted in Pacific Time, which is why a day in Search Console will not line up exactly with a day in your analytics.
• Rows. The table shows at most 1,000 rows. Larger exports need the Search Console API, the Looker Studio connector, or the daily bulk export to BigQuery.
• Rare searches. Queries searched very few times are left out of the table to protect privacy, although they still count in the chart totals unless you filter by query.
• Two ways of counting. The chart counts your site once per search; the Pages table counts each page. Totals can differ for that reason alone.

Two newer features make the report easier to read. The branded queries filter, announced in November 2025 and available to all eligible sites since March 2026, splits the data into searches that name your brand or its products and everything else; Google classifies them with an AI-assisted system, so the odd query can land on the wrong side (Google's announcement). Annotations let you pin a note of up to 120 characters to a date on the chart, so a site release or a migration is visible next to the line it affected.

Domain property or URL-prefix property?

When you add a site you choose one of two property types (Add a website property):

• A Domain property covers the whole domain: every subdomain (www, m, shop and so on) and every protocol. It can only be verified with a DNS record.
• A URL-prefix property covers only URLs that begin with the exact prefix you enter, protocol included. https://example.com/blog/ would not include http:// URLs or shop.example.com. It offers several verification methods.

If you can edit your DNS, start with a Domain property: it is the only view that cannot miss traffic going to a subdomain or a leftover http:// address. Add URL-prefix properties on top for sections you want to report on separately or hand to another team, such as a blog folder or a help-centre subdomain. One account can hold up to 1,000 properties. Data starts to appear within a few days, and Google collects it from the moment anyone adds the property, even before it is verified. The FAQ on Domain vs URL-prefix properties covers the edge cases.

What Search Console cannot tell you

Knowing the gaps saves you from asking the tool questions it was never built to answer.

• What happens after the click. Search Console stops at the click. Engagement, sign-ups and sales live in GA4 (GA4 in AutoPSEO).
• Other search engines. Bing has its own console, Bing Webmaster Tools (Bing in AutoPSEO).
• Searches you do not appear for. Search volume and keyword ideas outside your current visibility come from keyword research tools.
• One exact ranking. Position is an average over many searches, and results vary by location, language and device, so your own search is not a measurement.
• Anything older than 16 months, and every rare query.

Who can see your data

Search Console has several permission levels (Permissions in Search Console). A verified owner proved ownership with a verification token and has full control, including adding and removing users. A delegated owner was granted ownership by a verified owner and has the same rights. A full user sees all data and can take some actions; a restricted user has view rights on most data. When an agency or freelancer needs access, a full or restricted user is usually enough, and it keeps ownership with you. See owner vs user for the details.

Your first half hour with Search Console

1. Add a Domain property and verify it with the DNS record Google gives you (verification guide).
2. Submit your sitemap in the Sitemaps report, or list it in robots.txt with a Sitemap: line.
3. Wait a few days for data to arrive.
4. Open Page indexing and check that the pages that matter to your business are indexed. Not every URL needs to be: Google says not to expect every URL on a site to be indexed, only the key pages.
5. Open Performance, set the date range to three months, and note the ten queries and ten pages with the most clicks. That list is your baseline.
6. Add an annotation the next time you change something on the site, so you can see later whether it mattered.

How AutoPSEO builds on Search Console

AutoPSEO reads your Search Console data through a Google sign-in with read-only access; a fuller permission is only requested if you want to submit or delete sitemaps from the app (Connecting Search Console). From the same data it builds the reports this track refers to, such as content decay, cannibalisation, CTR benchmarks and striking-distance keywords, without the 1,000-row ceiling of the Search Console table.

The same numbers drive the content engine. Each day it reads the last 28 days of searches by page to find questions your site already appears for but has no page about, and each week it compares the last 28 days with the 28 before to find its own articles that are losing clicks. The content engine overview explains both. If you would rather ask questions in Claude or ChatGPT, the MCP server puts the same data behind your assistant.