The core idea
A URL tells a reader where to open a resource. A persistent record identifier helps a collection recognize the same item over time. Keep those roles separate, especially when paths, titles, or hostnames may change. Preserve source references instead of normalizing away distinctions whose meaning you have not checked.
A workable starting pattern
Define one preferred destination per published item and align navigation, feeds, and metadata with it. Document alias handling and test moved paths. Do not assume every query parameter is disposable or every similar-looking URL is a duplicate. Review normalization rules against representative examples.
A tracking parameter may be irrelevant to the editorial item, while another parameter selects a genuinely different resource. The collection needs an explicit rule and evidence, not a blanket instruction to remove every query string.
What this page does—and does not—offer
TagsFeed does not shorten links, crawl submitted URLs, or provide a live deduplication API. This guide concerns record and link design.
