Making My Blog Readable by AI Agents
The author describes making their static blog readable by AI agents: every post is also available as plain markdown via a .md suffix or an Accept: text/markdown header, with Vary: Accept and canonical/noindex headers to avoid duplicate-content issues. They add an llms.txt index and llms-full.txt, a homepage markdown version, an explicit robots.txt allowing major AI crawlers, JSON Feed entries with markdown URLs, fuller meta and JSON-LD tags, generated descriptions, and an IndexNow ping script for Bing.
Open original source deallocatedobjects.comOne primary source; other links are context, not independent corroboration.
- Primary sourceHacker News · AI
- Discovery linkHacker News
- Linked in source/llms.txt
- Linked in source/llms-full.txt
- Linked in sourceJSON Feed
- Linked in sourceIndexNow
A community post points to the original link. Discussion and upvotes do not establish accuracy.
- Community discussion+5
- Fetched source page+30
- No editor link review0
- Community link0
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
The author describes making their static blog readable by AI agents: every post is also available as plain markdown via a .md suffix or an Accept: text/markdown header, with Vary: Accept and canonical/noindex headers to avoid duplicate-content issues. They add an llms.txt index and llms-full.txt, a homepage markdown version, an explicit robots.txt allowing major AI crawlers, JSON Feed entries with markdown URLs, fuller meta and JSON-LD tags, generated descriptions, and an IndexNow ping script for Bing.
Key findings from the stored brief
- Any post can be fetched as markdown by adding .md or sending an Accept: text/markdown header.
- Responses send Vary: Accept so caches do not mix HTML and markdown, and .md responses carry a canonical link and noindex tag.
- The site adds /llms.txt and /llms-full.txt to describe content and list posts for agents.
- robots.txt explicitly allows named AI crawlers and includes a Content-Signal line permitting search, ai-input and ai-train.
Source claims not independently checked; the post describes one author's static nginx setup and does not measure agent adoption or citation outcomes.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
Agents increasingly fetch web pages to answer user questions, so publishing clean markdown and machine-readable indexes can make a site easier to cite and read accurately, while headers prevent duplicate-content penalties in search.
Limits and open questions
Source claims not independently checked; the post describes one author's static nginx setup and does not measure agent adoption or citation outcomes.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Discussion
Comments are reviewed before publication. Discuss the evidence, not the person.
No published comments yet.
Reader discussion opens with accounts. You can read the original source and published comments now.