Resolving WWW and non-WWW conflicts
A domain variant should clearly be preferred.
A domain variant should clearly be preferred, and canonical signals help consolidate URL variants. It will be problematic if canonical, status code, robots and internal links suggest different goals.
Track a main version across all page types
If www and non-www addresses provide the same content, it should be clear which version is preferred. The decision depends on the existing infrastructure and use; no spelling is basically better for every website. In addition to the homepage, also check detail and form pages.
Example: Recognizing the Result
Illustrative example: The homepage unifies www and non-www, but deep articles remain accessible among both hosts with different canonicals.
Limit cause and implement correction
Match forwards, internal links, canonicals and sitemap to the selected version. Additionally, test HTTPS certificates and required external return addresses. A change to the hostname must not damage logged-in processes or file addresses unnoticed. Control the final content and not just the presence of any forwarding.
What makes you recognize a suitable correction
Check the preferred host version for homepage, articles and language paths. Forwarding, certificates, internal links and canonicals must support the same choice.
Classification and boundaries
When is this indication not a clear error?
Both host variants can operate technically different offers. Consolidate only real variants of the same content.
Further documentation
WWW and non-WWW conflict after CMS and cause
Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where WWW and non-WWW conflict has a clearly separate cause or fixed route in the respective system.
Frequent causes of this error
Related SEO Errors
Appropriate Seitenreport checks
This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.