CanaryWP Docs

Start Here

Getting Started

Create your first CanaryWP testing environment and learn the core workflow.

Last updated August 3, 2026

What CanaryWP is for

CanaryWP helps teams test WordPress changes in isolated environments before touching production. Import a site, verify it, run tests, and keep the source site separate from the testing copy.

Where to find app workflows

  • Import Site covers archive upload, Try demo, and creating a CanaryWP testing environment.
  • Instances covers lifecycle actions, status, tags, filters, and instance detail tools.
  • Site Testing covers smoke tests, admin checks, page checks, form checks, screenshots, and visual diffs.
  • Scheduler covers recurring maintenance, test jobs, scripts, backups, and reports.
  • Connected Sites covers source profiles and CanaryWP plugin pairing.
  • Workspace areas cover activity, notifications, billing, plans, members, roles, and settings.

Core workflow

  • Import a WordPress site archive or use Try demo.
  • Review the source WordPress site and CanaryWP destination before import.
  • Open the created instance and confirm the site loads correctly.
  • Run Site Testing to check pages, admin access, navigation, forms, assets, and visual changes.
  • Use Scheduler for recurring maintenance tests when a workflow should repeat.

Important terms

  • Source WordPress site: the live or production site the archive came from.
  • CanaryWP testing environment: the isolated instance created from the archive.
  • Instance: the running or stopped WordPress copy managed by CanaryWP.
  • Temporary import file: an uploaded archive used for restore and cleanup.
  • Demo archive: the permanent demo file reused by Try demo.

First run checklist

  • Confirm the imported home page matches the source site.
  • Open WP Admin if credentials are available.
  • Run at least the smoke tests in Site Testing.
  • Check plugins, themes, WP/PHP versions, and site health.
  • Delete test-only instances when you no longer need them.