Thanks for reaching out. From inspecting your site at present I noticed the AMP Cache version of your content does match the AMP origin version of your content, with the first post also appearing up to date (“Il Napoli riparte sotto il segno di Mertens verso la Champions” – 11:45).
You’ll find the different variations here. If you’re not finding the most up to date content on your site you can use the Search Console URL Inspection Tool to request a refresh of your site. Once your site is reindexed the AMP cache version of your content will also be updated. If you’re finding any peculiar behavior with AMP cache you can also use this guide to update the Google AMP cache.
I noticed also you’re using Newspaper, with formats your AMP URLs in transitional mode on desktop the same as mobile. For a like for like experience in transitional mode to your non AMP you can follow up with TagDiv and enquire about full desktop AMP support.
Let me know if you have any further queries on this.
Ok instead load google url google.com/amp/s/www.calcioinpillole.com can i load my website url?
If you’re looking to load the AMP Cache version of your site you can use this guide:
https://amp.dev/documentation/guides-and-tutorials/learn/amp-caches-and-cors/amp-cache-urls/
This won’t force an AMP Cache update, it will allow you to just view the AMP Cache version.
Let me know if you have any further questions on this.
Ok thanks i just checked and i can confirm that homepage cache is not updated once i publish a new post. Is it possible to add a trigger in order to clear homepage cache once a new post is published?
Good question. Unfortunately this is something not possible within the plugin at present, you’ll find previous discussions on this below:
https://github.com/ampproject/amp-wp/issues/598
Note also that once the option to opt out of AMP cache is available via the AMP project we’ll be implementing this within the plugin:
https://github.com/ampproject/amphtml/issues/24326
Sorry to hop-in, I’m in the same dev team.
Is there any method ready-to-call (or close to) to provide a generic signed request to the AMP service?
From the github issue it looks like the problem to deal with it the update logic, however the functions to upload a new AMP page to the cache service should be already included and perfectly working.
Therefore my question stands: can I call a specific function to craft the call to be sent to AMP service?
Specifically I would like to avoid to have to deal with the crypto side of the request.
Thanks in advance!
Have a nice day
@jiraky90 Currently the AMP plugin does not provide any ready to call method to update AMP Cache.
As you’ll find when visiting the documentation it’s a technical process that requires creating RSA keys. We are working towards providing more feasible option which may be useful to all the users.
Specifically I would like to avoid to have to deal with the crypto side of the request.
Currently there is no other way to update AMP Cache without generating RSA keys. If you’d like to experiment with some user suggested solutions you’ll find some available when performing a GitHub search, although this is not something we support. Sorry we can’t be of more assistance.
Thank you @jamesosborne .
I’ll have a look into the provided resources.
You may close the ticket.
Have a nice day.
You also @jiraky90, have a nice day.
@fabioweb Let me know if you have any further queries on this, I’ll close this support topic in the meantime.
The best way to address this will be to turn off AMP Cache for the homepage. This isn’t yet an available feature, but the underlying capability is being tracked here: https://github.com/ampproject/amphtml/issues/29296
Once that lands in AMP core, then we’ll be implementing via: https://github.com/ampproject/amp-wp/issues/5378
For highly-dynamic pages, like the homepage, archives, (or any non-singular post/page), it probably makes sense to default to opting out of the AMP Cache.
