Query Classification & Content Mapper
Source: Bill Slawski's analysis of Google's query understanding, classification, and reformulation patents Application: Align content format, structure, and signals to the specific intent class Google assigns to target queries
Why Classification Matters
Google classifies every query before deciding what to rank. The classification determines:
- Which ranking signals receive the most weight
- What content format is most appropriate
- Whether to show local pack results, news, shopping, images, etc.
- How much freshness is required
- Whether E-E-A-T signals matter heavily
If your content format doesn't match Google's classification of the query, it will not rank consistently — regardless of how well-written or well-optimized it is.
The 6 Query Classes
Class 1: LOCAL
Definition: User wants results near a specific location, either implied or stated. Trigger signals:
- Geographic modifier: "plumber Miami," "dentist near Downtown Chicago"
- "Near me" phrase (explicit or implied from device location)
- Service + city/neighborhood combination
- "Open now," "hours," "address" combined with a business type
Content format for LOCAL queries:
- Location page with complete LocalBusiness schema
- GMB listing integration
- Map embed
- NAP (Name, Address, Phone) visible above the fold
- Local testimonials and reviews
- Nearby landmarks and neighborhood context
- Service area language if SAB (Service Area Business)
SERP features for LOCAL:
- Google Maps pack (local 3-pack)
- Local business Knowledge Panel
- Directions, hours, reviews in SERPs
Class 2: NAVIGATIONAL
Definition: User wants to reach a specific website, brand, or resource — not general information. Trigger signals:
- Brand name as the entire query (e.g., "Ahrefs", "Reddit", "Chase Bank")
- Brand name + specific resource ("Moz keyword explorer", "Google Search Console help")
- Domain name or URL fragment in query
Content format for NAVIGATIONAL queries:
- This is your homepage or primary brand page
- Clear brand identity — name, logo, tagline visible immediately
- Sitelinks optimization (see Sitelink Optimization Audit)
- Official social profiles linked and consistent
- Knowledge Panel signals: established entity, Wikipedia if appropriate
You cannot "optimize" your way into navigational queries for a brand you're not. Navigational queries are brand-locked.
Class 3: TRANSACTIONAL
Definition: User intends to complete an action — typically a purchase, sign-up, or download. Trigger signals:
- Commercial modifiers: "buy," "order," "price," "cost," "cheap," "discount," "deal"
- Dollar signs or price ranges: "$50," "under $100"
- Product/service name + "for sale," "near me" (purchase intent), "review" (pre-purchase research)
- Subscription terms: "plan," "subscription," "monthly fee"
- Download/access terms: "download," "free trial," "sign up"
Content format for TRANSACTIONAL queries:
- Product or service page (not a blog post)
- Clear pricing and CTA above the fold
- Trust signals: reviews, ratings, testimonials, guarantees
- Urgency signals where appropriate (scarcity, limited offers)
- Product/service structured data (Product schema with price, availability)
- Schema review markup (AggregateRating)
Common mistake: Writing an informational article for a transactional query. "Best coffee machines" with purchase intent needs product recommendations with prices and buy buttons — not a history of coffee machine development.
Class 4: INFORMATIONAL
Definition: User wants to learn something — not buy, not find a location, not navigate to a specific site. Trigger signals:
- Question words: "how," "what," "why," "when," "where," "which"
- Learning language: "guide," "tutorial," "learn," "explained," "definition of"
- Comparison without commercial intent: "X vs Y" (without "buy" or "best")
- Process language: "how to," "steps to," "ways to"
Content format for INFORMATIONAL queries:
- Long-form guide or article (1,500+ words for complex topics)
- Structured headings (H2/H3) that answer the question at each level
- Table of contents for long content
- FAQPage or HowTo schema where applicable
- E-E-A-T signals: author credentials, first-hand experience markers, sources cited
- No aggressive CTAs — serve the information first
The pogo-stick trap: Informational queries require immediate answer delivery. If users must scroll past ads, email capture, or intro fluff to reach the answer, they pogo-stick back to SERP. Put the answer first.
Class 5: TIME-SENSITIVE
Definition: User wants current, recent, or breaking information. Trigger signals:
- Explicit time modifiers: "latest," "recent," "2025," "this week," "today"
- News/event terms: "breaking," "update," "announcement," "just released"
- QDF-sensitive topics: algorithm updates, earnings reports, political events, sports results
- Topic categories that inherently require freshness: stock prices, weather, traffic
Content format for TIME-SENSITIVE queries:
- Visible publish date and last-updated date
- News-style format: most important information first (inverted pyramid)
- Datelines and timestamps on specific claims
- Quick summary/TL;DR at the top
- NewsArticle schema
The freshness decay rule: Time-sensitive content that isn't updated has a shelf life. Target its freshness decay class and build a review schedule (see Content Freshness & Decay Monitor audit).
Class 6: AMBIGUOUS
Definition: Query signals are mixed — multiple intent types possible. Trigger signals:
- Generic 1-2 word queries without modifiers: "coffee," "marketing," "SEO"
- Queries where intent varies significantly by demographic
- Navigational/informational overlap: "Facebook" (navigational for most, informational for some)
- Transactional/informational overlap: "laptop" (research phase vs. purchase-ready)
Content strategy for AMBIGUOUS queries:
- Hedge the format — serve multiple intents in one page
- Include an informational introduction + transactional recommendations + navigational anchors
- Use FAQ sections to cover edge case intents
- Monitor Search Console for which queries drive traffic — this reveals the actual dominant intent
- Look at the actual SERP: what format does Google show? That's Google telling you the dominant classification.
Signal Weight Matrix
Use this to score queries against each class:
| Signal | LOCAL | NAV | TRANS | INFO | TIME | AMB |
|---|---|---|---|---|---|---|
| Geo modifier | 5 | 0 | 1 | 0 | 0 | 1 |
| Brand name | 0 | 5 | 1 | 0 | 0 | 2 |
| "buy/price/cost" | 0 | 0 | 5 | 0 | 0 | 2 |
| Question word | 0 | 0 | 0 | 5 | 1 | 2 |
| "news/breaking" | 0 | 0 | 0 | 1 | 5 | 1 |
| "near me" | 5 | 0 | 2 | 0 | 0 | 1 |
| "review" | 1 | 0 | 3 | 2 | 0 | 3 |
| "guide/tutorial" | 0 | 0 | 0 | 5 | 0 | 1 |
| Year modifier | 0 | 0 | 0 | 1 | 5 | 2 |
| "$" or price | 0 | 0 | 5 | 0 | 0 | 2 |
Score each signal 0-5 based on presence/strength. Highest total column = likely class.
The SERP Classification Test
The fastest query classification method: look at the actual SERP.
Google's SERP format reveals its classification:
- Local 3-pack visible → LOCAL
- Knowledge Panel for a brand → NAVIGATIONAL
- Shopping ads + product results → TRANSACTIONAL
- Featured snippet + long-form articles → INFORMATIONAL
- News carousel + recent dates on results → TIME-SENSITIVE
- Mix of formats → AMBIGUOUS
If the top 3 results are all long-form guides and you have a product page targeting that query, you're fighting Google's classification. Match the format — or find a different keyword.
Content Format Recommendations by Class
| Class | Format | Length | CTA Level | Schema |
|---|---|---|---|---|
| LOCAL | Location page | 500-1500w | High | LocalBusiness |
| NAVIGATIONAL | Homepage/brand | Variable | Medium | Organization |
| TRANSACTIONAL | Product/service | 500-1500w | High | Product, AggregateRating |
| INFORMATIONAL | Guide/article | 1500-5000w | Low | Article, FAQPage, HowTo |
| TIME-SENSITIVE | News/update | 500-1500w | Low | NewsArticle |
| AMBIGUOUS | Hybrid | 1500-3000w | Medium | Varies |
Audit Output
For each target keyword in your content strategy:
- Classify using the signal weight matrix
- Verify against the actual SERP format
- Compare your current content format to the recommended format for that class
- Flag mismatches — these are high-priority rewrites
- Map the content format gap: what must change to match the correct class?