Menus, Post Content and Permalink Sources
Individual links stored in menus do not necessarily follow a changed post permalink. Check menu entries separately from dynamically generated post links.
Find the actual link in the menu, post, widget, or builder element. After a permalink change, manually stored paths can become obsolete, while automatically generated post links are already correct.
Where to check the setting in WordPress
Open the found link source in the post, menu or navigation block. Compare the saved destination with the current permalink. After a change in the permalink structure, manually entered URLs may need to be updated individually.
Example of this specific finding
Illustrative control case: Each category page still links to /product-old/, even though the article is permanently under /product-new/. The forwarding works, but is needed for every link call.
follow-up audit in WordPress
Reopen an affected find page after cache update. Control goal and href; a working forwarding does not replace updating a central old menu link.
Update the URL in the generating navigation or data source. Maintain the old forwarding for remaining external links.
Derogations and scope
A functioning redirect is less urgent than a defective target. Not every single forwarding justifies a major renovation.
Related: WordPress with classic or block theme. SEO plugins and page builders are different; there is no universal menu path for all installations.
Classify the general error
Definition, system-independent causes and further correction examples: Correct the linking template instead of just the redirect target