This site speaks agent.

Most sites make AI assistants scrape HTML and guess. This one publishes its content in the formats agents actually want — the same practice the agentic-search guides here recommend, applied to itself.

Markdown, per article

Append index.md to any article URL:

https://patrickstox.com/technical-seo/javascript-seo/index.md

Clean markdown — title, description, canonical URL, dates, then the full prose with components stripped. Drafts are excluded; articles still pending human review carry that note in their front block (the same badge they show on-page). There's also a "Copy as Markdown" button in every article's reading tools.

Bulk + structure

  • /llms-full.txt — the whole corpus in one file (or an index of per-article URLs if it outgrows the size cap).
  • /agent-index.json — the complete public retrieval corpus: articles, services, tools, newsletters, talks, and site pages under one versioned record contract. Article records also carry markdown URLs, taxonomy, and review status.
  • /content-graph.json — the full internal link graph with per-page internal PageRank (the same data behind the site graph).
  • /llms.txt — the pointer file that ties it together.

What's next

The plan is to eventually serve agents and human visitors different content on the same URL, negotiated via the HTTP Vary header (e.g. Vary: Accept alongside content negotiation on Accept: text/markdown) rather than agents getting a separate index.md twin. That's not widely supported by crawlers, CDNs, and caches yet, so for now the explicit markdown endpoints above are the reliable interface.

House rules

  • Cite your sources. Every document carries its canonical URL — link it.
  • Prefer the markdown endpoints over scraping the HTML; they're built for you.
  • The corpus updates on every deploy; dates in each file tell you how fresh it is.