Sunday - last edited Sunday
One would think this happens automatically if/when the blog post is updated.
Have you modified a HubSpot blog post and seen the AMP version fail to update?
If so, have you attempted to 'force' a refresh by appending a random URL variable to the end of the blog post URL (on mobile)?
Curious, why we would think that updating an AMP-enabled HubSpot blog post wouldn't update the AMP version?
Finally, HubSpot's AMP troubleshooting KB article clearly discusses fixing HTML in the original HubSpot blog post as a remedy to fix it's AMP enabled page.
Hi @MFrankJohnson ,
Yes, we have modified the blog post by updating a URL in the content but the AMP version is not updating. I've read something that Google should re-crawled the blog post and once crawled they will cache the updated AMP version. We actually have re-index and re-crawled the page from our Google Search Console but it didn't help as well, even the updated blog post page and its AMP version was crawled, it stills shows the old AMP version of the page.
I have tried appending random variables in the end of the AMP blog post URL for both mobile and desktop and I was redirected back to the blog post URL instead (not the AMP version).
Interesting. How long ago did you ask Google to re-crawl the page(s)?
If you share a link to the blog post we can test it from a virgin browser in the morning. Just remember to let us know what we SHOULD be seeing.
Hope that helps.
Last crawl was Feb 8, 2019, 11:54:55 AM. We have updated the highlighted URL from http to https, the updates reflects on the actual blog post but not in its AMP version (please see attached image).
Ok. Looks good to us.
A few things.
-1- Your screenshot (show above) is missing the browser's address bar, so we couldn't confirm the actual URL from which that screenshot was rendered. (important -- see #2)
-2- The highlighted 'TRIBE' link is a relative reference -- i.e., href="/". This means that it will link to the URL root for the rendering domain. In our case that relative reference resolved to https://www.tribegroup.co/ on both mobile and desktop (in Chrome) and also in Edge, and Firefox (on desktop -- Windows 10)
- see image
-3- Strangely enough, even though we see the relative reference when viewing the page with the Chrome Inspector, we found no evidence of that link in the page's HTML. (weird? or we're missing something)
- see image
-4- Finally, you shared a link with "hs_amp=true". You'll want to see this thread about the 'hs_amp=true' issue.
Looks fine on mobile (Android current release) and properly shows https link (before clicking). The easiest way to confirm for yourself is to view that blog post from a mobile device that's never seen it before (important). Once there, copy the TRIBE link and paste it into an email or text message. You'll see that it's properly rendering https before you click it (your goal).
Hope that helps. Gotta run.
Hi @MFrankJohnson ,
Apologies for the late response. Here is the link of the blog post I am referring, https://www.tribegroup.co/blog/ahead-of-the-wave-how-bacardi-created-their-mojito-moment?. The previous link that I have given to you was the link for its AMP version that is why there was a hs_amp=true in the URL.
I have actually tried disabling the Google AMP from our Blog Settings and enabled it, but still the same. The AMP version that it pulls was still the old version.