Support
The fastest way to get help with SiteReview is the SteadyPress support contact form at steadypress.ai/contact with the subject SiteReview. We do not maintain a public support forum or community channel for SiteReview in v1.
Before opening a ticket
A short triage checklist resolves the majority of common issues without a ticket:
- Check the troubleshooting guide. Common configuration issues — Action Scheduler not firing, license activation failures, PageSpeed Insights rate limits, scan timeouts, framing blocks on Accessibility, public URL 404s, oversized downloads, PHP version warnings, contrast warnings — are covered with diagnostic steps.
- Confirm your PHP and WordPress versions meet the minimums. SiteReview requires WordPress 6.4 or higher and PHP 8.1 or higher.
- Confirm you have a Google PageSpeed Insights API key set. Without one, the Performance, Mobile Friendly, and parts of SEO will produce degraded or empty results regardless of any other configuration.
- Confirm Action Scheduler is firing. Navigate to Tools > Site Health > Status. If WP-Cron is disabled and you have not configured an external cron ping, scans will not run. The synchronous fallback is available as a stopgap, but is degraded by design.
- Reload the SiteReview admin page. Some intermittent UI states clear with a fresh load.
Opening a support request
Use the form at steadypress.ai/contact with subject SiteReview. Include the following information so we can help on the first reply:
Environment
- WordPress version
- PHP version
- MySQL or MariaDB version
- SiteReview plugin version
- Hosting provider, if known
- Single-site or multisite
License
- The email address on the license purchase (do not include the license key itself in an initial message)
- The licensed domain — the host SiteReview is running on
- Approximate purchase date
The issue
- What you were trying to do
- What you expected to happen
- What actually happened, with exact error messages
- Screenshots of the error state if relevant
- Whether the issue reproduces on every attempt, intermittently, or only under specific conditions
- If a scan is involved, the report token (the 32-character string in
/sitereview-reports/{TOKEN}/)
Diagnostic information
- The output of Tools > Site Health > Info relevant to the issue (you can paste a specific section, no need to send the entire dump)
- Any recent changes to the site — plugin or theme updates, security plugin configuration changes, host migration, PHP version change
- Whether other SteadyPress plugins (PluginScore) are installed on the same site
Response times
We respond to support requests during business hours Pacific Time, generally within one business day. Complex issues that require server-side investigation may take longer; we will tell you when we have looked at it and what we need next.
What support can and cannot do
Support can:
- Diagnose plugin behavior against the published behavior contract
- Investigate license activation failures from the SteadyPress license server side
- Help interpret unusual scan results
- Reproduce reported bugs and confirm they will be addressed in a future release
- Free a license slot from a retired domain (case-by-case, contact us first)
Support cannot:
- Modify your WordPress site directly
- Run scans on your behalf
- Configure your host's cron, rewrite rules, or PHP version for you (we can point you at the right setting, but the change is yours to make)
- Provide custom development beyond the documented plugin scope
- Refund or transfer licenses outside the terms posted on steadypress.ai
What we will not ask for
We will never ask for your WordPress administrator password, your hosting control panel password, or your database root password. If a debugging step requires admin access to your site, we will offer a temporary-access plugin recommendation rather than asking for your credentials.
Security disclosures
Report security issues privately to the contact form with subject SiteReview security. Please do not file security issues on public channels. We will respond, confirm receipt, and coordinate on disclosure timing.
Bug reports and feature requests
Bug reports and feature requests are welcome through the same support form. Specific, reproducible bug reports are the most helpful kind of feedback we receive. Feature requests are evaluated against the v1 product scope and our internal priority list; we cannot promise inclusion but we read every one.
Need more help? Contact support.