GEO quickstart: 5-minute local dev environment
The shortest path to getting GEO running — a minimal starting point for first-time users.
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-quickstart.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. The fastest path to a win is one command to scaffold, start dev, edit a line, and see hot reload.
// 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 Quickstart · Key takeaways
- Node ≥ 20.19 and pnpm ready
- Official scaffold initialized
- Dev hot reload works
- First local page reached
FAQ & pitfalls
Why does dumping full text into llms.txt get me downranked?
AI crawlers prefer summaries plus canonical URLs; a full-text dump is judged low quality. llms.txt should be a map — details live on the destination pages.
Explore the hub
See all 5 guides in ArchitectureSame category as this article, sorted across the codebase.
AI Search quickstart: 5-minute local dev environment
The shortest path to getting AI Search running — a minimal starting point for first-time users.
Astro pSEO at scale: architecture and hands-on guide
From zero to a self-generating long-tail landing page architecture using Astro plus structured data.
Astro quickstart: 5-minute local dev environment
The shortest path to getting Astro running — a minimal starting point for first-time users.
Cloudflare Pages quickstart: 5-minute local dev environment
The shortest path to getting Cloudflare Pages running — a minimal starting point for first-time users.
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 →