Pro features

SiteReview Pro adds exactly five capabilities on top of the Free tier. The plugin code is the same — Pro features ship in the same wordpress.org download and unlock at runtime when an active Pro license is detected.

AI-authored narrative

In Free, every section of the report uses rule-based narrative derived deterministically from the measurements. In Pro, narrative for the executive summary, the recommendations list, and each section intro is authored by a large language model and presented as your agency's analysis. No "AI-generated" label appears anywhere in the rendered report.

What this looks like in practice:

• The executive summary becomes 2 to 4 paragraphs tying findings together — what the most important issues are, what they mean for the site's business, what the recommended priority is.
• Recommendations are AI-prioritized by business impact (which may differ from raw severity) rather than ordered by severity score. Each recommendation gets 2 to 3 sentences of analysis and an implementation effort estimate (Low, Medium, High).
• Each section's intro becomes 2 to 3 paragraphs of contextual interpretation — for example, the Performance section discusses what mobile-versus-desktop posture means for typical traffic, which Core Web Vitals are most concerning, and likely root causes.

A tone preference in Settings (Direct, Consultative, Educational) shapes the voice. Default is Direct.

AI narrative deliberately avoids common LLM tells: no em dashes used parenthetically, no "It's worth noting", no "However" at the start of a sentence, no hedging triplets, no "delve into" or "navigate the complexities".

Deep theme analysis

In Free, the WordPress Status section shows the active theme name, version, and parent theme. Nothing more.

In Pro, theme analysis branches on whether the active theme is recognized:

Recognized themes (wordpress.org Themes API or a bundled list of known commercial theme slugs — Astra Pro, Divi, GeneratePress Pro, Avada, Enfold, BeTheme, Bridge, Salient, X Theme, Newspaper, Soledad, Jupiter) get a version-gap analysis:

• Up to date — confirmation only
• Minor upgrade available — flagged as typically safe
• Major upgrade available — flagged with a note that customizations may break
• Multiple major versions behind — flagged with security and compatibility implications
• No upgrade available, theme inactive in directory — flagged as abandoned with a recommendation to plan migration

The Pro AI narrative writes 2 to 3 sentences interpreting the gap in business-impact terms.

Unrecognized themes trigger source-code analysis. The plugin concatenates all PHP, JavaScript, and CSS files in the active theme directory (and parent theme if present), with section headings naming each file path. Bundled artifacts (node_modules, vendor, .git, dist, build, *.min.js, *.min.css, files larger than 100 KB on their own) are excluded. The total bundle is capped at 500 KB with .php prioritized, then .js, then .css, smallest first within each extension.

The bundle is sent to the SteadyPress server's theme-analysis endpoint and the AI returns a structured response covering bug indicators (deprecated functions, undefined variables, broken control flow), security concerns (unsanitized input, hardcoded credentials, missing nonce checks, eval use, unescaped output), maintainability concerns, and compatibility risks. Findings render in plain-language prose suitable for client delivery — not raw code findings — with severity tags.

Before any theme bundle is uploaded, SiteReview shows a one-time consent modal explaining what gets sent, what comes back, where it goes, and what happens if you skip. A Don't ask again for this theme version checkbox is checked by default; your choice is persisted per-theme-version and revocable in Settings > Privacy summary.

Theme analysis includes a hash-and-cache optimization: the plugin computes a bundle_sha256 of the canonical theme bytes and the server caches the response at (license_id, bundle_sha256) for 30 days. Re-scans against unchanged theme code return cached results in under a second and do not count against your rate limit.

Inline editing

In the in-admin report viewer with an active Pro license, every text element is editable in place:

• Executive summary prose
• Section narratives
• Recommendation titles and descriptions
• Finding descriptions
• Theme analysis copy

Numeric measurements, scores, and visualization data are not editable — they are derived from measurement data and would become stale if hand-tweaked.

Clicking an editable element switches it to a contenteditable region with a subtle border indicator. Edits save automatically on blur or on Ctrl/Cmd+S. A small Saved indicator confirms persistence.

Edits are stored in the report data record in the database, not in the rendered static file. After save, the static HTML at the public URL is regenerated to reflect the edit. The single-file HTML download generated after the edit reflects it; copies downloaded before the edit are not retroactively modified.

Re-running a scan replaces the report data and discards inline edits. The viewer warns you about this before a new scan starts when edits exist.

White-label

White-label has four independently optional assets:

• Agency logo (PNG or JPEG, max 200 KB, transparent background preferred, dimensions ≥ 240×60 px)
• Agency name (text, max 60 characters)
• Optional tagline or sub-text (max 100 characters)
• Primary color and accent color (hex, with a paired HTML5 color picker and live preview card)

When a Pro license is active, the rendered report always carries zero SteadyPress brand references regardless of which white-label assets you have configured. Missing assets fall back to neutral placeholders ("SiteReview" eyebrow, no logo, default colors), never to SteadyPress.

State combinations and what renders:

The in-admin tool chrome stays SteadyPress-branded — the rendered report is what the client sees.

When you edit Primary or Accent, the settings UI computes WCAG 2.1 contrast ratios for the two render-critical pairings and surfaces an inline warning if either fails (Primary on white ≥ 4.5:1, Accent on white ≥ 3:1). The warning never blocks save — agencies can ship low-contrast reports if they choose. The intent is to flag a contradiction (an accessibility-audit product producing inaccessible reports) without taking the brand decision away from you.

SVG logo upload is not supported in v1 because of XSS risk on rendered output. Use PNG or JPEG.

If your Pro license expires while a public URL with white-labeled output exists, the existing static file is not retroactively re-branded. The agency keeps what they sent. New scans after expiry revert to Free output and re-add the SteadyPress credit and default colors.

Token rotation

The Rotate URL action in the report viewer issues a new public URL token, writes the current report to the new path, and deletes the old directory. The old URL stops working immediately.

Use rotation to revoke a leaked URL, distance a new client engagement from a prior one, or reset the share path after a personnel change. On Free, the equivalent is Delete Report, which removes the report entirely — there is no rename-in-place.

License activation

License activation lives under Settings > License.

1. Paste your license key into the input.
2. Click Activate.

On successful activation:

• The license status changes to Active
• The Pro features become available immediately — no plugin reinstall or page reload required
• The license card shows status, tier, expiration date, and remaining scan credits (for example, 18 of 25 credits remaining)

SiteReview Pro is priced as a credit pack. Each completed Pro scan consumes one credit from your account. Free scans on the same site do not consume credits. Pricing and credit-pack sizes live on the SteadyPress pricing page.

What unlocks when

Need more help? Contact support.