Domain research and assessment
Test whether a proposed domain supports the brand and arrives with manageable history.
- History and previous use
- Backlink and reputation review
- Clarity, extension and risk considerations
Domains, migrations and digital foundations
Change the address without losing the value.
Research the domain, map every important destination and coordinate the technical handover so customers, search engines and business systems can follow the move.
Strategy before redirectsValidate the destination and business case
Page-by-page planningPreserve relevance, journeys and established signals
Coordinated transitionConnect domains, SEO, DNS, analytics and teams
Why it matters
A domain is more than a website address.
It connects search visibility, backlinks, email, analytics, customer bookmarks, advertising, security and brand recognition. A successful migration tells every system the same story: this established resource now lives here.
Common reasons to move
- A rebrand or business name change
- Consolidating multiple websites or acquisitions
- Moving to a shorter or more durable domain
- Correcting a confusing legacy structure
- Separating or combining business divisions
- Preparing for expansion into new markets
Risks to control
- Valuable pages lose relevant destinations
- Redirect chains, loops or broad homepage redirects
- DNS, certificates or email records fail
- Canonical, sitemap or analytics signals conflict
- Old files, subdomains and campaigns are forgotten
- Too many major website changes launch together
The migration principleSearch systems process moves URL by URL. Give each established resource one clear, relevant destination and make the relationship technically unambiguous.
Domain and migration services
Plan the destination, the journey and the handover.
Choose a focused domain review or a connected migration program. Scope follows the number of websites, URLs, systems, stakeholders and risks involved.
Domain portfolio review
Understand which domains deserve protection, consolidation, redirection, renewal or release.
- Ownership and expiry inventory
- Use and traffic assessment
- Consolidation recommendations
Migration planning
Define scope, responsibilities, dependencies, timing and validation before launch.
- Risk and stakeholder plan
- Benchmark and backup requirements
- Launch and rollback considerations
URL mapping
Choose the closest relevant destination for each valuable old page, file and asset.
- Multi-source URL inventories
- One-to-one destination map
- Retirement and consolidation decisions
Redirect specifications
Provide clear rules developers or hosting teams can implement and test.
- Permanent redirect logic
- Variant and subdomain coverage
- Chain, loop and error testing
DNS coordination
Connect the launch plan with authorised domain, hosting, email and IT owners.
- Record and certificate requirements
- TTL and change sequencing
- Ownership and verification checks
Search Console transition
Prepare properties, sitemaps and eligible change-of-address steps for the new domain.
- Old and new property verification
- Canonical sitemap submission
- Transition annotations and checks
Post-launch monitoring
Track the handover by page group and investigate patterns before small issues grow.
- Crawl, index and redirect monitoring
- Traffic, query and conversion comparison
- 404 and external-link opportunities
URL mapping
The centre of a safer migration.
A controlled mapping file records what existed, where it should go, how it should respond and why the destination is relevant.
| Old resource | New destination | Action | Reason |
|---|---|---|---|
| /services/domain-advice | /domain-strategy | 301 redirect | Direct service equivalent |
| /articles/domain-guide | /guides/domain-migration | 301 redirect | Same resource, new structure |
| /old-team-profile | /about | Redirect if relevant | Person incorporated into team page |
| /expired-campaign | No replacement | 410 or useful archive | Content deliberately retired |
Avoid the homepage shortcutRedirecting every old page to the homepage frustrates customers and provides a weak relationship between old and new content. If no relevant replacement exists, an honest 404 or 410 may be more appropriate.
Launch sequence
Move in a controlled order.
Exact responsibilities are agreed before launch. Elmbridge Advantage can prepare and coordinate the SEO and domain plan while authorised developers, hosts, registrars and IT owners execute relevant changes.
Inventory and benchmark
Capture URLs, performance, DNS, integrations, verification, backups and owners.
Build and test
Validate the new site, HTTPS, canonical rules, analytics, sitemaps and redirect map.
Change and verify
Publish, activate redirects, update DNS where required and test priority journeys.
Monitor and refine
Watch crawls, indexation, traffic, conversions and unmatched requests across both domains.
What you receive
A migration source of truth.
Deliverables are designed to align decision-makers and give implementation teams specific, testable requirements.
Defined around risk
The right evidence before the irreversible moment.
Exact outputs depend on the type of move, technical environment and division of responsibility.
Domain assessmentHistory, reputation, backlink and strategic-fit findings.
Migration planScope, sequence, owners, dependencies, risks and checks.
URL inventory and mapOld resources, new destinations, actions and rationale.
Redirect specificationRules and expected behaviour for implementation and testing.
Launch checklistSEO, DNS, analytics, verification and customer-journey checks.
Monitoring frameworkBenchmarks, dashboards, review rhythm and escalation triggers.
Common questions
Protect the value before you move it.
Bring domain and search specialists into planning early—before a new site structure or launch date becomes difficult to change.
Will changing a domain name hurt SEO?
Expect some temporary movement while search systems process new URLs. Careful one-to-one mapping, permanent redirects, consistent signals and close monitoring reduce avoidable risk, but no responsible provider can promise zero fluctuation.
Should every old URL redirect to the homepage?
No. Each useful old page should normally redirect to its closest relevant replacement. Broad homepage redirects create poor customer journeys and weak page-to-page migration signals.
How long should redirects stay in place?
Google recommends keeping redirects for at least 180 days and retaining the old domain for at least a year. Important redirects are often worth maintaining longer while backlinks, bookmarks and customer habits still generate visits.
Can you coordinate DNS changes?
Yes. Elmbridge Advantage can research, document and coordinate requirements with authorised domain, hosting, email and IT owners. The parties responsible for making live changes and holding credentials are agreed before launch.
Should we redesign and change domains together?
Where possible, avoid combining every major change. A simultaneous domain, platform, design, content and navigation change increases risk and makes problems harder to diagnose. If they must happen together, the inventory and testing plan need greater depth.
Do we need Search Console's Change of Address tool?
It is useful for eligible domain-level moves after the new site and redirects are live, but not for every URL or hosting change. Property verification, sitemaps and monitoring remain important regardless.
Connected expertise
Explore our services.
Connect domain planning with search strategy, technical diagnosis, AI visibility, content and website clarity.
Before you move
Map the risk before changing the address.
Tell us what is changing, which domains are involved and when the transition is expected. We will help identify the safest place to begin.
Discuss your domain move ↗