# LLMS Amplifier Artifact Schema — v1 - **URL:** https://brianwinum.com/llms-amplifier/schema/v1/ - **Published:** 2026-08-24 LLMS Amplifier Artifact Schema — v1 This page is the schema profile for the AI-readable files published by the LLMS Amplifier WordPress plugin. Sites running the plugin reference this URL in the Link: <…>; rel="profile" HTTP header on their artifact files and in the generator.schema field of their llms-index.json. Version policy: the v1 schema is stable. Changes are strictly additive — new optional fields and sections may appear, but existing fields never change meaning, type, or disappear. A breaking revision would be published at a new URL (…/schema/v2) and announced in the plugin changelog. The artifact family A site running LLMS Amplifier publishes some or all of these files at its public root (each also available under /.well-known/ where noted): PathMedia typePurpose/llms.txt (also /.well-known/llms.txt)text/vnd.llms-amplifier.manifest+markdownCurated content index in Markdown: what the site is, which pages matter, usage guidance/llms-full.txt (also /.well-known/llms-full.txt)text/vnd.llms-amplifier.full+markdownFull readable site content in Markdown (posts, pages, products, guardrails)/llms-index.json (also /.well-known/llms-index.json)application/jsonStructured machine-readable index — the document this schema primarily describes/llms-sitemap.xml, /llms-supplemental-sitemap.xmltext/xmlSitemaps for the artifact files and supplemental documents/.well-known/okfapplication/jsonPointer to the site's Open Knowledge Format (OKF v0.2) bundle of per-concept Markdown files under /okf/…Supplemental documents (site-chosen paths, .md/.json)text/vnd.llms-amplifier.supplemental+markdown or application/vnd.llms-amplifier.supplemental+jsonOwner-authored files: FAQ/PAA, glossaries, reviews, brand information llms-index.json — structure The index is a single JSON object. Two sections are always present: generator and files. Every other section is optional and appears only when the site has that data. generator (required) "generator": { "plugin": "LLMS Amplifier", "version": "2.7.2", "schema": "https://brianwinum.com/llms-amplifier/schema/v1", "generated_at": "2026-08-24T00:00:00+00:00" } files (required) A manifest of every published artifact with integrity fingerprints, so a consumer can verify it fetched exactly what the site generated: "files": { "manifest_version": "1.0", "resources": [ { "id": "llms-txt", "path": "/llms.txt", "also_at": "/.well-known/llms.txt", "type": "text/vnd.llms-amplifier.manifest+markdown", "rel": "alternate contents", "description": "Content index in Markdown", "size_bytes": 25029, "sha256": "…hex…", "last_modified": "2026-08-24T00:00:00+00:00" } ] } Supplemental-document entries additionally carry a category field (e.g. faq-paa, reviews, brand, custom). Optional sections SectionContentssiteSite identity: name, description, url (the public front end), language; optionally type, industry[], logo, founded, location (primary address object), locations[] (only when more than one), social (object of slug: url)summaryOwner-authored business summarypagesSelected pages/posts: title, URL, description, datesproductsCommerce catalog entries: name, URL, description, price + currency (numeric, raw stored prices), in_stock, sku where availablecontact, people, servicesContact channels, key people, service descriptionsfaq, reviewsOwner-curated Q&A and testimonial datapermissionsDeclared usage permissions, including ai_training; the value "see_content_signals" defers to the content_signals sectioncontent_signalsDeclared preferences per contentsignals.org vocabulary — keys search, ai-input, ai-train with "yes"/"no" values; only explicitly set signals are emitted. These are declared preferences, not technical enforcementdisambiguation, corrections, agent_guidance, brand_voice, proof_pointsAI guardrails: what the brand is/is not, factual corrections, how assistants should describe and cite the brandoffersCurrent offers with codes/URLs and validity windows Consumers should ignore unknown fields and sections — additive growth is the compatibility contract. HTTP headers on artifact responses Responses for the artifact files carry machine-readable Link headers: Link: <…/.well-known/llms-index.json>; rel="canonical" — the canonical index location Link: ; rel="about" — the site the artifacts describe (the public front end, which differs from the WordPress origin on headless installs) Link: ; rel="profile" — this page Link: ; rel="license" — only when the site opted into CC attribution Artifact responses are cookie-free and served with X-Content-Type-Options: nosniff. Sites choose whether artifacts are indexable; by default they carry X-Robots-Tag: noindex. Content negotiation (optional module) Sites may enable Markdown content negotiation: a request to a normal page URL with an explicit Accept: text/markdown header receives the page as Markdown (200, text/markdown, X-Robots-Tag: noindex) instead of HTML. Browsers and crawlers that don't ask for Markdown are unaffected. Schema v1 · Maintained by Brian Winum · Plugin changelog and releases: the LLMS Amplifier product page.