# Help Center Migration Checker

Canonical: https://orka.chat/help-center-migration-checker
Updated: 2026-11-09
Publisher: Orka

Start with a help center home or collection page. See which internal URLs a visitor can discover there, then export them as a starting list for your migration.

## Inputs

- Help center or collection URL — Use a public HTTPS address.

## How it works

The checker lists distinct same-origin links in the initial HTML. Common article and collection paths receive a candidate label. Other paths stay in the export for review. Alternate-language declarations are read from the source page.

## Worked example

If a collection links to /articles/reset-password twice, the CSV contains one article candidate. A link to /collections/account appears separately so your team can preserve the collection hierarchy.

## Frequently asked questions

### Does the count include every article in my help center?

It covers links published on the page you enter. Scan additional collections or compare your provider’s article export for a full inventory.

### How can I use the inventory during a migration?

Review the candidates, flag outdated pages and record each new destination. Use the redirect map generator once your new article URLs are available.

### Will submitting a URL change my help center?

The checker reads public content and returns a CSV. Migration and publishing are separate actions in your chosen help desk.

## Related tools

- [Help Center Redirect Map Generator](https://orka.chat/help-center-redirect-map-generator)
- [Help Center Broken Link Checker](https://orka.chat/help-center-broken-link-checker)