Redirects and missing pages
Addresses change: a slug is renamed, a post is deleted, a blog moves from another platform. CMSKite keeps old links working in two ways, and shows you the ones that still break.
Renamed posts: automatic
Change the slug of a live post and the old one keeps answering. The hosted blog sends a permanent redirect. Your own site gets the post with slugRedirectedFrom set, and should redirect to the new slug (Add a blog to a Next.js site shows how).
Your own rules
Open Website settings → Redirects and Add redirect:
| Field | Example |
|---|---|
| From | /old-post |
| To | /new-post, or a full https:// address |
| Type | Permanent (most moves) or Temporary |
A rule is used only when the address does not exist, so it never hides a live post. Each rule shows how many times it was used and when, so you can delete the ones nobody needs.
Missing pages
Under the rules, Missing pages lists addresses that answered 404 in the last 30 days, on your hosted blog and on SDK sites that report them. Each has Add redirect next to it. Check it after a move: it is the list of links you forgot.
Moving from another blog
Keep your old slugs when you recreate the posts, and most links need no rule. For the rest, add one rule per old address. The full steps are in the migration guides.