Developers
For sites that deploy from GitHub
On the Strategist tier, the changes we make land as pull requests on a branch. One fix per PR, never a direct commit, evidence in the description. Your review and deploy do the rest.
How does AEOscore change a site that deploys from GitHub?
Fixes as pull requests
llms.txt, robots rules for AI crawlers, FAQ and answer blocks in your content directory, new pages from approved drafts. Merge tells us to re-check the answers at 7 and 28 days. Close the PR and the fix is marked declined.
Your data, your instance
Every customer runs on their own instance with their own database and backup bucket. Magic-link sign-in, no third-party auth. Security
Supported out of the box
Next.js, Astro, Hugo, Eleventy, Docusaurus and Jekyll are detected. Anything else takes a six-line aeoscore.yml naming the content and static directories.
aeo-check, a free Action
A GitHub Action that lints robots.txt AI-bot rules, llms.txt, JSON-LD on key pages and basic answer-readiness on every PR, and comments a summary with a link to your free score. On its way: this page links it the day it is on the Marketplace.
What it looks like
An example pull request
feat(aeo): answer block for “invoice software for UK sole traders” (AEOscore fix #14)
Why
“best invoice software for UK tradespeople” on ChatGPT and Perplexity names FreeAgent and Xero. Your /pricing page has no direct answer to the question buyers ask.
What this PR does
+ src/content/pricing.mdx: adds “Is this right for sole traders?” (210 words) and a FAQPage JSON-LD block.
No existing prose is changed or removed.
Facts to verify before merging
- “from £9 a month” (your pricing page, 2 Sept)
- “HMRC-recognised for MTD” (your /features page)
After merge
AEOscore re-checks this prompt at 7 and 28 days and reports what moved.
Want this on your site? It is part of Monitor + Strategist.