Site Migration Without Loss: Proper 301 Redirect Setup

Loss of traffic after a domain change — a classic scenario. A client moves, forgets to set up 301s, and search engines see 404s. In our experience, an e‑commerce site with 50,000 URLs saw a traffic drop of 80% in a week after migration. Proper mapping and correct redirects restored positions within a month. Without 301s you lose not only traffic but also link equity. Preserving rankings is far cheaper than relaunching ads. Saving budget on position recovery is another strong argument for a quality migration. A typical 301 redirect setup starts at $500, saving thousands in potential ad spend.

Proper 301 redirect setup preserves up to 99% of rankings. Even a single missed URL can cost thousands of visits per month.

What is 301 and why is it important?

HTTP 301 — code "Moved Permanently", passing 90–99% of PageRank to the new page. In comparison, 302 passes less than 10% — ten times worse. Google typically transfers positions within 2–8 weeks after correct setup. Use only 301 for permanent changes. For temporary campaigns or A/B tests, 302 is acceptable, but for migration — only 301.

Why is checking redirect chains important?

A chain of multiple redirects (e.g., A→B→C) dilutes the transferred link equity. Each step loses 5–10% of PageRank. We ensure chains do not exceed one step. After migration we crawl the site with Screaming Frog to detect such issues. On one project, a three‑step chain reduced weight transfer by 25% — fixing it restored traffic in two weeks.

How to avoid traffic loss during migration?

Before the move we compile a full URL mapping, paying special attention to high‑traffic pages and backlinks. After deployment we monitor Google Search Console for 404s. Over the next month we track positions and adjust redirects if needed. It is also useful to check www and non‑www versions of the domain to avoid additional gaps. Also, consider canonical tags and indexation settings to prevent duplicate content issues.

Practice case: migration of a site to Laravel. The original site was on WordPress with 15,000 URLs. We automatically imported the structure into the admin panel, set up redirects via middleware with Redis caching. After deployment we monitored 404s — found 2% errors caused by case‑sensitive paths. Fixed within an hour.

What is included in 301 redirect setup (turnkey)

Our turnkey service includes:

1. Audit of the old site: crawl all URLs, analyze traffic from Google Search Console, and evaluate crawl budget.
2. Map each old URL to a new one, prioritize by traffic and backlinks and link equity.
3. Implement redirects via .htaccess, Nginx, or middleware (Laravel, Django, Node.js) — we handle all technical details.
4. Test chains, absence of 404s, and correct weight transfer using Screaming Frog and Ahrefs.
5. Monitor in Google Search Console for 30 days after deployment.
6. Deliverables: detailed documentation of all redirects, access to monitoring dashboard, training for your team on redirect management, and 30 days of support.
7. Get a project estimate — contact us for a free consultation.

Migration strategy

Before the move:

• Crawl the old site (Screaming Frog, Sitebulb) — export all indexable URLs.
• Check via Google Search Console — find pages with traffic and rankings.
• Map old URLs to new ones (mapping table).
• Prioritize high‑traffic pages.

301 redirect setup process

Post‑migration checks

• Screaming Frog: crawl new site, verify redirect chains (no more than one step).
• Google Search Console: monitor Coverage → Not Found (404).
• Ahrefs/Semrush: verify backlinks are correctly redirected.
• Check www and non‑www versions of the domain.
• Validate canonical tags and indexation status.

Setup time: 1–3 days depending on mapping volume. Get a consultation on redirect setup before migration — it reduces risks. Order an express audit of current redirects to ensure correct weight transfer. Contact us for a turnkey solution or project estimate.

Website Redesign and Migration: CMS Change, SEO Preservation

A client came to us 6 weeks after a self-attempted redesign: 'We moved from WordPress to Tilda, traffic dropped by 70%.' I opened Google Search Console — 847 pages returned 404, the URL structure had completely changed, not a single 301 redirect was in place. Yandex hadn't reindexed the new site yet, positions collapsed. Recovery took 4 months and resulted in significant revenue loss for the quarter. Our experience — over 7 years and 80+ successful migrations, we guarantee position retention with the right approach.

Why Do Migrations Break SEO?

Search engines have indexed specific URLs. If /catalog/shoes/nike-air-max-270 turned into /products/nike-air-max-270 without a 301 redirect — all the link equity, traffic, and rankings go nowhere. Google says 301 passes ~99% of PageRank, but in practice positions recover over 2–8 weeks, not instantly.

Commonly, SEO gets broken not out of malice, but because a developer doesn't view the URL structure as a public API. Here are typical breakages:

How to Recover Traffic After a Failed Migration?

If traffic dropped, act immediately:

1. Crawl the new site for 404s and compare with the pre-migration URL list.
2. Create redirects for all lost pages with traffic >0.
3. Check structured data and meta tags on a test sample.
4. Daily monitor Coverage in Search Console and positions for top 50 queries.
5. If after 2 weeks traffic does not recover — deep audit of redirects (transitivity, chains, loops).

In our practice, a large e-commerce site lost 50% of traffic when moving from Bitrix to React + Strapi. We restored 95% of redirects in three days, and within 3 weeks traffic returned to 90% of original.

What Does a Pre-Migration Audit Include?

Before starting development on the new site:

1. Full crawl of current site via Screaming Frog or Sitebulb. Get list of all indexable URLs with traffic from Google Search Console.
2. Export all pages with organic traffic >0 over the last 6 months — these are priority for redirects.
3. Record all external backlinks to specific pages — Ahrefs, Semrush.
4. Snapshot current positions for key queries — baseline for post-migration comparison.
5. Save Core Web Vitals from Search Console for the previous 90 days.

Table for recording:

Contact us for a detailed pre-migration audit — we will help identify all risks and create an action plan.

URL Mapping and Redirects

For projects with 200+ pages, we create a mapping table: old URL → new URL → status (301, merged with another page, deleted). Each row is verified: does the content actually migrate here?

In Laravel, redirects are handled via configuration file and middleware, not .htaccess — faster and more manageable. For WordPress → Next.js: redirects are set in next.config.js (static) and at the Nginx/CDN level for dynamic ones. Old .htaccess on shared hosting with 500+ lines of redirects is a special hell. Each redirect is checked sequentially, performance suffers. We move to Nginx map directive or Redis cache for dynamic lookup. More at Wikipedia: HTTP 301.

How to Migrate Content from Different CMSs?

WordPress → Headless CMS (Contentful, Strapi, Sanity): WordPress REST API or WP All Export to export posts, meta fields, media files. Migration script in Node.js: parse export, transform structure, upload via CMS API. Media files are reuploaded to new storage, links updated in content. Typical problem — shortcodes in WordPress content ([gallery id="123"]): need parser and transformation to new format.

1C-Bitrix → modern stack: Bitrix stores content in non-standard tables with IBLOCK_ELEMENT_PROPERTY. Direct SQL export via phpMyAdmin or Bitrix API. Transformation is the longest part due to specific Bitrix data structure.

Heavy WYSIWYG → structured content: Years of editing in FCKEditor/TinyMCE leave inline styles, non-standard tags, broken attributes. HTML sanitize + transformation to Markdown or Portable Text (Sanity) with manual check of problematic pages.

How to Preserve Technical SEO Elements During Migration?

Structured data (Schema.org) — if the old site had Product, Article, BreadcrumbList markup, they must be on the new site too. Google Search Console → Enhancement reports will show loss of rich snippets.

Sitemap XML: generated automatically, submitted to GSC a day after launch. Old sitemap remains until full reindexing.

hreflang for multilingual sites: if tags are lost during migration, conflicts between language versions in search results will start within weeks.

Open Graph and Twitter Card meta tags — often forgotten when changing template, pages stop displaying correctly when shared on social networks.

Launch and First Weeks Monitoring

DNS propagation: DNS switching takes up to 48 hours, plan launch with buffer. Cloudflare as DNS provider — propagation takes minutes, not hours.

After launch, monitor daily: Search Console → Coverage (indexing errors), Analytics → organic traffic, year-over-year comparison, crawl site for 404 errors.

First 2 weeks are critical. If traffic drops more than 30% — immediate audit of redirects and comparison with pre-migration crawl.

What the Service Includes

Results you receive:

1. Migration plan with URL mapping and redirects in Excel/Google Sheets format.
2. Configured 301 redirects at server level (Nginx/Cloudflare/Vercel).
3. Migrated content with integrity check: images, meta fields, links.
4. Structured data (Schema.org) on the new site, identical to old or improved.
5. SEO report: position trend at 1, 3, and 6 weeks after launch.
6. Coverage monitoring in Search Console with error notifications.
7. Guaranteed position retention: if traffic drops more than 15% within the first month — free audit and correction.

Timelines and Estimates

• Redesign with migration for a small site (up to 100 pages): 4–8 weeks.
• E-commerce migration with 500+ product pages: 8–16 weeks.
• Only technical migration part (redirects, metadata) without redesign: 1–3 weeks.

Cost is calculated individually based on scope.

Get a consultation for your project — we will respond within a day. Order a pre-migration audit of your site and receive a detailed proposal with a redirect plan. Contact us to discuss details.