Documentation
Configuration
Set the queries, page profile, scoring weights, and history location for your project.
Jeff Patterson / Agency Enterprise. Updated August 30, 2026.
Config discovery
The command-line tool searches upward from the current directory for aiseo.config.json, .aiseo.config.json, or aiseo-audit.config.json. It stops at the first match. Pass --config to use a specific file.
Keep the file small and place it near the project code. Give the team one source for page queries, score rules, report paths, and saved runs. When a result shifts, check the file before changing the gate.
Representative configuration
{
"queries": ["how to audit ai seo", "ai seo evidence"],
"domain": "auto",
"engine": "generic",
"format": "pretty",
"weights": {
"answerability": 2,
"groundingSignals": 2,
"queryAlignment": 2
},
"historyDir": "./audits"
}Important fields
| Field or option | Description |
|---|---|
queries | Up to ten target queries. A focused set of five gives a stable coverage view. |
domain | auto, product, or informational. |
engine | An experimental category-weight overlay. |
weights | Relative category weights; missing keys default to 1. |
stageWeights | Optional overall-score calculation from the four stage percentages. |
historyDir | Storage location used by --diff. |
Calibrate thresholds
The tool sets no universal fail-under value. Record baselines for your own pages with a stable version and query set. Then choose a threshold that catches useful regressions without encouraging score chasing.