The short answer: a test copy is a second site, identical to yours, that only you see. You try the new theme, the big update, the plugin you do not know there. If it goes well, you repeat it on the real site; if it goes badly, you delete the copy and nobody noticed. It lives on a subdomain, with a separate database.
What the copy needs
| Piece | How |
| A separate address | A subdomain (for example, test.your-domain.com): Subdomain or folder. |
| The files | Copied into the subdomain’s folder. |
| A new database | With a copy of the site’s data and its own user. Never the same one as the real site. |
| The addresses swapped | The addresses inside the copy must point to the subdomain: Replacing old addresses. |
| Closed to the world | With a password on the folder and kept out of Google: Password protecting a folder. |
Step by step
|
|
|
|
|
| Do not bring the copy back over the real site if the site receives orders, comments or sign-ups: you would lose what came in meanwhile. On read-only sites it may be acceptable. If in doubt, repeat the changes by hand. |
| A copy indexed by Google creates duplicate pages and confusion. Make sure it is closed: robots.txt and sitemap.xml. And test that your backup restores: Testing a backup. |
|
Want help setting up a test copy? Open a ticket with the address. Open a support ticket |
RECOMMENDED PRODUCT WordPress hosting One-click install, updates handled, and speed that holds up. from R118.80/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful











