Frequently asked questions

Buying

What does Pro cost?

Pricing for SiteReview Pro is published on the SteadyPress pricing page. Pro is sold as a credit pack — each completed Pro scan consumes one credit from your account.

How do scan credits work?

When you activate a Pro license on a site, that site can run Pro scans against your credit balance. Each completed Pro scan consumes one credit. Free scans on the same site do not consume credits. The remaining balance is shown in the license card under Settings > License. Top up by purchasing an additional credit pack from your SteadyPress account.

Do staging and dev sites use credits?

Yes. A Pro scan run from staging.example.com consumes one credit, the same as a scan from example.com. If you want to test the Pro flow on a staging copy without spending a credit, run the scan on Free first — the underlying measurements are identical.

What does the Free tier include?

The Free tier is permanent and produces a complete report. You can run SiteReview against your site as many times as you like on Free without ever entering a license key. Pro is an upgrade for AI narrative, deep theme analysis, inline editing, white-label, and token rotation — the underlying measurements are identical in both tiers.

Is there a refund policy?

Yes. The current refund terms are published at steadypress.ai/refund/.

Can I bundle SiteReview with PluginScore?

Both SteadyPress plugins are sold separately today. A bundle SKU is plausible but not currently part of the catalog.

Can I resell SiteReview reports to clients?

Yes — that is the primary use case. White-label on Pro removes every SteadyPress brand reference from the rendered report, so the deliverable can be presented as your agency's own work product.

Privacy and data handling

What data does SiteReview send to api.steadypress.ai?

The Free tier sends zero data to any SteadyPress server. Free is fully self-contained other than the public APIs the plugin queries directly (PageSpeed Insights, Mozilla HTTP Observatory, Sucuri SiteCheck, RDAP, DNS).

On Pro, the plugin sends:

• Measurements and findings from the report, sent to the AI narrative endpoint when generating the executive summary, recommendations, and section intros
• Theme source bundle, sent to the AI theme-analysis endpoint only when the active theme is unrecognized and you have consented (per-theme-version, default checked, revocable any time in Settings)

All requests are HMAC-authenticated against your license key. The server does not retain measurement data once a response is returned. Theme analysis responses are cached at (license_id, bundle_sha256) for 30 days so re-scans against unchanged theme code do not re-call the AI provider.

What does SiteReview never send anywhere?

• Site content — posts, pages, attachments, comments
• WordPress users, customers, orders, subscribers, or any visitor data
• Database contents
• wp-config.php or any credentials
• Source code of WordPress.org listed themes or plugins
• Source code of the active theme unless you have explicitly consented to theme analysis on Pro

What gets sent to Google?

Google PageSpeed Insights receives the URL of each page being audited and returns Lighthouse and Core Web Vitals data. Google's terms apply to this data. SiteReview does not send any other site contents to Google.

What gets sent to Mozilla?

Mozilla HTTP Observatory receives the hostname being audited and runs a battery of header tests against the public URL. Mozilla's terms apply.

What gets sent to Sucuri?

Sucuri SiteCheck receives the hostname being audited and returns malware and blacklist results.

Are findings, scores, or scan results ever shared with other customers?

No. Reports are written to your site's uploads directory. They are accessed by URL token. SiteReview has no central report database, no telemetry, no analytics, and no cross-customer data sharing.

How does PSI rate limiting affect scan speed?

A free Google API key gives you 25,000 PageSpeed Insights queries per day. A SiteReview scan uses up to 12 queries (up to 6 pages × 2 strategies for mobile and desktop). That gives you roughly 2,000 scans per day before hitting the cap — well outside normal usage.

A scan can still hit transient rate limits if Google's per-minute throttle (typically 240 queries per minute per key) is exhausted by parallel scans. SiteReview surfaces a rate-limit error in the Performance section and offers a Retry section affordance. Other sections complete normally.

What happens if I use SiteReview without a PSI key?

Google's shared anonymous quota is exhausted in seconds. PSI returns HTTP 429 immediately. The Performance, Mobile Friendly, and (partially) SEO sections fail or return degraded data. The rest of the report is still produced.

The onboarding modal exists to make sure you set up a free PSI key on first run; this takes about three minutes.

Is the report data ever stored on SteadyPress servers?

No. Report data lives only in your WordPress database and on your uploads directory. Pro narrative requests send measurements to api.steadypress.ai during generation but the server does not retain them after the response.

Sharing reports

Can I send the report to a client?

Yes. The public URL /sitereview-reports/{token}/ rewrites to a static HTML file. You copy the URL, paste it into an email or message, and the client opens it in a browser. No login is required.

Can my client edit the report?

No. The rendered report is read-only. Inline editing is a Pro feature that only works inside the WordPress admin on the install where the scan was run.

How do I stop a client from sharing the URL externally?

You cannot prevent re-sharing — the URL is a regular web URL accessible by anyone who has it. SiteReview offers two soft mitigations:

• An optional password gate (Free and Pro) hashed with PBKDF2-SHA256 (200,000 iterations) and embedded in the static HTML.
• Token rotation (Pro) issues a new URL and invalidates the old one immediately.

Reports include <meta name="robots" content="noindex, nofollow"> and an X-Robots-Tag header on Apache so they are not indexed by search engines.

What happens to the URL if I deactivate the plugin?

The static report file lives under wp-content/uploads/. The web server serves it directly without WordPress in the request path. Existing URLs continue to work even with the plugin deactivated.

The clean URL /sitereview-reports/{token}/ is rewritten by a WordPress rewrite rule and stops working on deactivation; the direct URL /wp-content/uploads/sitereview/reports/{token}/ continues to serve the file in both cases. Settings displays which pattern your install will use. If you plan to deactivate eventually, share the direct uploads URL.

Are reports indexed by Google?

No. Each rendered report includes <meta name="robots" content="noindex, nofollow"> and an X-Robots-Tag header set via a per-directory .htaccess file on Apache hosts. On nginx and IIS, where per-directory rewrite is not possible, SiteReview surfaces a settings notice with a snippet you can hand to your host.

Is the report GDPR-compliant?

SiteReview itself collects no personal data from site visitors and stores no data on SteadyPress servers. A rendered report contains technical findings about your WordPress site, not user data. GDPR obligations depend on what you share and with whom. Consult your data protection officer about specific use cases.

What about data residency?

SteadyPress servers (used only by Pro features) run in the US. The Free tier sends nothing to SteadyPress and is unaffected. If your jurisdiction requires that AI narrative generation happen inside a specific region, the Free tier is the recommended option — it produces a complete report without sending data to SteadyPress.

Operations

How long does a scan take?

Typical: 3 to 6 minutes for a 1 to 6 page scan. Worst case: 15 minutes for a six-page Pro scan with slow PageSpeed Insights responses. The estimated scan time indicator on the New Scan view updates as you add pages.

Can I leave the WordPress admin during a scan?

For seven of the eight sections, yes — they run server-side via Action Scheduler. The Accessibility section runs in your browser tab (axe-core needs a real DOM) and requires the tab to stay open. The scan-progress UI tells you this explicitly. If you close the tab during Accessibility analysis, the section pauses and resumes when you return.

Does SiteReview store scan history?

No. Each scan replaces the previous report. There is no history view, no diffing, no comparison across scans. This is intentional — SiteReview is a one-scan-and-share tool, not a monitoring dashboard.

Can I schedule scans?

No. There is no scheduling in v1.

What if a section fails during the scan?

A failure in one section does not block the others. Failed sections render with an error state and a Retry section affordance. Common failure causes: PageSpeed Insights rate limit, Mozilla Observatory timeout, X-Frame-Options blocking the Accessibility iframe.

Can I re-run a scan?

Yes, from the report view. By default a re-run reuses the existing report token and overwrites the static HTML in place — the URL you have already shared stays valid. The viewer warns you if inline edits exist, since they are lost on re-run.

What happens if a Pro license expires?

Existing public URLs continue to work — they are static files. Inline edits already saved are preserved. New scans after expiry revert to Free output and re-add the SteadyPress credit and default colors. White-label is reapplied automatically if you re-activate Pro.

Support

Where do I get help?

The support contact form lives at steadypress.ai/contact with subject SiteReview. Tell us what you tried, what you expected, what happened, and include the diagnostic information described in the Support doc.

Is there a community forum?

Not at this time.

Need more help? Contact support.