Build a canonical link tag from a page URL. Use it to state the preferred address for duplicate or similar versions of a page.
How to use
Enter a full HTTP or HTTPS URL. Copy the tag into the page head. Review query parameters first; the generator removes fragments but keeps the query.
Example
For https://example.com/guide\#steps, the canonical points to https://example.com/guide without the section fragment.
FAQ
Does a canonical force Google to use that URL?
No. It is a signal. Keep internal links, redirects, and sitemap URLs consistent with your preferred address.
Related tools
A practical task
Choose the preferred page from the actual duplicates before generating a tag. A tracking query and a print view can refer to the same article, but a genuinely different language version should not be discarded merely to simplify URLs.
Another useful question
Should a canonical point to a redirected page?
Prefer the final intended address. Check that the target opens, represents the same content, and agrees with your internal links and sitemap.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Metadata and page content | A title and description should summarize the page a visitor will actually find. Search engines can choose other wording for a query. Clear, distinct summaries are more useful than repeating a keyword in every available field. |
| Canonical signals | A canonical tag indicates a preferred URL among duplicate or similar pages. It is a signal rather than a command. Internal links, redirects, sitemaps, and actual content should agree about the preferred address. |
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |
| Structured data | Structured data describes entities and facts in a machine readable format. It must match visible page content. A valid JSON document is not proof of eligibility for a search feature or a promise of richer display. |
| Source boundaries | A summary or rewrite works from the material you provide. A URL alone does not supply the full article in this interface. Include the relevant passage and keep citations attached to the claims they support. |