Automatic redirect rules (prevent 404 error)
L
Lemon chiffon Blackbird
Be able to configure if when a broken link or article URL not found, to redirect to the workspace main page (or other desired destination) instead 404 page.
Additionally, it could have redirect rules like we have at smarbars configuration, to a more wider configuration.
Log In
K
Kavya
Hi Lemon chiffon Blackbird,
Thank you for sharing this request. To better understand the requirement and expected behavior, could you please clarify:
Redirect destination: Should the fallback redirect be configurable to the workspace home page, or should admins be able to specify any custom URL?
Scope: Should this apply to all broken/not-found article URLs, or only specific types of 404 scenarios?
Redirect rules: What types of redirect rules would you like to configure, similar to the Smart Bar configuration?
Exact URL → destination
URL pattern/wildcard → destination
Old article URL → new article URL
Workspace/category-specific redirects
Priority: If multiple redirect rules match a URL, how should the system determine which rule takes precedence?
External URLs: Should redirects be allowed to destinations outside the Knowledge Base?
Use case: Could you share a few examples of broken URLs and where you would want each to redirect?
Analytics: Would you also expect visibility into 404s and redirect activity to identify frequently broken URLs?
L
Lemon chiffon Blackbird
Hi Kavya,
In our case, we have legacy URLs shared across multiple external platforms that are landing into the portal, but, since the URL is old or it was updated, it's returning 404 page. In our previous platform, if the article URL was not found, it would redirect to that workspace landing page, to keep user engaged.
I believe the best approach would be with a pattern or wildcard, in our scenario it would be hard to predict the old or exact URL that where previoursly shared to redirect to a new URL.
About the priority, the custom configuration made by the user would have priority above the system default configuration. If it's made my a pattern/wildcard, I believe it would be hard to have a scenario where it matches a URL it different redirect configurations. If that happens, maybe the newest configuration would have more priority?
It could be good to allow external links, but maybe that would be a cross configuration with ticket deflector? If the article was not found maybe it could redirect to the ticket support platform. In our case is not relevant.
Analytics would be great to progressively clean and reduce broken links.