Revenue is the result of many small decisions working together. A site diagnostic helps you see the technical and configuration details behind that result. The useful next step is to connect each finding to evidence, an owner, and a change you can measure.
Use the diagnostic to decide where to look. Use your own reporting to decide what a fix is worth.
Start with a baseline you can trust.
Choose the domain and the pages you want to investigate. Include the main page types your visitors use, such as articles, landing pages, and category pages. Look at the experience on both a narrow and a wide screen.
Keep a record of the metrics you already have. Fill rate, viewability, average CPM, revenue per session, monthly pageviews, and monthly sessions can give the diagnostic useful context. Use the same date range when comparing figures.
- Choose representative page types.
- Record the date range and device mix.
- Save the current ad configuration before making changes.
Run the diagnostic in your workflow.
Sulvo’s CLI and MCP provide free access to site diagnostics. Start with a public publisher domain. The public audit endpoint does not require an API key; account reporting and inventory access use separate account permissions.
The CLI is a direct starting point from your terminal. An MCP connection lets a compatible AI client work with the audit. Neither path makes a public site scan a substitute for your account’s revenue reporting.
Open the developer quickstartTurn findings into a short worklist.
Read the supporting evidence before acting on a finding. Ask where it appears, whether you can reproduce it, and which team owns the configuration. Separate a technical issue from an opportunity that needs a controlled experiment.
Give each item a next action. A delivery problem may need an engineering investigation. An awkward placement may need a format review. Suspected lost impressions may need a closer look at the delivery path and recovery eligibility.
- Confirm the page and conditions where the issue appears.
- Assign an owner and a specific next action.
- Choose the metric that will tell you whether the change helped.
Close the loop after the change.
Recheck the affected pages and rerun the diagnostic after a fix. Confirm that the original issue has changed, then review your own reporting over a comparable period.
Keep the visitor experience in the review. A higher rate on one unit is only part of the picture. Look at delivery, viewability, and revenue per session together before expanding a format or configuration change.
Explore the product details
This guide draws on Sulvo’s product and developer documentation.
Sulvo CLI and MCP setupAudit inputs and API access