Migrating a Directory to a New Domain Without Losing Rankings
A practical migration checklist for directories: URL mapping, redirect strategy, what to do about pages you should not carry over, and the realistic recovery timeline.
Directories are harder to migrate than most sites, because the whole value sits in a large set of similar URLs. Get the mapping wrong and you lose the long tail, which is most of the traffic.
This is the checklist. It applies whether you are moving platform, moving domain, or both.
Before anything: inventory
You cannot map what you have not listed.
Export every indexed URL. Search Console coverage report, plus your sitemap, plus a crawl. These three disagree with each other, and the disagreements are informative.
Record traffic and impressions per URL for the last twelve months. This tells you which pages actually matter, and it becomes your recovery benchmark.
Record backlinks per URL. Pages with external links need redirects even if they get no traffic, because the link equity is the point.
Group by template. Category pages, entry pages, facet pages, blog posts. Most mapping decisions are per template, not per URL.
For a small site this is an afternoon. For 25 URLs it is twenty minutes and there is no excuse for skipping it.
Decide what not to carry over
This is the step people skip, and a migration is the best opportunity you will get.
If you have thin facet pages, near-duplicate categories, or entries that were never substantial, do not recreate them on the new domain. Redirect them to the nearest meaningful parent, or let them 410.
Carrying dead weight across preserves whatever quality problem you had, on a domain with no history to absorb it. Given that Google's March 2026 enforcement was site-level in effect, arriving with a cleaner set is worth more than arriving with a complete one.
The rule: carry over a URL if it has traffic, links, or genuine substance. Otherwise consolidate it.
Map every URL explicitly
One to one wherever possible.
Entry pages should map to entry pages, ideally with the same slug. If slugs must change, map each one individually. Do not redirect a hundred entry pages to a category page. Google treats mass redirects to a single destination as soft 404s and the equity evaporates.
Category pages map to category pages. If you are consolidating three categories into one, that is three redirects to one destination, which is fine because the intent genuinely matches.
Blog posts map one to one. These are usually your strongest link targets.
Facet pages are the judgement call. Map the ones with traffic or links, consolidate the rest into their parent category.
Write the map as a spreadsheet with old URL, new URL, and reason. You will need it when something looks wrong in six weeks.
Redirects
301, permanent, every time. Not 302, not meta refresh, not JavaScript.
Single hop. Old URL to final URL. Chains of redirects leak and slow crawling. If you are moving from an old structure that already had redirects, collapse them so nothing goes through two hops.
Keep them forever. Not six months. Links from 2023 still send people, and removing redirects later produces a slow unexplained decline.
Handle the trailing slash and the www variant. Both should resolve to one canonical form with a redirect, not a duplicate.
The technical checklist for launch day
- Canonical tags on the new site pointing to the new URLs, not the old ones
- Sitemap regenerated, containing only the new URLs, submitted to Search Console and Bing Webmaster Tools
- Robots.txt on the new domain not blocking anything you want crawled
- Schema markup present on the new pages, entity type on entries, ItemList on collections, BreadcrumbList throughout
- Internal links updated to point at new URLs directly rather than through redirects
- Analytics and Search Console configured for the new property before you switch, not after
- Change of address submitted in Search Console if the domain is changing
That last one is specific to domain changes and it genuinely helps.
Timing
Do not migrate and redesign simultaneously. If rankings move, you will not know which change caused it. Migrate first, redesign a month later.
Avoid your seasonal peak. Whatever your busy period is, do not do this two weeks before it.
Do it in one go, not in phases. Partial migrations produce a period where two versions of the site are both live and both indexable, which is the worst state to be in.
What happens afterwards
Expect a dip. It is normal and it is not evidence you did it wrong.
Weeks one to two. Crawling of the new URLs ramps up. Rankings fluctuate. Impressions may drop noticeably. Do not touch anything.
Weeks three to six. Most of the recovery happens here if the mapping was clean. Search Console will show the old URLs dropping out of the index and the new ones entering.
Months two to three. Full recovery for a well-executed migration, sometimes with a net gain if you consolidated thin pages.
If you are still substantially down at month three, the problem is usually mapping. Recheck for URLs that got no redirect, redirect chains, or a robots or canonical directive pointing somewhere wrong.
The directory-specific traps
Slug changes on entries. The most common cause of long-tail loss. Entry slugs are usually the business name, and platform migrations love to reformat them. Preserve them if at all possible.
Facet URL patterns that do not exist on the new platform. If your old site generated /category/filter/value/ and the new one uses query parameters, you have a structural mapping problem. Solve it before migrating, not after.
Losing schema markup. Easy to overlook because nothing visibly breaks. Check with a structured data test on each page type after launch.
Pagination. Category pages with paginated results need their pagination preserved or consolidated deliberately, not accidentally.
The specific case of moving from a subdomain
If you built on a free subdomain that was noindex, this is not a migration in the SEO sense. There is nothing indexed to preserve.
Which is worth knowing in advance: on DirectoryFast free subdomains are noindex by design, so a shared domain does not become an SEO spam magnet. Attaching a custom domain is when the site starts accumulating search equity.
The practical implication is to attach the custom domain before building rather than after, so your content is indexed on its final URL from the start.
FAQ
How long do I keep redirects?
Indefinitely. There is no expiry date on an old link.
Will I lose rankings permanently?
Not with clean one-to-one mapping. A temporary dip is normal, permanent loss usually indicates a mapping or directive error.
Can I change URL structure at the same time?
You can, and it increases risk. If the current structure is bad enough to justify it, do it. Otherwise preserve it.
Should I keep the old domain?
Yes, and keep it pointed at the redirects. Letting it lapse hands your link equity to whoever buys it next.
What about the pages I decided not to carry over?
410 if they will never come back, or redirect to the nearest meaningful parent. Do not leave them 404ing silently or redirect them all to the homepage.
Describe your niche and see the schema an agent designs for it →