Redesigning Your Website Without Losing Search Visibility: A Migration Checklist

Most redesign projects are judged on how the new site looks on launch day. The more useful question is what happens six weeks later, when the organic traffic report comes in and someone asks why enquiries are down. A redesign that loses search visibility can quietly cost more than the build itself — and in a market like Montenegro, where a handful of well-ranked pages can carry an entire sales season, that loss is hard to recover from quickly.

Redesigns do not damage rankings because the design changed. They damage rankings because URLs, content, internal links, metadata and tracking changed at the same time, usually without a record of what existed before. This checklist is designed to prevent that.

Step 1: Define what is actually changing

Projects described as "just a redesign" often involve four separate changes bundled together. Separate them explicitly before you start:

• Visual redesign only — same CMS, same URLs, same content. Lowest risk.
• Replatform — new CMS or framework, URLs likely change, templates rebuilt.
• Information architecture change — pages merged, split, renamed or removed.
• Domain change — rebrand, moving from a .me to a .com, or consolidating two sites into one.

Each additional layer multiplies the risk and the testing required. If you can stage them — redesign first, domain change later — do so. Diagnosing a traffic drop is far easier when only one variable moved.

Step 2: Take a baseline before anyone touches anything

You cannot prove a migration went well, or fix it when it didn't, without a record of the previous state. Capture all of this while the old site is still live:

• A full crawl of the existing site: every URL, its title, meta description, H1, status code and canonical tag.
• Search Console exports for the last 12–16 months: queries, pages, countries and languages. Export, don't rely on the interface retaining history.
• Analytics exports: top landing pages by sessions and by conversions, not just traffic. A page with modest traffic that produces viewing requests matters more than a popular blog post.
• Backlink data: which URLs have external links pointing at them. Portal listings, press mentions, partner sites and directory entries all point somewhere specific.
• Current conversion rates and enquiry volumes, so you have something honest to compare against later.

Store these somewhere the whole team can reach. Six weeks after launch, a baseline spreadsheet is worth more than anyone's memory of how the old site was structured.

Step 3: Map every URL, one by one

This is the single most important task in a migration, and the one most often rushed. Build a spreadsheet with the old URL in one column and the new URL in the next. Every old URL needs a destination.

Rules that keep the map clean

• Redirect to the closest equivalent page, not to the homepage. Mass redirects to the homepage are treated as soft 404s and waste the link equity you are trying to preserve.
• Use permanent (301) redirects, not temporary ones, and avoid redirect chains — old URL should point straight to the final new URL, not through two intermediate steps.
• Handle retired property listings deliberately. A sold unit or closed development should redirect to its parent project or category page, not disappear. These pages often hold accumulated links and rankings.
• Do not forget non-HTML assets: brochures, floor plan PDFs, price lists and images that are linked from elsewhere.
• Check both trailing-slash and non-slash variants, plus any legacy parameter URLs.

Step 4: Protect multilingual structure

Sites serving Montenegrin, Russian, English, German and Serbian audiences are especially exposed during migrations. Common failures include dropping a language version because it was "only partly translated", losing hreflang annotations, or replacing language-specific URLs with a single page that switches content via cookies.

Keep each language on its own crawlable URL. Preserve the hreflang relationships between equivalents, and make sure every language version is included in the redirect map and the new sitemap. If a translated section is being retired, redirect it to the same section in the closest language rather than to a language homepage.

Step 5: Carry the content across, not just the layout

Minimalist redesigns frequently strip body text in the name of cleanliness. The result is a beautiful site with nothing for a search engine to understand. Before signing off on new templates, check that:

• Page titles and meta descriptions have been migrated or deliberately improved — not auto-generated.
• H1s exist and describe the page, rather than being replaced by a hero image with text baked into it.
• Descriptive copy on location, project and service pages survived the redesign.
• Structured data has been reimplemented on the new templates — organisation and local business details, hotel or accommodation markup, FAQs, reviews where genuinely present.
• Images have meaningful filenames and alt text, and internal links between related pages were rebuilt rather than reduced to a single navigation bar.

Step 6: Launch-day checks

The failure that causes the most damage is also the simplest: shipping the staging site's noindex tag or robots.txt block into production. Build a short launch checklist and have one named person run it within an hour of going live:

1. Confirm indexing is allowed — check robots.txt and the meta robots tag on several page types.
2. Test a sample of redirects from the map, including deep pages, PDFs and old language URLs.
3. Submit the new XML sitemap in Search Console; keep the old one accessible briefly so redirects get discovered.
4. Verify analytics and conversion tracking fire on form submissions, phone clicks and WhatsApp or Viber links.
5. Submit every enquiry form yourself and confirm the lead reaches the CRM with the correct source attribution.
6. Check canonical tags point to the live domain, not staging.
7. Confirm SSL, www/non-www handling and page speed on mobile.

Step 7: Monitor for the first eight weeks

Some ranking fluctuation after a migration is normal while search engines re-crawl and re-evaluate. What matters is the trend. Watch crawl errors and 404 reports weekly and add redirects for anything you missed. Compare landing-page performance against your baseline rather than against last week. Track enquiry volume separately from traffic — a drop in leads with stable traffic usually points at a broken form or a buried call to action, not at SEO.

Timing matters more than you think

In Montenegro, launching a new hotel site in late June or a development site at the start of the spring buying window means absorbing any migration turbulence during your highest-value weeks. Aim for the shoulder period: late autumn or early winter, when there is room to fix problems calmly before demand returns.

A migration done properly is largely invisible — visitors notice a better site, and the search results keep working. That outcome comes from the spreadsheet work nobody sees, not from the launch announcement.