Part 16 of 22

Search intent: pages that match what people actually type

Technical SEO makes your pages indexable; intent matching makes them chosen. Google's core job is matching a query's intent to a page's type — and no amount of Core Web Vitals will rank a service page for a question query, or a blog post for a "hire someone" query.

The four intents and their page types

IntentQuery looks likePage that wins
Informational"what is ISR in next.js"Guide, glossary, tutorial
Commercial"next.js agency vs freelancer"Comparison, case studies, pricing
Transactional"hire next.js developer"Service/landing page with a clear CTA
Navigational"vercel dashboard"You don't compete for these

The practical discipline: one intent per page, one page per intent. When a blog post and a service page both target "next.js seo audit", they compete against each other (cannibalization) and Google picks neither confidently. Decide which page owns which query, and link the loser to the winner with a descriptive anchor.

For a developer-services site the money pattern is the guide → service ladder: informational content (this guide) earns the visit and the trust; internal links walk the reader to the transactional page that converts.

Long-tail: where the traffic actually is

Head terms ("next.js seo") are contested by documentation sites and giants. Long-tail queries ("next js hreflang localized slugs not working") have:

  • a fraction of the volume, but far higher intent,
  • almost no competition,
  • and they're exactly what people ask AI engines — answer-shaped pages win both channels at once.

Mine them from: Search Console queries you almost rank for (positions 8–20), People Also Ask boxes, autocomplete, your own support inbox and sales calls. Every recurring client question is a page waiting to be written.

Titles are ad copy: optimize for CTR

Position 5 with a great title routinely out-earns position 3 with a lazy one — and CTR itself feeds back into rankings:

  • Numbers and years work: "22-topic Next.js SEO checklist (2026)" beats "Next.js SEO best practices".
  • Match the query's words — searchers scan for their own phrasing.
  • Front-load the differentiator: what do you offer that results 1–4 don't? (Completeness? Freshness? A tool? Actual code?)
  • Find pages with high impressions but low CTR in Search Console → rewrite title/description → measure again in two weeks. It's the highest-ROI loop in SEO.

Zero-click reality: pick fights you can win

An increasing share of informational queries end without a click — answered by AI Overviews or featured snippets. Strategy, not despair:

  • Informational content still earns brand impressions and AI citations — being the quoted source is the new position one. Structure content to be quotable: question heading, direct answer, detail.
  • Commercial and transactional queries still click — comparisons, case studies, pricing, service pages. AI engines answer "what is hreflang" themselves but hand off "who should build my Next.js store".
  • Weight your content roadmap accordingly: informational for authority and citations, commercial/transactional for revenue.

Checklist:

  • Every page has one declared intent; no two pages target the same query
  • Guide → service internal-link ladders in place for main revenue paths
  • Long-tail list mined from GSC positions 8–20, PAA and client questions
  • High-impression/low-CTR pages get title rewrites on a recurring loop
  • Content mix balanced: informational for citations, commercial for clicks

Want this handled for you?

I audit and fix technical SEO on Next.js sites — indexing, performance, hreflang and AI visibility.

Technical SEO service