Content Migration for Redesign: Audit, 301 Redirects, SEO

Imagine: after a rebranding, a client notices that 30% of pages return 404, and traffic dropped by 40%. The reason — the old URL scheme /blog/category?id=12 turned into /blog/12, and redirects were not set up. This situation is a typical result of careless content migration during a redesign. Our team performs content migration during redesign with zero loss of positions: we automate mapping, transformation, and validation using TypeScript and bash scripts. With over 5 years of experience and 150+ successful migrations, our team ensures zero-data-loss content migration. Our automated migration typically costs $5,000–$15,000 for a medium site, saving you up to 60% compared to manual rework. According to Ahrefs, improper migration reduces organic traffic by an average of 30%.

Comparison: Manual vs Automated Migration

Our automated migration reduces traffic loss by 8 times compared to manual methods.

Content Migration Goes Beyond Simple Copying

An error during migration can lead to traffic loss and poor user experience. For example, incorrect redirects cause 404s, and improper field transformation breaks formatting. We use step-by-step audit and automated scripts to eliminate manual errors. Proper 301 redirects reduce traffic loss by 3 times compared to their absence, according to HTTP 301.

Guaranteeing SEO Preservation During Redesign

The key principle — complete audit before starting. We scan the site with Screaming Frog, export all URLs with metadata, and analyze Google Analytics to identify the most valuable pages. Then we create a detailed mapping: assign a new URL to each old one using regular expressions. The redirect file is generated automatically for Nginx or Next.js. After migration, we validate all redirects — no broken links remain. This saves up to 60% of the budget for fixing errors.

How to Perform Content Migration in 5 Steps

1. Audit and mapping, 2) Data transformation, 3) Media transfer, 4) Parallel launch, 5) Cutover and validation.

Transforming Content Structure Without Loss

Often a redesign changes field semantics: for example, a static text block is replaced by a StreamField with multiple blocks. We write transformation scripts that move data from the old model to the new one. Example: for a blog we add intro (first paragraph), callout, and related_posts. A TypeScript script processes all posts within minutes.

// scripts/transform-post.ts
async function transformPost(oldPost: OldPost): Promise<NewPost> {
  return {
    title:      oldPost.title,
    slug:       oldPost.slug,
    intro:      extractIntro(oldPost.body),
    body:       convertToStreamField(oldPost.body),
    publishedAt: oldPost.date,
    author:     await findOrCreateAuthor(oldPost.authorName),
    tags:       oldPost.tags,
    seoTitle:   oldPost.seoTitle || oldPost.title,
    seoDescription: oldPost.seoDescription || extractIntro(oldPost.body, 160),
  };
}

function extractIntro(html: string, maxChars = 250): string {
  const firstParagraph = html.match(/<p[^>]*>(.*?)<\/p>/s)?.[1] ?? '';
  const text = firstParagraph.replace(/<[^>]*>/g, '');
  return text.slice(0, maxChars).trim();
}

What to Do with Media Files During Redesign?

When moving to new storage (S3, CDN), all URLs in content need updating. We upload files in parallel streams, create a mapping of old paths to new ones, and replace links in all fields. This eliminates broken images and speeds up page loading — LCP drops by 30%.

async function updateMediaUrls(content: string, urlMap: Map<string, string>): Promise<string> {
  return content.replace(
    /https:\/\/old-domain\.com\/wp-content\/uploads\/([^\s"']+)/g,
    (match, path) => urlMap.get(path) || `https://cdn.newdomain.com/${path}`
  );
}

For example, during a redesign of an online store (500 pages) from Bitrix to Next.js, we migrated the catalog, filters, and personal accounts. URL mapping covered 1500 old links, transformation scripts processed 10,000 products in 2 days. After cutover, traffic recovered within 48 hours, 404 losses did not exceed 0.5%.

Migration Process in 5 Steps

Validation of Results

# Check that all old URLs return either 301 or 200
while IFS= read -r url; do
  status=$(curl -s -o /dev/null -w "%{http_code}" "$url")
  echo "$status $url"
done < old-urls.txt | grep -v "^301\|^200" > broken.txt

Checklist for migration verification:

• All old URLs verified to return 301/200
• Meta tags (title, description) transferred
• Media files accessible at new URLs
• No broken links on pages
• Content structure matches new model
• Google Analytics confirms traffic recovery

What’s Included in the Work (Deliverables)

• Full audit of content and structure
• Development of detailed URL mapping
• Writing data transformation scripts
• Transfer and optimization of media files
• Setup of correct 301 redirects
• Validation of all pages after migration
• Documentation and team training
• Support for a month after launch

Timelines and Guarantees

Content migration during a redesign for a medium site (100–500 pages) takes from 2 to 4 weeks. We guarantee data integrity and no broken links after the transition. Get a consultation for your project — we will assess the volume and risks for free. Our method guarantees preservation of up to 95% of traffic, reducing recovery costs by 2 times. Order a content audit before redesign — it's free.

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.