What is a canonical URL in everyday terms?

A URL is a page's web address. A canonical URL is the address Google selects to represent a group of duplicate pages. Canonicalization means making that selection. Your declared preference and Google's chosen page are not necessarily identical. Google explains the distinction.

Think about one product with several entrances

Hypothetical example: a homeware shop sells a ceramic mug. Its marketing team uses a campaign address, while the navigation uses the regular product address. Open both and compare the product, description, and purchase options before treating them as duplicates.

Write the preferred address in a shared worksheet. Beside it, list the alternatives and explain why you grouped them together. Ask someone who knows the products to review the list before passing it to your developer.

This gives the discussion a clear starting point. Instead of asking for “better SEO,” meaning better visibility in search, you can request a specific change to a specific group of pages.

Why does Google consolidate duplicate pages?

Google groups pages with the same or very similar main content so it can show a representative version. Some duplication is normal and does not itself violate Google's spam policies. Multiple addresses can nevertheless confuse visitors and complicate performance tracking. Google's explanation of duplication.

Specifying a preferred address can also help consolidate signals, such as links pointing to different versions, around one page. Google lists clearer reporting and less crawling of duplicate content among the reasons to declare a preference. Crawling means fetching pages to examine them. Reasons to specify a canonical.

Describe the problem before buying a fix

Ask your team to show the actual addresses. “Duplicate content” is too broad a diagnosis on its own. For each example, request a short explanation of what is duplicated and what should become the preferred version.

• Collect an ordinary product address and any campaign variations.
• Compare category pages reached through sorting controls.
• Separate genuinely different products from alternative addresses.
• Record anything uncertain for a content review.

Do not set “every address must appear in search” as your success measure for duplicate pages. Instead, agree which page you want customers to reach and document why that is the right choice.

Should you use a canonical tag or a redirect?

Use the business purpose of the extra page to guide the conversation. Google presents canonical tags for duplicate or very similar pages and permanent redirects for retiring duplicate pages. A redirect sends visitors to another address. Google's comparison of methods.

A filter deserves an actual content check

Hypothetical example: a sports shop has “all running shoes” and “waterproof trail shoes.” Do not group them merely because they share a layout. Compare the selection and customer purpose, then write down your reasoning.

For a broader move involving changed addresses, use the domain migration guide to prepare a separate project brief. Avoid mixing a small duplicate-page cleanup with an unplanned site move.

How do you use the rel=canonical link element?

Place the element in the page's HTML <head>, the part containing page-level information. Google recommends a complete address and a self-referencing canonical on the preferred page itself. “Self-referencing” simply means pointing back to that page's own address. Google's implementation instructions.

A readable tag template

<link rel="canonical" href="[complete preferred page address]">

This is a template, not a finished tag. Replace the bracketed text with the full address, including the protocol and domain. Ask the person implementing it to show the finished page output alongside the agreed address.

What should a WordPress owner do?

For a content management system such as WordPress, the setting may be handled through the platform rather than direct HTML editing. Google advises checking instructions for the system you use. Google's CMS advice.

Before searching for a WordPress canonical tag plugin, ask what already manages this setting. Request a demonstration on one page. Make “show the resulting canonical address” part of the handover instead of accepting only a screenshot of a settings screen.

Next, review the sitemap, a list of page addresses provided to search engines. It is a weaker canonical signal than a tag, and Google advises keeping the choices consistent. Sitemap and canonical guidance. Use the XML sitemap guide for that part of your checklist.

How can you check whether the setup makes sense?

Compare the implemented address with your written decision. Then check whether the website's other signals support that same choice. Google advises consistent canonical declarations and internal links pointing to the preferred address. Canonical best practices.

Review a complete page group

• Open the preferred page and each agreed duplicate.
• Ask your developer to report the canonical address on each.
• Compare those values with the approved worksheet.
• Check the sitemap entry and relevant navigation links.
• Record remaining disagreements before expanding the change.

Use the internal linking guide to prepare the navigation review. Choose a few relevant entry points, such as the category listing and a related article, and ask which product address each uses.

Keep crawling controls as a separate review item. Google specifically advises against using robots.txt for canonicalization. Google's warning about robots.txt. If that file appears in the proposed fix, consult the robots.txt setup guide and ask the team to explain its purpose.

For a site with different mobile and desktop arrangements, include both in the review brief. Google lists device variants among possible duplication cases. Examples of duplicate variants. Continue with the mobile SEO checklist if that applies to your website.

What should you ask your website team to deliver this week?

Ask for a reviewed example before approving a sitewide rule. The following is a suggested working method, not a promise of search improvements. Choose a page group you understand well enough to assess yourself.

A brief you can adapt

Review these product addresses and identify which show equivalent content. Recommend a preferred address with a short reason. Apply the agreed rule, show the resulting canonical declarations, and check the sitemap and internal links for consistency.

Request a worksheet with five columns: inspected address, content relationship, preferred address, observed declaration, and next action. Include the person responsible for unresolved items in the final column.

Decide what counts as completion before work starts. A useful acceptance condition is that every inspected page has a documented decision and any mismatch has an owner. Keep implementation checks separate from later observations about Google's choice.

Finish by reviewing one borderline case together. If your team cannot explain why two pages belong in the same group, pause that grouping and compare their content again.