Consolidating multiple WordPress domains into one site: the 301 strategy that protects SEO.

Most established businesses have accumulated multiple domains over the years: the original brand domain, the rebranded one, the acquired companies' domains, the "we built a microsite for that campaign in 2018" domain. Each has its own SEO authority — backlinks, search ranking, indexed pages — built up over years. The right move is usually to consolidate everything onto a single canonical WordPress site, but a naive consolidation throws away the accumulated SEO value of every retired domain. The work that preserves it is mostly about thoughtful 301 redirects. Here's the strategy that holds up.

The scenario is common enough to count as a category: a business has five or six domains, each with a WordPress site of various vintages, and the marketing team finally decides to consolidate. The reasons are good: one canonical brand, one place to update content, one analytics pipeline, dramatically reduced hosting and maintenance overhead. The risk is that the consolidation throws away the SEO equity each retired domain built up over years.

That equity is real money. A retired domain that ranked well for industry terms, that has dozens of high-quality backlinks pointing to specific pages, that’s been indexed by Google for a decade. That authority can transfer to the canonical site if the consolidation is done right. Or it can evaporate entirely if the consolidation is done wrong. The difference is mostly in the redirect strategy.

What “done wrong” looks like.

The common consolidation mistakes:

• Park the retired domains on a generic landing page. Visitors to old URLs see “this site has moved” with a link to the new homepage. Google sees the same thing and over time drops the indexed pages because the destination doesn’t match the source. SEO authority decays into nothing.
• Redirect every old URL to the new homepage. Slightly better than parking, but still bad. Google penalizes “soft 404s” — redirects that send specific URLs to a generic page that has nothing to do with the source. Authority transfer is severely degraded.
• Let the retired domains expire. Worst case. All backlinks pointing to those domains become dead links. The SEO equity is gone and unrecoverable.

Each of these mistakes happens because the team consolidating doesn’t realize that the retired domains have specific pages that matter, and those pages need specific destinations on the canonical site.

What “done right” looks like.

The correct consolidation maintains a 1-to-1 mapping where it can:

• Every indexed URL on the retired domain gets a permanent (301) redirect to the most relevant URL on the canonical site.
• Where a direct equivalent exists, the redirect points to it (oldco.com/about → newco.com/about).
• Where no direct equivalent exists, the redirect points to the most topically relevant page (oldco.com/services/legacy-product → newco.com/solutions/equivalent-modern-offering).
• Where the page genuinely has no equivalent, the redirect goes to the most-relevant section landing page, not the homepage. (oldco.com/team/jane-smith → newco.com/about/team/ if Jane is no longer at the company, not the homepage.)
• The redirects are HTTP 301 (permanent), not 302 (temporary). Google treats 301s as instructions to transfer authority; 302s are treated as temporary and don’t transfer.

Done well, this preserves the bulk of the SEO authority from each retired domain. Google effectively reads the consolidated site as inheriting what the retired domains had built.

The redirect inventory.

Before any cutover, the team needs an inventory of every URL on every retired domain that matters. Sources:

• Each old site’s sitemap (sitemap.xml or generated via Screaming Frog / Sitebulb).
• Google Search Console history for each domain — lists every URL Google has indexed and what they rank for.
• Backlink analysis (Ahrefs, Semrush, Moz) — lists external pages linking to specific URLs on the retired domains.
• Internal Excel/Notion list of any URL the marketing team specifically wants preserved.

The output is a spreadsheet: one row per old URL, columns for “indexed status,” “backlink count,” “current ranking position for primary keyword,” and “target URL on canonical site.” Rows are sorted by importance (backlink count + ranking + traffic). The top of the list, typically the top 100-500 URLs across all retired domains, gets individual mapping. The long tail gets pattern-based redirects (everything under /blog/ to /insights/, everything under /products/ to /solutions/).

How to implement the redirects at scale.

A few options, depending on the consolidation architecture:

• DNS-level redirects via Cloudflare Bulk Redirects or Workers. The retired domain’s DNS points to a Cloudflare zone, and you can literally upload the CSV spreadsheet you just created directly into Cloudflare’s Bulk Redirects tool. Fast (zero origin hit), infinitely scalable, and costs nothing on a free Cloudflare account. (Note: Cloudflare deprecated legacy ‘Page Rules’ in 2024; use Bulk Redirects and Redirect Rules instead).
• Web-server-level redirects. If the retired domain still has its own hosting briefly during the transition, an .htaccess or nginx rewrite block handles the mapping. Higher maintenance burden (you’re keeping infrastructure alive just for redirects), but useful when complex logic is needed.
• WordPress-level redirects. A redirect-management plugin (Redirection, Yoast Premium’s redirect manager) handles the mappings inside the canonical WordPress site. Works when the retired domain DNS points to the canonical site at the DNS level. Easy for the team to manage; some performance overhead per request.

For a clean consolidation, the Cloudflare Bulk Redirects option is usually best: it turns your mapping spreadsheet directly into edge-level routing with zero origin overhead, the rules are auditable, and the retired domain doesn’t need its own hosting after cutover.

What to verify after cutover.

Once the redirects are live:

• Crawl the retired domains. Every URL should return a 301 to a working destination. Tools: Screaming Frog, the Wayback Machine for the old URL list, Sitebulb.
• Submit change-of-address in Google Search Console for each retired domain (Google has an official mechanism for this).
• Re-submit the canonical site’s sitemap to trigger re-indexing.
• Monitor the canonical site’s Search Console for backlink and ranking changes over the following 4-12 weeks. The authority transfer takes time but should show up.
• Spot-check the highest-value redirects manually (the ones with the most backlinks or highest historical traffic). Confirm they land where intended.

The full authority transfer typically completes over 3-6 months as Google re-crawls and re-evaluates. Patience is part of the job; declaring victory on day one is premature.

When this is worth doing.

The consolidation is worth the effort when:

• The retired domains have meaningful inbound link authority (more than ~50 backlinks each, or a handful of high-authority backlinks).
• The retired domains were indexed and ranking for terms relevant to the canonical business.
• The maintenance burden of running multiple sites is meaningfully high.
• The brand strategy has changed enough that maintaining the old domains as separate properties is confusing rather than valuable.

It’s not worth doing when the retired domains never had meaningful traffic. At that point you can let them expire without losing anything important.

For most established businesses with multiple acquired or rebranded domains, the consolidation is genuinely high-value work, both for the SEO authority preserved and for the operational simplification. The 301 strategy is what makes it preserve rather than destroy.

See legacy modernization for how this fits as part of broader consolidation work.