Skip to main content Scroll Top

Enterprise AEO: The Blockers Are Organisational, Not Technical

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Enterprise AEO uses the same five crawlers and the same scriptless fetch — but a robots.txt line that takes sixty days to approve, and a description that takes longer to agree than anything to build.

On this page · 12 sections
  1. At enterprise scale, the hard part is not technical
  2. Count templates, not pages
  3. Six governance questions to settle in week one
  4. Start the slow things before you need them
  5. Where the budget actually goes
  6. Pilot on one template family before requesting the programme
  7. How these programmes actually fail
  8. Everything else we have written on search, AI and getting found
  9. The same fix, priced by organisation
  10. What scales well, and what does not
  11. The six questions, and what a good answer looks like
  12. The failure pattern, stage by stage

The short answerAt enterprise scale the technical surface of answer engine optimization does not get bigger — there are still five crawlers, still a scriptless fetch, still passages to structure. What gets enormously bigger is the organisational surface. We have seen one robots.txt line take sixty days to approve, against a day for a sole trader. Scope by templates rather than pages, start the approval and engineering conversations in week zero before they are needed, agree one canonical description early because it is a negotiation rather than a writing task, and pilot on one template family before requesting programme budget.

Timeline and budget-split figures are our own observation across engagements, labelled as such rather than presented as research.

What actually blocks enterprise AEOWhat actually blocks enterprise AEO
Three greens, five reds. At enterprise scale the technical answers are the easy part; every genuine blocker is organisational.

At enterprise scale, the hard part is not technical

The technical surface of answer engine optimization does not get bigger with company size. There are still five crawlers to allow, still a scriptless fetch to pass, still passages to structure. What gets enormously bigger is the organisational surface around each of those.

We have watched enterprise programmes stall for sixty days on a single line in a robots.txt file — not because anyone disagreed with the change, but because the change had to pass a security review, a change board and a release train.

So the useful enterprise question is not what to do. It is who can approve it, how long that takes, and what you should start before you need it.

Blocker — robots.txt approval. 60+ days for one line.
Blocker — Engineering capacity. Rendering is their sprint, not yours.
Blocker — Regional disagreement. One description, many opinions.
Blocker — Unowned prompt set. Decays within two quarters.
Blocker — Three reporting stacks. Nobody reads the same number.
Not a blocker — Technical difficulty. The answers are known.
The same one-line robots.txt fix, priced by organisation sizeThe same one-line robots.txt fix, priced by organisation size
Identical technical change. The cost is governance, and pretending otherwise is how enterprise AEO proposals miss by a quarter.

The technical answers are known

Which crawlers, which templates, which passages. None of this is research at this point; it is execution.

The approval path is the critical path

One robots.txt line takes a day at a sole trader and two months at a regulated enterprise. Identical change, different governance.

Engineering capacity is somebody else’s sprint

Rendering fixes are not an agency deliverable in most large organisations. They are a ticket in a backlog you do not control.

The description is a stakeholder problem

Agreeing one canonical sentence about what the business does, across regions and business units, is routinely the hardest single deliverable.

Count templates, not pages

A hundred thousand pages built from four templates is a four-template job. This is the single most useful reframing for enterprise scoping, and it usually makes the work smaller than people expect rather than larger.

What genuinely multiplies is markets. Each language and region needs its own prompt set, run and stored separately, because answers are location-sensitive. Measurement cost scales with markets; implementation cost scales with templates.

Where enterprise complexity actually comes fromWhere enterprise complexity actually comes from
Markets multiply measurement cost; templates multiply implementation cost. Most enterprises underestimate the first and over-plan for the second.
Templates not pages — Unit. Four templates can carry everything.
Markets not keywords — Unit. Each market is its own prompt set.
Approvals not tasks — Unit. The critical path is sign-off.
Owners not roles — Unit. Named people, not departments.
Quarters not months — Unit. Governance runs on quarters.
One description — Unit. The hardest single deliverable.
Scales well — Template fixes. One change, thousands of pages.
Scales well — Schema patterns. Applied at template level.
Scales well — Entity description. Written once, deployed widely.
Scales badly — Prompt sets. Multiply by market and language.
Scales badly — Approvals. Multiply by stakeholder.
Scales badly — Manual review. Do not attempt at page level.

What it costs: Enterprise AEO

Answer engine optimization is priced like SEO, because most of the work overlaps with it. For Enterprise AEO, the ranges below are the published US bands we quote against; the number for a specific site is driven by rendering, template count and how much of the work already sits inside an SEO engagement.

AEO planning ranges (US figures)
EngagementTypical rangeWhat it covers
AEO audit$1,000–$4,000 one-offEight checks, roughly 10–20 hours, with a prioritized fix list
AEO added to an existing SEO retainerA few hours of setup, roughly $400Schema, extractable answers, entity clean-up on pages already being worked
Standalone AEO retainer$1,500–$20,000 / monthContent restructuring, schema, citations and monitoring across a site
Technical remediation for extractability$1,500–$6,000 one-offRendering, template and structured-data fixes

Ranges are US planning figures, not quotes. Every engagement is priced after a written scope, and the planning range tells you which tier the conversation starts in.

Six governance questions to settle in week one

Who approves a robots.txt change and how long does it take. Who owns the canonical business description. Who owns the prompt set after the agency leaves. Which team owns template-level rendering. How regional variations are reconciled. And which report the board actually reads.

All six are organisational. None is technical. Programmes that answer them in week one ship; programmes that defer them to ‘once we see the audit’ stall in quarter two with the diagnosis agreed and nothing implemented.

Governance questions to settle before the work startsGovernance questions to settle before the work starts
Six questions, all organisational, none technical. Programmes that answer them in week one ship; programmes that defer them stall in quarter two.
Who approves robots.txt — Settle first. And how long it takes.
Who owns the description — Settle first. One named person.
Who owns the prompt set — Settle first. After the agency leaves.
Who owns templates — Settle first. Rendering lives with them.
How regions reconcile — Settle first. Before they disagree.
Which report matters — Settle first. The one the board reads.

Start the slow things before you need them

Open the robots.txt change request in week zero, before the audit has even finished. Book engineering discovery in the same week. Begin the conversation about the canonical description immediately, because it is a negotiation rather than a writing task.

None of those three produces anything visible in the first month, and all three determine whether the programme ships. Work that produces no artefact is exactly the work that gets deferred, which is why it has to be scheduled deliberately.

Sequencing AEO inside a large organisationSequencing AEO inside a large organisation
The first four steps produce no output anyone can see and they determine whether the programme ships at all.

Week zero, approvals

The change is trivial and the path is not. Starting it early costs nothing and removes the commonest single point of failure.

Week zero, engineering

Rendering scope cannot be estimated without the people who own the templates. Scoping it without them produces estimates wrong by a factor.

Week one, the description

One sentence about what the business does, agreed across regions. Expect this to take longer than any technical task on the programme.

Week one, ownership

Name a person who owns the prompt set after the agency leaves. An unowned measurement decays within two quarters, and then the baseline is worthless.

Where the budget actually goes

Proposals typically assume most of the cost is technical implementation. In what we have observed, governance and approvals take roughly a quarter of the effort, and measurement at scale takes another fifth.

The governance line is almost never budgeted and is almost always the largest variance against plan. Putting it in the proposal explicitly is uncomfortable and it is the single thing most likely to make an enterprise estimate accurate.

Where enterprise AEO budget actually goesWhere enterprise AEO budget actually goes
Our observation, labelled as such. The governance line is almost never budgeted and is almost always the largest variance against plan.
Enterprise AEO, in numbersEnterprise AEO, in numbers
The technical surface is not bigger at enterprise scale. The organisational surface is enormously bigger.

Pilot on one template family before requesting the programme

One template family, one market, one owner, thirty prompts, eight weeks. Long enough to see leading indicators — crawler hits, render coverage, extractability — and short enough that it does not need a programme budget to start.

Then request the full budget with evidence rather than with a deck. Enterprise AEO proposals built on industry statistics get compared against other decks; proposals built on your own server logs get approved.

Pilot — One template family. Prove mechanism cheaply.
Pilot — One market. Avoid multiplying measurement early.
Pilot — One owner. Fast decisions.
Pilot — Fixed prompt set. 30 prompts, not 300.
Pilot — 8 weeks. Long enough to see leading indicators.
Then — Request programme budget. With evidence, not a deck.

How these programmes actually fail

The pattern is consistent and it is never a disagreement about what should be done. The audit lands and is accepted. The robots.txt change enters approval and nobody budgeted sixty days for one line. Rendering gets scoped without engineering in the room and the estimate is wrong.

Then content work starts anyway, to show momentum, on pages machines still cannot read. Regions disagree about the description. Quarter two arrives with no citations and no way to say which half failed — and the programme gets judged on an outcome that was never actually attempted.

How enterprise AEO programmes actually failHow enterprise AEO programmes actually fail
We have watched this sequence more than once. Every step is organisational and none of it is a disagreement about what should be done.
Content-first — Risk. Momentum theatre on unreadable pages.
Deferring governance — Risk. Stalls in quarter two.
Scoping without engineering — Risk. Estimates wrong by a factor.
Blended reporting — Risk. Hides which half failed.
No baseline — Risk. Quarter two is undiagnosable.
Agency owns measurement — Risk. It leaves when they do.

Scope the governance, not just the site

An AI visibility audit at enterprise scale should produce a template inventory, an approval-path map and a named owner for the prompt set — alongside the technical findings. We will tell you which of those is your actual bottleneck.

/ai-visibility-audit

Everything else we have written on search, AI and getting found

AI, AEO and what is changing

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Want this done for your site?We scope enterprise AEO by template rather than by page, and start the approval track on day one.

Get a free proposal

The same fix, priced by organisation

One identical one-line change, and what it costs in elapsed time at four organisation sizes.

One robots.txt line, from identified to live
OrganisationElapsed timeWhat sits on the critical pathTechnical difficulty
Sole trader1 dayEditing the fileNone
Small business3 daysAsking the developerNone
Mid-market2 weeksTicket, sprint, deployNone
Enterprise60+ daysSecurity review, change board, release trainNone
Regulated enterprise120+ daysAll of the above plus compliance sign-offNone
Franchise network90+ daysHead office plus per-franchisee rolloutNone

What scales well, and what does not

Some of this work gets cheaper per page at scale and some gets dramatically more expensive.

Plan around the second column
ActivityScales withEnterprise impactHow to handle it
Rendering fixesTemplatesUsually smaller than expectedCount templates, not pages
Schema patternsTemplatesLowApply at template level
Passage restructuringTemplatesModeratePilot one family first
Canonical descriptionStakeholdersHigh and underestimatedStart in week one
Prompt setsMarkets and languagesHighPilot one market before scaling
ApprovalsStakeholdersHighestOpen requests before you need them
Manual page reviewPagesDo not attemptSample at template level

The six questions, and what a good answer looks like

Six questions to put to an internal team or a vendor, with the answers that indicate readiness.

Settle these before kickoff, not after the audit
QuestionA weak answerA workable answer
Who approves a robots.txt change?IT, probablyNamed person, path mapped, SLA known
Who owns the canonical description?MarketingOne named person with authority across regions
Who owns the prompt set afterwards?We will decide laterNamed internal owner from week one
Which team owns template rendering?The web teamNamed team, capacity booked
How do regions reconcile?Case by caseA stated rule, agreed in advance
Which report does the board read?All of themOne, named, with two streams kept separate

The failure pattern, stage by stage

Enterprise programmes in this field fail in a recognisable sequence, and each stage has a specific remedy.

What we have watched happen, and where to intervene
StageWhat happensIntervention
Audit acceptedEveryone agrees the diagnosisOpen approvals in week zero
Approval queue60 days for one lineStart before the audit finishes
Rendering scopedEstimated without engineeringBook discovery in week zero
Content starts anywayMomentum theatre on unreadable pagesRefuse; fix rendering first
Regions disagreeEntity work stallsAgree the description in week one
Quarter two reviewNo citations, no diagnosisBaseline in week one makes it diagnosable
Programme judged failedOn work never shippedReport leading indicators throughout

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Frequently asked questions

What is enterprise AEO?
Answer engine optimization at organisational scale. The technical surface is the same as anywhere else — five crawlers, scriptless rendering, passage structure — but the binding constraints are governance, approval paths, engineering capacity and cross-region agreement.
Is enterprise AEO technically harder?
No. The technical answers are known and the same. What is enormously bigger is the organisational surface: who approves a robots.txt change, who owns the canonical description, whose sprint the rendering fix lands in.
How long does a robots.txt change take at enterprise scale?
We have seen sixty days and more, against a day for a sole trader. The change is identical; the difference is security review, change board and release train.
How should enterprise AEO be scoped?
By templates, not pages. A hundred thousand pages built from four templates is a four-template job, which usually makes the work smaller than people expect.
What multiplies enterprise cost?
Markets multiply measurement cost, because each language and region needs its own prompt set. Stakeholders multiply approval cost. Templates multiply implementation cost, and that is usually the smallest of the three.
What should we start in week zero?
The robots.txt change request, engineering discovery for rendering scope, and the conversation about a canonical business description. None produces a visible artefact, and all three determine whether the programme ships.
What is the hardest single deliverable?
Agreeing one sentence about what the business does, across regions and business units. It is a negotiation rather than a writing task and it routinely takes longer than any technical work.
Who should own the prompt set?
A named internal person, decided in week one. An unowned measurement decays within two quarters, and when it does the baseline becomes worthless.
Why do enterprise AEO programmes fail?
Almost never from disagreement about what to do. The audit is accepted, approvals take longer than budgeted, rendering is scoped without engineering, content work starts anyway on unreadable pages, and quarter two arrives with no citations and no way to diagnose which half failed.
Should we pilot first?
Yes. One template family, one market, one owner, thirty prompts, eight weeks. Long enough to read leading indicators, short enough not to need programme budget, and it produces evidence rather than a deck.
How much of the budget is governance?
In what we have observed, roughly a quarter — and it is almost never in the proposal. It is the largest single source of variance against plan in enterprise programmes.
Do we need more crawlers allowed than a small business?
No. The same five: GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended. Enterprise scale does not add crawlers, it adds approval steps.
How do we handle multiple regions?
Agree a reconciliation rule before regions disagree, and run a separate prompt set per market with results stored separately. Cross-market averages hide a total failure in one region.
What should the board report contain?
Two streams kept separate: search rankings and answer-engine results. Never a single blended visibility score, because it hides which half is working.
Can the agency decide the governance questions?
No, and an agency claiming it can is misunderstanding the problem. These are internal authority questions; an external supplier can map the path but cannot own it.
What is the template inventory and why does it matter?
A count of the distinct page templates carrying your commercial pages. It is the real unit of implementation work and it is usually a surprisingly small number.
Should we do content work while waiting for rendering?
No. Content work on pages that return nothing to a crawler is applied to nothing. It looks like momentum and it is the commonest way enterprise programmes waste a quarter.
How do we prove progress before citations move?
Leading indicators: crawler hits in server logs, status codes to AI user agents, scriptless render coverage per template, and whether restructured passages read standalone. All available within weeks.
When is the first honest read?
Month six, against a baseline recorded in week one. Earlier readings are mostly run-to-run variance rather than progress.
Is enterprise AEO worth it for every large organisation?
Not automatically. It is strongest where buyers research by asking questions — B2B software, professional services, healthcare, manufacturing with specification-led buying. Where demand is brand-led and the site is already clean, a baseline and monitoring may be the whole sensible programme.
How does this interact with our existing SEO programme?
It should sit inside it rather than beside it. Only two workstreams are genuinely new, so a separate contract typically produces duplicate technical work and two reports that disagree.
What is the one thing most enterprise proposals get wrong?
They budget technical implementation and omit governance. Putting the approval path in the plan explicitly is the single change most likely to make the estimate accurate.

Want this done for your site?We build and maintain the search, content and paid programmes described on this page.

Get a free proposal

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Our website uses cookies from third party services to improve your browsing experience. Read more about this and how you can control cookies by clicking "Privacy Preferences".
Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Privacy Policy
You have read and agreed to our privacy policy
Required
Contact Us