A canonical element identifies a preferred version of a page. It does not normally move the visitor to that address. If a parameter URL remains open after you load it, that is compatible with having a canonical pointing to another version.
The useful check is whether the preferred URL accurately represents the content and agrees with the website’s other signals. A canonical printed everywhere is not automatically a correct canonical.
Read the element and its destination
A typical HTML implementation appears in the document head:
<link rel="canonical" href="https://example.com/products/running-shoe/">
Inspect the head in page source, then compare the current DOM if scripts can change it. Record the exact destination, including protocol, hostname, path, and any parameters. Absolute URLs make the intended destination explicit. Relative references can resolve successfully, but their meaning depends on the document’s base URL.
A self-canonical points to the page’s own preferred address. An alternative URL may point to a matching canonical version, such as a tracking-parameter variation of the same product.
Use equivalent content as the starting point
Suppose /products/running-shoe/?campaign=email shows the same product as /products/running-shoe/. A canonical to the clean address can express the preferred version.
Now suppose a filter changes the page to a meaningful collection with different content. Pointing every filtered page to an unfiltered category requires a content and indexing decision. The presence of a parameter alone does not establish that two pages are duplicates.
The same applies to pagination. Distinct pages in a sequence should not all point to page one simply because they share a category template. Confirm the intended content relationship before applying a site-wide rule.
Compare the declared and selected canonical
In Search Console URL Inspection, the user-declared canonical and Google-selected canonical may differ. Inspect the stored result and last crawl date before comparing it with today’s HTML. Google may have assessed an older version.
Look for competing signals: internal links to another URL, a sitemap listing a different version, redirects, duplicate content, or an unintended noindex. These observations help explain the mismatch; none proves the cause by itself.
Google treats canonical declarations as signals. Its canonical documentation describes supported methods and common implementation mistakes. The preferred address should be consistent across the relevant mechanisms.
Decide whether the visitor should move
If a page has permanently moved and visitors should reach its replacement, investigate a redirect. If several equivalent URLs need to remain accessible, a canonical can communicate the preferred indexing version without navigation.
Avoid using both mechanisms with conflicting destinations. A source declaring A while redirecting to B gives the investigation another inconsistency to resolve.
Validate a template change
Check representative pages before and after changing the canonical rule. Include a normal page, a parameter variation, pagination, and relevant language versions. Confirm that each output points to its intended URL and that the destination is eligible for indexing.
For generated collections, my website architecture and programmatic SEO service covers the shared rules behind these outputs. A crawl and indexing analysis can then compare the declarations with crawl evidence and Search Console exclusions.