Google Search Console is the only tool showing how Google actually sees a website: which pages are indexed, which queries they appear for and where technical problems exist. Many teams only open it when something goes wrong. This article describes which reports matter for SaaS websites and how to derive a weekly work list from them.
The performance report
The performance report shows clicks, impressions, click-through rate and average position, filterable by query, page, country, device and period. The data goes back 16 months. Two views are most valuable for work: pages with many impressions and a low click-through rate, where title and description do not convince, and queries in positions five to fifteen, where a content improvement has the greatest effect. Regular expressions let you group queries, for example separating brand searches from generic ones. Some queries are not shown for privacy reasons.
Page indexing
The page indexing report shows which URLs are in the index and why others are not. For SaaS websites with many pages it is the most important technical report. “Crawled – currently not indexed” is usually a quality signal, “Discovered – currently not indexed” a sign of too many URLs or weak internal linking, and duplicates with a different canonical show where Google decides differently than planned. The background is in the glossary entry on indexing.
URL inspection and sitemaps
URL inspection shows for an individual page whether it is indexed, which canonical Google chose and what the rendered page looks like. After important changes you can request indexing here. In the sitemaps report you submit the sitemap and see how many submitted URLs are indexed. A sitemap should contain only indexable, canonical URLs; noindex pages or redirects in it generate errors and dilute the signal.
Core Web Vitals and structured data
The Core Web Vitals report shows field data from real users, grouped by similar pages, separately for mobile and desktop. It reacts slowly because it relies on several weeks of data; after an improvement it takes time to show. More in our article on Core Web Vitals on Next.js and Vercel. The structured data reports show whether markup such as FAQ, breadcrumbs or articles is recognised as valid; errors there are usually fixed quickly.
What Search Console does not show
Citations in AI answers such as AI Overviews are not reported separately; they flow into the normal figures. Search Console does not see conversions either. The full picture therefore needs a connection to your own analytics and a deliberate check of whether your brand appears in AI answers on your core topics.
A routine that produces work
- Weekly: check page indexing for new errors, compare the last seven days’ performance with the previous week, investigate notable drops of individual pages.
- Monthly: select pages with high impressions and low click-through rate and rework title and description; map queries in positions five to fifteen to the right pages and extend content deliberately.
- After every major release: resubmit the sitemap, inspect important new URLs and request indexing.
How we use Search Console
On innopulse.io, Search Console data drives the order of work. One example: articles that did not meet our quality standard were set to noindex, and we are rewriting them in order of their impressions so that the pages for which Google already sees demand return to the index first. For larger sites, exporting the data to a data warehouse also pays off, to cover longer periods and custom analyses. We offer setting up such a structure in our technical SEO audit; the content side is covered in our article on topical authority.