Retrofit or Rebuild?
Rebuilding a site to catch up on AI search feels like the obvious move. The data says it's usually the riskier one. Here's how to tell which your site actually needs — before you commit to either.
Last reviewed: July 28, 2026
What each path actually risks
None of that risk applies when the domain, URLs, and platform stay exactly as they are. A retrofit works within what already exists and already ranks — full sourcing and further data in the full write-up.
Two starting points, two very different risk profiles
Retrofit
- Your site ranks and gets real traffic today
- Content is real, crawlable HTML — not hidden behind heavy JavaScript
- Navigation and structure make sense to a visitor
- You want AI answer engines to cite you without risking what already works
Rebuild
- Content is hidden behind heavy JS rendering crawlers can't parse
- Architecture is genuinely confusing, not just dated-looking
- The current platform can't support basic structured data at all
- An audit confirmed the foundation itself is the problem
Same domain, same URLs, same rankings — plus this
| Addition | What it does |
|---|---|
| Structured data | FAQPage, Organization, and BreadcrumbList schema added to pages that already rank |
| Evidence-linked claims | Same-sentence proof links behind existing statements — tested to matter: 0/5 citations for promise-only claims vs. 3/6 for evidence-linked, across ChatGPT, Gemini, and Perplexity |
| llms.txt | A machine-readable site overview, added without touching a single existing page |
| Direct-answer blocks | Concise, quotable answers added under headings that already exist |
Should I rebuild my website to improve AI search visibility?
Usually not as the first move. Rebuilding changes your domain, URLs, or platform — exactly the kind of change search engines have to re-evaluate from scratch. Industry migration research puts typical post-migration traffic loss at 30–50%, with an average 17-month recovery. Retrofitting the existing site for AEO adds structured data, evidence-linked content, and machine-readable formatting without touching any of that.
When does a site actually need a rebuild instead of a retrofit?
When the technical foundation itself is broken — no crawlable HTML, content hidden behind heavy JavaScript rendering, or an information architecture too confused for AEO additions to have anything solid to attach to. That's a real, checkable audit finding, not a default assumption.
What does an AEO retrofit actually involve?
Structured data (FAQPage, Organization, BreadcrumbList schema) added to existing pages, same-sentence evidence links behind existing claims, a machine-readable llms.txt file, and direct-answer content blocks under existing headings — none of which require changing a domain, URL, or platform.
How do I know which one my site needs?
An independent, read-only audit checks the actual technical foundation before recommending either path — no production access required, and no assumption made either way until the site is actually reviewed.
Find out which one your site actually needs
An independent audit checks the real technical foundation first — before assuming a retrofit will work or a rebuild is required. Read-only, no production access needed.
Request an Audit →