Before consolidating domains, run four pre-migration checks: a complete URL inventory, a traffic and rankings baseline, a one-to-one redirect map from every old address, and a calendar freeze that keeps the cutover out of year-end giving. The preparation is what protects your organic traffic. The redirect push itself is the easy part.
The short version
- A domain consolidation loses traffic because URLs get dropped or redirected to the wrong page, not because Google penalizes mergers.
- Google recommends permanent server-side redirects, 301 or 308, and keeping them in place for at least a year so signals transfer.
- Inventory every indexed URL and baseline your rankings before you touch anything, or you will not be able to prove what broke.
- If year-end giving funds your organization, do not cut over in November or December. The window to migrate safely this year is closing now.
- Use Search Console's Change of Address tool for a domain move, and make one change at a time.
Why consolidations lose traffic, and it is almost never the redirect itself
Most of the organic traffic that disappears in a consolidation was thrown away, not penalized. It gets lost because somebody forgot a batch of URLs, or pointed a hundred old pages at the new homepage to “clean things up.” Google's own redirects documentation is clear that the indexing pipeline uses a permanent redirect “as a signal that the redirect target should be canonical.” That transfer only happens when the old URL points to its true equivalent. Redirect an old program page to the homepage and you have told Google the two are the same thing. They are not, so the signal evaporates and the ranking goes with it.
I am in the middle of consolidating two enterprise domains into one right now, and the single most valuable artifact in the whole project is not the redirect file. It is the spreadsheet that proves what traffic and rankings looked like the week before we flipped the switch. Without that, the first time a board member or a donor asks why December traffic dipped, you are guessing. With it, you can say exactly which pages moved, which held, and which need a second look.
Step 1: Build a URL inventory you can trust
You cannot redirect what you never counted. The most common failure in a nonprofit domain consolidation is an incomplete URL list, because the real inventory lives in four or five places that rarely agree with each other.
Pull indexed pages from Google Search Console (GSC), historical landing pages from Google Analytics 4 (GA4), every XML sitemap the site has ever published, a fresh crawl of the live site, and, if you can get them, server access logs. A membership association I worked with had collected three domains over fifteen years, and the crawl kept surfacing live URLs the sitemap had never listed. Those orphaned pages still ranked, still earned links, and would have been silently dropped if we had trusted the sitemap alone. Deduplicate the combined list, then sort by organic traffic and inbound links so you know which URLs actually carry weight.
Step 2: Baseline before you break anything
Export your current performance before the migration, because after it you will have no honest way to measure the damage. Seasonality alone can swing a nonprofit's traffic sharply between October and December, so a raw before-and-after comparison will lie to you unless you captured the baseline first.
Export the full GSC performance report, queries and pages, for at least the trailing 16 months. Save your top 50 landing pages by conversions in GA4, not just by sessions, because a page that drives donations matters more than a page that drives bounces. Record your positions for the keywords that actually bring in members and donors. This baseline is also what lets you separate migration damage from the normal year-end swing, which is the difference between a calm board report and a panicked one.
Step 3: Map every URL one-to-one
Every old URL gets exactly one best destination, and a blanket redirect to the homepage is not a destination. Google treats redirects to irrelevant pages as effectively soft 404s, so a lazy catch-all throws away the exact signal you are trying to preserve.
Build the map as a simple two-column file: old URL, new URL. For pages with no obvious match, decide deliberately whether to recreate the content, merge it into a related page, or let it go, and write that decision down. Use permanent server-side redirects. Google says to “use a permanent server-side redirect whenever possible” and that a server side redirect “has the highest chance of being interpreted correctly.” Only reach for JavaScript redirects if your stack genuinely cannot do server-side or meta refresh. If you want a repeatable way to decide which pages are worth keeping, I wrote up the scoring method I use in how I scored 436 pages for a domain migration.
Step 4: Freeze the calendar, and this is the timely part
The single best technical migration can still cost you the year if you ship it in the wrong week. Today is early October. GivingTuesday lands on December 1, and year-end giving runs hard through December 31. That is your highest-traffic, highest-revenue window of the year, and it is the worst possible time to introduce crawl errors, redirect loops, or a two-week ranking wobble while Google reprocesses your site.
Google recommends keeping redirects live for “at least 1 year” so it can “transfer all signals to the new URLs,” and it advises making changes “one after the other, not everything at the same time.” Read those two together and the timing rule writes itself. Either ship the consolidation before the end of October, which leaves a few weeks to catch and fix problems before traffic peaks, or wait until January. There is no safe middle. If you are reading this in mid-November with a merger half-planned, the right move is almost always to pause and relaunch in the new year. I have talked more than one organization out of a Thanksgiving-week cutover, and none of them regretted waiting.
For a true domain change, submit the move in Search Console's Change of Address tool after the redirects are live. Note that the tool is only for domain or subdomain moves, not for switching to HTTPS or moving paths within the same domain, both of which Google handles without it.
What this does not cover
This checklist is the readiness audit, not the whole migration. It does not cover multi-language setups, where hreflang mapping and per-locale redirects add real complexity. It does not cover a simultaneous replatform, moving content management systems at the same time as the domain, which Google explicitly warns against and which deserves its own plan. It also does not cover content pruning strategy or the paid media and email tracking parameters that break quietly when a domain changes. Each of those is a separate workstream, and trying to do them all in one week is how consolidations go wrong.
Frequently asked questions
How long does it take Google to process a domain consolidation?
Expect weeks, not days, and plan for some ranking volatility in between. Google keeps redirects as a signal and says to leave them in place for at least a year so it can recrawl old URLs and reassign the links pointing at them. Most of the movement settles within a month or two if your redirect map is clean, but the long tail of less-crawled pages can take longer.
Should I redirect old pages to the homepage if there is no matching page?
No. Google treats a redirect to an irrelevant page as a soft 404, so it passes little to no value and can leave the page out of the index entirely. If there is no equivalent page, either recreate the content at a sensible new URL or let the page return a 404 or 410 on purpose. A deliberate 404 is cleaner than a misleading redirect.
Do I lose my backlinks when I consolidate domains?
Not if you use permanent redirects and keep them live. Google's documentation says permanent redirects let it reassign links on other sites that point to your old URLs to the new ones. The links themselves still live on other people's sites pointing at your old domain, so if you ever drop the redirects, that equity disappears. This is why the at-least-a-year rule matters.
Can I still migrate during year-end giving if I absolutely have to?
You can, but shrink the risk. Freeze every other change, migrate one tightly scoped section rather than the whole site, keep the old URLs responding, and watch Search Console's coverage and crawl stats daily for the first two weeks. If the organization depends on December revenue, though, the honest answer is usually to wait until January rather than gamble your biggest fundraising window on a clean crawl.
Run the checklist before you move
If you are staring at two or three domains and a December deadline, book a 20-minute pre-migration read-out. I will walk your URL inventory and your redirect plan and tell you plainly whether to ship before the end of October or wait until January. Either way, you will go into your year-end window knowing your traffic is protected.