Changing a domain, moving to a new content management system, switching hosting providers or launching a full redesign are all moments when a business can quietly lose years of accumulated search visibility in a single afternoon. A migration is not just a design project or a developer task — it is a search visibility event, and Google treats it as one. Every URL that disappears, every redirect that points to the wrong place and every tracking tag that fails to fire has a measurable cost.
That is why a professional SEO company treats a migration as a controlled, staged process rather than a one-off launch. The work begins weeks before anything is moved and continues long after the new site goes live. Below is a clear picture of how that process actually looks for Irish businesses, from the first audit through to the post-launch recovery period.
Before the Move: Auditing, Mapping and Protecting What Already Works
The most valuable part of a migration happens before a single file is transferred. The first step is a complete baseline audit of the existing website. That means crawling every page and exporting a full inventory of URLs, HTTP status codes, page titles, meta descriptions, heading structures, word counts and internal links. This export becomes the reference document for the entire project — if a page exists today and performs well, it must exist in some form tomorrow.
Alongside the crawl, the consultant records performance benchmarks. Google Analytics (GA4) is checked to confirm that tracking is working properly and to save a record of organic sessions, landing pages and conversion events. Google Search Console is reviewed for queries, impressions, click-through rates and any existing coverage warnings. Rankings for priority keywords are logged, including local search terms such as “solicitor Dublin”, “emergency plumber north Dublin” or “clinic near Portmarnock”, so that any movement after launch can be measured against reality rather than guesswork.
A backlink review is equally important. Some pages earn external links, citations and mentions over time, and those pages must retain a live URL or a direct redirect. Losing a page that carries strong links can undo years of link-building effort in a day. The same logic applies to a content inventory: each page should be classified as keep, merge, rewrite or retire, with a clear reason noted for anything being removed.
From that inventory comes the single most important deliverable of the pre-launch phase — the URL mapping table. Every old URL is paired with its new destination, ideally one-to-one, with the new site keeping the same or very similar slugs wherever possible. Redirects should point directly at the final destination, never through a chain of two or three hops, and there should be no lazy blanket rule sending everything to the homepage. Working with an experienced SEO Company Dublin at this stage means the mapping is done by someone who understands which pages carry commercial value and which can safely be consolidated.
Practical logistics matter too. The new site should be built on a staging environment that is password protected or blocked from indexing, and the consultant must confirm that the staging robots.txt file does not get pushed live by accident. Launch timing should avoid seasonal peaks, month-end reporting periods and Friday afternoons when developer support disappears for the weekend.
Launch Day and the Technical Checks That Decide the Outcome
Go-live day is short, intense and entirely about verification. The moment the new site resolves on the live domain, the redirect map is tested URL by URL — not sampled, tested. The consultant crawls the live site with the same tool used for the baseline and compares the two crawls side by side. Any old URL returning a 404, a 500 error or an unexpected soft 404 is flagged and fixed immediately, and genuinely retired pages are returned as 410 responses so search engines understand the removal is deliberate.
Server-level configuration then gets a full review. The robots.txt file must be clean and free of leftover “Disallow: /” rules from development. The XML sitemap is regenerated, checked for accuracy and submitted. Canonical tags should be self-referencing, with no stray canonicals still pointing at the staging domain. HTTPS, the www versus non-www preference and trailing-slash consistency all need to resolve to one single version of every page, because duplicated versions split authority and confuse crawling.
Speed and technical health are checked next. Large uncompressed images, render-blocking scripts, outdated plugins and poor hosting are among the most common causes of rankings slipping after a redesign, so Core Web Vitals are measured on the live site rather than assumed. Structured data is carried across, including LocalBusiness schema with opening hours and service areas — critical for tradespeople, clinics and hospitality businesses that depend on local results. Internal linking is reviewed so that the new navigation does not orphan previously strong pages.
Measurement is verified before anyone celebrates. GA4 tracking and conversion events are tested with live submissions. A new Search Console property is verified, and where the domain itself has changed, the Change of Address tool is used. For local businesses, the Google Business Profile website link, categories, opening hours and review responses are updated in step with the launch, since a mismatched profile can quietly suppress local visibility even when the website itself is technically perfect. Where a business also sells into the UK or Europe, hreflang tags and currency or spelling variations are checked to ensure the correct version serves the correct audience.
The Weeks After: Monitoring, Fixing and Reporting
The post-launch period is where migrations are won or lost. In the first fortnight, Search Console is monitored closely for coverage errors, indexing changes and crawl anomalies, and key pages are submitted for indexing to speed up discovery. Rankings are tracked week by week, but always against the pre-migration baseline and by landing page rather than by keyword alone — a page that drops from position four to position nine tells a very different story from a page that has vanished from the index entirely.
Traffic and conversion data are compared like for like. Some fluctuation is normal and expected as search engines re-evaluate the new structure, so the consultant distinguishes between ordinary noise and genuine migration damage. Where a page loses impressions, the likely causes are checked in order: a redirect chain, a missing internal link, altered on-page content, a lost schema markup or a page that was consolidated without a proper redirect. Fixes are applied quickly, because search engines recrawl new sites frequently in the early weeks and problems corrected early rarely cause lasting harm.
Content work resumes once indexing settles. Pages that lost ground are refreshed, thin pages are expanded, and internal links are added to pass authority back to commercial pages. Safe, gradual link-building continues rather than aggressive tactics, since a migration is a volatile moment and stability matters more than speed. Redirect rules stay in place permanently — they should never be deleted once traffic appears to have recovered, because old links and bookmarks continue to arrive for years.
Reporting becomes the client’s window into all of this. Clear monthly reports show what changed, what was fixed and what is planned next, using plain language rather than jargon. For most businesses, ranking movement after a well-managed migration tends to become visible within the first two or three months depending on the site and the competitiveness of the industry, though a careful consultant will always frame timelines as expectations rather than promises. The real measure of a successful migration is simpler: the same pages still rank, the same enquiries still arrive, and the new site gives the business room to grow rather than a hole to climb out of.
Kraków-born journalist now living on a remote Scottish island with spotty Wi-Fi but endless inspiration. Renata toggles between EU policy analysis, Gaelic folklore retellings, and reviews of retro point-and-click games. She distills her own lavender gin and photographs auroras with a homemade pinhole camera.