2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Choose one URL group
Identify pages that actually share duplicate or near-duplicate content. Avoid grouping different useful pages solely because their layouts match.
Inspect current signals
Record response status, declared canonical, redirects, internal links, and sitemap references for each member of the group.
Compare search evidence
Where access is available, inspect the search engine's reported canonical and indexing context. Treat the report's scope and timing carefully.
Resolve the intended preference
Align supported signals around the chosen public URL and test the output. Keep distinct content independently useful and addressable.
Worked scenario
See the plan in practice.
A product's canonical names one URL while the sitemap and navigation favor another. Document that conflict before editing an unrelated page template.
Review your result
Your acceptance checklist
Group valid- Signals recorded
- Preference consistent
Use these checks to identify gaps in your canonical-signal comparison. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
- Canonical URLThe preferred representative URL selected or indicated for a set of duplicate or closely similar pages.
- Duplicate contentContent that is identical or substantially similar at more than one URL.
- XML sitemapA machine-readable file listing URLs a site wants search engines to discover, optionally with supported metadata.
Primary references
For the underlying concepts and current platform details:
