Ask the hard question first.

The scan loads the public homepage in desktop and mobile browser contexts, records visible action and trust signals, and runs 43 published checks across 8 source categories. Those checks cover crawler access, structured data, markup, security, email posture, consent, technology, and SEO metadata. It does not submit forms or enter private systems. The methodology page is the public registry.

No. SEO metadata is one source category. The scan also records rendered mobile behavior, visible action paths, broken links, performance, accessibility, security posture, crawler access, structured data, and other public signals. It does not track keyword rankings or backlinks.

No. Revvye records observable public-path conditions and detected failures. It cannot know conversion rate, lead quality, bookings, or recovered revenue without the operator's private analytics and financial systems. Implementation and outcome measurement remain separate work.

No. The scan checks declared crawler access and machine-readable public signals such as structured data and markup. It cannot confirm that an answer engine crawled, indexed, selected, or cited the page.

No guarantee. Fixing a detected access, markup, or structured-data problem can remove an observable barrier, but selection still depends on the engine, prompt, source set, and user context. Revvye does not control those systems.

Sometimes. Some fixes are copy and structure changes any operator can ship. Others (schema, robots.txt, rendering pipeline) usually want a developer or a CMS-aware team. The roadmap and review tiers exist for operators who want a clearer hand-off plan.

Yes, through a separately scoped Revenue Sprint. The scan itself does not change a website. Approved implementation scope, access, timeline, and verification are handled as a services engagement after the findings are reviewed.

Public-only is a deliberate boundary. It means the scan is reproducible, the results are fair, and we never store credentials or touch private systems. The price of that boundary is real: Revvye does not see your CRM, your internal analytics, your booking platform internals, or your payment data. The methodology page covers this in detail.

Most scans complete in a few minutes. Heavier pages take longer because the scan runs full performance and accessibility audits in a real browser. The result is delivered to a private result link and, if you have an account, attached to your saved scans.

No. The scan is read-only against public surfaces. Revvye does not bypass authentication, does not request credentials, and does not interact with private dashboards, CRMs, payment processors, or PHI-bearing systems.

It evaluates the submitted public page against robots.txt, served meta directives, and the X-Robots-Tag response header for the named crawlers Revvye tracks. It records declared access or blocking; it cannot confirm that an engine fetched, indexed, or cited the page.

Yes. The scan reads public pages, so the same scan can be run against a competitor exactly the way it runs against you — we treat that as a feature; it keeps the diagnostic honest. You are responsible for lawful use: Revvye only reads public pages a visitor or crawler could already see, never bypasses access controls, and may rate-limit targets. Some jurisdictions or contracts may restrict automated analysis. Our Terms cover this in full.

Account data (email, name, company), the URLs you submit for scanning, the public-page HTML and metadata our scanner fetches from those URLs, payment metadata returned by Stripe (we never see card numbers), and website analytics from Google Analytics 4. Product-usage events are written to our own database, not a third-party analytics SDK. We scan public pages only; we do not access password-protected content. The privacy page lists every category, every sub-processor (Supabase, Stripe, Cloudflare, Google Analytics 4, Brevo), and how long each is retained.

Yes. Email privacy@revvye.com with the request and we will verify your identity and delete account and scan data within 30 days. Some records (financial records, dispute history) we are legally required to retain — we will tell you what was kept and why. Scan data is also automatically purged 12 months after the scan unless you have an active paid order tied to it.

No. We do not sell personal information and we do not share it for cross-context behavioral advertising. The only third parties that touch your data are the sub-processors that operate the platform — Supabase (database, auth, storage), Stripe (payments), Cloudflare (hosting and the scan worker), Google Analytics 4 (website analytics), and Brevo (transactional email). We may use anonymized, aggregated patterns to improve methodology, but those aggregates cannot be re-linked to your account. The privacy page is authoritative.

No. The intake does not require an account. The private result link is the canonical receipt. An account can retain scans that are attached or claimed through the supported access flow.

If the scan is attached to your account, sign in and open the saved scan. Otherwise, contact support with the submitted domain and approximate scan date. Access still requires matching the stored scan record; support cannot recreate a result from memory.

The free scan returns a revenue-capture score, a total leak count, a severity breakdown, the top problem categories, and a recommended next step. That is enough to decide whether the paid report is worth it.

The $97 Full Revenue Report unlocks the complete findings available for that scan, including named rules, observed evidence, explanations, severity, and the affected public surfaces recorded by the scanner. The private report route is canonical; export availability is shown there rather than promised here.

After checkout, the unlock is attached to the original scan. The private result link starts showing the full report. If you created an account at checkout, the unlock also appears in your account history. If you used checkout without creating an account, the private result link is the canonical access path; treat it like a receipt and save it.

During our launch phase, yes — within 30 days of purchase, no questions asked. Email support@revvye.com with your order number. We're being generous on purpose; we'd rather have happy users telling us what didn't work than fight over chargebacks. Subscription products (Revvye Monitor) can be canceled at any time and you won't be charged for the next period; we don't pro-rate the current period. The terms page is the authoritative source and explains the launch-phase posture in full.

Approved refunds are issued to the original payment method through Stripe. The time required for a bank or card issuer to post the credit is outside Revvye's control. Email support@revvye.com with the order number if the Stripe refund record needs to be traced.

Yes, when sharing is enabled for the scan. Treat any private or shared result link like an unlocked artifact: anyone who receives a working link may be able to see the permitted report surface. The report route shows the current sharing and export controls.

There is a per-account quota that prevents abusive use. Most operators do not hit it. Revvye Monitor is the prelaunch recurring-monitoring product; until that loop is live, manual rescans are the available path.

That is a useful answer. The score is meant to tell the truth, not always sell something. If the public surface is already clean, the right next move is usually monitoring drift over time, not buying a sprint.