The page should expose a canonical tag.
Canonical tag
The canonical tag helps search engines understand which URL should be treated as the main version of a page. In a WordPress launch or handoff workflow, this check helps confirm that the canonical signal exists and points to the correct public URL.
Why it matters
A canonical tag helps consolidate signals when similar or duplicate URLs exist, making it easier for search engines to understand which version should be treated as representative. If the canonical is missing, incorrect, or inconsistent with the public page, the final setup becomes weaker and more confusing.
This matters especially on sites where the same content can appear through multiple paths, parameters, or alternate versions. The canonical does not replace redirects, meta robots, or the sitemap, but it should remain technically coherent with them and with the URL that the site actually wants to expose.
What to review
Before marking this check as correct, review the following points:
The canonical should point to the correct public URL for that page.
It should not point to an unrelated, outdated, or non-public version.
The canonical should remain coherent with the URL users and crawlers are meant to access.
It should not conflict with redirects, indexation signals, or the intended public structure of the site.
How PreFlight checks this check
PreFlight inspects the public page output and verifies whether a canonical tag is present and what URL it points to. The goal is to detect missing canonicals, incorrect targets, or signals that do not match the real public version of the page.
This check helps surface weak canonical handling before delivery, especially on WordPress sites where plugins, templates, or migration leftovers may output the wrong preferred URL. It is a practical review step in a launch-ready technical checklist.
PASS / WARN / FAIL
The page exposes a canonical tag and it points coherently to the correct public version of the URL.
A canonical exists, but something deserves review, such as an unusual target, inconsistent signals, or a setup that may not fully match the intended public version.
The canonical tag is missing, broken, or clearly points to the wrong URL in a way that weakens the final public setup.
Common mistakes
Pointing the canonical to an outdated or migrated URL.
Using a canonical that does not match the live public version of the page.
Sending mixed signals between canonical, redirects, and indexation directives.
Assuming the CMS always outputs the correct canonical automatically.
Treating the canonical tag as a substitute for noindex or redirects.
FAQ
Does a canonical tag force Google to use that URL?
No. The canonical is a strong signal, but search engines can still choose a different canonical if other signals contradict it.
Can a canonical be correct and the page still have SEO issues?
Yes. A correct canonical helps, but the page can still have problems with indexing, redirects, metadata, or duplicate signals.
Is a canonical tag the same as a redirect?
No. A redirect moves users and crawlers to another URL. A canonical tag is only a signal about which URL should be treated as the main version.
Check your WordPress site before delivery
Reduce rework, catch last-minute issues and review critical points before launch.
Run analysis