GSC knowledge base
GSC search performance tutorial and troubleshooting guide
Locate metric changes to queries, pages, countries, and devices rather than only looking at site-wide averages. Choose a tutorial by the specific problem and check operations, limitations, and verification results item by item.
Locate the change before deciding what to rewrite
What to prepare
Record complete comparison periods, search type, target country and the affected URL. Keep clicks, impressions, CTR and position separate.
| Your situation | First action | Read next |
|---|---|---|
| Clicks dropped | Locate the first date and the affected pages, then separate demand, ranking and technical evidence. | Search traffic drop: locate by scope and time |
| Impressions grew but clicks did not | Check query composition and position before comparing the title with the actual answer. | High impressions, low clicks: first distinguish four types of causes |
| The site average hides market differences | Compare the same country and device with a consistent window before drawing a conclusion. | Country and device: find the users actually affected |
| You need to group related queries | Test your regex against included and excluded examples; keep brand and non-brand groups explicit. | GSC regex filters: validate rules with positive and negative examples |
When to stop and verify
Your result is an affected page and a testable explanation, with filters and dates recorded. A low CTR alone is not a reason to change every title.
Choose another Search Console problem · Check the official requirements
Search performance
Locate metric changes to queries, pages, countries, and devices, rather than only looking at site-wide averages.
Clicks, impressions, CTR, ranking: understand the calculation before looking at changes
Read clicks, impressions, CTR and average position together. A changing total can reflect a changing mix of queries rather than better or worse performance for the same audience. Calculate ratios from their underlying counts, then check one comparable page-query segment before deciding what to change.
Steps · error branches · checklistHigh impressions, low clicks: first distinguish four types of causes
Low CTR needs a diagnosis before an edit. Determine whether the page is exposed to low-ranking or unsuitable queries, whether the result already answers the task, or whether its promise is unclear. Test one defensible change within a comparable segment; there is no universal target CTR.
Steps · error branches · checklistSearch traffic drop: locate by scope and time
Locate the lost clicks by date and page before naming a cause. Restore confirmed availability, security or indexing faults first. When the site works, investigate demand, query mix and competing results. An update occurring at the same time is context, not proof that it caused the loss.
Steps · error branches · checklistGSC regex filters: validate rules with positive and negative examples
A regex filter is useful only when it classifies the intended inputs correctly. Start with a small rule, test positive and negative examples, then inspect the returned rows. A rule being accepted does not prove it is accurate, and filtering does not reveal hidden queries.
Steps · error branches · checklistBrand and non-brand queries: build a dictionary before comparing
Build a documented brand dictionary before separating brand and non-brand search. Include genuine names and spelling variants, keep ambiguous words unresolved, and compare periods with the same rule. Brand growth is useful evidence of demand, but does not prove that an SEO article caused it.
Steps · error branches · checklistCountry and device: find the users actually affected
Country and device differences tell you where to investigate, not why performance changed. Fix one page and task, compare sufficiently sized segments, then test the relevant language, device and business conditions. A country label is not evidence of a visitor's nationality or preferred language.
Steps · error branches · checklistDiscover data: missing report does not equal zero impressions
Discover has no manual article submission that guarantees exposure. Check whether its report is available, then review the page's eligibility, image and reader experience. Missing reporting is an unknown state; a recommendation spike is not evidence of dependable future traffic.
Steps · error branches · checklistGoogle News and Web news results: do not mix definitions
Separate Google News platform traffic from the News tab in Google Search. The Google News performance report covers news.google.com and the News apps; the Search performance report's News search type covers the search tab. Compare each source within its own scope and account for a story's life cycle.
Steps · error branches · checklistCheck guide coverage and product capabilities separately
SEO operations adds bounded technical checks, saved index-version reads, laboratory records and human content review. Native Google security, Discover, News and enhancement reports still require their own tools. A guide explains a method; it does not establish every report is connected.
View real product capabilities