Rebuilding a 10,000+ Page Website Without Losing SEO
A website with more than 10,000 pages needed a complete redesign, and thousands of those pages were indexed and ranking. Meek Media planned the rebuild so search value carried across: URL architecture, page templates, metadata migration, redirects, structured data, internal linking and a structured launch QA process that checked the new site before and after it went live.
- Client
- Large website (10,000+ pages)
- Privacy
- Client name withheld
How do you redesign a large website without losing SEO?
Treat SEO as a build requirement from day one. On this 10,000+ page rebuild, Meek Media planned the URL architecture, built SEO into every template, migrated metadata at scale, mapped redirects for every changed URL, carried structured data across, preserved internal linking and ran launch QA against the full URL set.
Why is redesigning a 10,000+ page site so risky for SEO?
The client's website had more than 10,000 pages and needed a complete redesign. Thousands of those pages were indexed, and their rankings had to survive the change. A redesign at that scale touches almost every signal Google uses: URLs, templates, titles and descriptions, structured data, internal links and the way pages connect.
On a small site, a mistake affects a few pages and can be fixed by hand. On a site this size, one template error is repeated across thousands of URLs the moment it ships. A missing canonical tag, a dropped meta description field or a navigation change that orphans a section can wipe out visibility across whole categories overnight. Redirects have to be defined for every URL that changes, and at this volume that cannot be done by hand one page at a time. The challenge was to deliver a new site while treating every existing ranking as something to protect, and to prove it worked before and after launch.
What we found
- More than 10,000 pages in scope for a complete redesign
- Thousands of indexed pages with rankings to preserve
- URL architecture that had to be planned before build
- Metadata needing migration across every page template
- Redirects required for every URL the new structure changed
- Structured data and internal linking at risk in new templates
How did Meek Media protect rankings through the rebuild?
Instead of auditing SEO at the end, we built it into the project plan. Decisions about URLs, templates and data were made with search in mind before development started. Everything was handled by rule and template rather than page by page, then verified at scale in staging and again after launch.
-
1
URL architecture planning
The first decision was which URLs would stay the same. Keeping existing URLs wherever possible is the safest way to preserve rankings. Where the new structure required changes, we designed clean, logical, consistent patterns that reflect the site hierarchy. Every current URL was inventoried from crawls, sitemaps, analytics and Search Console so nothing indexed was left out of the plan.
-
2
SEO-ready templates
Each page template was specified with its SEO elements built in: one H1, a clear heading hierarchy, self-referencing canonical tags, indexation controls, crawlable HTML links and fields for titles and descriptions. Because each template powers many pages, checking the template carefully protects every page it generates. Templates were reviewed in staging before any content was loaded into them.
-
3
Metadata migration at scale
Titles, meta descriptions and other page-level metadata were exported from the old site and mapped to the matching pages on the new one. Pages with hand-written metadata kept it. For pages without it, rule-based templates generated unique, descriptive values. Bulk checks then flagged blanks, duplicates and truncation so the migration did not quietly replace good metadata with generic defaults.
-
4
Redirect mapping by rule and exception
With thousands of URLs involved, redirects were defined through pattern rules for predictable changes, plus a one-to-one map for exceptions and high-value pages. Every changed URL got a permanent 301 to its closest equivalent. The full map was tested against the old URL list to catch chains, loops, errors and redirects to irrelevant pages before launch.
-
5
Structured data and internal linking
Structured data from the old site was inventoried and rebuilt in the new templates using valid schema.org markup that matches visible content. Internal linking was modelled so navigation, breadcrumbs, category pages and related links kept important pages close to the homepage and prevented orphans. Link targets pointed at final URLs, not redirects. Orphaned sections were ruled out before launch.
-
6
Launch QA before and after go-live
The staging site was crawled in full and compared against the live site for status codes, canonicals, metadata, structured data, internal links and indexability. On launch, redirects were tested against the complete old URL list, updated sitemaps were submitted and staging blocks were confirmed removed. Search Console was then monitored for crawl errors, indexing changes and unexpected drops.
What We Delivered
- Complete inventory of existing indexed URLs
- New URL architecture and naming rules
- SEO specification for every page template
- Metadata migration map with bulk validation
- Rule-based and one-to-one 301 redirect map
- Structured data implementation across templates
- Internal linking model for the new site
- Pre-launch and post-launch QA checklists and crawl reports
What Other Teams Can Learn From This
Keep URLs unless there is a real reason to change them
A new design does not require new URLs. Every URL you change needs a redirect and gives Google something to re-process. Where the existing structure works, keep it. When change is necessary, make it once, make it consistent and plan it so redirects can be written as clear rules. Consistency matters more than perfection.
Audit templates, not just pages
On a large site, a template is the unit of risk. A single mistake in one template can hit thousands of pages at once. Review each template's SEO elements in staging, then crawl a sample of pages built from it. Fixing a template before launch is far cheaper than fixing its output after launch.
Crawl staging like it is already live
Launch QA should compare the new site with the old one at full scale, not rely on spot checks. Crawl staging for status codes, canonicals, metadata, structured data and links, and test every old URL against the redirect map. Just make sure staging stays blocked from indexing until launch, then unblock it on the day.
Frequently Asked Questions
Will a website redesign hurt my SEO?
It can, but it does not have to. Redesigns hurt SEO when URLs change without redirects, content is cut, metadata is lost or templates break technical signals. When those elements are planned from the start and checked before launch, a redesign can keep rankings stable and often improve them.
How do you create redirects for thousands of URLs?
Use pattern-based rules for predictable URL changes, such as a folder being renamed, and a one-to-one map for exceptions and high-value pages. Then test the complete list of old URLs against the rules to catch errors, chains and loops before launch. Manual, page-by-page work does not scale safely.
What should be checked before launching a large redesign?
Crawl the staging site and confirm status codes, canonical tags, titles, descriptions, headings, structured data, internal links and indexability. Test redirects against the full old URL list. Check sitemaps. On launch day, remove staging blocks such as noindex tags or password protection and confirm the live site can be crawled.
Does structured data need to be migrated in a redesign?
Yes. Structured data lives in page code, so new templates often lose it unless it is rebuilt deliberately. Inventory existing markup, add it to the new templates, make sure it matches visible content and validate it before launch. Missing markup can cost pages their eligibility for rich results.
Related Case Studies
Recovering a Website After a Google Algorithm Traffic Collapse
After a major Google update, this site lost 60–80% of its organic traffic. Meek Media audited everything that shapes how Google judges a site: content quality, backlinks, site architecture, duplicate pages, search intent and technical SEO. We then rebuilt the organic strategy around the pages that deserved to rank, rather than chasing the update itself.
Read the case study →
Core Web Vitals Rescue for a High-Traffic Website
This website had strong traffic but failed Core Web Vitals. Heavy scripts, large images, layout shifts, slow server responses and third-party integrations were all dragging down the experience. Meek Media tackled the problem on two fronts, optimising the front-end architecture and the server infrastructure behind it, so pages loaded faster, responded quicker and stayed visually stable.
Read the case study →
Fixing Millions of Crawled URLs With Only Thousands of Valuable Pages
Search engine bots were crawling millions of URLs on a site that only had thousands of pages worth ranking. Filters, archives, parameters, internal search results, pagination variants and duplicates were soaking up crawl activity. Meek Media restructured how the site exposed URLs so crawlers concentrated on valuable pages and the index reflected what the business actually wanted found.
Read the case study →
Facing a similar problem?
Every engagement starts with a free audit. We find what is holding your site back, show you the fix, and scope the work to your goals before you commit.