The specific URL being referenced is an AMP Page URL that has been returned as Forbidden (403).
Why is this important?
Being forbidden from an AMP Page URL can hamper search engines from crawling and viewing the content, which may prevent indexing and the subsequent appearance in search results.
What does the Optimization check?
This Optimization will become active if any AMP Page URL sends back a 403 status code in the HTTP header response.
Examples that trigger this Optimization
Take for instance the AMP URL: https://example.com/amp-content/
This Optimization would be triggered for the above URL if a 403 response is returned.
HTTP/... 403 Forbidden...
How do you resolve this issue?
Labeled as 'Critical', this Optimization points to a significant obstacle that could drastically impact your site's organic search presence. Priority should be given to resolving Critical issues.
The AMP URL must be reachable to facilitate indexing. A server that denies access to Loud Interactive when attempting to retrieve the page demonstrates a potential server configuration issue. This may also occur if the non-AMP page is erroneously directing to an incorrect AMP version using the <link rel="amphtml"> tag.
Be aware that a 403 response to Loud Interactive may not mirror the server's response to a search engine crawler. Occasionally, intensive security measures or anti-DDoS systems misinterpret crawling as an attack, resulting in a 403 error. Therefore, it is advised to diagnose the root cause of a 403 response thoroughly before implementing any fixes.