Where the checks came from
SEO Audit Agent is based on 190 audit items from an Excel worksheet and 102 Trello cards. They are the rules, order, and sequence that Mikhail K., an SEO specialist with 15 years of experience, developed in practice.
Mikhail K. previously ran audits manually: working through Trello cards in order, comparing measurable metrics and thresholds in Excel, and recording issues and recommendations. Those working methods are now published in SEO Audit Agent so AI can apply the same complete checklist step by step.
About Mikhail K. and his experience · Practical SEO videos on YouTube
The full lifecycle
- Create. The agent sends a domain to
start_audit, pins a ruleset version, and immediately returns a public URL such as/audit/XXXX-XXXX-XXXX-XXXX, 0/N, and an outline of stages. - Open by link.
open_auditopens the same server-side log in a new ChatGPT, Codex, or Claude chat. No account or sign-in is required. - Queue.
get_next_checkreturns one item, its area, scenario, links, dependencies, and required evidence; the agent shows the number, title, and goal before it begins. - Check. The model uses HTTP, code, and SEO tools. Browser access to a rendered page is requested only after recording a specific reason: the item, site, public pages, purpose, and read-only mode.
- Save.
save_audit_progressrecords the observation, measurement, evidence, access checkpoints, and recommendation. The server calculates severity. - Repeat. Deferred and dependent checks return to the queue when their conditions are met; if access is denied, the partial report remains available.
- Report.
generate_reportcreates complete Markdown in the chat and structured data for all 183 applicable checks. The linked page is an additional interactive view.
Retention
An audit is automatically deleted 90 days after its last saved result change. Viewing the page or report does not extend this period. Save the link to continue; there are no accounts or lost-link recovery.
How rules change
A revised item creates a new immutable catalogue version. It is published to the MCP after review. New audits receive it automatically; active audits continue with their pinned version.