Technical SEO
Google Search Console Analysis Workflow
A practical workflow for using Search Console performance, indexing, URL inspection, sitemaps, and enhancement data to diagnose SEO opportunities and risks.
Google Search Console is the primary source for understanding how Google discovers, indexes, and surfaces a site in Search. It is not a full analytics platform, rank tracker, crawler, or CRM, but it gives essential evidence for SEO decisions.
Use Search Console to answer specific questions: which pages are eligible, which queries create impressions, where clicks changed, which page groups need attention, and whether Google sees technical or structured-data issues.
Main reports to use
| Report or Tool | Use It For |
|---|---|
| Performance | Clicks, impressions, CTR, average position, queries, pages, countries, devices, search appearance, and dates. |
| Generative AI performance | Impressions from supported generative AI features, grouped by page, country, device, and date where the report is available. |
| Page indexing | Whether Google can find and index pages, and why some pages are not indexed. |
| URL Inspection | Page-level indexing, canonical, crawl, and rendered-page checks for specific URLs. |
| Sitemaps | Whether submitted sitemap files are discovered and processed. |
| Enhancements | Structured data and experience reports where eligible. |
| Removals | Temporary hiding and safe-removal workflows when needed. |
The Performance report is best for demand and visibility patterns. Indexing and URL Inspection are best for eligibility and page-level diagnosis.
Generative AI performance and controls
Google is rolling out a separate Generative AI performance report to a subset of eligible properties. The report currently covers impressions from supported generative AI features in Google Search, including AI Overviews and AI Mode. It does not expose queries, clicks, click-through rate, citation position, or a separate total for each individual AI surface.
Use it to:
- Establish a baseline when the report first appears.
- Identify pages receiving generative AI impressions.
- Compare changes by date, country, and device.
- Connect page-level patterns to content updates, indexation, and conversion data.
Treat the report as provider-specific visibility evidence, not a complete AI citation tracker. An impression shows that a link to the site appeared in a supported generative experience; it does not explain why the page was selected or prove that one optimization caused the appearance.
Google is also testing a Search Console control that lets participating website owners decide whether their site can appear in and help ground generative AI Search features. The control is separate from rankings outside those generative features. Before changing it, document the business decision: opting out also gives up impressions and possible traffic from the affected experiences.
Performance analysis workflow
Start with the question before touching filters:
| Question | Filter or Dimension |
|---|---|
| Did organic visibility change? | Compare clicks and impressions by date. |
| Which pages changed? | Pages dimension. |
| Which queries changed? | Queries dimension. |
| Is the change market-specific? | Countries dimension. |
| Is the change device-specific? | Devices dimension. |
| Did click-through change while impressions stayed stable? | Compare CTR, title/meta changes, and SERP features. |
| Did rankings drop or demand drop? | Compare impressions and average position together. |
| Did a search appearance change? | Search appearance dimension where available. |
Do not interpret average position alone. It is useful context, but clicks, impressions, CTR, page role, and query type matter more.
Page-group analysis
Group pages by role before reporting:
- Homepage and brand pages.
- Service or product pages.
- Category or collection pages.
- Local pages.
- Guides and blog posts.
- Tools, templates, and calculators.
- Research assets.
- Archives, tags, filters, and other low-value templates.
Then compare each group:
| Signal | Meaning |
|---|---|
| Impressions up, clicks up | Visibility and traffic improved. |
| Impressions up, clicks flat | Snippet, SERP layout, intent, or ranking position may limit clicks. |
| Impressions down, clicks down | Demand, ranking, indexation, or page relevance may have weakened. |
| Impressions stable, CTR down | SERP feature changes, title/meta rewrites, or mismatched promise may matter. |
| Average position down, impressions down | Ranking or relevance loss is likely. |
Page-group reporting makes Search Console more useful than a single sitewide chart.
Query analysis
Separate query types:
| Query Type | What It Tells You |
|---|---|
| Brand | Entity demand, reputation, navigational visibility. |
| Non-brand commercial | Category and buying-stage visibility. |
| Informational | Topical reach and guide usefulness. |
| Local | Market and service-area relevance. |
| Comparison | Decision-stage demand and competitor framing. |
| Problem/diagnosis | Opportunity for troubleshooting content and tools. |
| Research/statistics | Opportunity for original data and citation assets. |
If brand demand falls, the issue may not be on-page SEO. If non-brand impressions fall for a page group, review rankings, competitors, intent fit, and indexing.
Indexing workflow
Use Page indexing for patterns and URL Inspection for examples.
| Finding | What To Check |
|---|---|
| Important page not indexed | URL Inspection, robots, noindex, canonical, internal links, sitemap, rendered content. |
| Duplicate without user-selected canonical | Whether the page should consolidate, redirect, or become unique. |
| Crawled or discovered but not indexed | Page quality, duplication, internal links, crawl focus, and demand. |
| Soft 404 | Whether the page has enough useful content or should return another status. |
| Redirected | Whether redirects are expected and sitemap/internal links use final URLs. |
| Blocked by robots | Whether blocking is intentional and safe. |
Not every URL should be indexed. The question is whether important pages are indexed and whether non-indexed pages are excluded for good reasons.
URL Inspection workflow
Inspect representative URLs, not every URL:
- Pick affected or important URLs.
- Check whether the URL is indexed.
- Compare user-declared canonical and Google-selected canonical.
- Review last crawl information and crawl permission.
- Test live URL when a recent fix shipped.
- Check rendered HTML or screenshot where rendering is relevant.
- Request indexing only after the page is fixed and important.
URL Inspection is for page-level evidence. It should support decisions made from page-group patterns.
Sitemaps and discovery
Use sitemaps to reinforce the canonical indexable set. A sitemap should not be a dump of every URL the site can produce.
Check:
- Sitemap files are submitted and processed.
- Sitemap URLs return
200. - Sitemap URLs are canonical and indexable.
- Removed or redirected URLs are not still listed.
- Important new pages appear in the correct sitemap.
- Low-value tags, filters, parameters, or internal search URLs are excluded.
If important pages are not found by Google, strengthen internal links first. Sitemaps help discovery, but they do not replace site architecture.
Combining GSC with other data
Search Console answers search visibility questions. Combine it with:
| Source | Adds |
|---|---|
| Analytics | Sessions, engagement, conversions, landing-page behavior. |
| Rank tracking | More controlled query and location monitoring. |
| Crawls | Template-level technical and internal-link patterns. |
| Server logs | Bot crawl behavior and response patterns. |
| CRM or lead data | Lead quality and revenue context. |
| Google Business Profile | Local actions and Maps visibility context. |
SEO decisions improve when Search Console is connected to technical evidence and business outcomes.
Common mistakes
- Treating average position as the only KPI.
- Comparing mismatched date ranges or ignoring seasonality.
- Reporting total site clicks when only one page group changed.
- Assuming all non-indexed URLs are problems.
- Requesting indexing before fixing page quality or technical issues.
- Forgetting that Search Console and analytics count different things.
- Ignoring query intent and page type when judging performance.
Practical monthly review
Each month, review:
- Top gaining and declining page groups.
- Top gaining and declining query groups.
- Important pages that are not indexed.
- New indexing issues by template.
- Sitemap coverage and unexpected URLs.
- Structured data issues on important templates.
- Pages with high impressions and low CTR.
- Pages with declining impressions and clear business value.
- Generative AI impression trends and cited pages where the report is available.
- The current generative AI participation setting where the control is available.
- Changes shipped during the period.
- Next actions by owner and priority.
For traffic loss, use Traffic Drop Diagnosis. For broader audit sequencing, use the SEO Audit Operating System.