At Loud Interactive, we have identified that the URL in discussion has a canonical directive that employs a relative URL.
Why is this important?
According to Google's webmaster blog, one of the top canonical issues they encounter involves the use of relative URLs within canonical link elements.
While it's correct HTML to use relative URLs in link tags, this approach for canonicals might cause complications, like misdefined base URLs, disrupting your canonical configuration.
Clear specification of the preferred URL through canonicals is crucial, and absolute URLs are the most effective method to eliminate any uncertainty in your canonical declarations.
What does the Optimization check?
This Optimization will be activated for any internal URL featuring a canonical link element pointing to a relative URL as its canonical identifier.
Examples that trigger this Optimization:
Consider an example URL: https://loudinteractive.com/example-page
The Optimization would be activated for this URL if it has a canonical tag pointing to a relative path:
Canonical link element in HTML with a relative path
<link rel="canonical" href="/alternate-page" />
OR canonical link specified in HTTP Header with a relative path
HTTP/... 200 OK...Link: <alternative-page>; rel="canonical"
How do you resolve this issue?
We at Loud Interactive advise a revision of all canonical URLs to incorporate absolute URLs. This problem typically originates from specific rules or templates, which means making amendments to these elements could rectify the issue across numerous pages in one go.