Audit · implementation · verified re-crawl

Make your site legible to machines that don't click.

AI crawlers arrive without JavaScript, without patience and without a browser. Technical AEO fixes what they hit — access, rendering, structure and markup — so your pages can be understood and quoted.

The engagement

Audit, fix, verify.

Five days to a full picture. Three weeks to a fixed site.

01
Audit
Every template on your site is fetched as each AI user agent — no JavaScript, real headers, real rate limits.
02
Prioritise
Issues are ranked by how much they block understanding, not by how many URLs they touch.
03
Implement
We ship the fixes: llms.txt, schema, structured on-page facts, header and robots rules. Or hand your devs a patch-level spec.
04
Verify
A re-crawl confirms each fix landed, and the change is logged against your visibility score.
What we fix

The layers between your server and an answer.

Each one can silently drop you out of a response.

Crawler access

We audit robots.txt, meta robots and sitemaps to confirm GPTBot, ClaudeBot, PerplexityBot, Google-Extended and Bingbot can actually reach you — and flag anything blocking them.

llms.txt & content maps

Per-client llms.txt and llms-full.txt: a curated plain-text index pointing assistants at the canonical version of every fact that matters.

Freshness signals

Visible dateModified plus in-schema timestamps, and stale pages flagged for refresh — so assistants always read your current facts, not last year's.

Structured data

LocalBusiness, Product, Offer, FAQPage, Article, Breadcrumb and Speakable markup — generated with a canonical @id entity anchor and sameAs, deduplicated and kept in sync with the page.

Instant indexing

Every new or updated page is pushed through IndexNow the moment it publishes, so engines pick up changes without waiting for a crawl.

Entity consistency

One name, one description, one set of facts across your pages, schema and profile — anchored to a single canonical entity so assistants never get conflicting signals.

Before / after

What actually changes.

A typical fix on a client-rendered marketing site.

Before
<title>Home | Acme</title>
<div id="app"></div>

// no llms.txt
// no JSON-LD
// content requires JS
After
# /llms.txt
> Acme runs payroll for UK agencies.
## Pricing /pricing.md
## Integrations /docs/integrations.md

<script type="application/ld+json">
{"@type":"Product","name":"Acme Payroll",
 "offers":{"price":"49","priceCurrency":"GBP"}}
</script>
Questions

The practical ones.

Answer Engine Optimisation: making a site legible to the systems that assemble answers rather than rank links. Same discipline as technical SEO, different consumer.

Adoption is uneven, but it costs an afternoon and is already read by several crawlers. We treat it as one signal among nine, never the whole fix.

No. AEO doesn’t require a rebuild. The fixes that matter most — llms.txt, schema markup, freshness signals and entity consistency — sit alongside your existing stack, whether that’s Next.js, Nuxt, Astro or WordPress.
The platform does the recurring work automatically — scans, llms.txt, schema, content and IndexNow pings, every month. You get a spec-level report of anything that needs a developer’s hand on your own site. If you need help we can help you just contact us.
The first scan runs in minutes and gives you a full visibility picture. The platform then works on a monthly cycle, publishing and re-checking on a set schedule.

When AI answers, make sure it's your name.

See exactly where ChatGPT, Gemini, Claude and Perplexity leave you out — then let us put you back in.

Monthly plans from €149. Cancel anytime.