Most GEO programs stall in the same spot. A team reads that schema markup helps AI engines parse a page, so they bolt FAQ and HowTo markup onto a dozen thin articles and wait. Nothing moves. The mention rate in ChatGPT stays flat, Perplexity keeps citing a competitor, and the team quietly concludes that generative engine optimization is hype. The real problem is that they started at layer three.
Rachel Whitmore made the case for the fix in How to Build a GEO Strategy from Scratch in 2026 on the Geology blog. Her framework has four layers, and the point that most teams skip is that the layers are a dependency chain, not a menu you pick from. Schema gets ignored when the content underneath it has no depth. Monitoring tells you nothing if you never recorded a baseline. This piece takes her four layers and works through why the order is the whole game.
A quick note on terms first. Classic SEO ranks your pages on Google. GEO earns your brand a mention inside an AI answer from ChatGPT, Perplexity, or Gemini. The work overlaps more than it looks like it does, and if you want the clean split between the two, GEO vs SEO covers it. The four layers below are the GEO half.
Layer one: get a baseline before you touch anything
Before you write a word or add a single tag, measure where you stand. Run about 20 prompts across ChatGPT, Perplexity, and Gemini. Split them into three buckets: category prompts ("best payroll software for remote teams"), problem prompts ("how do I handle multi-state payroll tax"), and direct brand prompts ("is Acme good for payroll"). For each answer, write down whether you were mentioned, which competitors showed up, and which sources got cited.
Then pick one metric you will defend for 90 days. Mention rate across the category prompts is a good default. The number itself matters less than committing to it, because every later decision points back to whether it moved.
This is layer one for a reason. You cannot claim a win you never measured, and "we feel more visible" is not a result anyone can act on.
Layer two: build authority where you actually have depth
Pick three to five topics where you can go deeper than an aggregator listicle ever will. For each one, write a pillar page plus five to eight supporting articles, and publish on a steady weekly cadence rather than in occasional bursts.
The constraint that does the work here is depth. AI engines synthesize answers from sources that demonstrate they understand the question, not from pages that restate the obvious. Every piece in a cluster should add something a reader could not get from the first page of search results. If a draft only summarizes what is already common knowledge, it will not get cited, and it dilutes the cluster around it.
This is also why breadth is a trap. Forty shallow posts spread across forty topics give an engine no reason to treat you as the authority on any of them.
Layer three: add structured signals on top of real content
Now the schema work pays off, because there is something underneath it worth parsing. Three jobs sit in this layer.
Fix entity consistency first. Your brand name, description, and key facts should read the same on your site, your LinkedIn, your Crunchbase entry, and anywhere else an engine cross-references you. Inconsistent entities make a model less confident about who you are.
Add the schema that fits the content: Organization, Article, FAQ, and HowTo where they genuinely apply. Format pages for extraction with clear headings, tables, and numbered steps, so an engine can lift a clean answer straight out of the page. Then reinforce internal linking so the cluster reads as a connected body of work instead of scattered posts.
Done in this order, schema amplifies depth. Done at layer one, it decorates pages that have nothing to say.
Layer four: monitor, and tie every number to an action
Rerun the baseline prompts weekly. Track mention rate, the sentiment of those mentions, which sources the engines cite, and your share of voice against the competitors who keep appearing. The discipline that separates a real program from a dashboard is connecting each metric to a specific action. If Perplexity cites a competitor's comparison page, that is the brief for next week's article, not just a line on a chart.
What this looks like in practice
Whitmore's worked example is a company called Northwind Ledger, starting from a 20 percent mention rate. They built two clusters, one on multi-state payroll and one on expense categorization, fixed their brand consistency across platforms, and reviewed their numbers every week. The visibility gain came from the layers reinforcing each other, not from any single tactic firing on its own.
A 90-day version of the same plan: weeks one and two for the audit and baseline, weeks three through six to build the first clusters and fix entity consistency, weeks seven through ten to add structured data and tighten internal linking, and weeks eleven and twelve to review what moved and plan the next phase.
Each engine rewards something slightly different
The four layers hold across platforms, but the emphasis shifts. ChatGPT rewards entity consistency and long-term depth. Perplexity favors citation-ready formatting and a clear, liftable answer. Gemini cares about crawlability and what renders in the initial HTML. Google AI Overviews tends to synthesize from pages that already rank, so classic SEO and GEO meet most directly there.
Where teams go wrong
The failure patterns are consistent: skipping the baseline so no win is provable, chasing breadth instead of depth, adding schema to thin content, publishing in sporadic bursts, and ignoring entity consistency across platforms. Each one is a layer attempted out of order, or skipped.
That is the whole argument. The four layers are not four projects you can run in parallel and bolt together at the end. They are a sequence where each one only works because the one before it is already in place. Consistency over a quarter reads to an engine as ongoing authority, which is exactly what a single burst of effort cannot fake.
For the full framework, including the prompt buckets and the worked example in detail, read Rachel Whitmore's original: How to Build a GEO Strategy from Scratch in 2026.
Mehul Jain writes about how search is shifting from keywords to model-mediated discovery at Geology. This article builds on the GEO strategy framework by Rachel Whitmore.
Top comments (0)