Usually, a staging website does not require another domain purchase. Your host may provide a protected preview address, or support a staging subdomain of your existing domain. A separate .co.uk domain can be useful when you need a distinct test hostname or want to keep test-domain administration separate, but it adds a renewal commitment. Privacy, isolated test data and safe payment settings must be configured whichever address you choose.
Before you begin
- Ask your host whether an access-controlled staging address is already included.
- Choose between that preview, an existing subdomain and a separate registration.
- Confirm the test address supports HTTPS and restricted access.
- Use test data and independently configured email and payment test settings.
- Record which DNS records serve the live website and business email.
- Agree a launch check, rollback plan and any test-domain renewal responsibility.
1. Start with the test environment your host provides
A staging website is a working copy used to review changes before publishing them to the main website. Its address and its hosting environment are separate decisions. Buying a new domain supplies a name; your host or developer still needs to provide the test site, its configuration and a safe way to publish it.
Ask whether your current hosting plan includes a staging feature, whether invited reviewers can access it, and how changes move to production. Some services use their own preview address. Others let you connect a subdomain or a separate registered name. Confirm support before paying for a domain intended only for testing. A new address alone does not create a second database or isolate a copied website’s integrations.
2. Compare the three address choices
For an occasional redesign, an included protected preview may cover the whole requirement. A staging subdomain can provide a recognisable address under your current name, if your host supports it. You can normally add the necessary DNS records without buying that subdomain as another registration.
Consider a separate domain when your testing process specifically needs a different registered hostname, or when the team needs to manage its test-domain configuration separately. Check what is actually isolated. Two domains in the same account, using the same DNS service and server, can still share important dependencies. Choose on that basis rather than assuming a second renewal bill automatically creates a separate infrastructure.
| Choice | Domain registration needed? | Check before choosing |
|---|---|---|
| Host’s preview address | Usually no additional purchase | Included access controls and how publishing works |
| Subdomain of your existing name | No separate subdomain registration | Host support, HTTPS and the exact DNS record |
| Separate .co.uk domain | Yes, for an available name | Renewal budget and which dependencies remain shared |
3. Protect the preview before sharing its address
Use the host’s authentication or another properly configured access control, and test the address while signed out. A hard-to-guess name is easy to copy or accidentally share. HTTPS protects the connection, while access control decides who may view the draft. Make sure both work for the people reviewing it.
Crawler instructions have a different role. The Robots Exclusion Protocol explicitly says its rules do not provide access authorisation. Do not rely on a robots.txt file to protect unfinished pages or copied records. Ask the host how it prevents indexing of staging content as well as restricting entry. Use sanitised example data wherever possible, and keep private customer records out of a public preview.
Sources: IETF RFC 9309, Robots Exclusion Protocol and its security limits ↗
4. Keep test email, payments and DNS deliberate
A copied site can retain live settings. Have the developer check mail sending, payment integrations, webhooks, scheduled jobs and any customer-account connections before the test copy is opened. Use the payment provider’s supported sandbox and test credentials. Restrict outgoing test email so a design review cannot unexpectedly contact real customers.
For the address itself, get the precise record name and value from the staging host. Adding a test subdomain usually calls for a specific record, rather than replacing the whole domain’s nameservers. Inventory the live website and mail records first. If a nameserver move is genuinely required, plan it separately and preserve every needed service. Keep test credentials and production credentials clearly identified in secure storage.
5. Budget for the extra name only when it adds value
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.
Compare the cost of an additional registration with what your existing hosting preview already provides. If you choose a second domain, record its renewal date and responsible person alongside the main business name. A longer initial term may suit an ongoing test environment; a short redesign does not by itself justify another long-term registration.
These are domain prices. Any staging hosting, backup, email testing or developer work has its own scope and price. NameUK can suit a buyer who needs a separately registered UK name, visible renewal pricing and dashboard DNS controls. This is our own recommendation for those requirements. An included host preview may be the more economical choice when it already meets the brief.
6. Work through a redesign before changing the live address
Consider a hypothetical workshop replacing its brochure site. Its host supplies a private staging subdomain, so the owner keeps the existing .co.uk registration and reviews the new design there. They test mobile navigation, images, enquiry forms and confirmation messages with sample data. The developer checks links for accidental references to the staging address.
Before launch, they agree how to back up the current site and restore it if needed. The host explains whether publishing changes the site at its existing destination or requires a specific DNS update. After publishing, they open the actual public domain, check HTTPS and test the agreed customer journeys again. Browser redirects and cached configuration can behave differently on the final hostname, so a successful preview is one part of the acceptance check.
7. Decide what happens to the staging domain after launch
If testing will continue, keep the environment protected and maintain its software and integrations. If the temporary site is finished, remove or close its public access through the host. Remove obsolete DNS entries only after checking that nothing still uses them. Keep any continuing mail or account-recovery dependency in the domain inventory.
A separately registered test domain needs an explicit keep-or-expire decision before renewal. Check old links, automated jobs and verification dependencies before letting it lapse. If you do need a dedicated name, search its exact spelling, choose the term and confirm the completed registration before configuring the test environment. Give that extra domain a clear operational purpose and a named renewal owner.
NameUK’s own buyer guidance, reviewed 2 November 2026. The workshop redesign is a hypothetical planning example. The illustrations are conceptual artworks rather than screenshots or customer evidence.
Further readingIETF RFC 9309, Robots Exclusion Protocol and its security limits ↗Extension rules and provider processes can change. Check the current registrar instructions before a registration, transfer or renewal.
Low-cost registration. Affordable UK renewals.
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.