Does AI care about page speed?

Indirectly. Slow, broken or hard-to-render pages get retrieved less often. Page speed isn't a direct AI ranking signal, but it is a retrieval-eligibility signal.

Do AI engines render JavaScript?

Some do, some don't, and even when they do, JS-only content gets retrieved less reliably. Server-render or pre-render any content you want AI to extract.

Is robots.txt enough to control AI crawlers?

No. Different AI engines respect different directives (GPTBot, Google-Extended, PerplexityBot). Audit and explicitly allow/block each one based on your strategy.

How important is internal linking for AI?

Very. Internal links shape the entity graph AI builds of your site and reinforce topical clusters.

What's the single highest-impact technical fix?

For most sites: clean, server-rendered HTML with valid schema and a fast TTFB. Everything else compounds on top of that foundation.

Technical SEO Factors That Affect AI Visibility

If AI can't reliably crawl, render and parse your site, no amount of content or PR will land. Technical foundations are what every AI visibility program is built on.

Technical SEO for AI visibility is mostly classic technical SEO — applied with awareness that the consumers of your HTML now include AI crawlers, not just Googlebot. The fundamentals are the same. The stakes are higher.

1. Crawlability

Audit robots.txt for explicit AI bot directives (GPTBot, Google-Extended, PerplexityBot, ClaudeBot)
Decide your stance per bot — most local businesses should allow them all
Ensure no key pages are blocked by noindex/nofollow accidentally
Submit XML sitemaps; keep them clean and current

2. Rendering

Prefer server-rendered HTML for any page you want AI to extract
Avoid client-only React/Vue rendering for primary content
If you must use SPA, implement SSR or pre-rendering for critical pages
Test how each page renders without JS — that's what most AI crawlers see

3. Structured data

See our schema deep dives. Technical owners are responsible for ensuring schema deploys with templates and validates after every release.

4. Internal linking

AI uses internal linking to model your entity graph. See How Internal Linking Impacts AI Search Visibility for the full framework.

5. Site architecture

Pillar + cluster structure with clear URL hierarchy
Breadcrumbs on every non-home page
Avoid orphan pages (pages with no internal inbound links)
Limit depth: critical pages within 3 clicks of the homepage

6. Page speed & Core Web Vitals

Not a direct AI ranking signal, but slow pages get crawled less, rendered less reliably, and retrieved less often. Aim for sub-2s LCP and stable CLS.

7. Indexability

Canonical tags on every page
One version (https + non-www, or your chosen canonical)
Pagination handled properly
Faceted navigation that doesn't generate infinite low-value URLs

8. Entity consistency

Brand name, logo, NAP identical across every page
Schema NAP matches GBP and citations
Author names match across articles and bio pages

9. Semantic HTML

Single H1 per page
Proper heading hierarchy (no skipping levels)
Lists use ul/ol, not styled divs
Tables use table/th/td
Article content wrapped in <article>

10. Technical audit workflow

Crawl the site (Screaming Frog, Sitebulb)
Identify rendering issues with JS off
Validate schema across templates
Check robots.txt and AI bot directives
Check Core Web Vitals on top 50 pages
Run Recometric to tie technical findings to AI visibility movement

11. Common technical problems we see

JS-only menus that block crawl paths
Lazy-loaded content that AI never sees
Schema only present in dev, missing in prod
Multiple competing canonicals
Old robots.txt blocking AI crawlers by accident

12. Local business technical SEO checklist

Server-rendered HTML for service & location pages
LocalBusiness schema validating across all locations
Sub-2s LCP on mobile
HTTPS with valid certificate
Clean URL structure (/services/[service]/, /locations/[city]/)
Sitemap submitted; AI bots allowed in robots.txt
No orphan service or location pages
Breadcrumbs with schema on every non-home page