Define the change
State whether only the domain changes or whether hosting, design and paths also change. Identify authorized account managers. Inventory important service, project, guide, language and campaign URLs, including links already used in printed materials.
Request a test record
Record each old URL, intended new destination, result and reviewer. Test as a visitor, not only as an administrator. Google recommends permanent server redirects such as 301 or 308 to relevant destinations, avoiding unnecessary chains and unrelated homepage redirects. Review internal links, canonical, language annotations and sitemap URLs.
Test the actual inquiry journey
Separate page display from form processing. With the owner's approval, verify that a test inquiry is saved at its intended destination without using real customer data. A success message does not prove storage or email delivery. Check public downloads and previously distributed standalone files separately.
Record rollback scope
Keep the previous version, source reference and authorized recovery owner. Clarify whether recovery covers code, configuration, files and data. A source copy is not a verified backup of customer records or attachments. Record unresolved issues and the pages or functions affected.
Interpret search monitoring carefully
Google notes that visibility can fluctuate while a move is processed. When authorized access exists, distinguish sitemap submission, URL discovery and indexing. Do not promise a fixed ranking or indexing date. Keep monitoring evidence separate from a developer's local tests.
Prepare your request
For a Riyadh business website project, share the current URLs, languages and functions that must remain available. Discuss the migration, testing and follow-up scope with Banyan Art before approval.