How to Keep Your SEO When You Change Course Platforms

Your rankings live inside the URLs of your old course platform, not the content on them. When you migrate, you keep those rankings by mapping every ranking URL to its new address and serving 301 redirects that pass authority through. Do this before you cancel the old account, or those URLs vanish and the links pointing at them start returning 404s to Googlebot within days. Before you touch anything, export URLs from Search Console, build the mapping spreadsheet, and decide whether you are keeping the domain. During migration, launch on the new platform, set up 301s, submit the sitemap, set canonicals, and submit Change of Address if the domain changed. After launch, watch Search Console for four weeks and act on real errors, not on the temporary traffic drop that always happens.

What actually carries your rankings: URLs, not content

Google associates authority with a specific URL, not with the words on the page or the platform behind it. When creators lose rankings during a migration, it is almost never because the new content is worse. It is because oldplatform.com/courses/signature-program still holds the links, the click history and the ranking signals, and the new page at yourdomain.com/products/signature-program has none of that until you connect the two.

Google's own site move with URL changes documentation is blunt about this: without 301 redirects from the old URLs to the new ones, you are asking Google to rediscover and re-rank your pages from scratch. That process takes weeks in the best case and can silently drop pages that never regain their previous position.

The pages that matter most are usually not your lesson pages. They are your sales pages, your "what is included" pages, and any blog posts you published on the old platform's subdomain. A sales page ranking for "your-course-name review" or "your-course-name vs [competitor]" is directly tied to bottom-of-funnel searches. Losing it costs sales for months.

Before you touch anything, open Google Search Console for the old property and export the Performance report filtered by page. Sort by clicks over the last 12 months. The top 20 URLs on that list are the ones your migration has to preserve. Everything else is a lower priority.

Mapping old slugs to new ones before you cancel anything

The mapping spreadsheet is boring, and it is the single artefact that determines whether your migration keeps traffic. Skip it and you will be reconstructing it under pressure with rankings already dropping.

Crawl the old site with the free tier of Screaming Frog (500 URLs, enough for most creator businesses) or a similar tool, and export every internal URL. In a spreadsheet, create four columns: old URL, new URL, monthly clicks from Search Console, and priority. Fill the new URL for every ranking or backlinked page. Leave low-value pages blank on purpose, so you know which ones you are intentionally letting go.

If you can keep the same domain, do it. A migration that stays on yourdomain.com and only changes the path (/p/course-name to /products/course-name) is a fraction of the work of a full domain change and holds rankings far better. This is the strongest reason to migrate to a platform that runs your business under your own domain rather than a shared subdomain like you.teachable.com.

Zanfia is one option here, best for creators who want custom-domain control from day one and want to drive the URL mapping through an API rather than a UI. Every workspace gets a custom domain and the creator controls the URL structure directly, so a migration into Zanfia can be a path change on the same domain rather than a full domain move. That matters for SEO because it lets you point new paths at the same host you have been ranking under. Zanfia also exposes a public REST API and an MCP endpoint (on higher plans, see the current Zanfia pricing) that lets you bulk-generate the product slugs from your mapping spreadsheet by voice or chat with the built-in assistant, instead of clicking through the interface for every URL. Honest limitations: the assistant can create the new URL structure inside Zanfia, but it cannot write the 301 redirect rules on your old platform for you. Zanfia does not offer server-side rewrite rules for arbitrary legacy paths from outside the workspace, so redirects from a third-party old host still have to live on that host or at the edge (Cloudflare, Vercel, Netlify). API and MCP access are plan-gated and start from higher tiers, not the entry plan.

Anchor your priority column on real numbers, not intuition. A page with 40 clicks a month is not more important than one with 200 just because the topic feels central to your brand. Google decides which pages are important based on inbound signals, and Search Console shows you the same list Google is looking at.

301 redirects when the old platform will not give you any

Course platforms vary widely in what they let you do here, and the differences are worth checking before you commit to a launch date.

When the old platform will not serve real 301s, the workaround is to sit Cloudflare (or another edge proxy) in front of the old domain and serve Page Rules or Bulk Redirects from there. Cloudflare edge redirects work only when you own the domain, not when the URL sits on a shared platform subdomain. If the old URL is on a shared platform subdomain (you.teachable.com), you cannot put Cloudflare in front of it and you are dependent on whatever the platform provides.

This is the point where the platform's decisions become your SEO ceiling. A creator who never plans to move can ignore this. A creator who already moved once should not build the next home on a platform that would repeat the problem.

The other detail people miss: 301 redirects have to be preserved for at least six months, and honestly indefinitely. Google's John Mueller has said publicly on the Google Search Central blog and in the official 301 redirects documentation that redirects should be kept in place for at least a year to give Google time to consolidate signals to the new URL. Cheap-to-maintain redirects at the edge (Cloudflare, a small Vercel or Netlify rewrite config) beat any solution that ties them to a platform subscription you might later cancel.

Sitemaps, canonicals and the sales pages people already link to

Once the redirects are in place, Google needs to be told to look. Two mechanical actions and one manual one.

First, generate a fresh XML sitemap for the new site and submit it in Search Console under the new property. Most modern platforms do this automatically at /sitemap.xml. Verify the URL count matches what you expect: if you migrated 47 pages and the sitemap shows 12, something is misconfigured and search engines are only seeing a fraction of your site.

Second, set the canonical tag on every new page to point to itself. This sounds obvious, but a common failure is inheriting the canonical from a template that still points at the old URL. Run a crawl of the new site after launch and check the rel="canonical" value on the top 20 pages by traffic. If any of them still reference the old domain, fix them before you do anything else.

Third, the manual part. Your top backlinks are worth more than any technical work you can do. Pull them from Ahrefs, Moz or the free tier of Google Search Console under Links > Top linking sites. For the top 10 to 15 that point at pages you consider critical, send a short email to the site owner asking them to update the link to the new URL. Redirects will pass authority, but a direct link is always cleaner and the request is welcome from a real person more often than creators expect.

If you are moving both platform and domain in the same step, add the Change of Address tool submission in Search Console once redirects are live. The Change of Address tool does not replace 301 redirects, it tells Google to expect them and speeds up consolidation.

The four weeks after launch: what to watch in Search Console

Migration recovery is measurable, and most panic during this period comes from creators not knowing what to look at.

Week 1. Open the Coverage report on the new property. You should start seeing pages move from Discovered to Indexed. Pages stuck on "Excluded by no-index" or "Blocked by robots.txt" are configuration errors, not delays. Fix them. Also spot-check five of your 301 redirects by pasting the old URL directly into a browser and confirming it lands on the new URL with a 200 status.

Week 2. Traffic will still be down 30% to 60% in most cases, a range consistent with what Moz reports across documented site migrations where redirects were in place but signals had not yet consolidated. This is expected. What matters is that the Performance report shows the new URLs starting to accumulate impressions. Zero impressions on your top pages after two weeks means indexing failed, and you should re-check the sitemap and redirects.

Week 3. Rankings usually start to stabilise around here. Pull the same top-20-pages list you exported before migration and compare current positions to the pre-migration baseline. A drop of 2 to 5 positions is normal and recovers. A drop of 20 positions or more on multiple pages suggests a systemic problem (wrong canonicals, missing redirects, or duplicate content).

Week 4. Look at the old property in Search Console (leave the old verification in place for at least a year). Under URL Inspection, spot-check three or four old URLs and confirm Google shows them as "Redirected". If they still show as indexed on the old property four weeks after launch, Google has not yet processed the move, and you should submit a re-crawl request.

One question our support team receives regularly during migration season: "My rankings recovered on the homepage but my sales pages are still down. What did I miss?" Nine times out of ten, the answer is that the sales page slug changed and the redirect either was not created or points at the new homepage instead of the new sales page. Sales pages are almost always the highest-authority URLs in a course business. They deserve individual attention, not a wildcard rule. Migrations where entire top-linked pages return 404s can drop 40% to 70% of organic sales in the medium term, a scale of loss documented by Search Engine Land in botched migration case reviews and consistent with what we see when creators contact us after cancelling the old platform first.

If you have not yet chosen the new platform, weigh domain control heavily. A platform that runs your business under your own domain, exposes an API and can be driven by chat or voice removes the biggest single risk of the next migration: being unable to serve your own redirects. For a broader walkthrough of leaving a specific platform, our step-by-step checklist for migrating off Teachable covers the operational side. If you are also weighing whether to keep the old checkout domain, our note on custom-domain checkout and conversion explains why owning the URL matters past SEO. When you are ready to run the mapping through an API instead of a UI, start a Zanfia trial and import your URL map on a plan that includes API and MCP access.

Frequently asked questions

How long does it take to recover rankings after a course platform migration?

With clean 301 redirects and a submitted sitemap, most pages recover within four to six weeks. Traffic in the first two weeks typically drops 30% to 60% and then climbs back. Pages that never recover usually have a missing redirect or a canonical still pointing at the old URL, not a Google penalty.

What happens if I skip 301 redirects entirely?

You lose the ranking authority tied to the old URLs. Google will eventually rediscover the new pages, but they start from zero, and any backlinks pointing at the old URLs return 404s. For a business with meaningful search traffic, this often means a permanent 40% to 70% drop in organic sales rather than a temporary dip.

Can I migrate to a new platform without changing my domain?

Yes, and you should when it is possible. If you own the domain and the new platform supports custom domains, you point DNS at the new host and the URL structure is the only thing that changes. Rankings hold much better than during a full domain move because Google keeps associating authority with the same host.

Should I keep the old course platform live during the transition?

Keep it live for at least two to four weeks after the new site launches, so redirects on the old platform (if any) continue to serve while DNS and search engine caches update. Do not cancel the account until you have verified the redirects are serving from somewhere you control, such as Cloudflare or the new platform.

Do 301 redirects need to stay in place forever?

Effectively yes. Google recommends preserving them for at least a year and, in practice, indefinitely, because backlinks from other sites keep pointing at the old URLs long after you have forgotten they exist. Redirects at the edge (Cloudflare, Vercel, Netlify) are cheap to maintain and worth keeping past any subscription you might later cancel.

FAQ

How long does it take to recover rankings after a course platform migration?

With clean 301 redirects and a submitted sitemap, most pages recover within four to six weeks. Traffic in the first two weeks typically drops 30% to 60% and then climbs back. Pages that never recover usually have a missing redirect or a canonical still pointing at the old URL.

What happens if I skip 301 redirects entirely?

You lose the ranking authority tied to the old URLs. Google will eventually rediscover the new pages, but they start from zero, and any backlinks pointing at the old URLs return 404s. For a business with meaningful search traffic, this often means a permanent 40% to 70% drop in organic sales rather than a temporary dip.

Can I migrate to a new platform without changing my domain?

Yes, and you should when it is possible. If you own the domain and the new platform supports custom domains, you point DNS at the new host and the URL structure is the only thing that changes. Rankings hold much better than during a full domain move because Google keeps associating authority with the same host.

Should I keep the old course platform live during the transition?

Keep it live for at least two to four weeks after the new site launches, so redirects on the old platform continue to serve while DNS and search engine caches update. Do not cancel the account until you have verified the redirects are serving from somewhere you control.

Do 301 redirects need to stay in place forever?

Effectively yes. Google recommends preserving them for at least a year and, in practice, indefinitely, because backlinks from other sites keep pointing at the old URLs long after you have forgotten they exist. Redirects at the edge are cheap to maintain and worth keeping past any subscription you might later cancel.