You test a staging site by working through a private copy of the migrated site and confirming content, links, forms, and settings before you point the live domain to the new system. A staging site is a password-protected copy of the new site, while a CMS migration means moving site content and structure from one content management system to another. Block outside access and search engine crawling during testing. Use the same content, media, users, and settings you plan to launch with, so fixes carry over cleanly.
Official resources:
- Follow Google's hosting-change checklist to test a staged CMS copy — Verify staging with restricted access, temporary hostname, and Search Console before pointing DNS live.
- Use Google's site-move guide to validate URL mappings and redirects — Check how to prepare, map, redirect, and monitor URLs when migration changes addresses.
Table of Contents
- What should be ready before testing starts?
- How do you check pages and layout?
- How do you test forms, logins, and site tools?
- When is staging ready to launch?
What should be ready before testing starts?
Freeze content changes on the old site or track them in a list. Testing fails when editors keep adding pages to the old site while testers check the new one. Load final content, images, files, users, and redirects into staging.
Check that the staging server matches the planned live setup for language, time zone, and file storage. Give each tester a role, a checklist, and a way to report page address, expected result, and actual result. Include content, design, development, and site ownership so decisions move fast.
How do you check pages and layout?
Compare high-value pages side by side with the old site. Look at home, contact, key service pages, menus, headers, footers, images, and downloads.
Read pages on phone, tablet, and desktop. Watch for cut-off text, overlapping buttons, missing images, odd line breaks, and forms that are hard to tap.
- Confirm titles, text, images, videos, and files appear in the right place.
- Confirm menus, buttons, internal links, and file links open the right target.
- Confirm spelling, dates, phone numbers, addresses, and legal text match the approved copy.
How do you test forms, logins, and site tools?
Submit every form with valid and invalid entries. Confirm success messages arrive, error messages guide fixes, notifications reach the right inbox, and spam controls still block junk. Test accounts, password resets, member areas, comments, search, and connected tools such as newsletters, payments, maps, and calendars.
Use test roles for subscriber, editor, and administrator, and confirm each role can only do its allowed tasks. Measure main pages for load speed on a slow mobile connection. Heavy themes, large images, and extra scripts often cause the worst delays after a move.
- Try checkout, donation, booking, or signup from start to finish.
- Test password reset, locked accounts, and expired links.
- Confirm media uploads, file limits, and permissions behave as planned.
When is staging ready to launch?
Run a redirect check for old addresses, changed slugs, and removed pages. Every important old address should send visitors to the closest matching new page, not to the home page or an error. Review launch settings in staging, including domain name, security certificate, backups, error pages, site search, and privacy controls.
Remove test users, test orders, and draft content, then set access and crawling controls for public launch. Do one final pass after the last import or fix, then record approval with names and date. Keep the old site backup and login access until the new site runs cleanly in public.
