How aiseo-audit configuration works: overview

The configuration is a project-level record of the inputs and defaults shared by repeated audits.

The command searches upward for a supported file name, loads the first match, and then applies explicit command options as overrides.

A shared file prevents accidental drift because people and automated jobs start from the same settings. This means a stored baseline remains easier to reproduce and explain.

aiseo-audit configuration: queries, weights, stages, and history terms

Configuration file

A configuration file refers to a JavaScript Object Notation file that stores audit defaults.

Query list

A query list refers to the audience questions used for query alignment.

Page profile

A page profile means that product and informational pages receive the checks suited to their purpose.

Category weight

A category weight is defined as the relative influence of one audit category.

Stage weight

A stage weight refers to the relative influence of one pipeline stage on the overall score.

History directory

A history directory is a type of local storage used by comparison runs.

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.

How to use this reference

Create one supported configuration file at the project root.
Record the target queries and page profile.
Keep default weights unless the project has a documented reason to change them.
Run representative pages and save their baselines.
Review the file whenever the team changes a major tool version.

Key takeaways

The file is discovered from the working directory upward.
The option is the final override when it conflicts with the file.
The limit is ten queries and a focused set is easier to maintain.
The weight is relative, so changing one value changes category influence.
The directory is required only for stored comparisons.

Bottom line: Keep one reviewed configuration beside the project so every run starts from known inputs.

Official sources and verification

According to the npm package page, aiseo-audit publishes its current version and installation command [1]. According to the GitHub repository, the source code and project documentation are public [2].

According to the evidence map, every scored factor records an evidence tier and pipeline stage [3]. According to the release history, major versions document scoring changes that require new baselines [4]. According to the project license, aiseo-audit uses the MIT license[5].

aiseo-audit on npm: package, version, and installation details.
agencyenterprise/aiseo-audit: source code and documentation.
aiseo-audit evidence map: factor tiers, stages, and research sources.
aiseo-audit releases: version history and migration notes.
MIT license: project license text.