📖 In This Issue

  • Featured Snippets: (News & Resources)

  • Cover Story: Stop Chasing Keywords: Use AI to Find Your Content Gaps

  • Operator of Interest: Jeff Coyle

  • Learn This: Multimodal AI

  • SEO For LLMs (GEO/AEO) Checklist

📰 Featured Snippets (News & Resources)

Lavall Chichester, gives an interesting overview of the SEO strategies employed by ChatGPT, Perplexity, and Claude, over on the Land of Search Engines.

Tom Critchlow points out that Google, for the 2nd time, is blocking referral traffic data from AI Overview citations. The first time this happened they “fixed“ it. But why would this mistake happen again?

Our friend, Aleyda Solis, discuses the rise of Paid Search ads in the SERPs.

Joshua Squires gives a great look into how Google plans to speed up LLM-based search with it’s STATIC framework. Reminds me of Google Caffeine from 2010.

Stop Chasing Keywords: Use AI to Find Your Content Gaps

If your content is “optimized,” why do users still leave?

You can hit every on-page checkbox and still watch people bounce, backtrack, or convert somewhere else.

That’s not always a “rankings” problem. Often it’s a coverage problem. Not in the “we missed 47 keywords” sense, but in the “we didn’t help someone make the decision they came here to make” sense.

If you want a definition of a content gap, you can ship, use this: a gap is any moment in the journey where the user needs clarity, proof, or direction, and your site either doesn’t have it or buries it behind the wrong page.

AI can help you find those moments faster. Not by writing more pages. By showing you what your site actually does when you zoom out.

The assumption that keeps teams busy and users unconvinced

The default assumption is simple: content gaps equal missing keywords.

That assumption isn’t totally wrong. Keyword data can be a useful signal for discovery and prioritization, especially when you need to quantify demand or find adjacent topics. Search Console query data, for example, can show which queries are already generating impressions and clicks, and where performance is weak.

But keyword-first gap work often flattens intent into a list. It treats “what is,” “which one,” and “how do I prove this worked” as variations of the same thing. Then it produces “comprehensive” content that looks complete in a spreadsheet and still fails in the real world.

A better frame is jobs-to-be-done plus journey steps plus trust requirements. A gap might mean you’re missing a comparison step. Or you’re making claims without evidence. Or you’re answering the wrong question on the page that actually ranks.

In other words, a gap is not always a missing topic. Sometimes it’s missing usefulness.

What AI is good for here, and what it isn’t

AI is valuable in this workflow when you treat it as a system for organizing information, not a source of truth.

It’s good at clustering similar pages, labeling patterns, summarizing what a URL appears to be doing, and spotting inconsistencies across a big inventory. It helps you compress the painful parts of an audit.

It’s not good at deciding what the market truly demands, what’s accurate in your domain, or what your strategy should be. It will happily produce fluent nonsense if your inputs are thin, inconsistent, or biased. That’s not a moral failing. That’s the tool doing what it does.

Also, AI doesn’t replace SEO infrastructure. Crawlability, internal linking, indexation, and quality signals still gate what gets seen. Google’s own guidance keeps returning to the same point: focus on people-first content, avoid creating search-engine-first pages. AI can’t “prompt” you out of those fundamentals.

So the right positioning is boring and useful: AI helps you audit faster. It doesn’t absolve you from being right.

A practical workflow: Demand → Journey → Inventory → Gaps

Step 1: Define real demand without starting with keywords

If you start with a keyword dump, you’ll end with a keyword-shaped strategy. That usually means you overproduce top-of-funnel explanations and underproduce decision support.

Instead, start with demand signals that are closer to reality than a phrase list.

Search Console is one anchor because it reflects what people actually typed and how Google actually surfaced your pages, even if it’s imperfect and sampled. Internal site search logs tell you what users expected to find once they trusted you enough to search your site. Support tickets and sales objections tell you what blocks conversion and retention. Competitor page themes and SERP features tell you what Google believes the dominant intent looks like for a query set, which matters if you want to rank and convert.

Your output from this step should read like human problems and decision stages. It should not look like a spreadsheet of phrases. The phrases can come later, when you need to validate demand and map to SERPs.

Step 2: Model the journey like a product team would

Most content audits quietly assume a single stage: “learn.” That’s why so many sites have ten versions of “what is X” and one weak “how to choose X.”

A journey model forces you to admit that understanding is not the same as deciding.

A simple, durable set of stages looks like this: understand, compare, validate, implement, troubleshoot, and prove ROI. The exact words don’t matter. The progression does.

At each stage, define what “good coverage” requires in your world. Early stages might need definitions and constraints. Middle stages need comparisons, tradeoffs, and selection criteria. Later stages need proof, examples, edge cases, and next steps.

This is where SEO and product reality meet. If your content never helps someone validate, you shouldn’t be surprised when they validate somewhere else.

Step 3: Inventory your content like you’re going to be accountable for it

Now you collect your URLs and the boring metadata that makes decisions defensible later: topic, format, intended stage, last updated date, conversions influenced, internal links in and out, and whether the page is indexable and actually indexed.

Then you use AI for what it’s good at: describe what each page actually does.

Have the model produce a short “page intent summary” per URL in plain language. Not what the title tag claims. What the content would help a user do. This becomes your baseline truth for gap detection, because it separates “we meant for this page to be a comparison” from “this page is actually a glossary with two examples.”

From there, you can create a content-to-journey matrix that shows themes by stage and where your existing URLs sit. The matrix is not the goal. It’s the diagnostic surface.

Step 4: Gap detection, where most teams accidentally lie to themselves

This is the part people botch because they confuse coverage with usefulness.

The first category is missing steps. You might have strong “understand” content and zero “how to choose” content, which means you’re present early and absent at the decision.

The second category is missing proof. If you claim outcomes without showing evidence, constraints, or real examples, you’re asking users to trust you on vibes. That’s fragile, especially in B2B.

The third category is mismatch gaps. The page ranks for a query pattern, but the page intent doesn’t match what the SERP suggests users want. This is where “we have a page for that keyword” becomes a trap.

The fourth category is cannibalization-by-theme. You have a pile of similar pages, none decisive. The site looks busy and still fails to guide a user to an answer. You’re not missing a page. You’re missing a single best page.

The fifth category is linking gaps. The journey breaks because the path doesn’t exist. Users shouldn’t need to go back to Google to reach the next step. Internal linking is not “related posts.” It’s navigation through decisions.

The risks when you scale this

The first risk is that fluent nonsense becomes your roadmap. AI will label themes and intent confidently, even when the underlying data is weak. The danger isn’t that the model is wrong. The danger is that it sounds right enough to ship.

The second risk is optimizing for coverage instead of usefulness. A perfect matrix can still produce content nobody trusts. Google’s people-first guidance is a reminder that “made for rankings” content is a liability over time, even if it temporarily fills a spreadsheet.

The third risk is drifting from search reality. If you don’t anchor your map in Search Console behavior and SERP patterns, you can end up modeling an imaginary journey that your buyers don’t follow and Google doesn’t reward.

The fourth risk is overfitting to competitors. “They cover it” is not the same as “users need it from us.” Competitor themes are inputs, not marching orders.

The fifth risk is governance debt. Every new page adds maintenance, internal linking, QA, and update burden. AI makes content expansion easier, which means it can also make content decay faster if you don’t have rules.

When keyword-first is still okay

There are cases where keyword-first work is defensible.

If you’re launching into a new market with no behavioral data, you may need terminology-led discovery to avoid blind spots. If you work in a constrained or regulated space, consistent language matters, and keyword-level mapping can prevent dangerous ambiguity. If you’re diagnosing technical indexing issues, query-level tracing is the right tool because you’re debugging how Google is interpreting and surfacing pages.

Even then, the output shouldn’t stay a keyword list. It should be translated back into journey steps and decision outcomes, otherwise you’ll ship content that ranks but doesn’t land.

What “good” looks like when you’re done

Good outputs are shippable, not impressive.

You want a topic coverage map that shows themes by journey stage and the URLs you already have. You want a gap backlog that prioritizes based on business impact, likelihood of ranking given your authority and SERP fit, and effort level, with a bias toward consolidation over expansion.

That consolidation bias matters. Tools and blogs often talk about “content gap analysis” as finding what you don’t have, but the real wins often come from deciding what you have too much of and merging it into something users can trust. Even mainstream SEO tool vendors define content gap analysis around identifying missing topics or keywords relative to competitors, which is useful, but incomplete if you stop there.

You also want a linking plan that makes the journey navigable, so users can move from understanding to deciding without leaving your site.

A simple scoring model that doesn’t pretend to be precise

You don’t need a fancy framework. You need one that can be defended later.

Score each theme and stage using four lenses. First, demand signal strength, grounded in Search Console impressions, SERP presence, and internal search frequency. Second, journey criticality, meaning how often that stage blocks conversion or retention based on what sales and support see. Third, current coverage quality, meaning accuracy, proof, freshness, and structure. Fourth, technical support, meaning indexability and internal linking that actually routes users.

The point of the score isn’t precision. It’s discipline. It forces you to explain why something matters and why now.

What to do right now

Stop treating content gaps as missing keywords.

Use AI to audit coverage against real demand and real journeys, not to invent more content. Anchor your map in Search Console and SERP behavior, then use AI to compress the grunt work of summarizing and clustering what you already have.

Then ship the highest-leverage fixes first. Consolidate before you create. Clarify page intent so it matches the job. Add proof where you’ve been making claims. And connect the journey so users don’t need to bounce back to Google to keep moving.

👤 Operator of Interest: Jeff Coyle

Learn This:

Multimodal AI: AI systems that process multiple input types such as text and images.

SEO For LLMs (GEO/AEO) Checklist

I finally finished writing a comprehensive SEO For LLMs (GEO/AEO) checklist that I can’t wait for you to see! But first I need to ask a small favor: Please share this newsletter with your friends, and I’ll email you this checklist for free as a thank you gift!

  1. Ask your friends to subscribe with this URL: {{rp_refer_url}}

  2. If just one of them subscribes, I’ll email you the free checklist.

One more thing: AI is only as good as it’s operator, and if you are reading this newsletter, you are better than most!

Till next time,

Joe Hall

PS: Let me know what you think of this issue, or anything else here: [email protected]

Keep Reading