A Guide to Website Migration Without Losing Organic Search Visibility

A new website is exciting: a fresh design, a faster platform, sharper branding. Yet many Norwegian businesses launch their new site and then watch organic traffic fall within weeks. Pages that used to rank vanish from Google, enquiries slow down, and nobody is quite sure why.

Usually the cause is simple. Old URLs were not redirected, valuable content was cut in the redesign, or the new site was accidentally blocked from search engines on launch day. For a business in Oslo, Bergen or Trondheim that relies on organic search for leads, a few months of lost visibility can cost far more than the new website itself—making specialized digital marketing services in Norway critical to protecting your existing organic traffic. 

The good news is that most of these losses are preventable. A well-planned website migration protects the rankings, links and traffic you have spent years building, so your new site starts strong rather than from zero. It comes down to eight steps:

1. Plan the migration and benchmark your current performance.
2. Crawl and inventory every URL on the old site.
3. Map old URLs to new ones and set up 301 redirects.
4. Preserve content and on-page SEO on pages that already rank.
5. Check the technical setup on staging before launch.
6. Follow a launch day checklist to catch problems immediately.
7. Monitor closely after launch and fix issues fast.
8. Measure recovery and keep improving.

This guide walks through each step for businesses in Norway, with a migration risk table, a NOK example of what a failed migration can cost, Norway-specific checks, a summary in Norwegian, common mistakes and 12 FAQs.

What a Website Migration Is and Why Visibility Drops

A website migration is any significant change that can affect how search engines find, understand and rank your site. That includes obvious projects such as moving to a new domain, but also redesigns, CMS or platform changes, new URL structures and merging websites. Even when the design is the only thing you meant to change, a lot often changes behind the scenes.

Google has built up an understanding of your old site over time: which URLs exist, what each page is about and which external links point to it. When that changes without clear signals, rankings can drop. These are the most common causes of lost visibility after a migration:

• Missing or incorrect redirects, so old URLs return 404 errors and lose the value of their backlinks.
• Removed or thinned content, where pages that ranked well are cut or shortened during the redesign.
• Changed titles, headings and internal links that weaken the signals search engines relied on.
• Blocked crawling or indexing, such as a staging robots.txt file or noindex tag left in place at launch.
• Technical problems, including slower pages, broken canonical tags, missing hreflang or JavaScript that hides content.
• Lost tracking, which makes it hard to spot problems quickly and diagnose them.

Some short-term fluctuation is normal after any migration while search engines recrawl and process the changes. A well-planned migration keeps that dip small and short.

Website Migration Types and Their SEO Risk

Not every migration carries the same level of risk. A design refresh on the same URLs is very different from changing domain, platform and URL structure all at once. The table below shows common migration types, what changes and what to protect most closely.

Where you can, avoid combining several high-risk changes in one launch. Changing domain, platform and URL structure at the same time makes problems harder to diagnose and recovery slower.

Step 1: Plan the Migration and Benchmark Current Performance

Successful migrations start long before launch day. SEO should be part of a redesign or platform project from the first meeting, not added in the final week. Early planning also gives you a clear baseline, so you can tell after launch whether performance has dropped and by how much.

Put these planning steps in place before design or development begins. They make the rest of the project much smoother:

• Define the scope: list exactly what is changing, such as domain, platform, URLs, design, content or languages.
• Bring everyone into one plan: SEO, developers, designers and content owners, each with clear responsibilities.
• Choose a sensible launch date outside your busiest season and away from holidays when the team is away.
• Benchmark performance: export organic traffic, key events, top landing pages and rankings for your most important keywords from GA4, Google Search Console and your SEO tools.
• Record your most valuable pages by traffic, conversions and backlinks, since these need the most protection.
• Agree on success measures, such as returning to baseline organic traffic and enquiries within a set period.
• Plan a rollback in case something goes seriously wrong at launch.

Keep the benchmark data safe. After launch, it becomes your reference for spotting problems and showing progress. If your GA4 setup is unreliable, fix it first with our guide to GA4 marketing channels and conversions.

Step 2: Crawl and Inventory Every URL on the Old Site

You cannot protect what you do not know exists. Many websites have far more URLs than the team realises, including old campaign pages, PDFs, images, filtered category pages and blog posts from years ago. Some of these still rank or attract backlinks, and losing them costs traffic.

Build a complete list of existing URLs from several sources. These are the most useful:

• A full site crawl with a tool such as Screaming Frog or Sitebulb, capturing URLs, status codes, titles, headings, canonical tags and internal links.
• XML sitemaps, which may list pages the crawl misses.
• Google Search Console, especially the Performance report for pages receiving impressions and clicks.
• GA4 landing pages, to find pages that receive organic or paid traffic.
• Backlink tools, to identify URLs with external links pointing to them.
• Your CMS export, to catch pages, posts, files and media that are not linked anywhere.
• Google Ads, email and campaign links, so paid landing pages and newsletters do not break.

Combine everything in one spreadsheet and remove duplicates. Then mark each URL by priority, such as high traffic, high conversions, strong backlinks or low value. This becomes the foundation of your redirect map.

Step 3: Map Old URLs to New URLs and Set Up 301 Redirects

Redirects are the most important part of most migrations. A 301 redirect tells browsers and search engines that a page has moved permanently and helps pass the old page's signals to the new one. Without redirects, old URLs return 404 errors, visitors from bookmarks and links hit dead ends, and rankings fall.

Create a redirect map that pairs every important old URL with the most relevant new URL. Follow these principles:

• Redirect one-to-one wherever possible, sending each old page to its closest equivalent on the new site.
• Do not send everything to the homepage. Google may treat irrelevant redirects like missing pages, and visitors get frustrated.
• Use 301 (permanent) redirects for permanent moves, not temporary 302 redirects.
• Avoid redirect chains and loops. Point each old URL straight to its final destination.
• Handle URL variations, such as http and https, www and non-www, trailing slashes and uppercase letters.
• Include PDFs, images and other files that rank or have backlinks.
• Let obsolete pages return 404 or 410 if there is no relevant replacement, rather than forcing an unrelated redirect.
• Update redirects from earlier migrations so they point straight to the new URLs.

Test the redirect map on the staging site before launch, then again as soon as the site goes live. A redirect map is only as good as its implementation.

Step 4: Preserve Content and On-Page SEO

Redesigns often focus on looks and simplicity, and content gets cut along the way. A service page that used to have detailed explanations, prices and FAQs becomes a short paragraph and a large image. It may look cleaner, but if that content helped the page rank and convert, removing it causes a drop that redirects alone cannot fix.

Protect the elements that help your pages perform. These checks matter most on high-priority pages:

• Keep valuable content on pages that rank or convert, and improve it rather than cutting it.
• Carry over title tags and meta descriptions, or improve them deliberately rather than replacing them with templates.
• Keep headings meaningful, so H1s and H2s still describe the page topic clearly.
• Preserve internal links, so important pages are still linked from navigation, related pages and content.
• Keep structured data, such as Organization, LocalBusiness, Product, FAQ or Article schema, and test it on the new templates.
• Retain image alt text and file names where they add value.
• Merge rather than delete when consolidating overlapping pages, keeping the best content from each.

Improving content as part of the migration is fine, as long as it is deliberate. Joined-up content marketing and search engine optimisation planning lets you upgrade pages without losing what already works.

Step 5: Check the Technical Setup on Staging Before Launch

A staging site lets you test the new website before search engines and visitors see it. It is the safest place to catch technical problems, but it also causes one of the most common migration mistakes: staging settings that block search engines get copied to the live site at launch.

Protect the staging site from indexing, then run thorough checks before going live. Work through these items:

• Block staging properly, ideally with password protection, so it is not indexed during development.
• Crawl the staging site to check status codes, titles, headings, canonical tags, internal links and broken links.
• Check canonical tags point to the correct live URLs, never to staging URLs.
• Check hreflang tags if you have Norwegian and English versions, so each version points to the right equivalent.
• Test page speed and mobile usability with PageSpeed Insights and real devices.
• Check rendering, so important content and links are visible to search engines even if the site relies on JavaScript.
• Prepare new XML sitemaps listing only the final live URLs.
• Review the live robots.txt so it does not block important sections.
• Test forms, tracking and consent, including GA4 key events, Google Ads conversions and your cookie consent banner.

A careful staging review is far cheaper than fixing a broken launch. If your project involves a new platform, make sure your website design and web development partners build these checks into their process.

Step 6: Follow a Launch Day Checklist

Launch day is when most migration problems are either caught or slip through. A clear checklist and the right people on hand make it far easier to fix issues within hours rather than weeks.

Run through these checks as soon as the new site goes live, and assign each item to a named person:

• Remove staging blocks: confirm there is no password protection, noindex tag or robots.txt disallow rule blocking the live site.
• Test redirects: crawl the list of old URLs and confirm each one returns a single 301 to the correct new URL.
• Check key pages: open your most important pages and confirm content, titles, headings and calls to action are correct.
• Submit new XML sitemaps in Google Search Console and Bing Webmaster Tools.
• Use Google's Change of Address tool if you have moved to a new domain. Google's Change of Address tool guide explains that you must own both properties in Search Console, and that HTTP-to-HTTPS moves do not need the tool.
• Verify the new property in Search Console if the domain or protocol has changed.
• Check tracking: confirm GA4, Google Ads conversion tracking, call tracking and consent mode all work on the live site.
• Update Google Ads and campaign links so paid traffic lands directly on new URLs rather than going through redirects.

Keep the old domain registered and the redirects in place for the long term. Google's guidance is at least 180 days, and Google's John Mueller has recommended at least a year. Keeping them permanently is safest.

Step 7: Monitor Closely After Launch

The first weeks after launch are critical. Search engines need time to recrawl your site and process redirects, and this is when problems appear in the data. Close monitoring lets you fix issues before they cause lasting damage.

Check these signals daily for the first week, then weekly for at least two to three months. Compare everything with your pre-launch benchmark:

• Crawl errors and 404s in Google Search Console and in a fresh crawl of the old URL list.
• Indexing status, including whether new URLs are being indexed and old ones are dropping out as expected.
• Organic traffic and key events in GA4, compared with the same period before launch.
• Rankings for your most important keywords, especially those that drive enquiries.
• Redirect behaviour, watching for chains, loops or redirects pointing to the wrong pages.
• Page speed and Core Web Vitals, since new templates sometimes perform worse than expected.
• Paid campaigns, checking that Google Ads landing pages work and conversions are still recorded.
• Enquiries and sales, since some issues, such as broken forms, never show up in SEO tools.

Keep a dated log of every issue found and fixed. It explains changes in performance and speeds up troubleshooting if problems return.

Step 8: Recover Quickly and Measure the Impact

Even well-planned migrations can see a temporary dip while search engines process the changes. How long it lasts depends on the size of the site, the type of migration and how cleanly it was done. Google notes that most pages on a medium-sized site can move within a few weeks, while larger sites take longer.

It helps to know what is at stake. Here is an illustrative example for a Norwegian service business where each new client is worth around NOK 25,000:

• Before the migration: 10,000 organic visits a month. At a 1% enquiry rate that is 100 enquiries, and 20% become clients: 20 new clients worth NOK 500,000 a month.
• After a poorly planned migration: missing redirects and lost content cut organic traffic by 40% to 6,000 visits. That means 60 enquiries and 12 new clients worth NOK 300,000 a month.

That is NOK 200,000 in lost new business every month. If the drop lasts six months, the loss reaches about NOK 1.2 million, many times what proper migration planning usually costs. The figures are illustrative, but they show why planning pays.

A small, short dip is normal; a large or lasting drop needs action. If traffic falls more than expected, work through these recovery steps:

• Find the pages that lost the most traffic by comparing landing page data before and after launch.
• Check their redirects, making sure each old URL points to the right new page with a single 301.
• Compare old and new content on those pages and restore anything important that was removed.
• Check indexing and canonical tags for pages that no longer appear in search results.
• Fix internal links so important pages are well linked again.
• Protect enquiries with paid search while organic visibility recovers, using targeted PPC ads on well-built pages (see our guide to Google Ads landing page experience).

Most recoverable issues come down to redirects, content, indexing or internal links. Fixing them quickly shortens the recovery period.

Website Migrations in Norway: Local Checks

Most migration best practice applies everywhere, but Norwegian businesses have a few extra points to plan for. Domain rules, Norwegian characters, two written standards and local directories can all trip up an otherwise solid project.

Add these Norway-specific checks to your migration plan. They are easy to overlook in a busy project:

• Moving to or from a .no domain: .no names are administered by Norid and registered through approved registrars, and organisations need a Norwegian organisation number. Check eligibility early, and never let the old domain expire while redirects depend on it.
• æ, ø and å in URLs: most Norwegian sites use plain alternatives such as "ae", "o" and "a" in slugs. If the new site changes this convention, every affected URL needs its own redirect.
• Norwegian and English versions: keep a clear structure, such as /nb/ and /en/ subfolders, and use the hreflang language codes "nb" or "no" for Norwegian. If you also publish Nynorsk, give it its own "nn" version.
• The Norwegian calendar: avoid launching just before fellesferie in July, at Easter or in the busy weeks around Black Week and Christmas, when key people are away or demand peaks.
• Vipps, Klarna and checkout: on e-commerce sites, re-test Vipps MobilePay, Klarna and card payments end to end, and add payment domains as unwanted referrals in GA4 so sales are not credited to them.
• Local listings and links: update your website address on Google Business Profile, Gule Sider, 1881, Proff, Finn and industry directories, and ask partners and local media to update their links.
• Prices on new templates: check that prices shown to consumers still include MVA after the move, especially on new product and service templates.

If you serve several cities, check that location pages for Oslo, Bergen, Trondheim and Stavanger survive the migration with their content and redirects intact. Our local SEO team checks this as part of every move.

Norwegian Compliance Basics for Website Migrations

A migration is also a good moment to check that the new site meets Norwegian rules. Consent banners, forms and accessibility are often rebuilt from scratch, and gaps can appear without anyone noticing.

Check these points before launch:

• Cookie consent (ekomloven): since 1 January 2025, Norwegian rules require valid consent for non-essential cookies such as analytics and advertising. Reinstall and test your consent banner and Google's consent mode on the new site.
• Privacy and GDPR: update your privacy policy if the platform, forms or data processors change, and sign data processing agreements with new suppliers.
• Universal design: Norwegian websites must meet universal design requirements based on WCAG. Test new templates, forms and menus for accessibility before launch.
• Prices and marketing claims: prices shown to consumers must include MVA, and claims on new pages must be accurate under markedsføringsloven.

This is general information, not legal advice. Check with a qualified adviser if you are unsure how these rules apply to your business.

Sammendrag på norsk

En ny nettside eller et nytt domene trenger ikke å bety at du mister synligheten i Google. Det viktigste er å planlegge migreringen tidlig og beskytte sidene som allerede gir trafikk og henvendelser.

• Lag en måling av trafikk, rangeringer og konverteringer før prosjektet starter.
• Lag en fullstendig oversikt over alle eksisterende URL-er.
• Koble hver gamle side til den mest relevante nye siden med 301-omdirigeringer, ikke til forsiden.
• Behold innholdet, titlene og internlenkene som allerede rangerer godt.
• Test alt på et testmiljø, og sjekk at nettsiden ikke er blokkert for søkemotorer når den går live.
• Bruk verktøyet for adresseendring i Google Search Console hvis du bytter domene.
• Sett opp samtykkebanner, samtykkemodus og sporing på nytt, og oppdater nettadressen i Google Business Profile, Gule Sider og 1881.
• Følg nøye med i Search Console og GA4 de første ukene, og rett opp feil raskt.

Med god planlegging kan den nye nettsiden starte sterkt i stedet for å begynne på nytt.

Common Website Migration Mistakes

Most migration losses come from a small number of avoidable mistakes. Many happen because SEO joins the project too late or launch day is rushed. Watch out for these:

• Starting SEO planning after the new site is built, when key decisions are already locked in.
• No complete inventory of old URLs, so valuable pages are forgotten.
• Redirecting everything to the homepage instead of to relevant pages.
• Using temporary 302 redirects where permanent 301 redirects are needed.
• Leaving redirect chains from old and new migrations combined.
• Cutting content that ranked, in the name of a cleaner design.
• Leaving staging settings live, such as noindex tags or a blocking robots.txt.
• Forgetting tracking and consent, so performance cannot be measured after launch.
• Launching just before fellesferie, Easter or Christmas, when nobody is around to fix problems.
• Letting the old domain expire or removing redirects too soon.

Why BeBran Digital Is the Best Marketing Agency for Website Migrations in Norway

A website migration touches SEO, design, development, content, tracking and paid search at the same time. When those sit with different suppliers, the gaps between them are where rankings get lost. BeBran Digital marketing agencies Norway brings them together under one accountable team.

Here is what sets our approach apart for businesses across Norway:

• SEO from day one: we join before design starts, so URL structure, content and templates are planned with search in mind.
• Complete redirect maps: every valuable URL is inventoried, mapped and tested on staging and again at launch.
• Design and development under one roof: our website design and web development teams build the migration checks into the project.
• Norway-ready setup: natural Norwegian content, hreflang for Bokmål and English, .no domain moves, consent mode and universal design.
• Paid search as a safety net: Google Ads support to protect enquiries while organic visibility settles.
• Reporting on what matters: calls, qualified leads and revenue tracked before, during and after the move.

How BeBran Helps You Migrate Without Losing Visibility

If you are planning a new website, platform or domain, BeBran can help you protect the search visibility you have already earned. We are a senior-led digital marketing team working as one partner across SEO,website design,web development,content marketing and PPC ads.

Here is what working with BeBran looks like:

• A migration plan and benchmark created before design and development begin.
• A complete URL inventory and redirect map, tested on staging and again at launch.
• Content, metadata and technical SEO checks, including hreflang, structured data, consent and tracking.
• A monthly roadmap with direct access to the specialists doing the work.
• A dashboard that tracks calls, qualified leads and revenue, so you can see performance before, during and after the move.

Ready to launch your new website without losing your Google rankings?Book a call with BeBran and let us plan your migration together.

Start catching, stop chasing.

BeBran Digital: Best Digital Marketing Agency in Norway.

Frequently Asked Questions

What is a website migration?

A website migration is any major change to a website that can affect search visibility, such as moving to a new domain, changing platform or CMS, restructuring URLs, redesigning templates, merging sites or adding language versions.

Will I lose rankings when I migrate my website?

Some short-term fluctuation is common, but large, lasting losses are usually preventable. Careful planning, complete 301 redirects, preserved content and thorough technical checks keep the impact small.

How long does it take to recover after a website migration?

It depends on the size of the site and the type of migration. Google notes that most pages on a medium-sized site can move within a few weeks, while larger sites take longer. A clean migration often settles within a few weeks to a few months.

What is a 301 redirect?

A 301 redirect tells browsers and search engines that a page has moved permanently to a new URL. It sends visitors to the new page and helps pass the old page's signals to it.

Should I redirect old pages to the homepage?

Not as a general rule. Redirect each old page to its most relevant new equivalent. Sending many pages to the homepage frustrates visitors, and Google may treat those redirects like missing pages.

How long should I keep redirects in place?

Keep them for as long as possible, ideally permanently. Google's Change of Address guidance says at least 180 days, and Google has recommended at least a year, because old links, bookmarks and search results keep sending visitors to old URLs.

What should I do in Google Search Console when changing domain?

Verify both the old and new domains, set up 301 redirects, then use the Change of Address tool from the old property. Submit the new XML sitemap and monitor indexing and errors closely.

Can I change domain from .com to .no without losing SEO?

Yes, if you redirect every important URL to its equivalent on the new domain, use the Change of Address tool, update internal links and listings, and keep the old domain registered so redirects keep working. Check Norid's eligibility rules for .no first.

Should I change URLs during a redesign?

Only if there is a clear benefit, such as a much better structure. Keeping existing URLs where possible reduces risk. If you do change them, map and redirect every important old URL.

How do I handle Norwegian characters like æ, ø and å in URLs?

Most Norwegian sites replace them with simple alternatives such as "ae", "o" and "a". Whatever you choose, be consistent, and redirect any URLs that change during the migration.

Do I need to set up cookie consent again after a migration?

Yes. Reinstall and test your consent banner, consent mode and analytics on the new site. Under Norway's Electronic Communications Act (ekomloven), analytics and advertising cookies generally require valid consent.

Who is the best agency in Norway for website migrations without losing SEO?

The best agency for you joins before design starts, builds a complete URL inventory and redirect map, tests everything on staging and at launch, handles .no domains, hreflang, consent and universal design, and reports on leads and revenue rather than rankings alone. BeBran Digital helps businesses in Oslo, Bergen, Trondheim, Stavanger and across Norway on exactly that basis