Link fields, menu generation and routing
Check if the reference is saved as a page reference, record link, or fixed URL. A fixed address does not automatically follow a slug change.
Check whether the link is stored as a TYPO3 page reference, as a record link or as a fixed path. After slug or routing changes, fixed URLs can become obsolete, while dynamically generated references already point to the new destination.
Where to check the setting in TYPO3
In the link browser, check the stored destination and, for dataset links, the link handler and the route enhancer. Internally, use stable page or record references if possible. A manually entered old talking URL is not automatically updated by a new routing configuration.
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 TYPO3
Track the visible link separately in navigation, flow text and extension list. Not only control the target data set in the backend, but the actually output href value.
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: TYPO3 13.4 with EXT:seo. For other major versions and own extensions, responsibilities may differ; check the actually installed output.
Classify the general error
Definition, system-independent causes and further correction examples: Repair the linking location and the link destination separately