Illustration of a man checking freshly transplanted young trees in an orchard with a notebook, staking one that leans, while older trees blossom behind him.

SEO After a Community Migration

What to check in Google Search Console after a forum or community migration, day one to month six: indexing, redirects, 404s and rankings, what a normal dip looks like and when to worry.

By Founder, Jatra Updated
Talk through your move See plans

After we moved CrazyEngineers to XenForo in 2011, our Google traffic dropped about 40%. It stayed there for six to seven months.

I wasn't worried. vBulletin 4 had been so bad, slow pages and almost every problem people complained about on vBulletin's own forums, that I knew we were finally on good software. I expected the traffic to come back, and by 2012 it had.

Then, in September 2012, I woke up to find almost 80% of our traffic gone. Not because of the migration this time: a plugin on another part of the site, as I remember it, led Google to crawl at least 400,000 bad URLs in a very short time. Everyone told me 404s don't matter. A flood of them does. I've told that story in full in why your community isn't ranking on Google.

Those two years taught me what to watch after any big change to a community: the slow dip you wait out, and the sudden spike you fix today. This guide is the checklist, from moving day to month six.

What's normal after a migration

How much you lose depends almost entirely on what happened to your URLs.

You kept every URL. Google only has to re-read your pages, and usually only the HTML has changed. Expect a small wobble, not a drop.

You changed URLs and redirected every one of them. Google has to recrawl the old URLs, follow the redirects and move everything across. Rankings move around while it does. Google's own site move guide says to expect temporary ranking fluctuation, and that a small to medium site can take a few weeks for most pages to move. Larger sites take longer. That's normal, and it settles.

You changed URLs without redirects. Google has to discover your whole community again, almost like a new site. Expect a drop for months, like we had in 2011, and there's no guarantee you'll rank the same again.

If you haven't moved yet, read forum URL mapping and 301 redirects before you do anything else.

Moving day: check what staging left behind

The most common launch problems aren't Google's fault. A setting from the staging site gets left switched on. Check these within the first hour:

  • robots.txt isn't blocking the site. A staging "Disallow: /" left in place stops Google cold. Paste yours into the robots.txt validator.
  • No noindex tags on public pages. Open a few threads and look.
  • Canonical tags point to the new live URLs, not the staging domain or the old site.
  • Public content is readable without logging in. Open a thread in a private window.
  • Your sitemap lists the new URLs and loads without errors. Check it with the XML sitemap validator, then submit it in Search Console.
  • Redirects work on the live site: test your top old URLs from Search Console and make sure each one lands on the right page in one hop.
  • Structured data made it across. Run a few thread URLs through the schema validator.

The first two weeks: watch the errors

Open Google Search Console every day. In the Pages report, watch three things:

  • Not found (404). A few is normal. A sudden flood means a pattern is broken: a redirect rule that doesn't match, or a plugin generating URLs that don't exist. Find the pattern and fix it today. That was my 2012 lesson.
  • Page with redirect. These are your old URLs. The count should go up as Google finds the redirects, and that's fine.
  • Crawled or discovered, but not indexed. Some is normal. If your best threads are in here, inspect them one by one with the URL Inspection tool.

Use URL Inspection on your top 20 pages too. Check that Google can fetch each one and sees the same content you do.

Months one to six: compare the right numbers

Don't stare at the total traffic line every morning. It'll wobble and it'll make you nervous.

Compare page by page instead. Take your top pages from before the move, find where each one lives now, and compare clicks and impressions for the same period. You want to see impressions moving to the new URLs as the old ones fade.

Hold your nerve. If you're playing by the rules, if you're doing the right things, you shouldn't worry about temporary changes. In Google's world they can last three to six months.

And don't change anything else while Google re-learns your site. No redesign, no category shuffle, no rewriting old titles in bulk. Keep post dates, like counts and authors exactly as they were. Give Google one change to digest, not five.

When to worry, and what to check

If traffic is still sliding after the first couple of months, or it drops suddenly, here's the order I'd check things in:

  1. The technical side of your public pages. Internal links, and especially pagination. Pagination is where most communities get it wrong: infinite scroll with no real page links hides older threads from Google, because Googlebot doesn't scroll or click. Each paginated page needs its own canonical URL, so page 2 points to page 2, not page 1. Check your links too: member links should be rel="ugc nofollow", and your own internal links should be normal links.
  2. Content quality. Be honest: does this forum deserve to rank? A migration is a good moment to move thin, off-topic threads into a private section that isn't indexed.
  3. The shape of the drop in Search Console. Did a few big pages lose their rankings, or did the whole site go down evenly? A few pages points to something specific on those pages or their redirects. The whole site points to something site-wide: a crawl problem, a robots or noindex mistake, or an algorithm update that happened to land the same month.

Don't confuse a Google update with a migration problem. Check the Google Search Status Dashboard for recent ranking updates before you tear anything apart.

How Jatra handles this

Jatra was built by someone who lost traffic to a URL change, so the defaults are the things this guide checks:

  • Once a thread is published, its URL never changes.
  • Every public page is plain HTML that loads without a login, with structured data for discussions and Q&A.
  • Pagination uses real page links with their own canonical URLs.
  • Member links get rel="ugc nofollow" automatically.
  • Sitemaps are built for you.

If you're planning a move, the rest of the process is in the community migration guide. Or talk to me about your migration.

Frequently asked questions

How long does SEO take to recover after a forum migration?

If you kept your URLs, there's usually little to recover. With full 301 redirects, rankings move around for a while as Google recrawls, then settle. Without redirects, expect months. Ours took six to seven months in 2011.

Why did my traffic drop after migrating my community?

Most often: URLs changed without redirects, a staging setting like noindex or a robots.txt block went live, public pages now need a login, or a redirect pattern is broken and sending people to 404s. Check those before anything else.

What should I check in Search Console after a migration?

The Pages report (404s, redirects, pages not indexed), URL Inspection on your top pages, your submitted sitemap, and a page-by-page comparison of clicks and impressions against the same period before the move.

Should I submit a new sitemap after a migration?

Yes. Submit the sitemap with your new URLs in Search Console on moving day, and check it loads without errors.

Planning a move? Plan your community migration with Jatra.

Plan your migration

Community builder since 2005.

Kaustubh Katdare

Founder, Jatra

A note from the founder

I write from the work, not the sidelines.

I'm Kaustubh Katdare. I've been building online communities since 2005, from growing CrazyEngineers to hundreds of thousands of members to creating Jatra. These articles draw on the work I still do myself: auditing platforms, planning migrations, protecting years of searchable knowledge, and helping community teams build something people want to return to.