Seryvon FAQ: availability, scoring and self-hosting
Evaluate Seryvon with clear expectations about what the open core does, how to interpret its evidence and what the coming-soon managed offering means. These answers link to the detailed guides and implementation where a short answer needs context.
What is Seryvon?
Seryvon is a web visibility audit tool published by Powehi. It groups technical, content and agent-facing checks into five pillars: SEO, GEO, GSO, AEO and ASO. Its purpose is to make findings inspectable and useful for prioritisation. Start with the product overview for the complete workflow.
Can I use it today?
The public repository contains an open-core implementation for self-hosted evaluation. The managed product is coming soon. Running the source locally is different from receiving access to an operated service. Consult the quickstart for setup and the status page for configuration-dependent capabilities.
What does “open core” mean here?
The repository contains the audit core and publishes its license. The project distinguishes this from its planned operated offering. You can inspect the rules and implementation directly. Read the repository's license and third-party notices when assessing your own use or distribution.
Does a high score mean I will rank or get cited?
No. A score summarises measured criteria under Seryvon's rules. It is not a Google score, a probability of citation or a guarantee of traffic. Readiness checks and provider observations answer different questions. Use the limitations guide before reporting results to a client or using them to approve a release.
How can scoring be deterministic if AI responses vary?
Fixed signals, rules and configuration produce a repeatable calculation. A fresh crawl or provider response can change the inputs. Keep the measurement profile and source evidence to explain differences. Determinism applies to scoring; it does not make a remote website or an AI service return identical data over time.
Do I need API keys for every audit?
No. Some checks use information collected from the target website. Additional measurements depend on configured providers. Citation tracking supports provider-specific credentials, and missing credentials leave the associated checks unmeasured. Bring your own key means you supply the account access and remain responsible for provider usage charges.
Why does my report say “not measured”?
The criterion lacks the data it needs. Check the recorded reason, connector configuration, request outcome and crawl scope. The criterion is excluded from the score while remaining relevant to coverage. It is not a zero, a pass or a finding to silently discard. The methodology explains the difference from “not applicable”.
Can it inspect JavaScript websites?
The source contains an optional Playwright rendering path. It requires a suitable browser runtime and configuration. A static response can differ from rendered content, and rendering does not automatically cover authenticated pages or every interaction. Choose a representative target and inspect the evidence before assuming full site coverage.
Are ASO and app store optimisation the same?
No. Seryvon uses ASO to mean Agentic Search Optimization: signals relevant to software agents discovering and interpreting a website. Its static checks do not prove that an agent successfully completed a transaction. Read the ASO pillar guide for the exact scope.
How do I choose my next action?
Start with a finding that affects an important page and has clear supporting evidence. Confirm it, assign an owner, implement the fix and verify the deployed page. Rerun a comparable audit, then evaluate traffic or conversion outcomes independently. The illustrative report shows how to keep evidence, actions and limitations together.
Need to discuss a specific evaluation? Contact Seryvon with your use case. Check the security guide before sharing credentials or opening a self-hosted service to other users.