LaunchRanked

Search Console for founders: the 5 reports that matter

Google Search Console has dozens of screens. Founders need five: Performance, Page indexing, URL Inspection, Sitemaps and Links. What each tells you.

Published 6 min readBy the LaunchRanked team

  • search console
  • seo
  • indexing

Search Console is free, it comes straight from Google, and most founders open it twice: once to verify, once when traffic drops. In between, it sits there with the answers to most of their SEO questions.

It's also cluttered. There are reports for things most startups will never need. So here are the five we actually use, what each tells you, and what to do with it. We ran this routine on Versely, our own product, every week.

Short answer: Five reports cover almost everything a founder needs: Performance (what people search and click), Page indexing (what Google keeps or drops), URL Inspection (how Google sees one page), Sitemaps (whether Google can read your list of URLs), and Links (who links to you and how you link internally).

1. Performance: what people search, see and click

This is the report that matters most. It shows how your site does in Google Search.

Google's definitions are worth knowing exactly:

  • Clicks: "The number of times a user clicked your site from Google Search results."
  • Impressions: "How many times your site appeared in Search results."
  • CTR: "The click count divided by the impression count."
  • Average position: "The average position of the topmost result from your site."

The default view is the last three months. Newer data "can be preliminary," so don't react to the last day or two.

How founders should use it

Sort pages by impressions, then look at CTR. A page with thousands of impressions and a CTR under 1% is showing up and not getting chosen. That's usually a title problem, and it's the cheapest win you'll find. On Versely, rewriting titles and snippets on pages already on page 1–2 produced our biggest gains. We explain the method in title tags that get clicked.

Filter by page, then open the Queries tab. You'll see the actual words people typed to find that page. They're often different from what you targeted. Use their words.

Compare date ranges after a change. Change a title, note the date, then compare 28 days before and after. Keep a log. Without one, you'll forget what you changed and why.

Read average position carefully. It's an average of your topmost result across all queries. A page ranking #3 for one query and #40 for another shows an average that describes neither. Versely's average position over the last three months is 11.8, which tells you a lot of it sits right on the edge of page one, and nothing about any single query.

One more thing: clicks from AI Overviews and AI Mode are counted here too. Google's AI features documentation says they're "included in the overall search traffic in Search Console" under the Web search type.

2. Page indexing: what Google keeps and what it drops

The Page indexing report shows which pages Google can find and index, and why the rest aren't indexed.

Start with Google's own reality check: not every page should be indexed. The goal is to "be sure that the key pages on your site are indexed," not to reach 100%.

The statuses founders will see most:

  • Crawled – currently not indexed. Google fetched the page and chose not to index it. No need to resubmit. Usually it means the page isn't different or useful enough yet.
  • Discovered – currently not indexed. Google knows the URL but hasn't crawled it, typically because crawling then "was expected to overload the site," so it rescheduled.
  • Duplicate without user-selected canonical. Google found near-identical pages, picked one itself, and won't show this one.
  • Excluded by 'noindex' tag. Fine, if you meant it. A disaster if staging settings leaked into production.
  • Page with redirect and Soft 404. Usually cleanup items, not emergencies.

How founders should use it

Check the trend weekly, not the total. A rising "Crawled – currently not indexed" count is your early warning that you're publishing faster than Google wants to index, or publishing pages too similar to each other. We learned this at scale when we published 2,500 posts in a month.

When you fix a real issue, use Validate fix. Google rechecks sample pages and then recrawls affected URLs "over several days or weeks." Be patient with it.

If you want the vocabulary, our glossary covers indexing and crawled – currently not indexed.

3. URL Inspection: how Google sees one page

URL Inspection answers "what does Google know about this exact URL?" It shows whether the page is indexed, which canonical Google chose, when it was last crawled, and any structured data it found.

Test live URL fetches the page now, which is how you confirm a fix before waiting for a recrawl. Look at the rendered HTML and screenshot. If your content loads through JavaScript and isn't in the render, Google may not be seeing it.

Request indexing is useful for one important page, like a new pricing page. Google is clear about its limits: "Submitting a request does not guarantee that the page will appear in the Google Index," there's a daily quota, and for many pages you should submit a sitemap instead. Hammering the button for every blog post does nothing a sitemap doesn't.

How founders should use it

Inspect your five most important URLs after any big deploy: homepage, pricing, and your top landing pages. Check that the canonical Google selected is the one you declared. When they differ, Google is telling you it disagrees about which page is the real one.

4. Sitemaps: whether Google can read your list

The Sitemaps report shows each sitemap you've submitted and one of three statuses: Success, Couldn't fetch, or errors. It also shows "Discovered pages," the number of URLs Google parsed from it.

It's a small report, and it breaks quietly. A deploy changes a route, the sitemap starts returning an error, and Google keeps crawling from its old copy until you notice.

How founders should use it

  • Submit a sitemap index if you have more than one sitemap, so a single entry covers everything.
  • Check that "Discovered pages" roughly matches the number of pages you expect. A big gap means URLs are missing, or you're including URLs that shouldn't be there.
  • Keep lastmod honest. Google's sitemap guide says it uses lastmod if it's "consistently and verifiably" accurate.

Run your sitemap through our free sitemap checker to catch URLs that redirect or error before Google does.

The Links report has two halves. External links show your top linked pages, top linking sites and top linking text. Internal links show which of your pages you link to most.

Know its limits. Google says it "isn't a comprehensive list of every link," it shows a sample, tables stop at 1,000 rows, and it "doesn't specify if a link is marked as nofollow." It won't replace a backlink tool for counting. It's still useful for patterns.

How founders should use it

External: confirm that your launches and directory listings show up over time, and see which pages attract links on their own. Those pages are telling you what people find worth citing.

Internal: this half is underrated. Sort by internal links and look at the bottom. If an important page has only one or two internal links, Google gets the message that it isn't important. Fix that with a simple internal linking system.

Worth a glance: the Generative AI performance report

Since August 31, 2026, Google has rolled out a Generative AI performance report to all sites with enough data. It shows impressions from AI Overviews and AI Mode by page, country, device and date. Two results from the same site in one AI response count as a single impression.

It shows no clicks and no queries, so it can't tell you what drove an appearance. It does tell you which pages Google's AI features lean on. We cover what to do with that in AI Overviews and AI Mode for founders.

A 30-minute weekly routine

  1. Page indexing (5 min): any new error types? Is "Crawled – currently not indexed" rising?
  2. Performance by page (10 min): find two pages with high impressions and low CTR. Queue title rewrites.
  3. Performance by query (5 min): note queries you rank for but don't answer well.
  4. Sitemaps (2 min): still Success? Discovered pages roughly right?
  5. URL Inspection (5 min): check anything you changed this week.
  6. Links (3 min): anything new? Any important page with too few internal links?

That's the loop. It's also what we're automating in Autopilot, which reads Search Console and rewrites titles on pages that already rank. Until then, a calendar reminder and this list will do most of the work.

Frequently asked questions

How often should I check Google Search Console?

Once a week is enough for most early-stage sites. Look at Page indexing for new problems and Performance for pages with impressions but few clicks. Daily checking mostly shows noise, especially on a new domain.

Why does Search Console show fewer backlinks than SEO tools?

Google says the Links report shows a sample of links, not every link, and tables are limited to 1,000 rows. It also doesn't say whether a link is nofollow. Use it to spot patterns, not to count.

Does Search Console show traffic from AI Overviews?

Clicks from AI Overviews and AI Mode are included in the regular Performance report under the Web search type. Since August 31, 2026, the separate Generative AI performance report also shows impressions from those features, but not clicks.