Flocon AI vs MDX files in Git
MDX or Markdown files in Git are free and simple: your AI (Claude Code, Cursor) writes a file, you commit and deploy. Flocon AI keeps SEO pages out of your code: your AI publishes through MCP, and the page is live on the next visit, with no commit and no redeploy. Pick MDX for a handful of pages you edit like code. Pick Flocon when SEO pages pile up or non-developers publish them.
Quick comparison
| MDX / Markdown in Git | Flocon AI | |
|---|---|---|
| Setup | Add MDX support to Next.js, build your layout and SEO metadata | One npm install (`@flocon-ai/next`) and one catch-all route |
| Where content lives | Files in your repo | Flocon, hosted for you |
| New page | Write file → commit → deploy | Your AI publishes → live, no redeploy |
| SEO features | Whatever you build (metadata, JSON-LD, sitemap) | Title, description, JSON-LD, OG image, FAQ blocks, sitemap and llms.txt helpers |
| Works from Claude/Cursor | Yes, any coding agent can write files | Yes, from any MCP client, even claude.ai chat |
| Price | Free | Free (10 published pages), Pro 5€/month, Business 29€/month |
| Best for | Few pages, rich layouts, code blocks | Many SEO pages, published from a chat |
Why I didn't use MDX for my SEO pages
"I needed something my agent could use without entering a cycle of pull request reviews for every page. And I wanted a small, efficient tool: I made the page data format myself, so agents understand it easily and it's easy to support more frameworks." — Alfred Gauthier, founder of Flocon AI
What each one does better
MDX is hard to beat for free, versioned content: any React component, code blocks, custom layouts, every change reviewed like code. With 5 to 10 pages and a developer on hand, it's a fine choice. We still use MDX for the Flocon docs, because Flocon has no code block. Flocon wins as pages pile up: no commit or redeploy per page, scheduled pages, drafts, and SEO parts (JSON-LD, sitemap, OG images) built in. You get fewer layout options in return: no image block, no custom components.
Is MDX bad for SEO?
No. MDX pages are normal HTML once built. SEO depends on what you write and the metadata you add.
Why not just let Claude Code write MDX files?
You can. It works well for a few pages. It gets slower when every page needs a commit, a review and a deploy, or when the person publishing isn't in the codebase.
Can I keep MDX and add Flocon?
Yes. Keep MDX for docs or blog, and serve SEO pages like comparisons from Flocon on a separate route.