Free tools Windows power users keep installed
One-click scans. No signup required.
The safest way to change a client website is to work on a staging copy, not on production. On an agency hosting plan with staging built in, open the site dashboard, select the live or production environment, and choose Create staging or Add staging site. If the host has no such control, clone WordPress into a protected subfolder, subdomain, or separate host. Test the work there, back up production, check for new live data, and deploy only the files or database tables that actually changed.
The exact menu names, plan eligibility, clone contents, URL handling, and push controls vary by provider. Treat the procedure below as a decision path, then follow the linked documentation for your host.
As an Amazon Associate I earn from qualifying purchases.
What an agency staging site is—and why it matters
A staging site is a working copy of a live, or production, website. It normally contains the WordPress files, database, theme, plugins, media, settings, and user data needed to reproduce the site away from its public URL. You can use it to test a redesign, WordPress core update, plugin or theme update, custom code, layout change, form, checkout, or integration without exposing half-finished work to visitors.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchStaging is not automatically a backup and it is not automatically private. It is another environment that can become stale, publicly reachable, or capable of sending email and processing payments unless you configure it. The value comes from keeping changes separate until someone has reviewed and approved them.
#1 Best Overall
Copies can be broader than the files you expect. For example, WordPress.com says its staging workflow copies users, configuration, API keys, and database data; for WooCommerce, that includes customers, products, and orders. Read what your provider copies before cloning a client site, especially one containing personal or payment-related information.
Check these prerequisites before you create the clone
- Identify the CMS and environment. Confirm that the site is WordPress and distinguish its production URL from any existing development or test copy.
- Verify the hosting plan. A staging button on one plan does not prove that another plan includes it. Check the host’s current feature list and documentation.
- Confirm permissions. You need an administrator-level hosting or site account. WordPress.com states that any administrator on the site can create a staging site, subject to the plan’s availability.
- Record integrations. List payment gateways, webhooks, email delivery, analytics, search indexing, scheduled jobs, membership systems, and external APIs that could act on staging data.
- Check capacity. A clone requires disk space for WordPress files, uploads, and a second database. Large media libraries and logs can make the copy substantially larger than the installation itself.
- Decide how changes will return to production. A file-only deployment is safer for a theme or code change. A database deployment is more consequential because it can replace content created on the live site.
Create staging from a hosting dashboard
When the provider manages staging, the workflow usually starts from the site’s production environment. Look for labels such as Live, Production, Staging, Clone, or Push. Do not assume that a button called “sync” is one-way; inspect whether it copies staging to production, production to staging, or both.
Provider-neutral dashboard procedure
- Sign in to the hosting control panel and open the website’s dashboard.
- Select the live or production environment.
- Choose the staging action, such as Create staging, Clone, or Add staging site.
- Choose the destination name, subdomain, directory, or region if the panel asks for one. Use a name that identifies the client and purpose without exposing confidential information.
- Wait for the copy to finish, then note the staging URL and its separate WordPress login or access method.
- Read the completion notice for exclusions. Some systems omit cache, logs, large files, scheduled tasks, or certain database tables.
- Open staging in a private browser window and verify that the home page, administrator login, media, menus, forms, and key templates load before editing.
WordPress.com dashboard path
On WordPress.com, the documented path is Hosting Dashboard → select the site → Production dropdown → + Add staging site. The staging feature is restricted to Business and Commerce plans in that documentation. WordPress.com says staging sites are blocked from search-engine indexing by default, but that setting can be overridden, so confirm it after creation. The provider’s instructions were last reviewed September 14, 2026: Create a Staging Site in WordPress.
Recommended Free Tools
What to verify immediately after a managed clone
- Is the staging URL protected by a login, password, or host-level restriction?
- Does WordPress use the staging URL for links, images, REST requests, and AJAX calls, or do links still point to production?
- Are outgoing email, webhooks, cron jobs, and payment gateways disabled or redirected?
- Are caches, CDN rules, and object-cache settings appropriate for a non-production site?
- Is search indexing disabled, and is a
noindexcontrol actually present?
When the host has no staging feature
You still have two practical routes: a cloning plugin or a manually configured subdomain. Both require more responsibility for permissions, URLs, security, and deployment.
Option 1: Clone with a staging plugin
WP STAGING documents a free clone into a subfolder. Its Pro workflow adds destinations such as a subdomain or an external host. A subdomain destination must already exist, and the target directory must be writable. The plugin’s current instructions are at How to Create a WordPress Staging Site.
- Install and activate the staging plugin on production, using an administrator account.
- Choose the clone destination. A subfolder is simplest; a subdomain or external host gives stronger separation.
- Check the destination path and confirm that the web server account can create files and write the database.
- Start the clone and keep the browser or server session open until the plugin reports completion.
- Open the generated URL and test login, links, images, permalinks, forms, and media before making changes.
- Record how the plugin handles URL replacement and database tables. A clone that still references the production domain can send editors or visitors back to the live site.
WP STAGING reports that its own typical shared-hosting subfolder clone takes “under a few minutes.” That is a vendor-reported experience updated June 4, 2026, not a benchmark or guarantee; transfer time depends on the site’s size, server load, and database.
Option 2: Build a manual subdomain
A manual copy involves creating a subdomain, copying WordPress files, exporting and importing the database, and changing the site’s URLs. DreamHost’s standard-hosting instructions use a dreamhosters.com subdomain as an example and explicitly require updating database URLs during the copy: Creating a staging WordPress site.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- Create the subdomain and its document root in the hosting panel. Wait for DNS or local routing to resolve.
- Copy the production WordPress files, including
wp-contentand uploads, into the staging document root. - Create a separate database and database user, then import a production database export.
- Update
wp-config.phpwith the staging database credentials. - Perform a careful search-and-replace of the production URL in the database. Use a tool that understands serialized WordPress data rather than a blind text replacement.
- Log in to staging, resave permalinks, and test links, images, REST endpoints, forms, and redirects.
- Protect the subdomain with authentication and block indexing before sharing it with a client.
Manual staging does not provide a one-click deployment. Returning approved work means repeating a controlled file and database process, so document every change and retain a production backup.
Protect staging from visitors and automated systems
Restrict access
Use the host’s password protection, HTTP authentication, VPN, allowlist, or a WordPress access-control method. Do not rely on an obscure URL. Remove or rotate test accounts and credentials before handing the site to a client.
Prevent indexing
Enable the host’s search-engine blocking option and verify the response with your SEO plugin or a page source check. A provider’s default is not universal; even where staging is blocked by default, an override can make it crawlable. Keep staging out of XML sitemaps and avoid linking to it from production.
Stop side effects
- Disable real payment processing and replace gateway credentials with sandbox keys.
- Prevent transactional and marketing email from reaching customers. Route test mail to an internal mailbox.
- Pause webhooks, third-party callbacks, and scheduled jobs that could alter production records.
- Use fake customer data where possible, and apply your agency’s retention and privacy rules to the copied database.
- Tell every editor which environment they are using; a browser bookmark or visible environment banner prevents accidental production edits.
Test the changes in a repeatable way
Test the same journeys that matter to the client, not only whether the home page looks correct. Record the browser, device, user role, and result so another team member can reproduce a failure.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsCore WordPress checks
- Log in as an administrator, editor, and ordinary user where those roles exist.
- Open representative pages and posts, search results, archives, menus, widgets, media, and downloadable files.
- Check responsive layouts at the breakpoints used by the site’s audience.
- Update the intended theme, plugin, or core version, then review PHP errors, browser-console errors, and broken styles.
- Submit forms and verify validation, confirmation messages, spam controls, and the internal notification path without sending mail to customers.
Store, membership, and community checks
- Use sandbox payments and test checkout, tax, shipping, coupons, refunds, and order emails.
- Check account registration, password reset, subscriptions, access rules, and renewal hooks.
- Review comments, forums, search, and moderation workflows if the site supports them.
Capture the deployment set
Before pushing anything, write down the exact files, theme settings, plugin settings, pages, products, or database tables that changed. This inventory determines whether a file-only, selective database, or full deployment is appropriate.
Push approved work without overwriting live activity
Deployment is where staging can cause irreversible damage. The staging copy is older than production as soon as a visitor submits a form, an editor publishes a post, or a customer places an order. Treat every database push as a potential overwrite.
Choose the narrowest deployment scope
| Change | Usually deploy | Risk to production data |
|---|---|---|
| Theme PHP, CSS, JavaScript, or template files | Selected theme files or a version-controlled release | Low database risk, but test cache and compatibility |
| Plugin code update with no settings or content changes | Plugin files, if the host supports file-only push | May still run database migrations; check the plugin’s instructions |
| Page, post, menu, or site-setting change | Selected database tables or a documented content export | Can overwrite newer edits if pushed broadly |
| WooCommerce catalog or configuration | Only the required records, using a store-aware workflow | High; customers, orders, and products may have changed on production |
| Full environment replacement | Files and database together | Highest; all newer production database activity can be replaced |
Use a host’s selective push controls when available
Kinsta’s push-environment documentation allows selecting specific files or folders and specific database tables. It also creates a backup of the target before a push. Its guidance distinguishes a file-only push, suitable for changes that do not write to the database, from a database push and a full push. Review the controls at WordPress Hosting – Push Environments.
- Freeze the approved release: record the staging URL, commit or backup identifier, changed files, and database objects.
- Back up production immediately before deployment and confirm that the backup can be restored.
- Compare production activity with the staging copy’s creation time. Note new orders, comments, posts, signups, form entries, and membership changes.
- Schedule a low-traffic maintenance window. For a busy store or community, pause new transactions during the database operation.
- Select the smallest push scope that contains the approved change. Do not choose a full database because it is convenient.
- If a database crosses domains, run the host’s search-and-replace operation so internal links, media URLs, and serialized settings use the production domain.
- Run the deployment, then clear application, object, page, and CDN caches as appropriate.
- Test the live home page, login, forms, checkout, analytics, email routing, and the specific feature changed.
- Monitor error logs and transactions, and keep the pre-deployment backup until the release is accepted.
Reconcile live data before a database push
A broad push can replace production changes made after staging was created. Documented examples include comments, new posts, ecommerce purchases, membership signups, and forum posts. Export or manually record the live records that must survive, then reapply them after deployment only when the application and data owners approve the method. If the host cannot merge safely, a file-only release or manual recreation of a small theme change is often safer.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special precautions for WooCommerce and other stores
Store data changes continuously, so a staging database is almost never current enough to replace production without reconciliation. A clone may include customers, products, and orders, while production receives new orders during testing. If those environments are synchronized indiscriminately, the newer production records can be permanently lost.
- Use sandbox payment credentials and disable real order emails on staging.
- Compare the staging and production customer, product, inventory, coupon, and order data before any push.
- Pause new orders for the shortest practical maintenance window when a database sync is unavoidable.
- Prefer a narrow theme-file deployment for visual changes. For a small page or product change, consider manually recreating it or using a store-aware export/import rather than replacing the entire database.
- Verify inventory, order numbers, taxes, shipping, subscriptions, and webhook status immediately after release.
Troubleshoot common staging failures
The staging button is missing
Check the site’s plan, CMS, account role, and whether staging is available in the selected region or site type. If the feature is not included, use a documented plugin clone or manual subdomain instead of installing an unverified script.
The clone shows the production URL
Review the site’s home and site URL settings, then perform a serialized-data-aware search-and-replace. Clear caches and resave permalinks. Never replace URLs by editing database text blindly when serialized values are present.
Images, CSS, or permalinks return 404 errors
Confirm that uploads were copied, the web root points to the correct directory, rewrite rules are active, and permalinks have been resaved. Check whether a CDN or hotlink rule still references production.
The plugin cannot write the destination
Verify directory ownership and permissions, available disk space, PHP limits, and database credentials. A subdomain clone may require a pre-created document root and a writable target folder.
Test emails or payments reached real people
Immediately disable the integration, rotate exposed credentials, notify the site owner, and review logs for additional deliveries. Add an environment banner and safe-mail routing before testing again.
The live site lost content after a push
Stop further writes, preserve logs, and restore the pre-push production backup if the owner approves. Compare the backup with current records, then recover orders, comments, signups, or posts using the application’s supported import or recovery process. Do not attempt another full sync as a shortcut.
A repeatable agency workflow
- Intake: record the requested change, affected URLs, integrations, data sensitivity, and rollback owner.
- Clone: create staging from the dashboard, plugin, or documented subdomain method.
- Harden: restrict access, block indexing, disable side effects, and add an environment label.
- Develop: make and document changes only on staging.
- Validate: run the agreed browser, role, form, store, and integration tests.
- Approve: obtain client sign-off and freeze the deployment inventory.
- Back up: create and verify a fresh production backup.
- Deploy: push only the required files or tables during a planned window; use search-and-replace when domains change.
- Verify: test the live journeys, monitor logs, and confirm analytics and email behavior.
- Retire or refresh: remove obsolete staging copies or refresh them from production after confirming that no work remains there.
How to choose the right staging method
| Method | Eligibility and setup | Control over separation and deployment | Best fit |
|---|---|---|---|
| Built-in host staging | Depends on provider and plan; some managed plans expose a dashboard action. | Often includes managed cloning and push tools, but scope and clone contents vary. | Agencies that need repeatable environments and a supported rollback path. |
| Plugin clone | Works where WordPress and server permissions meet the plugin’s requirements; subdomain or external-host modes may require a paid tier. | Depends on destination, URL mapping, database handling, and the plugin’s deployment features. | Sites on standard hosting without native staging. |
| Manual subdomain | Requires DNS or hosting-panel access, file transfer, a second database, and URL rewriting. | Maximum manual control, but every copy and deployment step is your responsibility. | Teams that can administer WordPress and need a custom or isolated environment. |
There is no universal “best” option. Choose the method that gives your agency a documented clone, controlled access, a verified backup, and a deployment scope narrow enough to protect live data.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
