Help center Core configuration Knowledge base Manage article redirects and old links Updated Thursday, October 29, 2026 · Marc Staine Article redirects preserve useful entry points when content moves or is retired. They help customers and search visitors reach the intended replacement without losing an established URL. Applies to: Supportbench Core. Location: Settings → Knowledge Base → Redirects. Editing requires Manage article redirects. Before you begin You need Manage article redirects; ordinary article editing is not the same permission.Publish and verify the meaningful replacement and its intended audience before changing a link. Record the old URL and the relevant customer portal.Reopen the saved result and test a representative consuming workflow. A successful save alone does not verify every reader, assignment or rendered result. Configure and verify Open Settings → Knowledge Base → Redirects. Search existing redirects first to avoid conflicting records.Choose Add redirect. Select Portal, enter Old link, and use Search articles or paste a URL to choose Destination. Review Enabled. There are no Name/Description or hierarchy fields in this editor.Choose Save redirect and reopen the row to verify the actual source, destination and enabled state.For an existing redirect, use Edit redirect and Save redirect. Automatically preserved sources keep Portal and Old link read-only while allowing the supported destination change; do not try to rewrite historical source identity.Test the old link in the intended customer context and confirm the actual destination content and access. Test an excluded or signed-out reader where the replacement is restricted.Use Remove redirect only after reviewing links that depend on it. Read the confirmation and retest the old path; removing a redirect is separate from deleting an article. Settings reference Settings and actionsSettingWhat it controlsHow to choosePortal / CommunitySelects the portal whose redirects are being managed.Verify the affected customer-facing site before editing.Search / RefreshFinds and reloads redirects; lists are paged.Search for the complete old URL or relevant article.Old linkSource URL, up to 2,048 characters. Manually entered sources can be edited; automatically preserved sources may be read-only.Use the actual historical link, including its relevant path.DestinationSearch for a replacement article or enter an allowed HTTP/HTTPS URL.Verify audience, relevance and successful access at the destination.EnabledTurns the redirect on or off.Enable after checking the source and destination.Status / Updated / Open destinationShows active, disabled or needs-attention state and offers a destination check.Investigate Needs attention before relying on the link.Save / RemoveSaves or removes the redirect.Removing a redirect can break an established visitor path. Behavior to knowThe interface describes permanent redirects. Review the destination carefully.Article retirement separately offers Redirect visitors or Retire without redirect. Without a redirect, visitors reach the retired-page/search experience.A redirect does not grant access to a restricted destination. Recommended use Choose a destination that answers the same task instead of sending every old link to the home page.Preserve useful history and keep the replacement’s audience appropriate.Check direct old links as well as navigation and search after a retirement or URL change. Worked example: preserve an old installation link after replacing the guide A controller installation guide has been replaced by a complete procedure for the same task. Record its actual old URL and portal, and publish and verify the replacement first. Do not redirect an unrelated release announcement to this procedure just because both mention controllers.Choose Add redirect, select the actual Portal and enter the complete Old link. Search for the replacement under Destination and verify that it is the intended article. Review its publication and reader access before leaving Enabled on and choosing Save redirect.Reopen the redirect and compare the saved source, portal and destination with the intended pair. If the source was automatically preserved, Portal and Old link may be read-only; review the allowed destination change rather than attempting to rewrite the old identity.Open the old URL as an intended customer and confirm that the replacement actually answers the original installation task. For a restricted destination, also test a signed-out or excluded reader: the redirect must not be treated as an access grant.If the link reaches the wrong article, correct the specific destination and retest. If it reaches an access error, resolve the intended audience or choose an appropriate replacement; do not make unrelated internal content public merely to eliminate the error. Troubleshooting ProblemWhat to checkPortal or Old link cannot be editedAn automatically preserved source intentionally locks those fields; review its destination instead.The old link still failsCheck the selected Portal, exact Old link, Enabled state and the saved destination.The redirect lands on an inaccessible articleVerify the replacement’s publication and actual reader access; a redirect does not grant authorization.Several old links appear similarCompare the complete source and portal scope before changing or removing records.I can edit articles but not redirectsCheck Manage article redirects separately. Related configuration Knowledge Base → Organize knowledge-base topics and accessKnowledge Base → Configure article templates and AI authoring guidanceKnowledge Base → Manage knowledge-base tags and audiencesKnowledge Base → Configure shared article styles and calloutsMake Supportbench knowledge useful and discoverable in search and AI answersCreate, review, schedule, and publish a knowledge article Was this article helpful? Yes No Thank you for your feedback.