The goal of segmentation
Step 1 tells you the drop is real.
Step 2 tells you where the drop lives. We are here.
This is the step that turns a scary headline (“organic is down”) into a fixable problem (“non-brand informational queries to our /blog/ directory on mobile in the US dropped 32%”).
You’re hunting for the 80/20:
- The smallestre segments that explain most of the loss.
- The smallest number of pages/query groups you can act on first.
Start with three cuts (in this order)
- Brand vs non-brand: confirms whether this is a demand/awareness story or a competitive/SERP story.
- Query class (intent): tells you what kind of SERP you’re fighting on.
- Page type/template: tells you whether this is content, architecture, or a template-level technical issue.
Cut 1: Brand vs non-brand
Brand queries are your canary. They behave differently because demand is anchored to you.
Non-brand is where the world decides whether you deserve to be in the conversation.
How to do it fast in Search Console:
- Export queries for the affected date range and prior period.
- Filter brand queries by your company name, product names, and common misspellings.
- Everything else is non-brand (yes, it’s imperfect; it’s still useful).
What patterns usually mean:
- Brand stable, non-brand down: SERP features (AI Overviews), competitors, intent shifts, content quality, or cannibalization.
- Brand down, non-brand stable: tracking/measurement, sitewide technical issues, or a major reputation event impacting demand.
- Both down: technical indexing/crawl, broad algorithm impact, or a site migration problem.
Cut 2: Query classes (intent) that matter for diagnosis
You don’t need a perfect taxonomy. You need a practical one that predicts the SERP.
Use these four classes:
- Informational: definitions, guides, troubleshooting, how-to. High risk for AI Overviews and zero-click behavior.
- Commercial investigation: comparisons, best-of, alternatives, reviews. High risk for competitor displacement and SERP feature volatility.
- Transactional: buy, pricing, quotes, demo, near me. High risk for ads, local packs, and shopping modules.
- Navigational: brand + login, brand + pricing, brand + support. Usually stable unless tracking or site functionality broke.
Quick method:
- Bucket queries using simple rules (contains “best”, “vs”, “pricing”, “how”, etc.).
- You’re not publishing this taxonomy. You’re using it to choose the right fix path.
Cut 3: Page types and templates
The fastest route to a root cause is usually through templates, not individual URLs.
Group your affected landing pages into templates such as:
- Blog posts / guides
- Category or collection pages
- Product or feature pages
- Location pages
- Help center / documentation
- Programmatic pages (city + service, SKU pages, glossary pages)
Template-level drops scream one of two things:
1) a technical/template change (rendering, canonical, noindex, internal links), or
2) intent mismatch across the whole template (content format no longer matches SERP expectations).
See Also: Traffic Drop Recovery Framework
Build the Impact Table (your Step 2 deliverable)
You need one table that tells you where to spend the next week.
Columns to include:
- Segment name (ex: Non-brand informational /blog/ US mobile)
- Clicks delta (Search Console)
- Impressions delta
- CTR delta
- Avg position delta
- Top 5 pages in the segment (by click loss)
- Likely driver (SERP change vs ranking/indexing vs content/intent vs tracking)
- Owner (SEO, content, engineering)
You’ll know you did it right when the next step is obvious.
The “what this means” cheat sheet
- CTR down is a SERP story until proven otherwise.
- Impressions down is a visibility story (rankings or indexing).
- Position down on a subset of URLs is often intent/quality or competition.
- Position down sitewide suggests algorithmic impact or broad technical issues.
- Only one template down suggests a template-level technical or internal linking change.
FAQ
What if our brand name is also a common word?
Use a tighter brand filter: include your full brand phrase, product names, and navigational modifiers (login, pricing, support). Then validate a sample manually.
How many segments is too many?
If you can’t act on it, it’s too many. Step 2 should end with 2–5 priority segments, not 50.
About The Author
Dave Burnett
I help people make more money online.
Over the years I’ve had lots of fun working with thousands of brands and helping them distribute millions of promotional products and implement multinational rewards and incentive programs.
Now I’m helping great marketers turn their products and services into sustainable online businesses.
How can I help you?





