Article
Do I need to rebuild my website to do AIO?
What actually needs to change on the site to be cited by AIs — and what can stay as is
Rebuilding your website is not a prerequisite for doing AIO. Most companies can implement the necessary changes on top of their current CMS — whether WordPress, Drupal, HubSpot CMS, Sitecore, Adobe Experience Manager, or proprietary platforms — without a platform migration. What AIO requires are three adjustment layers that exist independently of the platform: structured data (Schema.org), ensuring that content is accessible in HTML without JavaScript execution, and a content strategy oriented toward RAG citability. None of these three layers require rebuilding the site.
When the current site is sufficient
The current site is sufficient for AIO when:
- The content of strategic pages is available in static HTML (without depending on JavaScript to appear)
- It's possible to add JSON-LD blocks in the
<head>or<body>— which virtually all modern CMSs allow via plugin or customization - The CMS allows editing meta tags and creating new content pages
- The site is live on HTTPS with basic contact and about information
This is the situation for the vast majority of corporate websites at medium-to-large enterprises. The platform is rarely the bottleneck.
When the platform can be an obstacle
Some scenarios where the platform creates significant limitations for AIO:
100% SPA (Single Page Application) site without SSR:
If the site is a React, Vue, or Angular application that loads all content via JavaScript in the browser, AI bots that don't execute JS — GPTBot, PerplexityBot, ClaudeBot — arrive at an empty HTML shell. This is a serious problem that may require adding SSR or pre-rendering, depending on the platform.
CMS without JSON-LD customization capability:
Rare, but it exists. Some older proprietary platforms don't allow adding custom scripts to pages. In this case, Schema.org implementation is limited to what the CMS natively offers.
Content in PDFs or legacy formats:
Relevant technical content (white papers, product specifications, implementation guides) available only as PDFs is not processed by AI bots the same way HTML is. Migrating this content to HTML pages is recommended — but doesn't require rebuilding the site, just creating new pages.
What needs to change on any platform
Schema.org via JSON-LD
On any CMS, it's possible to add JSON-LD in page templates. In WordPress, plugins like Yoast, Rank Math, or Schema Pro handle this. In enterprise CMSs like Sitecore or Adobe Experience Manager, JSON-LD can be added by the development team to the base template.
For large companies with hundreds of product pages, implementing Schema.org at scale may require automation — generating JSON-LD dynamically from product or service data already stored in the CMS.
Rendering of strategic content
Checking which strategic content is available in HTML without JS is the first technical diagnostic. Tools like view-source: in the browser or Bing Webmaster Tools (which shows how Bing renders the site) reveal what bots actually see.
RAG-structured content
This is platform-independent: heading structure, paragraph semantic density, and the presence of concrete data depend on how content is written — not on which system hosts it.
Cases where rebuilding the site makes sense in the AIO context
There are situations where a platform modernization, already planned, can be leveraged to implement AIO from the ground up on the new platform:
- Legacy site migration to a modern SSR platform (Next.js, Nuxt) — ideal for implementing AIO by default across all templates
- Information architecture revision — opportunity to reorganize content into thematic clusters from the URL structure up
- Site redesign with the goal of increasing lead generation — AIO can be incorporated as a success criterion from the project start
In these cases, AIO isn't the reason to rebuild the site — it's a discipline that leverages the rebuild to be implemented correctly from the beginning.
FRT Digital evaluates the technical state of your site and defines the AIO implementation path with the minimum change effort possible, as part of the AIO Score Audit. Learn about the AIO service.