Google’s John Mueller Clarifies Markdown Pages for Developer Docs, Not for Non‑Developer Sites
Focus on improving core SEO signals for non‑developer sites instead of creating markdown versions of content.
Focus on improving core SEO signals for non‑developer sites instead of creating markdown versions of content.
Summary
John Mueller’s recent Bluesky thread explains that markdown pages are useful only for developer documentation sites, where AI coding systems can parse reference material more efficiently. He argues that markdown is a temporary crutch to save tokens, as AI systems can read HTML just fine. For non‑developer sites, Mueller says markdown pages make no sense and will not drive more sales, even with future agentic traffic. He compares the distinction to calls to action, noting that markdown is not for SEO discovery. Mueller emphasizes prioritizing discovery and conversion rates over speculative agentic optimization. He also notes that Google Search and Lighthouse guidance diverge on llms.txt, adding to the confusion. Mueller’s comments carve out an exception for developer documentation while holding the line for all other site types. The thread underscores that the industry should focus on core SEO signals rather than preparing for a future that may or may not materialize.
Key changes
- Markdown pages are only useful for developer documentation sites, not for non‑developer sites
- Markdown is a temporary crutch to save tokens for AI systems
- For non‑developer sites, markdown pages are unnecessary and will not drive sales
- Mueller compares markdown to calls to action, not for SEO discovery
- He emphasizes prioritizing discovery and conversion over speculative agentic optimization
- Google Search and Lighthouse guidance diverge on llms.txt, adding confusion
- Mueller’s comments carve out an exception for developer documentation
- The industry should focus on core SEO signals rather than preparing for a future that may or may not materialize