Service
Models cannot cite what they cannot fetch. Technical AEO ensures your evidence is reachable, fast, and canonical.
Fifteen prompts, four engines, five business days.
Start with a visibility checkDiagnosis
Crawl logs look healthy while answer engines skip your templates: blocked fragments, slow LCP on comparison URLs, or JavaScript-only content in the passages models need.
Approach
We audit extractability for AI crawlers and human browsers, then fix indexation, rendering, and internal links that surface citable passages. Changes are verified against fetch tests and your prompt baseline.
Process
Days 1–5
Baseline
Approve prompts, engines, and competitors. Record today’s answers — labelled baseline, not a forecast.
Week 2+
Ship
Publish answer blocks, schema, internal links, and disclosed mentions. Strategists approve customer-facing copy.
Weekly
Report
Ship log plus named / cited / absent on the agreed set. Next sprint targets the largest gap.
Deliverables
A technical roadmap from logs and Search Console
A list of pages blocked from crawling or rendering
Canonical and hreflang notes for the templates we touch
Included work
Log-file and GSC-driven technical roadmap
Included work
JavaScript rendering and SSR compatibility review
Included work
Sitemap, robots, and AI crawler policy updates
Sample artefact
A strategist-readable table tied to your prompt list. We do not paste invented win rates into this layout.
Sample weekly excerpt · layout only
Technical AEO
| Prompt | Status | Engines |
|---|---|---|
| Best vendor for [job]? | Cited | |
| Who is trusted in [category]? | Named | Sample row |
Figures appear only when measured for your account. This is not a client export.
Measurement
Prompt status
Named, cited, or absent on each agreed buyer question.
What shipped
Pages, schema, links, and disclosed mentions that week.
Sources cited
Which URLs or domains the assistant attributed when it answered.
Next sprint
The smallest change queued to address the largest gap.
Engine angle
AI crawlers and human browsers do not always fetch the same DOM. Technical AEO verifies the passages models need are in static HTML and linked from hubs assistants retrieve.
Strong fit
Usually not a fit
FAQ
Start with a complimentary AI Visibility Check, or commission a $997 audit if you already know this is a priority.