Preserving SEO When Migrating Your Knowledge Base

Moving your help center to cStar does not mean losing your search rankings. Here is what matters and how to do it right.

Why SEO Matters During Migration

Your existing help articles have Google rankings, backlinks from other sites, and domain authority built up over months or years. When you move to a new platform, URLs change. Without proper handling, Google sees 404 errors everywhere, backlinks break, and organic traffic drops.

With proper 301 redirects, Google follows the redirect and transfers ranking signals to the new URL. Traffic dips briefly, then recovers.

The Strategy

1. Keep the Same Subdomain

This is the single most impactful decision. If your help center lives at docs.example.com (pointed at Zendesk), build your new cStar-powered site on the same subdomain.

All your backlinks and domain authority live on that subdomain. Keeping it means you only need to handle URL path changes, not a full domain move.

2. Build with the Headless SDK

cStar Library API and the LibraryClient SDK let you build a custom help center at any URL structure. The API serves article content; you control the routing.

You are not locked into cStar URL patterns. Serve articles at /docs/, /help/, /articles/, or even /hc/en-us/articles/ if you want to match your old structure exactly.

3. Preserve Article Slugs During Import

When importing articles with the Universal Importer, map the source slug field to the cStar slug field. This keeps your URL-friendly identifiers consistent.

For Zendesk articles, the slug is the hyphenated title after the article ID: in /hc/en-us/articles/7253090768539-Installing-Something, the useful part is installing-something.

4. Set Up 301 Redirects

This is the critical step. Every old URL needs a 301 redirect to its new URL.

Old: /hc/en-us/articles/7253090768539-Installing-Something New: /articles/installing-something

How you implement redirects depends on your hosting:

Vercel — Add redirects to vercel.json (up to 1,024 rules). For more, use Vercel middleware.

Cloudflare — Bulk redirects support up to 20,000 URL pairs on free plans. Upload a CSV of old-to-new URL pairs.

SvelteKit — Add redirect logic in hooks.server.js that parses the old URL pattern and maps to the new path.

Next.js / React — Use Next.js middleware (middleware.js) to intercept old URL patterns and redirect. For smaller sets, use the redirects array in next.config.js. Both support 301 permanent redirects.

5. Preserve Meta Descriptions

cStar articles support meta_description and excerpt fields. During import, map your existing meta descriptions to preserve your search result snippets.

6. Submit Your Sitemap

cStar auto-generates a sitemap at /sitemap.xml that includes all published articles. After your new site is live:

  1. Go to Google Search Console
  2. Add or verify your property
  3. Submit the new sitemap URL
  4. Monitor Index Coverage for crawl errors

7. Keep Redirects Permanent

There is no good reason to remove 301 redirects. Keep them indefinitely. External sites will link to your old URLs forever.

The Migration Checklist

  1. Export all articles from your current platform (including slugs, meta descriptions, published dates)
  2. Import into cStar with the Universal Importer (preserve slugs and metadata)
  3. Build your new help center using the LibraryClient SDK on the same subdomain
  4. Generate your redirect map (old URL to new URL for every article)
  5. Deploy redirects via Vercel, Cloudflare, or your hosting platform
  6. Switch DNS from old platform to new site
  7. Submit new sitemap to Google Search Console
  8. Monitor Search Console for crawl errors

What to Expect After Migration

With proper 301 redirects in place, rankings may fluctuate slightly for a few weeks, then recover to previous levels within a couple of months. Without redirects, expect 50-80% organic traffic loss that can take many months to recover from, and some pages may never recover.

What cStar Provides

  • Custom slugs on every article (preserve your existing URL identifiers)
  • Meta description field (preserve search result snippets)
  • Schema.org JSON-LD structured data (automatic on all article pages)
  • Open Graph and Twitter card tags (automatic)
  • Canonical URLs on every article (prevents duplicate content)
  • Dynamic sitemap at /sitemap.xml with all published articles
  • Headless SDK for building custom help centers at any URL structure
  • CORS-enabled API for cross-origin access from any domain
  • Timestamp preservation during import (article age signals carry over)