Agent-Readable Content Model
How to shape AstroWEBTheme content so humans, search engines, and AI agents can read it reliably.
Agent-readable content is written for people first, but structured so software can understand, cite, and route it.
AstroWEBTheme supports this with stable URLs, frontmatter, collection metadata, RSS, sitemap, taxonomy pages, schema, and LLMS exports.
Minimum Content Contract
Every important page should have:
- a clear
title - a useful
description - a stable
slug - a
publishedDate - a
lastModifieddate - taxonomy fields such as
tags,categories, andsubjects index: truesearch: truesitemap: truerss: truewhen the content belongs in feedsllms: "full"when the content is important for agents
Good Page Structure
Use headings that describe the actual content:
- what the page explains
- who it is for
- when to use the feature
- how to configure it
- how to verify it
- what can go wrong
Avoid vague headings such as “Overview” when a more specific heading would help.
LLMS Guidance
Use llms: "basic" for normal indexable content.
Use llms: "full" for:
- installation guides
- API or schema references
- important feature pages
- pricing or service explanations
- live content examples
- security documentation
Use llms: "none" or llms: false for private, low-value, duplicate, or temporary content.
Why Taxonomy Matters
Tags, categories, and subjects help agents understand relationships between pages.
For example:
agentic-webcloudflared1r2securityinstallation
These terms can power tag pages, related content, search facets, and retrieval workflows.
Keep Content Useful Without JavaScript
Important page meaning should exist in HTML and text, not only in client-side interactions. Agents and crawlers should be able to understand the page from the rendered document.
Use interactive components for enhancement, not as the only place where content exists.
