CanaryWP gives you an isolated WordPress environment where you can import a site, make changes, run updates, perform tests, and inspect the results without making those changes directly on the source site.
The basic CanaryWP workflow is:
Source WordPress site → CanaryWP testing environment → Change → Test → Review results → Make a release decision
What CanaryWP is for
WordPress maintenance can affect many parts of a site at once. A plugin update may introduce a PHP error. A theme change may alter page layouts. A PHP upgrade may make an older plugin incompatible. A database operation may affect content or URLs.
CanaryWP creates a separate environment where these changes can be evaluated before they are applied through your normal production workflow.
You can use CanaryWP to:
- Import an existing WordPress site into an isolated environment.
- Create temporary testing instances.
- Inspect WordPress and PHP versions.
- Review installed plugins and themes.
- Create and restore backups.
- Run automated site tests.
- Compare screenshots before and after changes.
- Schedule recurring tests and maintenance workflows.
- Review previous testing results.
- Monitor site health, uptime, and performance.
- Connect source WordPress sites to CanaryWP.
- Review operational activity and notifications.
Before you begin
You should have access to a CanaryWP account and workspace.
For a real site import, you will normally also need a supported WordPress backup archive. CanaryWP currently accepts common WordPress backup formats such as .wpress, .zip, and supported tar-based archives.
If you only want to explore the platform, use Try demo instead.
Your first CanaryWP workflow
1. Create a testing environment
Open Import Site.
Upload your WordPress archive or choose Try demo.
Review the destination settings before starting the import.
2. Wait for the environment to become available
During creation, CanaryWP provisions the environment, restores the site data, prepares WordPress, performs required URL changes, and checks that the environment can start.
Do not begin testing until the instance is in a usable state.
3. Verify the imported site
Open the CanaryWP URL.
Check the homepage and several important pages.
If WordPress administrator credentials are available, also open WP Admin and confirm that the dashboard works.
4. Review the environment
Before making changes, review:
WordPress version
PHP version
Active theme
Installed plugins
Available updates
Site health
Recent activity
Backup status
This gives you a baseline for comparison.
5. Run baseline tests
Open Site Testing and select the instance.
Run the appropriate smoke, page, admin, functional, form, and visual checks.
A baseline is important because a failure that already existed before an update should not automatically be attributed to the update.
6. Make the intended change
Examples include:
Updating a plugin
Updating a theme
Updating WordPress
Changing PHP
Modifying database content
Testing a configuration change
7. Test again
Run the relevant tests after the change.
Compare the new results with the baseline and inspect failures individually.
8. Review the evidence
Use Testing History, screenshots, logs, activity, site health, and other instance tools to determine whether the environment remained healthy.
Important CanaryWP terms
Source site
The original WordPress site from which the testing copy originates.
Testing environment
The isolated WordPress copy created and managed by CanaryWP.
Instance
The individual WordPress environment inside CanaryWP.
Import archive
The backup file used to create a testing environment.
Baseline
A known test result collected before a change.
Retest
A test performed after a change so it can be compared with the baseline.
First run checklist
Before considering your first testing environment ready:
- The public site loads.
- Important pages open correctly.
- WP Admin works when credentials are available.
- WordPress and PHP versions are correct.
- Plugins and themes are present.
- Critical functionality works.
- Baseline tests have been completed.
- Unexpected errors have been reviewed.
- A backup exists before risky maintenance work.
What CanaryWP does not do automatically
A CanaryWP testing environment is separate from the source site.
Changes made inside the testing environment should not be assumed to have been applied to the source or production site.
Use your organization’s normal deployment or WordPress release process when a tested change is ready for production.
Next steps
Continue with:
- Product Overview
- Importing Sites
- Testing Environments
- Instances
- Site Testing