Separate real URL problems from cosmetic preferences
Avoid changing working addresses without a practical reason.
Use this for: New URL planning and reviews of an established site’s address conventions.
Collect representative current paths from products, services, guides and any regional sections. Mark actual defects such as collisions, broken routing or uncontrolled duplicates separately from style preferences. A working older path may be an intentional exception to your new naming rules.
Choose a rule for new URLs and say which established addresses should stay. Before proposing a rename, identify the problem it solves and the links, bookmarks, integrations and redirects it would affect. Do not treat a shorter slug as an automatic SEO improvement.
Hypothetical example: An established guide includes an old year in its path but remains useful at that address. Keep the route while adopting a year-free pattern for new evergreen guides.
- Sample the live patterns used by each important content type.
- Separate functional defects from cosmetic differences.
- Define the new-URL rule and keep justified existing exceptions.
More help and optional notes
If it fails: Keep healthy established URLs and limit changes to a justified, safely mapped scope.
Retest: Review the planned changes and confirm that each addresses a concrete need.
Not applicable: No public URLs or proposed URL conventions are in scope.
Keep in mind: Blocked: Current routes or the dependencies of a proposed change are unknown. This planning task can pass while separately identified defects still need repair.
Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

