Canonical URL review protects the relationship between a page and its preferred address. It is especially useful when content is copied, refreshed, filtered, or moved between routes.
Identify the preferred page
For each article, record the intended public slug and the content family. Blog and Research pages need separate ownership. Search both collections before creating or changing a canonical reference.
Check consistency
Compare the page route, canonical value, internal links, sitemap entry, and metadata. They should point to the same preferred page. Look for host, protocol, trailing-slash, and capitalization differences.
Handle changes carefully
If a slug changes, record the old and new route and confirm the redirect plan separately. Do not remove content to make a duplicate disappear. The SEO redirect review guide covers the decision record.
Validate the build
Run the repository's content and build checks, then inspect generated route data where available. Canonical review is complete when the preferred page is unique, consistent, and supported by an owner. +## Resolve conflicts by intent
Different routes may deserve to exist when they answer different questions. If they answer the same question, choose the clearer page and document why. Do not use canonical tags to hide duplication without checking links and content family.
Verify the whole path
Inspect metadata, generated routes, sitemap inclusion, and representative links. Check host, protocol, casing, and slash behavior. Record expected and observed values, evidence, owner, and follow-up.
