An open-source SEO audit you can inspect and automate
Seryvon’s open core provides an inspectable foundation for website audits across SEO, GEO, GSO, AEO and ASO. It is in active development. The managed product is coming soon. For technical evaluators, the value of the repository is the ability to examine how signals become findings and how those findings contribute to a score.
Built for reproducibility
- Deterministic scoring for the same input signals and configuration.
- CLI and Docker workflows for evaluating the development version.
- JSON, HTML and Markdown reports for review and processing.
- Bring-your-own-key configuration for supported external providers.
The scoring engine is available for inspection. It excludes unavailable criteria from the measured average, then applies coverage to pillar scores. This distinction matters: “not measured” means no observation was supplied, but it can still affect the final score through reduced coverage. It is not an estimated measurement.
Evaluate the source before adopting a workflow
Begin with the repository README and the quickstart. Use the documented environment setup and migrations for your chosen deployment. External services may require credentials; you should understand which connectors are configured before interpreting the first report.
The CLI source defines seryvon run https://example.com for a full audit and seryvon aso https://example.com for an agent-readiness audit. These are illustrative targets. Use a site you are authorized to inspect and review the crawl settings for that environment.
For citation evaluation, seryvon citations https://example.com --dry-run allows you to review the planned run before making provider calls. Bring-your-own-key access means you supply the relevant credentials; it does not make external API usage free or remove provider limits.
Make an audit reviewable
Keep the report and configuration together. Inspect the affected pages and the underlying criterion before implementing a recommendation. For example, a metadata finding should lead to a review of the relevant template and intended page identity, rather than an automatic replacement of every title.
If you run the audit again, use the comparison logic to understand whether the profiles support a meaningful score comparison. A changed rule catalog, threshold or provider configuration can change the meaning of the result. Deterministic calculation does not mean that websites and external responses remain unchanged between runs.
Open core and operational responsibility
The repository identifies Powehi as publisher and distributes the core under AGPL-3.0-or-later. Read the repository license and third-party notices when evaluating reuse. The presence of open-core code does not establish availability of the separate managed offering.
Self-hosting also leaves operational decisions with you: where the service runs, how credentials are supplied, which targets it can access and how reports are retained. Read the security guidance before deploying. Neither a successful installation nor a high audit score guarantees search rankings, citations or business outcomes.