Measuring Return On Generative Engine Optimization Work
2026.08.14 14:54
Control the Session Conditions Personalisation quietly corrupts this. Run from a signed out session, or a fresh session with memory and history disabled, and do not use an account that has been researching your own company all week.
The most citable content most businesses could publish already exists, unwritten, in sales calls and support tickets. It is the set of questions people actually ask, with the answers your team gives verbally every week and has never put on a page.
This is a plan rather than an explanation. It assumes you have already accepted that some of your buyers are asking an assistant for recommendations before they contact anybody, and that you would prefer to be named.
Revisit the answers when the business changes rather than on a content schedule. Price changes, new capabilities and discontinued services all silently invalidate published answers, and an outdated answer stated confidently is worse than no answer at all, because it can be quoted back at you by an assistant that has no way of knowing it is stale.
Inside your own organisation, the useful move is to write a single sentence defining whichever term you adopt and put it wherever your team will see it. Most of the confusion these acronyms cause is internal rather than external, with two people using the same word for different scopes and discovering the mismatch three months into a project.
The pages that earn citations are consistent across industries: an honest comparison of the options including where you are not the right choice, a plain definition page for the thing you sell, a specifications page with real numbers, and a pricing page that says something concrete.
Statistics without sources. This field circulates figures faster than it checks them, and a number arriving without a publisher, a sample size and a date should be discounted rather than repeated to your board.
Three acronyms, considerable overlap, and no governing body to settle the definitions. Different agencies use them differently, some interchangeably, and a few have invented a fourth to differentiate a proposal.
That emphasis is worth watching, since retrieval is where most current influence actually lies. A proposal built primarily on getting into training data is describing a slower and far less controllable mechanism than one built on being retrievable now.
Then listen for language. When prospects begin describing your business using phrasing you did not write and your competitors do not use, that phrasing came from somewhere, and generated answers are an increasingly likely source. It is anecdotal, it is not a number, and it is often the earliest indication that anything is working.
Days One to Fourteen: Find Out Where You Stand Somebody writes fifty questions your buyers would ask, in their words. They run each one three times across the two or three assistants your customers use, from a signed out session, and record the full answers and every source cited.
If nothing has moved on any of the three, that is real information and a legitimate reason to scale back or change supplier. Set that review date at the start, while everyone is still optimistic, because it is much harder to set fairly once money has been spent. Generative engine optimization
Test it rather than assuming. Load your key pages with Javascript disabled and see what survives. If the product specifications, pricing, service areas and contact details vanish, that is what a machine reads.
If your category still gets meaningful traffic from those, a proposal scoped only to assistants will leave that work undone. Conversely, if somebody proposes an answer engine optimization programme and delivers only snippet optimisation, they are working on the older half of the definition.
One structural decision saves a lot of trouble later. Keep the raw answers in plain text files named by date, assistant and run number, rather than pasting them into a document that gets reformatted. Six months in you will want to search across every run for the first appearance of a competitor or a source, and a folder of plain files supports that while a slide deck does not.
Crawler access restored on a date. Listings claimed and corrected, with a count. Factual errors fixed on third party sources, with a count. Pages published that answer prompts your baseline showed were being answered badly. Reviews responded to.
The same applies to limitations. Stating plainly what you do not do, what size of job you decline and which situations suit a competitor produces the constraint statements that models lift as impartial facts.
One organisational habit makes this sustainable. Give the sales and support teams a single place to drop questions as they hear them, with no process attached beyond writing down the question in the customer's words. Anything more elaborate stops being used within a month, and a shared document with fifty verbatim questions in it is worth more than a formal intake process nobody completes.
The most citable content most businesses could publish already exists, unwritten, in sales calls and support tickets. It is the set of questions people actually ask, with the answers your team gives verbally every week and has never put on a page.
This is a plan rather than an explanation. It assumes you have already accepted that some of your buyers are asking an assistant for recommendations before they contact anybody, and that you would prefer to be named.
Revisit the answers when the business changes rather than on a content schedule. Price changes, new capabilities and discontinued services all silently invalidate published answers, and an outdated answer stated confidently is worse than no answer at all, because it can be quoted back at you by an assistant that has no way of knowing it is stale.
Inside your own organisation, the useful move is to write a single sentence defining whichever term you adopt and put it wherever your team will see it. Most of the confusion these acronyms cause is internal rather than external, with two people using the same word for different scopes and discovering the mismatch three months into a project.
The pages that earn citations are consistent across industries: an honest comparison of the options including where you are not the right choice, a plain definition page for the thing you sell, a specifications page with real numbers, and a pricing page that says something concrete.
Statistics without sources. This field circulates figures faster than it checks them, and a number arriving without a publisher, a sample size and a date should be discounted rather than repeated to your board.
Three acronyms, considerable overlap, and no governing body to settle the definitions. Different agencies use them differently, some interchangeably, and a few have invented a fourth to differentiate a proposal.
That emphasis is worth watching, since retrieval is where most current influence actually lies. A proposal built primarily on getting into training data is describing a slower and far less controllable mechanism than one built on being retrievable now.
Then listen for language. When prospects begin describing your business using phrasing you did not write and your competitors do not use, that phrasing came from somewhere, and generated answers are an increasingly likely source. It is anecdotal, it is not a number, and it is often the earliest indication that anything is working.
Days One to Fourteen: Find Out Where You Stand Somebody writes fifty questions your buyers would ask, in their words. They run each one three times across the two or three assistants your customers use, from a signed out session, and record the full answers and every source cited.
If nothing has moved on any of the three, that is real information and a legitimate reason to scale back or change supplier. Set that review date at the start, while everyone is still optimistic, because it is much harder to set fairly once money has been spent. Generative engine optimization
Test it rather than assuming. Load your key pages with Javascript disabled and see what survives. If the product specifications, pricing, service areas and contact details vanish, that is what a machine reads.
If your category still gets meaningful traffic from those, a proposal scoped only to assistants will leave that work undone. Conversely, if somebody proposes an answer engine optimization programme and delivers only snippet optimisation, they are working on the older half of the definition.
One structural decision saves a lot of trouble later. Keep the raw answers in plain text files named by date, assistant and run number, rather than pasting them into a document that gets reformatted. Six months in you will want to search across every run for the first appearance of a competitor or a source, and a folder of plain files supports that while a slide deck does not.
Crawler access restored on a date. Listings claimed and corrected, with a count. Factual errors fixed on third party sources, with a count. Pages published that answer prompts your baseline showed were being answered badly. Reviews responded to.
The same applies to limitations. Stating plainly what you do not do, what size of job you decline and which situations suit a competitor produces the constraint statements that models lift as impartial facts.
One organisational habit makes this sustainable. Give the sales and support teams a single place to drop questions as they hear them, with no process attached beyond writing down the question in the customer's words. Anything more elaborate stops being used within a month, and a shared document with fifty verbatim questions in it is worth more than a formal intake process nobody completes.