Support » Plugin: AMP » Not a valid AMP page – Indexing error

  • Resolved ahmad7110

    (@ahmad7110)


    Hello;

    Suddenly all posts had been changed from valid to Not valid AMP page, i don’t why and there is nothing wrong in plugin supperssion

    Google AMP validation is saying only Not a valid AMP page – Indexing error
    Invalid AMP pages will not have AMP-specific features in Google Search results

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • @ahmad7110 thanks for reaching out!

    When I check your AMP page in the AMP Test tool, I’m seeing the following error:

    Referenced AMP URL is not an AMP

    This can indicate that the required link to your AMP page from the canonical (non-AMP) page can be altered it some way preventing its detection.

    When I check the original non-AMP page here, interestingly it being served as an AMP page even though your theme (Newspaper) supports Transitional mode.

    Have you made any changes to the site recently?

    It may be the theme or plugin causing the issue. If you able to safely switch to a default theme, disable other plugins temporarily, and test the AMP URL in the test tool that might help narrow down the source.

    Thread Starter ahmad7110

    (@ahmad7110)

    Hello;

    There is not changed at all, only one this which is an update in All in One SEO
    Disable the theme is a really difficult option now

    is there any way to do debug
    Regards

    @ahmad7110 thanks for your reply.

    Could you try to temporarily disable All in One SEO and test your AMP URL?

    If the issue still occurs, please send your Site Health information through this form.

    Thread Starter ahmad7110

    (@ahmad7110)

    Hello Renee;

    I found the root cause, It is CloudFront, I changed the routing to ELB and it works fine, but this can’t be the final solutions since I will lose the speed of indexes and CLS

    Can you please explain to me a bit more what is the error and what shall be done so I can change CloudFront config.

    I think this will help a lot of people if we can fix it togeather

    @ahmad7110 thanks for the insight! I’m not wholly familiar with the ELB technology, so this may require some further research on our side. Additionally, there may be some specific configuration aspects to your site that may be contributing to the issue.

    The key is ensuring your canonical, original page is accessible to search engines. In the source code of the page, there should be a clear link to the AMP version of the site.

    So on your canonical page: https://7yatak.net/%D8%A7%D9%81%D9%84%D8%A7%D9%85-%D9%83%D9%8A%D9%81%D9%8A%D9%86-%D9%87%D8%A7%D8%B1%D8%AA-%D9%88-%D8%AF%D9%88%D9%8A%D9%86-%D8%AC%D9%88%D9%86%D8%B3%D9%88%D9%86-%D8%A8%D8%A8%D8%B7%D9%88%D9%84%D8%A9-%D9%85/

    The source code should have this reference to the AMP page as it currently does now:

    <link rel="amphtml" href="https://7yatak.net/%D8%A7%D9%81%D9%84%D8%A7%D9%85-%D9%83%D9%8A%D9%81%D9%8A%D9%86-%D9%87%D8%A7%D8%B1%D8%AA-%D9%88-%D8%AF%D9%88%D9%8A%D9%86-%D8%AC%D9%88%D9%86%D8%B3%D9%88%D9%86-%D8%A8%D8%A8%D8%B7%D9%88%D9%84%D8%A9-%D9%85/?amp">

    Previously, the canonical/ original page had AMP HTML in the source code which is incorrect.

    Since you are using a paired serving method through Transitional mode correct non-AMP and AMP versions need to be accessible.

    Based on your configuration at Cloudfront, are there options that alters the source code or could potentially serve a cached AMP version on the original page (perhaps Cloudfront support can also provide insight)?

    Plugin Support Bethany Chobanian Lang

    (@shetheliving)

    As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.