Staging Sites: Test Website Changes Without Breaking Your Live Website

A developer uploads a "small fix" on a Friday evening. Suddenly the homepage shows a blank screen, the enquiry form stops working, and nobody notices until Monday. Most website disasters begin with changes made directly on the live site. A staging site — a private copy of your website for testing — prevents this.

What is a staging site?

A staging site is a duplicate of your live website, usually on a subdomain like staging.yourbusiness.com or a separate folder, with its own copy of the database. You make and test changes there. When everything works, you apply the same changes to the live site.

When you need staging

• Design changes or new pages.
• PHP version upgrades. See upgrading PHP safely.
• WordPress core, theme or plugin updates.
• New features: booking systems, payment gateways, forms.
• SEO changes like URL structures and redirects.
• Any code change by a new developer.

Tiny content edits like fixing a typo can usually be done live.

How to create one on shared hosting

Option 1: Built-in staging tools

Many hosts, including Hostinger on some plans, offer one-click staging for WordPress sites. Check your hosting panel.

Option 2: Manual staging for PHP sites

1. Create a subdomain (for example staging) in your hosting panel.
2. Copy all website files to the subdomain's folder.
3. Export the live database and import it into a new database.
4. Update the staging site's configuration file with the new database details.
5. Update any hard-coded site URLs in config to the staging address.
6. Disable outgoing emails, payment live mode and SMS on staging — or switch them to test mode — so test actions don't reach real customers.

Keep staging private and out of Google

A public staging site can be indexed by Google and create duplicate content — or let strangers see unfinished work. Protect it:

• Password-protect the folder (HTTP basic authentication through your hosting panel or .htaccess). This is the most reliable method.
• Add noindex meta tags as a backup.
• Don't link to staging from your live site.

Blocking staging only with robots.txt isn't enough — URLs can still appear in search results if linked elsewhere.

A safe workflow

1. Back up the live site. See backup guide.
2. Refresh staging with a recent copy of live data if needed.
3. Make changes on staging.
4. Test on desktop and mobile: key pages, forms, admin, payments in test mode.
5. Check the error log. See reading error logs.
6. Get approval from the business owner.
7. Deploy to live at a quiet time.
8. Test live immediately after deployment.
9. Keep the backup until you're sure everything works.

Be careful with databases

The trickiest part is the database. Live sites keep receiving new orders, enquiries and bookings. Copying the staging database over live would erase them. Usually, you deploy only code changes and apply database changes (new tables or columns) with careful scripts, never by overwriting the whole live database.

Version control

Developers often use Git to track code changes, making it easy to see what changed and roll back. Even on shared hosting, keeping code in a private Git repository is good practice.

When a staging site isn't necessary

For a tiny static website that rarely changes, a careful backup before each edit may be enough. But once a site has forms, bookings, payments or an admin panel, a staging copy pays for itself the first time it catches a problem before customers see it.

Frequently Asked Questions

Does a staging site cost extra?

Usually not on most hosting plans — it uses a subdomain and a database you already have. Larger sites may need more storage.

Will staging hurt SEO?

Only if it's publicly indexed. Password protection prevents this.

Can I test payments on staging?

Yes, using your payment gateway's test or sandbox mode — never live keys.

How often should staging be refreshed?

Before each major round of changes, so you're testing against current data and code.

Want safer website updates?

Joboo Web uses staging and backups for every update. See our maintenance checklist, web development, or contact us.