Content Audit Before Website Migration: Complete Guide

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1250
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947

You are planning to migrate your site to a new CMS? Without a thorough audit of existing content, it's easy to lose SEO traffic and move hundreds of unnecessary pages. Our experience: over 5 years and 100+ successful migrations for sites from 200 to 50,000 pages. We help conduct a full inventory, technical SEO audit, evaluate the quality of each URL, and create a transfer plan. We'll assess your project in 1 day.

Content audit is the inventory and analysis of all materials on the current site. It answers the questions: what to transfer, what to update, and what to delete. Without an audit, you risk losing up to 40% of organic traffic due to broken links and duplicates. Additionally, migration without an audit often leads to cluttering the new CMS with outdated content, increasing load times and complicating maintenance. In the worst case, you lose search positions for 3-6 months. Our approach minimizes this risk. The average project saves up to $3,500 during the transfer phase; our content audit starts from $500 for small sites.

Importance of content audit before migration

Content audit is the inventory and analysis of all materials on the current site. It answers the questions: what to transfer, what to update, and what to delete. Without an audit, you risk losing up to 40% of organic traffic due to broken links and duplicates. Our Python crawler processes the site 3 times faster than manually copying all URLs.

Step-by-step process

  1. Crawl the site – collect all URLs and metadata using Screaming Frog SEO Spider.
  2. Collect metadata – export CSV with title, meta description, H1, status, word count, etc.
  3. Analyze SEO performance – merge crawl data with Google Search Console export to identify traffic and keyword metrics.
  4. Classify content – label each URL as migrate, update, merge, delete, or archive based on traffic, uniqueness, and relevance.
  5. Generate report – provide summary statistics, detailed tables, and prioritized action plan.

How is content inventory performed?

We start with site crawling. The main tool is Screaming Frog SEO Spider. It allows quick collection of metadata. Configuration:

Configuration → Spider → Crawl all subdomains
Enable: JS rendering (for SPA)
Export: All tabs → Save as CSV

Result: CSV with fields: URL, Title, Meta Description, H1, Status Code, Indexability, Word Count, Inlinks, Outlinks. For deeper analysis, we use a Python crawler:

import scrapy
from scrapy.crawler import CrawlerProcess

class ContentAuditSpider(scrapy.Spider):
    name = 'content_audit'
    start_urls = ['https://books.toscrape.com']
    custom_settings = {
        'DEPTH_LIMIT': 10,
        'DOWNLOAD_DELAY': 0.5,
        'FEEDS': {'audit_results.csv': {'format': 'csv'}}
    }

    def parse(self, response):
        yield {
            'url': response.url,
            'status': response.status,
            'title': response.css('title::text').get(''),
            'h1': response.css('h1::text').get(''),
            'meta_description': response.css('meta[name="description"]::attr(content)').get(''),
            'canonical': response.css('link[rel="canonical"]::attr(href)').get(''),
            'robots': response.css('meta[name="robots"]::attr(content)').get('all'),
            'word_count': len(' '.join(response.css('main *::text').getall()).split()),
            'internal_links': len(response.css('a[href^="/"]')),
            'images_without_alt': len(response.css('img:not([alt])')),
            'last_modified': response.headers.get('Last-Modified', b'').decode()
        }

        for link in response.css('a::attr(href)').getall():
            yield response.follow(link, self.parse)

Why is SEO metadata analysis important?

Export from Google Search Console provides data on clicks, impressions, CTR, and positions. We match these with crawl data in Python:

import pandas as pd

crawl_data = pd.read_csv('audit_results.csv')
gsc_data = pd.read_csv('gsc_pages.csv')

merged = crawl_data.merge(gsc_data, on='url', how='left')
merged['has_seo_value'] = merged['clicks'] > 0

def classify_page(row):
    if row.get('noindex') or row['status'] != 200:
        return 'skip'
    if row.get('clicks', 0) > 100 or row.get('inlinks', 0) > 5:
        return 'migrate_priority_high'
    if row.get('word_count', 0) < 100:
        return 'review_thin_content'
    if row.get('clicks', 0) > 0:
        return 'migrate'
    return 'archive'

How to classify content for migration?

Each page gets a label according to the table:

Decision Criteria
Migrate Clicks > 0, unique content, relevant
Update on transfer Content outdated but has SEO weight
Merge Duplicate pages on the same topic
Delete + redirect No traffic, duplicate, thin content
Do not transfer Test pages, archive, service URLs

Metrics for prioritization:

Metric Threshold Action
Clicks in GSC > 100 High priority
Incoming links (inlinks) > 5 High priority
Word count < 100 Thin content — needs revision
Status code 4xx, 5xx Delete or fix

Media files analysis and metadata inventory

We check which images are used and which are dead weight. Example command for finding unused files:

find /var/www/uploads -type f | awk -F. '{print $NF}' | sort | uniq -c

Also, find pages without meta description and with duplicate titles:

missing_meta = merged[merged['meta_description'].isna() | (merged['meta_description'] == '')]
duplicate_titles = merged[merged.duplicated(subset='title', keep=False)]
missing_meta[['url', 'title', 'h1']].to_csv('tasks_add_meta.csv', index=False)

Why content classification matters

Classification allows focusing on valuable pages and avoiding moving junk. It is the foundation of content strategy and content optimization. Without it, you waste budget transferring thousands of useless URLs. Our labeling system (migrate, review, archive) reduces the volume of transferred data by 50-70%.

Problems solved by content audit

  • Traffic loss: up to 40% of visitors leave after migration without redirects.
  • Cluttering the new CMS: moving unnecessary pages increases load time.
  • Duplicates and thin content: worsen indexing and rankings.

Our audit saves up to 60% of the migration budget by filtering out junk. 85% of our clients see traffic recovery within 2 weeks.

Deliverables

We provide a complete package of results:

  • Documentation: comprehensive report in PDF and CSV formats with full inventory, SEO analysis, and classification.
  • Access: integration setup with Google Search Console for post-migration tracking.
  • Support: 2 weeks of consultation after report delivery.
  • Training: optional knowledge transfer session for your team.

Detailed deliverables:

  • Full URL list with metadata (CSV).
  • Technical SEO issues report.
  • Content classification table with action recommendations.
  • Prioritized migration plan.
Example classification logic

For each page, we assign a label based on traffic, links, word count, and status. Pages with over 100 clicks or 5+ internal links are high priority. Thin content (under 100 words) requires review. Pages with no traffic and no links are archived. This ensures only valuable content moves to the new site.

Our guarantees and experience

We have been working with content audit for over 5 years. During this time, we have conducted 100+ migrations for sites from 200 to 50,000 pages. We guarantee data accuracy and confidentiality. We use certified tools: Screaming Frog SEO Spider and Google Search Console. With 5+ years of experience and 100+ successful projects, we are trusted by companies worldwide.

Contact us for a free consultation. Order a turnkey content audit — get a clear transfer plan with minimal risks.

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:

Problem Cause Solution
Duplicate content New site opened parallel to old Disable indexing of dev version, set canonical
Loss of metadata Title and description left in old CMS Export via API, mass import with verification
Canonical changes Pagination and filters reset Lock before development, implement in template
Speed drop Heavy sections, unoptimized images Optimize LCP, CLS, TTFB before launch

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:

Audit Stage Tool Criticality
URL collection Screaming Frog + GSC High
Page traffic Google Analytics / Search Console High
External links Ahrefs / Majestic Medium
Positions Yandex Wordstat / Serpstat Medium
Core Web Vitals GSC CrUX High

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.

CMS Migration Tools Complexity Risks
WordPress WP All Export, WP-CLI, REST API Medium Shortcodes, meta fields
1C-Bitrix Bitrix API, SQL export High Complex structure, infoblock properties
Joomla J2XML, direct DB export High Outdated extensions
Tilda/Readymag API export (limited) Medium No full content access

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.

Launch checklist (spoiler)
  • [ ] All 301 redirects work and do not form chains
  • [ ] Sitemap submitted to GSC and Yandex.Webmaster
  • [ ] Canonical tags set on all pages
  • [ ] Open Graph / Twitter Card display checked
  • [ ] robots.txt and noindex meta tags adjusted
  • [ ] Core Web Vitals in green zone (LCP <2.5s, CLS <0.1, INP <200ms)

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.