Search has expanded to AI. The brands it recommends win the customer.

Technical AEO

Technical AEO makes your site readable to the crawlers that feed AI answers. Most sites block them by accident, render content in JavaScript the crawlers never execute, or ship pages with no structured data at all. We fix the layer underneath your content, so the work you do on top of it actually gets seen.

Book a Call

The Crawl Report

What each AI crawler can and can't reach on your site

Crawl report

OAI-SearchBot

Claude-SearchBot

PerplexityBot

The Fix List

Every issue ranked by what it's costing you

Fix list

Unblock crawlers

Server-render content

Add schema

Crawler access

Whether GPTBot, ClaudeBot, and PerplexityBot can reach your pages, and what your robots.txt is blocking.

Render check

Whether your content is in the raw HTML or only appears after JavaScript runs, which most AI crawlers skip.

Structured data

Organization, Product, FAQ, and Article schema, implemented and validated so models parse your pages as facts.

Site architecture

Internal linking, URL structure, and sitemaps that let crawlers find everything you've published.

We audit what the crawlers actually see

We fetch your pages the way GPTBot and ClaudeBot do, without JavaScript execution, and compare that to what a browser renders. On sites built in modern frameworks the difference is often most of the page.

Then we check your access rules

Robots.txt, meta robots tags, CDN rules, and bot protection. Blocking AI crawlers is frequently unintentional, inherited from a template or a security setting nobody revisited. We map exactly which agents are allowed and which are being turned away.

Finally, we implement and validate

Schema markup, server-side rendering fixes where they're needed, sitemap and internal linking corrections. Everything gets validated after the fact, and we re-fetch as each crawler to confirm the pages are now reachable.

Every model your buyers use

What is technical AEO?

Technical AEO is the infrastructure work that makes a site readable to the crawlers that feed AI answers. It covers crawler access rules, server-side rendering, structured data markup, and site architecture. It's the layer beneath content: if a crawler can't reach or parse your pages, nothing written on them can be cited.

Which crawlers should I allow?

The main ones are GPTBot and OAI-SearchBot from OpenAI, ClaudeBot from Anthropic, PerplexityBot, and Google-Extended. Each is controlled separately in robots.txt, and some sites allow one while blocking another without realizing it. Worth noting these are distinct from the crawlers that index for traditional search.

Why does JavaScript rendering matter?

Most AI crawlers fetch raw HTML and don't execute JavaScript. If your site is built in React, Vue, or a similar framework without server-side rendering, the crawler may receive an almost empty page while a human sees a full one. Your content exists, but not in a form the crawler can read.

Does schema markup actually affect AI answers?

It helps, though it isn't the only factor. Schema gives a model explicit structured facts rather than prose it has to interpret, which makes extraction more reliable and reduces the chance of your information being paraphrased incorrectly. It matters most for Organization, Product, and FAQ data.

How do I know if I have a technical problem?

The clearest signal is a gap between traditional search performance and AI visibility. If you rank well on Google but rarely get mentioned by models, something in the crawl or render layer is usually part of the reason. The audit identifies whether that's the case before any content work starts.

Can you implement the fixes or just find them?

Both. Some clients want us working directly in their codebase or CMS. Others want the specification and hand it to their own engineering team. Either works, and we validate the result regardless of who implements it.

How long does technical AEO take?

The audit is about a week. Implementation depends on the fixes. Robots.txt and schema changes ship in days. Server-side rendering on a large JavaScript site is an engineering project that can take weeks, and we'll tell you upfront which category you're in.