AI agents: fetch the documentation index at llms.txt. Markdown versions are available by appending .md to any page URL, including this page's markdown.
Learn how Blode.md generates robots.txt, sitemaps, llms.txt exports, and per-page meta tags so search engines and AI crawlers can index your docs.
| Auto-generated |
| Complete documentation content in plaintext format. |
| Yes |
/{page}.md | Auto-generated | Individual pages in Markdown format for programmatic access. | Yes |
The llms.txt and llms-full.txt files follow the emerging llms.txt
standard for making documentation accessible to large
language models.
Append .md to any page URL to get its Markdown export. For example,
/docs/quickstart becomes /docs/quickstart.md.
By default your site publishes at its Blode.md subdomain, or at your custom
domain once you add one. If you put a proxy in front: serving docs from
yourdomain.com/docs while we see acme.blode.md: declare where the site
actually lives:
{
"seo": {
"siteUrl": "https://yourdomain.com/docs"
}
}Include the path prefix if you serve under one. Canonical tags, og:url,
JSON-LD, the sitemap, llms.txt and the .md alternates are all built from
this one value, so they stay consistent no matter which URL a request arrives
on.
You only need this when something sits between your readers and Blode.md. A proxy is invisible to us: a proxied request is indistinguishable from a direct one: so it is the only case we cannot work out on your behalf.
Control how search engines index your site with the seo.indexing option in docs.json:
{
"seo": {
"indexing": "all"
}
}| Value | Behavior |
|---|---|
"all" | All pages are indexed. Page-level noindex frontmatter is ignored. |
"default" | Pages with noindex: true in frontmatter are excluded from indexing. |
To exclude a specific page from search engine indexing, add noindex: true to its frontmatter:
---
title: Internal notes
noindex: true
---
This page will not appear in search engine results.Enable last-modified metadata with the metadata.timestamp option. This adds <meta> tags and updates your sitemap entries with accurate dates:
{
"metadata": {
"timestamp": true
}
}Timestamps are derived from your deployment history. Each page's last-modified date reflects the most recent deploy that changed its content.