How to Read Google Search Console as a Founder: The Reports That Matter and the Ones You Can Skip

Which Search Console reports should a founder read?

A founder should read four reports on a schedule: Performance (Search results), page indexing, URL Inspection and Sitemaps, plus the newer Generative AI performance reports once the basics are in place. The rest are either alert-driven, as Security issues and Manual actions are, or only useful in specific situations.

• Check Search Console about once a month and after significant site changes, the cadence Google's own documentation suggests.
• Read the Performance report for clicks, impressions, click-through rate and average position, and treat it as a list of pages and queries to improve.
• Use the page indexing report and URL Inspection to confirm that the pages you care about are in Google's index.
• Submit a sitemap once, then look at the Sitemaps report only if something breaks.
• Security issues and Manual actions are alert-driven: Google says that if your dashboard shows nothing, you do not need to open them.

Search Console tells you what happened on Google. It does not tell you what to do about it, so every section below ends with the decision that report supports.

What decision does each Search Console report support?

Each report answers one question and supports one decision, and the table below puts them side by side. Kanso put it together from Google's Search Central and Search Console Help pages, using four criteria: the question the report answers, what to read in it, the decision it supports and how often the sources say to look.

This table is not a set of annotated screenshots. The research behind this page included no captures from Kanso's own property, so none are shown, and report names and layouts may differ from what you see in your account.

How do you set up Search Console and choose a property type?

Setup needs a Google account and proof that you own the site, and the main choice is between a Domain property and a URL prefix property. Google's getting-started guide says a Google account is the only requirement, and that ownership must be verified because Search Console shows information only site owners should see.

Per Semrush's guide, a Domain property covers every protocol, subdomain and path under the domain and can only be verified through your DNS provider. A URL prefix property covers one address, such as a blog subfolder, and accepts several verification methods: an HTML file, an HTML tag, Google Analytics, Google Tag Manager or the domain name provider. Yoast adds that the Domain option only works with DNS verification.

Semrush says DNS changes can take anywhere from a few minutes to 48 hours, so a failed first verification is not necessarily a mistake. Our suggestion: choose Domain if you control your DNS, because it gives the broadest view, and fall back to a URL prefix with the HTML tag method if you only control the site's code.

Access is a founder decision too. Semrush lists verified and delegated owners with full control, full users who can view all data and take certain actions, restricted users who can view most data, and associates who cannot open Search Console directly. A contractor who only needs to read reports does not need to be an owner.

How do you read the Performance report?

Read the Performance report by choosing metrics, then a dimension, then a date range, and treat the table beneath the chart as the part you act on. Google's Performance report help page says the default view shows clicks and impressions for the past three months, and that you can switch the metrics and the grouping.

The grouping is called a dimension: Queries, Pages, Countries, Devices, Search appearance or Dates. A search type filter separates web (text-based or multimodal), image, video and news traffic. Time granularity can be hourly, daily, weekly or monthly, and Google says weekly and monthly smooth out fluctuations such as weekends and holidays.

A useful move, described by Yoast, is to click a query so it becomes a filter, then open the Pages dimension to see which of your pages ranks for it. If the page that appears is not the one you want ranking, that is your decision: improve the right page or link to it from relevant pages.

Semrush lists three patterns to look for: pages with strong rankings but low click-through rates, which may need clearer titles and descriptions; important queries that are missing altogether; and high positions with low impressions or clicks. Yoast adds a caution that rewriting titles will not move the needle much for a page that is not yet on the first page of results.

Google also provides separate performance reports for News and Discover if your site is eligible. Our suggestion is to ignore them until the Search results report is a habit.

What do clicks, impressions, CTR and average position mean?

The four Performance metrics are clicks, impressions, click-through rate and average position, and Google defines each on its Performance report help page. The table repeats those definitions next to the caution a founder most often needs.

CTR is the one metric you can calculate by hand, which makes it a good check on your reading. As a hypothetical example with made-up numbers, 30 clicks from 1,500 impressions gives 30 ÷ 1,500 = 0.02, or a 2% CTR.

Average position needs the most care. Google says it is the average position of the topmost result from your site, and that in the chart it covers your whole site while in the table it covers the specific URL or grouping in that row. Open a single query before trusting a page-level position. Google's help page on impressions, position and clicks explains exactly how each is counted.

Is Google Search Console accurate?

Search Console is Google's own record of how your site appeared in Search, but its numbers carry documented limits that explain most of the confusion founders have with it. The limits below come from Google's Performance report help page.

• Preliminary data. The newest data can still be collecting and may change within hours. A dotted line on the graph marks it.
• Chart versus table totals. Data grouped by queries, countries, devices or dates is aggregated by property, while data grouped by pages or search appearance is aggregated by page. Totals can therefore differ between the chart and the table.
• What you see yourself. A query may appear in your list even though your site does not show when you run it, because results depend on the time, place, device and recent history of the searcher.
• Exports. Values shown as ~ or - in the report become zeros in a downloaded file.

The practical rule is to compare like with like: the same dimension, the same date range and the same search type each month. Our suggestion is to use Search Console for trends and decisions rather than for exact totals, and not to expect its clicks to match the visits counted by another tool.

What does the page indexing report tell you?

The page indexing report tells you which pages Google has indexed or tried to index, and which have errors, warnings or exclusions. Google's Search Central page on getting started with Search Console calls it the Index Coverage report, while Google's other help pages call it the Page Indexing report, so expect both names.

The report matters because indexing is a stage a page can fail. Google's guide to how Search works describes three stages (crawling, indexing and serving results), says not all pages make it through each one, and says Google does not guarantee that it will crawl, index or serve your page, even if the page follows Google Search Essentials.

The decision it supports is which indexing problem to fix first. Google's start page suggests reviewing the list and trying to fix page errors and warnings, and its guidance for developers adds that the report shows impressions for affected pages, which helps you judge how an issue might have affected traffic.

A simple founder test: count the pages you would be glad to see ranked, then compare that number with the indexed count. Kanso's weekly growth checklist includes a table of the common not-indexed statuses and a usual response to each.

When should you use the URL Inspection tool?

Use URL Inspection when one specific page is not behaving as expected, such as a new page that does not appear in Google. Google's Search Console product page says the tool provides detailed crawl, index and serving information about a page directly from the Google index.

Google's Search Central documentation adds the actions available: see the current index status of a page, test a live URL, ask Google to crawl a specific page, and view the resources the page loaded. Google's role guidance also says you can open it by drilling into a single URL from a report and clicking Inspect.

The decision is binary: fix the page, or ask Google to look at it again. Asking for a crawl is a request and not a guarantee, because Google says it does not promise to index any page. Fix what the inspection shows first, then request the crawl.

Do you need to submit a sitemap?

You do not need to, but submitting one is a low-cost step for a new site. Google's Search Central documentation says pages can be discovered without a sitemap, and that submitting one through Search Console might speed up discovery and lets you monitor information about it.

Google's guide to how Search works lists three ways a URL gets discovered: Google already visited it, Google followed a link from a known page, or you submitted a sitemap. A new site with few inbound links has fewer of the first two, which is why a sitemap helps most early on. That reasoning is our suggestion, not Google's statement.

To submit, Semrush describes opening the Sitemaps report, entering your XML sitemap URL and clicking Submit. Once Google processes it, Search Console shows a status saying whether the sitemap was submitted successfully or has errors. After that, revisit the report only when pages stop being picked up.

Where does the Generative AI performance report fit?

The Generative AI performance report is a separate report that Google introduced in June 2026, and it is where AI-feature data lives instead of the standard Performance report. Google announced it in the Search Central Blog post Introducing Search Generative AI performance reports in Search Console.

The research behind this page contains the post's title and date but not its text, so this article does not describe the report's metrics, surfaces or availability. Read Google's announcement for those. The AI search section of the weekly growth checklist summarizes the rollout from that post.

One earlier statement is worth reading with that in mind. Semrush's 2026 guide says the Performance report does not report AI Overviews or AI Mode metrics separately, which is the gap a separate report addresses. Google's own documentation, not a third-party guide, is the place to confirm what the new report covers today.

Which Search Console reports can a founder skip?

A founder can defer most reports outside the core four until a specific event calls for them. In each case below, "skip" means do not make it part of the monthly routine, not that it is useless.

• Security issues and Manual actions. Google's getting-started guide lists both as critical but says that if the property dashboard shows no issue, you do not need to open the report, and you will receive an email if one occurs. Make sure that email reaches someone who reads it.
• Removals. Google's Search Central page describes it as a way to temporarily hide pages from Search, with a successful request lasting only about six months.
• Change of Address. Use it only if you move the site from one domain or subdomain to another.
• Rich result reports. They show what structured data Google could or could not read. They matter only after you have added structured data.
• Core Web Vitals and usability reports. Google marks the usability group as optional in its getting-started guide, and describes Core Web Vitals as field data from real-world usage.
• Links. Yoast describes it as an overview of internal and external links. Our suggestion is to leave it until you start internal-linking work.

Google also says that if you run a small site on a hosted platform such as Blogger, Wix or Squarespace and have little time, you might not need Search Console at all. It still recommends a short list of reading about search, which it says takes under half an hour. For hosted sites, Google points to the Insights report for a simplified overview of search performance.

What does a monthly Search Console routine look like?

A monthly routine is eight short steps that end with one recorded decision. The time boxes add up to about 30 minutes and are Kanso's suggestion; Google specifies only the monthly cadence.

1. Overview (2 minutes). Look for security or manual-action flags and any email alerts you received.
2. Performance chart (5 minutes). Keep the default three-month range, switch to weekly granularity, and note whether clicks and impressions are rising, flat or falling.
3. Queries table (5 minutes). Sort by impressions and list the top queries that are not your brand name.
4. One query, one page (4 minutes). Click a query to filter by it, open the Pages dimension and check that the right page ranks.
5. Striking distance (4 minutes). Filter by average position and list queries just below page one, using one definition consistently.
6. Page indexing (4 minutes). Compare the indexed count with the pages you want ranked and read any new errors.
7. URL Inspection and Sitemaps (4 minutes). Inspect the one page you changed or launched this month, and check the sitemap status.
8. Decide (2 minutes). Write down one fix and the number you will check next month.

Striking distance has no single definition. Semrush uses positions 4 to 15, while Kanso's weekly growth checklist uses positions 11 to 20 for queries just below the first page. Choose one and keep it, so month-to-month comparisons mean something.

What is documented, and what is our analysis?

The facts below are documented in the named sources, and the interpretations are Kanso's own. Keeping them apart lets you check each claim against its source.

• Documented: Google suggests checking Search Console about once a month, or when you change the site (Google Search Central).
• Documented: the Performance report defaults to three months, and defines clicks, impressions, CTR and average position (Search Console Help).
• Documented: chart and table totals can differ, and the newest data can be preliminary (Search Console Help).
• Documented: Security issues and Manual actions do not need checking if the dashboard shows nothing (Search Console Help).
• Documented: Google does not guarantee that it will crawl, index or serve a page (Google Search Central).
• Secondary source only: 16 months of performance data (Yoast); striking distance as positions 4 to 15 and DNS verification taking up to 48 hours (Semrush).

• Analysis: the four reports to read on a schedule are Performance, page indexing, URL Inspection and Sitemaps.
• Analysis: the decision column in the table, and the labels "skip" and "later".
• Analysis: the time boxes in the monthly routine, and the advice to choose Domain over URL prefix when you control DNS.
• Not covered: screenshots from Kanso's own property, and the details of the Generative AI performance report.

Where does Kanso fit?

Kanso's SEO Agent is a natural next step once the monthly routine is a habit, because it audits your site and Search Console data and turns what it finds into recommendations and tracked tasks for your approval. It works from the same kind of data covered in this guide.

It does not replace reading the reports yourself, and it does not promise rankings. The recommendations are yours to approve or reject.

Google Search Console for beginners: frequently asked questions

Sources

• How To Use Search Console, Google Search Central
• Performance report (Search results): Overview and basic setup, Search Console Help
• Getting started with Search Console, Search Console Help
• Get started with Search Console, Search Console Help
• In-depth guide to how Google Search works, Google Search Central
• Google Search Console, Google product page
• What are impressions, position, and clicks?, Search Console Help
• Introducing Search Generative AI performance reports in Search Console, Google Search Central Blog
• How to use Google Search Console: a beginner's guide, Yoast
• Google Search Console: the ultimate guide for 2026, Semrush