Collection links and stored redirects
Compare collection links with fixed paths. After slug changes, manual buttons can still point to the old address.
Check whether a link is dynamically tied to a collection item or entered as a fixed path. After Slug changes, only the fixed links can become obsolete.
Where to check the setting in Webflow
In the link element, check the binding to Current Item or a URL field and compare the published slug. In rich text content, old manual URLs can remain. Only check forwardings after deciding which address should apply in the future.
Example of this specific finding
Illustrative control case: A guide links to /sortiment/alt/, the landing page responds with 404. The location is the guide, the error answer comes from the destination.
follow-up audit in Webflow
Publish the linking page and the destination together. Test old public addresses with the intended redirects and set new internal links directly to the final destination.
Change the link at the location to a suitable, accessible address. After that, retrieve the same found page and follow the link that was actually issued.
Derogations and scope
If there is no suitable replacement, removing or rephrasing can be better than redirecting to the start page.
Reference: Websites published on Webflow and CMS Collections. Exported HTML or an upstream own proxy layer may have other responsibilities.
Classify the general error
Definition, system-independent causes and further correction examples: Repair the linking location and the link destination separately
Configuration and test signal documentation
Webflow: Collection Links and Current Item