Most redesign horror stories are migration failures. We map every old page to a new one, carry over the content and markup that get you found, and watch the index after launch.
A site can look better and perform worse. Four things cause almost all of it, and every one of them is preventable before the new site goes live.
A new site structure renames pages. If nothing points the old address at the new one, every link and every search result that pointed there lands on an error page.
The pages that answered a specific question are often the ones a redesign deletes for being wordy. Those are frequently the pages search sends people to.
Business details, review markup, service and FAQ markup, and product data exist in the old code. A rebuild that skips them removes information search engines were already using.
Analytics, conversion events, call tracking, and CRM connections are wired to the old pages. If they are not rebuilt and tested, the site looks fine while the reporting goes blank.
Six stages. The first two happen before a single new page is designed, because the redirect map is what decides the structure.
Inventory
A full crawl plus Search Console and analytics data, so we know which pages are indexed, which ones get found, and which ones actually receive inquiries. Nothing is deleted on instinct.
Map
A one to one redirect map written before the build, covering pages, categories, images where they matter, and any old domains still pointing at the site.
Carry over
The copy and questions that earn visibility are kept and improved rather than replaced with shorter marketing lines. Titles, headings, and structured data are ported and checked.
Rebuild tracking
Analytics, conversion events, forms, call tracking, and CRM routing are rebuilt on the new pages and tested with real submissions on a staging address.
Launch
The redirect map goes live with the site, the sitemap and robots file are updated, and the new site is submitted for indexing immediately.
Watch
Coverage, crawl errors, redirect chains, and query data are reviewed after launch so anything that slipped is caught while it is still easy to fix.
This is the structure we build toward on a rebuild: one page per service, areas stated plainly, and the next step above the fold. A migration gets that structure without discarding the pages already doing work.
Whether the new site is scoped as a project or built into a monthly plan depends on its size and complexity. Search work and lead follow-up are scoped alongside it.
It can, when URLs change with no redirects, content is cut, or markup is dropped. That is exactly what the mapping and carry over steps are for. We cannot guarantee positions, because nobody controls the ranking, but we can make sure nothing is thrown away and that we can see what happens after launch.
The content that earns visibility and answers real buyer questions is kept and improved. Pages that exist for no reader get consolidated into one that does, with a redirect from the old address.
A straightforward rebuild for a service business can fit the monthly website plan. A redesign of an established site with a large page library, ecommerce, custom integrations, or a domain move is scoped as a project with an upfront build fee and agreed milestones.
We monitor indexation, redirects, and search queries through the first ninety days. Ongoing search work, paid media, and content are separate services added when they make sense.
We will tell you which pages are worth keeping, what the redirect map has to cover, and whether this is a monthly website or a scoped project.