Should you rebuild on a new domain or redesign incrementally?
Rebuild incrementally in almost every case. A new domain starts with no history, no links and no established crawl pattern, so it discards years of accumulated signals for a clean slate you rarely need. Change domains only for a genuine rebrand or merger — and then redirect path for path, and keep the old domain registered indefinitely.
What each option costs you
A new domain discards everything the old one accumulated — links other sites point at you, the crawl relationship, brand recognition in search. Expect three to six months before local terms produce anything, and longer for competitive ones.
An incremental redesign keeps all of that. Pages get rebuilt in place, URLs stay where they are, and nothing has to be re-earned.
The only genuine reasons to change domain
- A real rebrand where the business name has changed
- A merger or acquisition
- A domain carrying a manual action that cannot be cleared
- A name so misleading it costs you customers
Wanting a fresh start is not on that list. Neither is disliking the current design — design lives on the domain, not in it.
If you must change domain
- Build the redirect map before development finishes, sourced from a crawl, the sitemap, Search Console, analytics and server logs
- Redirect path for path, mapping your top-traffic pages by hand rather than by pattern
- Anything with no equivalent returns 410 rather than redirecting to the homepage
- Keep the old domain registered indefinitely and on auto-renew — the redirect only works while you pay for it
- Use the change of address tool and keep both properties verified
Doing an incremental redesign well
Rebuild in place, section by section, keeping URLs stable. Where a URL genuinely must change, redirect it at the same moment and update every internal link rather than relying on the redirect.
The advantage is that you can measure. A rebuild landed all at once makes every subsequent change ambiguous; a section at a time tells you what helped.
The mistake that compounds
Changing the domain and redesigning in the same release. When traffic moves afterwards, nothing is attributable — you cannot tell whether the migration or the new design caused it. If both must happen, separate them by about a month.
What it costs
A refresh where the structure is sound is $2,500 setup and $750 a month at BayouEdge. A full rebuild with a conversion-focused structure is $5,500 and $1,500. Adding service lines or cities is $8,500 to $12,500 — and the added cost there is content and architecture, not design.
The honest read
If the current site is slow, unclear and does not rank, a rebuild on the same domain fixes all three. Moving domain adds risk and months of delay to a problem the domain was not causing.
Frequently asked questions
When should I move to a new domain?
A genuine rebrand where the name changed, a merger, a domain carrying an unclearable manual action, or a name so misleading it costs customers. Wanting a fresh start is not on that list.
What does a new domain cost me?
Everything the old one accumulated — inbound links, the crawl relationship, brand recognition in search. Expect three to six months before local terms produce anything and longer for competitive ones.
How do I move domains safely?
Build the redirect map before development finishes, redirect path for path with top pages mapped by hand, return 410 where nothing is equivalent, keep the old domain on auto-renew indefinitely, and use the change of address tool.
Why is an incremental redesign easier to judge?
Because you can measure it. A rebuild landed all at once makes every later change ambiguous; rebuilding a section at a time tells you what actually helped.
Can I change domain and redesign together?
You can, and you should not. When traffic moves afterwards nothing is attributable. If both must happen, separate the releases by about a month.