Download the PHP package calevans/answer-engine-optimization without Composer
On this page you can find all versions of the php package calevans/answer-engine-optimization. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download calevans/answer-engine-optimization
More information about calevans/answer-engine-optimization
Files in calevans/answer-engine-optimization
Package answer-engine-optimization
Short Description StaticForge Feature: AnswerEngineOptimization
License MIT
Informations about the package answer-engine-optimization
AnswerEngineOptimization
A StaticForge feature package that optimises your site for AI-powered answer engines (LLMs, RAG pipelines, AI search). It handles structured data injection, llms.txt generation, AI-bot robots.txt rules, and data-driven FAQ schema — all automatically as part of the StaticForge build pipeline.
Installation
feature:setup copies this package's siteconfig.yaml.example into your site root as siteconfig.yaml.example.answer-engine-optimization — merge the keys you need into your site's real siteconfig.yaml.
This plugin does not generate your site's identity schema (Organization/LocalBusiness/PodcastSeries/etc.). That data — your business name, address, social profiles — doesn't change per page or per build, so it belongs as a single hand-written JSON-LD <script> block in your theme's <head> partial, not in build-time plugin config. This plugin only handles things that genuinely vary per page or need aggregating across a build: Article/BreadcrumbList/FAQPage schema, llms.txt, the AI-bot robots.txt allowlist, and the .md mirror.
Features
| Feature | Description |
|---|---|
AI-bot robots.txt |
Adds Allow: / rules for OAI-SearchBot, ChatGPT-User, Google-Extended, Anthropic-ai, and Claude-Web |
| Article JSON-LD | Injects Article structured data into every page <head> (headline/dateModified/publisher fields are omitted, not fabricated, when the underlying data is unavailable) |
| BreadcrumbList JSON-LD | Injects BreadcrumbList structured data on all non-home pages |
| FAQ JSON-LD | Injects FAQPage structured data from frontmatter, [faq] shortcodes, or a shared JSON data file |
llms.txt |
Generates a site-wide llms.txt index for AI crawlers, with a titled header and per-page descriptions |
llms link tag |
Injects <link rel="llms" href="/llms.txt"> into every page <head> |
.md copy |
Publishes a stripped Markdown copy of each page alongside its HTML output |
Configuration
siteconfig.yaml
All keys are optional. The package works with sensible defaults when they are absent.
Identity schema belongs in your theme, not here
Organization, LocalBusiness, PodcastSeries, or whatever schema.org type
identifies your site as an entity is the same on every page and every build —
it's not build-pipeline data. Add it once as a JSON-LD <script> block in your
theme's <head> partial. Example for a podcast site:
Per-page frontmatter
FAQ data file
When answer_engine_optimization.faq_data_file is configured (or the default content/assets/faq.json exists), the package loads a shared bank of FAQs that can be referenced from any page via data-faq HTML attributes.
content/assets/faq.json
Reference an entry in your Markdown by adding a data-faq attribute to any HTML element:
The matching entries are automatically included in the FAQPage JSON-LD schema for that page.
Priority order for FAQ sources
FAQs from all three sources are merged in this order:
aeo.faqsin page frontmatter[faq question="…" answer="…"]shortcodes in page contentdata-faq="id"references resolved from the shared JSON data file
Priority order for llms.txt summary
The per-page summary line in llms.txt is resolved in this order:
aeo.key_takeawaysin page frontmatter (author-written, highest priority)descriptionin page frontmatter- Empty string (the colon is still emitted; the AI crawler can infer context from the
.mdcopy)