Skip to content
SteadyPress
Home SiteReview documentation Developer reference

Developer reference

SiteReview v1.0 does not expose any custom WordPress filter or action hooks for third-party extension. The plugin is designed as a self-contained tool with no public extension surface in this release.

Why no hooks

The product surface is intentionally small in v1. SiteReview is positioned as a one-scan-and-share tool with a single user (the agency operator); the cost of supporting an extension API — versioning hooks across releases, documenting stable contracts, taking backwards-compatibility constraints on changes to internal data shapes — was not justified by demand in the first release cycle.

If you have an extension use case that would benefit from a stable hook surface, contact support at steadypress.ai/contact with subject SiteReview hooks request and describe what you would build with it. Concrete proposals carry weight in deciding what hooks land in a future minor release.

Constants you can define in wp-config.php

These are not hooks, but they affect plugin behavior at runtime:

  • WP_DEBUG_LOG — enables SiteReview log output to wp-content/debug.log (standard WordPress behavior; the plugin uses error_log() for its diagnostic messages).
  • SITEREVIEW_DEBUG — when defined as a truthy value, enables verbose logging including REST request and response payloads. Useful for debugging support tickets. Do not enable in production.

REST API surface

SiteReview registers a REST namespace at steadypress/sitereview/v1 with 22 routes covering scan management (/scan/start, /scan/status, /scan/cancel, /scan/retry-section, /scan/a11y-results, /scan/start-sync, /pages), report management (/report/current, /report/render, /report/visibility, /report/edit, /report/rotate-token, /report/delete, /report/download, /report/password), settings (/settings/save), license (/license/activate, /license/refresh), white-label (/white-label/upload-logo), and onboarding (/onboarding/dismiss).

All routes require the manage_options capability and a valid WordPress nonce. They are intended for the plugin's own admin JavaScript, not for third-party integration. The route surface is not under a backwards-compatibility commitment in v1.

Database tables

SiteReview creates three custom tables, prefixed with the WordPress table prefix:

  • {prefix}sitereview_reports — one row per current report (the plugin retains only the most recent scan)
  • {prefix}sitereview_scan_jobs — per-section scan job tracking with Action Scheduler integration
  • {prefix}sitereview_scan_psi_subjobs — per-page-strategy PSI sub-job tracking for the Performance section's decomposed work model

Schema details are documented internally in docs/sitereview-schema-v1.0.md within the plugin source. The schema is not part of the public extension surface and is subject to change between releases.

Action Scheduler hooks

The plugin schedules work through three Action Scheduler hooks. These are internal contracts between the plugin's components and are not stable extension points:

  • sitereview_scan_section — runs an individual section's measurement work
  • sitereview_scan_psi_page — runs a single PageSpeed Insights page-strategy sub-job
  • sitereview_scan_orchestrator — checks per-section job state and triggers downstream work (AI narrative generation, static HTML re-render)

Attaching custom callbacks to these hooks is not supported. The argument shapes and timing semantics may change in future releases without notice.

Need more help? Contact support.