In 2011, CrazyEngineers moved from vBulletin to XenForo. The migration itself was super smooth. XenForo's developers had an automated migration service that did all the work, and I didn't have to touch anything technical.
Then our Google traffic dropped about 40%. It stayed down for six to seven months.
Nothing was lost. The content was all there. But every URL had changed. We'd been running vBSEO on vBulletin, which gave our threads one URL format, and XenForo had its own. So Google had to recrawl the whole site and work out the new structure from scratch.
I don't think I set up redirects from the old URLs. I'm not certain, it was a long time ago. But if I didn't, it was one of the biggest mistakes I've made.
In 2018, we moved again, from XenForo to a platform I built myself. This time I kept every thread URL exactly as it was. Links to crazyengineers.com/threads/ from the XenForo days still work today. That has helped us a lot.
This guide is everything in between those two moves: how to map your old URLs, redirect them properly and keep the Google traffic you spent years earning.
The best redirect is the one you don't need
Before you map a single URL, ask your new platform one question: can you keep our old URLs exactly as they are?
If the answer is yes, most of this guide doesn't apply to you. Google only has to re-read your pages. It doesn't have to find them again.
If the answer is no, you need redirects. A redirect is a signpost on the old address that says "this page lives here now". Done right, people and Google follow it, and most of the page's ranking value goes with it.
Ask this before you sign, not after.
Step 1: List the URLs that matter
You can't redirect what you haven't listed. Pull old URLs from four places:
- Your database export: every thread, post, forum, member profile and article, with its ID.
- Your sitemap: what you've been telling Google about.
- Google Search Console: export your top pages from the Performance report. These are the pages that bring people in today.
- Pages other sites link to: any backlink tool will give you your most-linked pages. Lose those and you lose the links too.
The pages in Search Console and your backlinks list are the ones you check by hand later. The rest you handle with rules.
Step 2: Find the patterns
Forum URLs follow patterns, and that's what makes this possible on a big community. You're not mapping hundreds of thousands of URLs one by one. You're writing a handful of rules.
A few common thread URL patterns:
- phpBB: viewtopic.php?t=123
- vBulletin 3: showthread.php?t=123
- vBulletin with vBSEO: /forum-name/123-thread-title.html
- XenForo: /threads/thread-title.123/
- Discourse: /t/thread-title/123
See the number? That's the thread ID. If the ID survives the migration, one rule can redirect every thread you have: take the ID from the old URL, send it to the new URL with the same ID.
Tip: Ask your migration team to keep the old IDs, or at least to keep a table of old ID to new ID. Without one of those, you're matching titles by hand, and titles aren't unique.
The big forum platforms work this way. XenForo's official redirect add-on for vBulletin uses the import log to send old vBulletin URLs to the right place, and XenForo's import notes warn that if you ever delete or empty that log table, the redirects stop working, permanently. Discourse calls its version permalinks, and many of its official importers create them for you.
Step 3: Decide where everything goes
Threads are the big one, but they're not the only pages with traffic. Go through each type:
- Threads: to the same thread.
- Links to a single post inside a thread: to the thread, ideally to that reply. Old forums link to posts a lot.
- Forums and categories: to the matching channel or category.
- Member profiles: to the same member's profile, if it's public on the new platform.
- Attachments and images that other sites embed: to the same file, if you can.
- Search pages, RSS feeds, login and other system pages: these rarely matter. Let them go.
Content you're deliberately removing doesn't need a redirect. Let it return a proper 404 or 410.
Don't redirect everything that doesn't match to your homepage. It feels safe, but Google's site move guide warns that many old URLs pointing at one irrelevant page, like the homepage, might be treated as soft 404s, which is Google's way of saying "missing". Your visitors land somewhere useless too. Send each page to its closest real match, or let it go.
Step 4: Use permanent, single-hop redirects
Three rules, and they're not optional:
- Permanent. Use 301 (or 308) redirects. Google shows the new page in search results for a permanent redirect, and keeps showing the old one for a temporary 302. Wrong message for a migration.
- Server-side. The redirect should happen on the server, not with JavaScript after the page loads.
- One hop. Old URL straight to the final new URL. Google can follow a few hops, but every extra hop is another chance for something to break. If you've migrated before, update the old redirects too, so nothing goes old → older → new.
Step 5: Test before you launch
On your staging copy, test the rules against real old URLs:
- Every URL from your Search Console top pages.
- Every URL from your most-linked pages.
- A random sample of a few hundred more, across every pattern.
For each one, check three things: it returns a 301, it lands on the right page in one hop, and that page loads.
Fix anything that fails, and test again. This is slow, boring work. Do it calmly before launch, not in a panic after.
Step 6: Launch, then watch
On moving day, turn the redirects on at the same moment the new community goes live. Then:
- Check a sample of old URLs again on the live site.
- Submit your new sitemap in Search Console.
- Watch the Pages report for new 404s every day for the first few weeks, and fix the patterns behind them.
Keep the redirects for as long as you can. Google's site move guide says generally at least a year. Keep them forever if you can. They cost almost nothing, and old links on other sites keep sending people for years.
What to watch after launch, and what's normal, is in SEO after a community migration.
Moving to a new domain too?
If the domain changes as well, say from a subdomain on your vendor to your own domain, everything above still applies. On top of that, use the Change of Address tool in Google Search Console, which tells Google the whole site has moved to another domain or subdomain. You have to own both the old and the new site in Search Console, which isn't always possible when the old one was the vendor's subdomain. If you can't, the redirects have to do the work on their own.
If only the paths change and the domain stays the same, Google says to just add redirects and update your sitemaps.
If you're moving to Jatra
Once a thread is published on Jatra, its URL never changes: not when the title is edited, not when it moves to another channel. So this is the last time your community goes through a URL change.
For the move itself, we plan the redirect map with you as part of the migration: which old URLs matter, how the patterns map and what gets tested before launch. Start with the free community migration planner or talk to me about your migration.
The rest of the move, people included, is in the community migration guide.
Frequently asked questions
Do I need redirects if I keep the same domain?
Yes, if any URL changes. The domain staying the same doesn't help when the paths change. Google sees /threads/my-question.123/ and /t/my-question/123 as two different pages.
Should I use 301 or 302 redirects for a forum migration?
301 (or 308). A migration is permanent, and a 301 tells Google that. Use a 302 only for something genuinely temporary.
How long should I keep redirects after a migration?
Google's site move guide says generally at least a year, and its Change of Address help page says at least 180 days, longer if the old URLs still get traffic. Keep them forever if you can. They're cheap, and links on other sites keep sending people for years.
What happens if I don't set up redirects?
Old links break, visitors from Google land on errors and Google has to discover your community again from scratch. When we changed every URL in 2011, our traffic dropped about 40% for six to seven months.
Can I redirect old URLs to the homepage?
Not as a blanket rule. Google says many old URLs redirected to one irrelevant page, like the homepage, might be treated as soft 404s, and visitors land somewhere useless. Redirect each page to its closest real match.