GEO scaling: from a single page to a million
Horizontal scaling strategy for GEO across huge page counts and high concurrency.
Quick answer
Which schema.org version should JSON-LD use?
Always use the latest stable @context and keep node types (TechArticle, FAQPage) canonical. Outdated patterns get downranked by AI engines.
Machine-readable page data: /data/geo-scaling.json
In-depth analysis
GEO (Generative Engine Optimization) aligns your site with generative AI engines: clean JSON-LD plus a summarized llms.txt let large models cite your pages reliably. Scaling is data-driven templates plus edge delivery — full SSG pre-render hands peak traffic to cache.
// JSON-LD hardcoded in the page <head> (GEO rule: place centrally, SSG static output)
<script type="application/ld+json">
{ "@context":"https://schema.org", "@type":"TechArticle",
"headline":"...", "mainEntityOfPage": { "@type":"WebPage" } }
</script>GEO 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 often do AI engines re-index?
There is no fixed schedule. Keep llms.txt and sitemap fresh and structured data SSG-static so engines pick up updates whenever they crawl.
Explore the hub
See all 5 guides in Traffic & SEOSame category as this article, sorted across the codebase.
AI Search scaling: from a single page to a million
Horizontal scaling strategy for AI Search across huge page counts and high concurrency.
Astro scaling: from a single page to a million
Horizontal scaling strategy for Astro across huge page counts and high concurrency.
Cloudflare Pages scaling: from a single page to a million
Horizontal scaling strategy for Cloudflare Pages across huge page counts and high concurrency.
GEO in practice: optimizing for AI search engines and LLMs
How to embed canonical Schema.org structured data so large language models and AI search engines can pick up your pages precisely.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
Why is a full-length llms.txt being downweighted?
AI crawlers prefer a summary plus canonical URLs; padding it with the entire corpus reads as low quality. Keep llms.txt as a map and let the landing pages carry the detail.
See the full guide → - 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 → - 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 →