A website redesign loses rankings when pages Google already trusts disappear, move without a redirect, or lose the words that made them rank. You keep those rankings by treating the old site as an asset. List every address and what it earns, then decide what happens to each one. Point each old address at its true replacement, and watch Search Console closely after launch.
We are writing this for the owner or marketing lead of an established Irish business planning a rebuild. If your current site brings in enquiries from Google, that traffic deserves protecting before anyone opens a design file.
What causes the drop
Ranking loss after a redesign is rarely a mystery. It comes from a short list of causes, and a launch that goes wrong usually hits more than one.
Changed addresses with no redirect
Google ranks individual addresses. If /services/conveyancing/ becomes /what-we-do/legal/ and nothing connects the two, the old address returns an error page. The history it built up goes with it, and links from other websites now point at nothing.
Pages dropped in the tidy-up
Rebuilds tend to cut content. An old blog post or a plain location page can look like clutter and still bring in steady visits every week. Delete it without checking and that traffic simply stops.
Titles and headings rewritten for tone
A new copywriter replaces "Solicitors in Galway" with "Your partners in law". The page reads better and no longer matches what people type into Google.
Slower pages
Large background videos, heavy scripts and oversized images slow a new site down. Speed is one signal among many, but a slow page on a phone loses visitors before it loses rankings.
Crawling blocked by accident
Staging sites are hidden from Google with a noindex rule or a robots.txt block. If that setting reaches the live site, Google is told to drop every page. It can also come back later, when a routine update changes how the server behaves.
No measurement
If nobody recorded clicks and positions before launch, nobody can say what changed afterwards. Nor can they say which pages to fix first.
The order of work
None of this is difficult. It is detailed, and it has to happen in the right order, before launch rather than after.
- Inventory every address with its traffic. Crawl the current site and export page data from Search Console for at least the last 90 days. Include PDFs, old campaign pages and addresses that still get visits although nothing on the site links to them.
- Decide keep, merge or retire for each one. A kept page has the same job on the new site. A merged page folds into a stronger one. A retired page has no direct equivalent, so it points to the nearest useful section rather than the homepage.
- Map the redirects one to one. Every old address gets a permanent (301) redirect to its closest match, in a single step. Chains of redirects slow Google down, and sending hundreds of pages to the homepage is treated much like deleting them.
- Carry over what earns traffic. For pages that bring in visits, keep the title, the main heading and the substance of the copy. Improve the writing by all means, but keep the words people search for.
- Test on staging. Before launch, run the full redirect list against the new site and confirm every old address lands on a working page. Check for broken links, missing titles and how fast key pages load on a phone.
- Launch and check the basics the same day. Confirm the live site is open to Google, robots.txt is correct and no page carries a noindex header. Submit the new sitemap in Search Console.
- Watch Search Console for the first weeks. Compare clicks by page against the baseline from step one. Fix any missing redirect the day it shows up. Some movement in the first fortnight is normal. A steep fall on particular pages usually points to a lost redirect or rewritten copy.
Budget for this as its own piece of work. If you are still at the budgeting stage, our guide to what a business website costs in Ireland explains where migration sits in the overall cost.
How we did it for Colin Graham Residential
Colin Graham Residential (CGR) is an estate agency in Northern Ireland. The new site had to serve buyers, sellers and renters better while keeping the search traffic the old site had earned. You can read the full project on our CGR case study.

The old site ran on ASP.NET. Before launch we crawled it, then built the redirects from that crawl and 90 days of Search Console page data.
One detail shows why the inventory matters. Property pages on the old and new sites follow the same pattern, with the area, a listing number and the street. But the property software issued every listing a new number. On paper the addresses looked unchanged. In practice every old property link would have broken.
So the new site matches an old property address to the same listing under its new number. If the property has since sold or been withdrawn, the visitor goes to that town's listings instead. Old search pages, paginated results, brochure PDFs and old development pages all have their own rules. Each one reaches its new equivalent in a single redirect.
We kept the www version of the domain as the main address. The old site and the existing Search Console property already used it. Changing it would have added a redirect to every page for no gain.
We also used the rebuild to earn more search traffic. Buyers and renters now have their own page for each town. Those pages ranked for searches like "houses for sale ballyclare" but carried no local copy. So we added a summary of each area to them. Listings carry structured data that describes each property to Google. The site also publishes separate sitemaps for its pages, areas, town listings, properties, blog and new developments.
In the first month after the new site went live, clicks from Google were up 51%.
That is how we approach every website we rebuild for an established business. Design and copy get the attention, but the migration decides whether the new site starts ahead or behind.
What to ask whoever builds your site
Whoever you choose, these questions will tell you quickly whether the migration has been thought through.
- Will you give us a list of every current address and where each one goes on the new site?
- Which of our pages bring in search traffic today, and how will you keep their titles, headings and copy?
- Will every redirect be permanent and reach its destination in a single step?
- How will you confirm the live site is open to Google after launch, and after later updates?
- What will you measure after launch, against which baseline, and for how long?
- If a missing redirect turns up three weeks after launch, who fixes it and how quickly?
If you are planning a rebuild and want the rankings you have earned to carry across, you can start a project with us.
