AMP Page URL has canonical URL which is Error (5XX)
This means that the URL in question is an AMP Page URL, and contains a canonical tag which returned Error (5XX).
Why is this important?
AMP HTML documents are required to have a canonical to the non-AMP equivalent (or a self-reference, if no equivalent exists). If this canonical is pointing to a URL that is Error (5XX) URL, search engines may be unable to access the page.
The canonical tag is a mandatory element for AMP pages to be considered valid, and the canonical tag is supposed to point back at the original 'non-AMP' version of the page. If this page is inaccessible then search engines cannot crawl it, which makes the AMP pages more difficult to discover, and sends conflicting and confusing signals to search engines - increasing the chances that the AMP page will not show up in search results.
What does the Hint check?
This Hint will trigger for any AMP Page URL which has a canonical tag pointing to a URL that returned Error (5XX) when Sitebulb attempted to crawl it.
Examples that trigger this Hint
Consider the AMP Page URL: https://example.com/amp/page-a/
The Hint would trigger for this URL if it included a canonical URL,
where this canonical URL had a 500 (Internal Server Error) header response:
Similarly, URLs with other 'server error' statuses will trigger the Hint (i.e. any other 5XX response).
How do you resolve this issue?
This Hint is marked 'Critical' as it represents a fundamentally breaking issue, which may have a serious adverse impact upon organic search traffic. It is strongly recommended that Critical issues are dealt with as a matter of high priority.
Assuming the canonical is pointing at the correct URL, you would need to look into why the server responded with an error.
5XX errors indicate an issue with the server itself (rather than the website). Server errors affect access to your site, for search engines and users alike, and you really want to get to the bottom of why they occur - you may need to deal with a developer or server admin to understand what is causing the server errors.
If the canonical is pointing to the incorrect URL, you would need to fix the canonical on the AMP page so that it points back to the (correct) non-AMP version of the page, and ensure that the non-AMP version of the page has a self-referencing canonical. It should look like this:
For the URL: https://example.com/pages/page-a/
This page defines a self-reference canonical and an AMP page:
Then the AMP page has a canonical pointing back at https://example.com/pages/page-a/
