Google selected the wrong canonical on WordPress

When Google selects a different canonical than the one WordPress declares, the first check is whether the page sends mixed preference signals through templates, internal links, sitemap entries, parameters, archives, or duplicate content.

Send this symptom All problem paths

TRIGGERS / WHEN

When this usually appears

after SEO plugin canonical changes
after migration or URL cleanup
after creating similar landing pages
after enabling filters or parameters
after taxonomy or pagination changes

ROOT PATHS / WHY

Where the failure often sits

duplicate templates
parameter URLs compete with clean URLs
pagination or archive conflicts
SEO plugin canonical output is wrong
internal links point elsewhere
sitemap and canonical disagree
another URL looks stronger

FIRST PASS

Checks closest to the symptom

declared canonical in rendered HTML

Google-selected canonical in GSC

sitemap alignment

internal links to both versions

redirect and parameter behavior

template similarity

SPRINT OUTPUT

Fix or implementation-ready path

map declared and selected canonical paths
fix safe canonical, sitemap, redirect, or link conflicts
identify duplicate templates for consolidation
hand off the preferred URL clearly

VERIFICATION

The change needs a second measurement

GSC URL Inspection
rendered canonical check
sitemap review
internal-link crawl
duplicate URL sample

USEFUL INPUT

What helps reproduce it

affected URL examples
GSC canonical evidence
sitemap URL
what changed recently
WordPress and GSC access

SCOPE BOUNDARY

What this path does not promise

full content consolidation
backlinks
ranking guarantee
sitewide redesign
unrelated SEO setup

RELATED FAILURE PATHS

Continue only when the symptom crosses a layer

START / Indexing

Have the URL and one exact symptom?

The remaining technical context can stay collapsed unless it helps reproduce the failure.

Send this symptom