Service 04

Technical SEO Foundation

GEO does not replace SEO. It sits on top of it. A page a crawler cannot reach cannot be cited by anything, however well written it is.
Included in every retainer from Foundation upward.See pricing
00In short
Technical SEO remains a prerequisite for answer engine optimization. AI systems still rely on crawlable, indexable content and structured data to identify and retrieve sources. Technical work covers crawler access, render path, indexation, Core Web Vitals, internal linking and schema — the foundation AEO is built on, not an alternative to it.
01The problem

A recurring claim in this category is that AI search has made technical SEO obsolete. It has not. Every answer engine, whether it retrieves live or draws on training data, ultimately depends on content that was crawlable at some point. Blocked crawlers, JavaScript-dependent content, broken canonicals, and slow pages fail in exactly the same way they always did — only now the penalty is exclusion from the answer rather than a lower position.

What has changed is which crawlers matter. GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot and a dozen others now decide whether your content enters the systems people ask for recommendations. Many sites block some or all of them without knowing it, because CDN security products ship AI-bot blocking enabled by default.

The second change is that structured data carries more weight than it did. Schema was always a nice-to-have for rich results. For an entity-reasoning system it is closer to a passport: it tells a model what kind of thing you are, who runs you, what you sell, and which other identities across the web are the same entity as you.

So we treat this layer as unglamorous infrastructure and do it properly, because every stage above it inherits its failures.

02Deliverables

What you actually receive.

01

AI and search crawler access audit

Verification that every relevant user agent can reach your content, including CDN-level and managed-rule blocks.

02

Render-path audit

Confirmation that primary content exists in the initial HTML response, not only after client-side hydration.

03

Canonical and indexation hygiene

Correct self-referencing canonicals, clean sitemap, no conflicting directives, no stray staging references.

04

Structured data implementation

A connected schema graph with stable identifiers, validated and monitored rather than pasted once.

05

Core Web Vitals

Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift brought into and held in the green.

06

Internal linking architecture

Topical clustering that makes relationships between your pages legible to both crawlers and retrieval systems.

03Questions

Common questions.

Is technical SEO still relevant with AI search?

Yes. Answer engines depend on content that is crawlable and indexable, so blocked crawlers, JavaScript-only content, broken canonicals and slow pages exclude you from AI answers just as they suppressed rankings before. GEO sits on top of technical SEO rather than replacing it.

Which AI crawlers should I allow?

For most businesses, all of them: GPTBot, OAI-SearchBot and ChatGPT-User for OpenAI, ClaudeBot for Anthropic, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Bytespider and others. Blocking them removes you from the systems your buyers use for research. Publishers licensing content have a genuine reason to be selective; service businesses almost never do.

Do Core Web Vitals affect AI citations?

Indirectly. There is no evidence that page speed is a direct AI citation factor, but slow or unstable pages are crawled less thoroughly and convert worse when a high-intent AI referral does arrive. Given that ChatGPT referral traffic converts at 15.9% against 1.76% for Google organic, losing those visitors to a slow page is expensive.

Next step

Tell us what you are building.

If the question is about discovery, reputation, a new site, or a market move, send the context. AIGNCI will tell you whether an Audit, a build, or a more focused engagement is the right starting point.