# SEO is table stakes. GEO is the moat.

*By The Strand CMS Team · 2026-06-14 · 1 min read*

Canonical: https://www.strandcms.com/blog/seo-is-table-stakes-geo-is-the-moat

> **Summary:** GEO needs content in the server's HTML, clean extractable Markdown, structured data, and cited sources - and MDX-in-Git is unusually well suited to all of it.

Classic SEO is now the price of entry. The differentiator is whether ChatGPT, Perplexity,
Claude, and Google's AI Overviews can read, trust, and cite you. That is **GEO**, and it
has concrete requirements.

## Content has to be in the HTML

AI crawlers largely do not run your JavaScript. If your article is assembled client-side,
it is invisible to them. Static generation or server rendering - content in the initial
HTML response - is non-negotiable. This is why Strand CMS keeps the crawlable surface static.

## Give machines clean source

MDX is already the format models ingest cleanly. Strand CMS serves a content-negotiated `.md`
of every page and publishes `llms.txt`, so an assistant gets your prose, not your markup.

## Structure and citations build trust

`FAQPage` and `speakable` schema, author-entity markup, and visible cited sources all
raise the odds that an engine quotes you accurately. Cited claims travel further.

## Why MDX-in-Git fits

The same files that render your site are already clean, structured, and diffable. GEO is
not a bolt-on for Strand CMS; it falls out of the content model.

## FAQ

**What is GEO?**

Generative Engine Optimization: making your content easy for AI search engines and assistants to ingest, trust, and cite.

**Does serving content from an API hurt SEO?**

The indexed surface must be in the server's HTML - static or server-rendered, not assembled client-side. A JSON API for app consumers is a separate channel.

## Sources

- [llms.txt proposal](https://llmstxt.org)