aicode8
Traffic & SEOUpdated: 2026-09-08

AI Search scaling: from a single page to a million

Horizontal scaling strategy for AI Search across huge page counts and high concurrency.

On this page

Quick answer

What are the hard requirements for FAQPage structured data?

Every Question needs an acceptedAnswer, and the Q&A must be truthful and verifiable. Fabricated answers get downranked by ChatGPT Search and Perplexity.

Machine-readable page data: /data/ai-search-scaling.json

In-depth analysis

AI search engines prefer structured Q&A (FAQPage) and a clear content hierarchy; plain prose rarely gets cited as the answer. Scaling is data-driven templates plus edge delivery — full SSG pre-render hands peak traffic to cache.

AI Search · Config example
// FAQPage node: feeds Perplexity / ChatGPT Search with answer pairs
{ "@type":"FAQPage", "mainEntity": [
  { "@type":"Question", "name":"...",
    "acceptedAnswer": { "@type":"Answer", "text":"..." } }
] }
Best practices:Pages are driven by one data source; full SSG pre-render hands the peaks to edge cache. Structured data covers every page to prevent duplicates.
Pitfalls:FAQPage answers must be truthful and verifiable — fabricated answers get downranked by AI engines. The homepage should expose an ItemList so engines can map your site's content structure. Drive pages from one data source instead of hand-maintaining each page, or structure drifts and duplicates appear.

AI Search Scaling · Key takeaways

  • Pages driven by a single data source
  • Build output fully static
  • Structured data covers every page
  • Edge cache load-tested

FAQ & pitfalls

How does AI search result cache update?

Update FAQPage and ItemList and rebuild static pages — engines pick up the new answers on their next crawl. No manual refresh needed.

Share & save

My shelf0
← Back to homeTopic: Ai Search Scaling

What readers are asking

Questions that keep coming back in reader feedback, already answered.

  1. 01
    What are the hard requirements for FAQPage structured data?

    Every Question needs an acceptedAnswer, and the Q&A must be real and verifiable — fabricated answers get downweighted by ChatGPT Search / Perplexity.

    See the full guide →
  2. 02
    Why is my Astro component's interactivity not working?

    Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.

    See the full guide →
  3. 03
    Why is my custom Tailwind v4 brand colour not applied?

    Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.

    See the full guide →
All questions →

Follow along as I build with AI

Get the honest, real-time record: what I build, what breaks, and what I learn — from a non-technical founder. No jargon, no fluff.

We respect your inbox. One click to unsubscribe, anytime.