Content revised 20 October 2026.
Old Google Webmaster Tools tutorials can describe controls that no longer match Search Console. Today, begin with the preferred page and align the website’s own URL signals.
Choose the actual destination
Identify which version should serve visitors. Check that it loads successfully, contains the intended content and can be indexed when search visibility is wanted. A preferred address that redirects elsewhere or carries an accidental noindex instruction creates a problem before any reporting tool is opened.
Distinguish a redirect from a canonical
A redirect sends a request to another address. A canonical annotation expresses a preference among duplicate or very similar pages that may remain accessible. Decide which behaviour fits the situation; the two controls are not interchangeable buttons for every problem.
Make the surrounding site consistent
- Link to the intended page from navigation and relevant content.
- Use the preferred URL in the sitemap.
- Avoid conflicting canonical tags from multiple components.
- Check both host and protocol variants.
Use Search Console to investigate
Verify the appropriate property with a method you can maintain. Inspect representative URLs and compare the reported canonical information with the public output. Verification gives access to reports; it doesn't itself merge hosts or move a page. Old Fetch as Google instructions should not be mistaken for the current URL Inspection workflow.
Allow for reassessment
After a justified change, test the final page and monitor the reports. A declared preference is not a guarantee that it will be selected immediately. Keep a log of what changed so later findings can be connected to a real deployment rather than repeated setting changes without a diagnosis.
Official guidance: Google’s URL Inspection documentation.