A forum is one of the worst things to migrate from a search perspective. Its value is decades of deep, internally-linked discussion, and every one of those addresses is about to change. The move is recoverable; the redirect map is what recovers it.
A forum's search position is built from thousands of threads, each with its own address, linked from other threads, from external sites, and from search results themselves. When the platform changes, that structure is replaced with a different one. Without a complete mapping from old to new, the accumulated authority points at addresses that no longer exist — and the loss is gradual, which is what makes it dangerous.
You know the platform change is right and you need the search consequence managed rather than discovered afterwards.
Traffic has not recovered and you need to establish what the redirect strategy missed.
The old platform generated addresses in several different patterns over the years, and the mapping has to account for all of them.
Engineering faults are rarely confined to the engineering layer. These are the commercial consequences we see most often.
Redirecting the main thread pattern and missing profiles, tag pages, search results, pagination and archived forums leaves whole classes of URL dead. The visible decline is then attributed to the platform change rather than to the gap, which makes it much harder to fix.
Threads run to hundreds of pages, each addressable, and replies are quoted across the community. The internal link graph is large, and a redirect strategy that handles only the first page of each thread discards most of that structure.
Even a complete redirect map does not restore visibility immediately. The search engine has to re-crawl, re-evaluate and re-assign, which means the measurement window after the move is as much part of the work as the move itself.
This is stated plainly because it is true. A well-executed migration can hold visibility and sometimes improve it, because the new platform is typically faster and structurally cleaner. No responsible party promises a ranking outcome for a platform change, and any who do are describing their own confidence rather than the mechanism.
Each of these is work we carry out, not an area we advise on.
Enumerating what the forum currently serves, including the patterns nobody remembers creating. Old platforms accumulate several URL schemes over their lifetime — imported content, renamed forums, changed pagination, added features — and every scheme needs mapping.
Building rules per class rather than per URL: threads, replies and their anchors, pagination, member profiles, forums, tags, search results, archived sections. Class-level rules mean new content is covered by the strategy rather than relying on a list that is already stale.
Redirects that express a move rather than a removal, canonicals that agree with where the redirect lands, and consistency between the two. A redirect chain or a canonical pointing at the pre-migration address splits the signals the migration was meant to consolidate.
Updating the links inside the content itself. A forum's posts are full of internal references, and those are the most heavily used paths on the site — a member following an old quote link should not be redirected to reach a thread that is one hop away.
Fragments and page parameters are where forum redirects most often break. A reply permalink is a distinct address that matters to the conversation, and pagination that is not mapped leaves a thread's later pages unreachable.
Recording what the forum's visibility actually is beforehand — indexed pages, impressions, clicks, crawl rate — so recovery is measured against evidence rather than against a feeling about how it used to be.
Tracking crawl, indexation and impressions through the weeks after the move, identifying the classes that have not recovered, and correcting what the redirect map missed. This is where a partial map becomes visible.
Sitemaps regenerated for the new structure, and the same source of truth feeding them as feeds the pages — so a sitemap cannot describe URLs the site does not have.
The sequence is deliberate. The order is usually what determines whether the work holds or has to be repeated.
No redirect strategy is designed until the current URL estate is known. On a forum this is the step that reveals how many schemes exist, and it is frequently more than anyone expected — imported content, an older platform underneath, renamed sections.
A per-URL mapping is stale the moment new content appears. Rules expressed per class apply to everything, including content created after the move, and they can be reviewed by a human because there are tens of them rather than millions.
Redirects activate at the same moment as the new platform. The gap between the two is where search visibility is lost, and it is lost without any visible error — the pages simply return nothing.
Content that genuinely no longer exists is handled as a removal with the appropriate status, not redirected to the homepage. A redirect to an unrelated page is treated as a soft 404 and wastes the equity it was meant to preserve.
Redirects are for external references and for the search engine. Internal links are updated in the content, because routing every internal navigation through a redirect adds latency to the most-used paths on the site.
Crawl, indexation and impressions tracked against the pre-migration baseline for weeks after the move. The report describes what happened rather than asserting success, because rankings fluctuate for reasons outside the migration and a claim of a guaranteed outcome would be false.
Documentation is a deliverable, not an afterthought. On most of these engagements a large part of the value is a defect report precise enough for another team to act on.
Engagements where this capability was the substance of the work rather than a line item.
Since 2019, Soludome has managed infrastructure and platform operations for one of Spain's largest online communities. The work covers server and performance optimisation, CDN architecture, load balancing and site security under sustained traffic.
An established community platform had accumulated three separate problems that compounded each other: page loads that had degraded with growth, search visibility that had not kept pace with the community's authority, and a security posture that had not been revisited as the platform's profile grew. The engagement addressed all three concurrently.
These overlap at the edges. Sending you to the right page is more useful than having you work it out.
Source-schema conversion, compatibility position and reconciliation.
Forum migration to XenForoThe two source platforms with their own importer positions and pages.
vBulletin to XenForo migrationThe general migration discipline, including CMS and replatform moves.
Website migrationsCrawl and indexation constraints beyond the redirect map.
Crawl and indexation diagnosisWe will not put a number on it, and anyone who does is describing confidence rather than mechanism. What can be said is that a complete redirect map, activated with the platform rather than after it, usually holds a forum's visibility across a platform move — and that partial maps reliably do not. The outcome also depends on factors outside the migration: what else changed on the site, what competitors did, and how search infrastructure reassesses a domain after significant change.
No responsible answer promises that. Rankings fluctuate through a migration for reasons that are partly the migration and partly everything else, and a guaranteed outcome is not something anyone can offer for a platform change. What we commit to is a complete and reviewed redirect map, correctness in the status codes and canonicals, and measurement against a baseline so you can see the actual trajectory rather than infer it.
It is normal and it is the main reason this work needs an inventory rather than a pattern. Forums accumulate schemes over their lives — an earlier platform underneath, imported content, renamed sections, changed pagination. Every scheme has to be enumerated and mapped, and the schemes nobody remembers are the ones that leave dead classes of URL behind.
The equivalent page, and where none exists it should be an honest removal rather than a redirect to the homepage. Sending unrelated URLs to the homepage is treated as a soft 404 by search infrastructure, so it does not preserve what it was meant to preserve — it simply hides the fact that the content is gone. Content that genuinely no longer exists is better returned as such, because that is the truthful answer and it is treated as one.
Weeks, and the observation period is part of the engagement rather than an afterthought. Crawl and indexation respond first, impressions follow, and the full picture takes longer than either. We track it against the pre-migration baseline and report what recovered and what did not — which is also how a gap the inventory missed becomes visible while it can still be corrected.
Describe what is happening rather than what you think the cause is. If we are not the right people for it, we will say so.