Plain answers about scans, reports, privacy, and refunds.

The scan reads your public website pages, the public booking path, on-page schema, sitemap and robots, the public review and trust surface, local profile signals where available, and the public crawler-access posture. It returns a leak summary across five categories: visibility, trust, booking, follow-up, and conversion. The full methodology lives at /methodology.

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.

No. SEO is one input. The scan also checks booking friction, trust gaps, weak service-page messaging, missing proof, local signals, follow-up gaps, and AI-facing crawler access. The score is built around revenue leaks, not search rankings.

Most scans complete in a few minutes. Larger sites with many service or location pages take longer because the scan walks more public surfaces. The result is delivered to a private result link and, if you have an account, attached to your saved scans.

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.

The free scan returns a Revenue Recovery 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 paid report unlocks the full leak list, the affected pages, evidence and explanations, severity tiers, schema findings, local trust findings, mobile conversion findings, follow-up gap analysis, and the prioritized next-step recommendation. PDF delivery is being completed as part of the prelaunch monitor build.

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.

Once we approve a refund we initiate it against the original payment method through Stripe the same business day. From there, bank and card processing typically takes 5 to 10 business days to appear on your statement, which is outside our control. If it has been longer than 10 business days, email support@revvye.com with your order number and we will trace it.

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), usage telemetry from PostHog, and error reports from Sentry. We scan public pages only; we do not access password-protected content. The privacy page lists every category, every sub-processor (Supabase, Stripe, Cloudflare, Sentry, PostHog), 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. 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.

Yes. The scan reads public pages. That means the same scan can be run against a competitor exactly the way it can be run against you. We treat that as a feature; it keeps the diagnostic honest.

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), Sentry (error monitoring), and PostHog (product analytics). 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. We do not promise inclusion in any specific answer engine. What the scan checks is whether your public posture would let those crawlers in if they tried, plus the schema and entity signals that decide whether your business shows up cleanly when they do. That is a real but bounded signal.

It is a check of whether your public site, robots.txt directives, and rendering pipeline would let well-known AI crawlers read the pages they would need to read in order to describe you in an answer. If those crawlers are silently blocked, that is a hard ceiling on visibility in the answer layer of search. The methodology page explains this in more detail.

Not directly, and we do not claim it will. Showing up in any specific answer experience depends on the engine, the prompt, the user's context, and many factors outside any single site. What the report does is remove the public-surface reasons your business cannot be cited. That is the part Revvye can actually measure.

No. Revvye does not guarantee rankings, leads, bookings, or revenue. It identifies the leaks most likely to be suppressing demand on your public surface. The implementation, the team, and the measurement still belong to the operator.

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.

The Revenue Sprint tier is the done-for-you path for operators who want help shipping the highest-impact items. It runs against the prioritized findings, with a named scope ceiling, and includes a follow-up scan after implementation.

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.

No. The free scan generates a private result link. You can save it like a receipt. If you create an account, scans you ran with the same email get attached to your account history, which makes them easier to find later.

If you used the same email for the scan, sign in to /account and the scan should be there. If you used a different email and never created an account, contact us with your business URL and the approximate date of the scan; we will help match it where we can.

Yes. The private result link is shareable, but treat it like an unlocked artifact: anyone with the link can see the report. Exported PDF access will appear once the report delivery lane is complete.