I’m testing AMP and can successfully preview an AMP page using the AMP test button, but what will the actual AMP URL be when it’s published?
You can use this post URL as an example: https://www.interestinganswers.com/animals/do-ants-have-hearts/
Firstly disable any untested plugins (WP Rocket and etc.).
AMP URL is URL + /amp in your address:
https://www.interestinganswers.com/animals/do-ants-have-hearts/amp
See example for demo-site of developers:
Hmmmm..That’s what I thought originally but it isn’t working.
I now have WP-Rocket turned off and it doesn’t work. TagDiv AMP is enabled.
See here: https://i.imgur.com/0qfpv9M.png
I appreciate the help.
Any other ideas?
Make sure you resave permalinks after enabling any AMP plugin, as that clears the rewrite transients and allows the dynamic redirect to work for that ‘endpoint’
Heh. Yeah. It’s one of the “stupid AMP tricks” (our sites were in the beta back in 2015, so have suffered through quite a bit with it… ).
Google will start checking. But good to resubmit your site maps via search console. When they are aware, it will show up and they will start poking you with error emails — some you can deal with, some will happen while you’re doing an update, and then next day “we couldn’t access two of your pages…” — which, of course, you were updating! LOL. So, then you resubmit those pages, then you get another email “we validated your fixes.” #SHEESH ! 😉
Ha. Thanks.
I wish there was a tool in Google search console or I could tell Google not to index certain pages after it pops up errors.
Since you have a good amount of experience with amp. What do you see as the pros and cons of using it?
Welllll….. the main benefit is for slow edge connection mobile users; and since something like 80% of Google traffic is mobile, their thinking is that a slim line version of a page (stupidly it’s a lot like the old print friendly pages we used to do, so in many ways it’s ripping off the old school “simple print friendly version” page of olden timez).
For many things like company info pages, not useful as in a B2B setting you lose all the value of things like complex javscript elements and stuff like bootstrap layouts.
For our news pages we have 100 score with pagespeed and 100 seo score with lighthouse, running wordpress for the non AMP pages; so those work fine. However for our news pages, it is true the dumbed down version without our logos and branding and such, load faster if you’re on a phone with sloooooow connection, to not abandon the pages altogether.
So my preference is
> desktop – best experience
> desktop > responsive – iPad portrait, best experience
> mobile > resposive – best collapsing experience with same content/page materials
> dead slow in middle of nowhere visitor > AMP
on the other hand, why the hell would somebody want to read our news in the middle of nowhere on a connection that is one bar, and the speed is 1/50th normal?
So, on one hand it’s another stupid way of Google to put their ideas first, and on the other it’s useful for very slow connections, and if your content is useful in certain locations with slow internet for desktop, or 3G connections in general — it does make the page work. Still, they could have just said “hey, if you have print friendly page, we’ll drop back to that version…” and called it a day, which we’d been doing since 1996. (double sheesh).
Sorry, you asked 😉
haha.
Thanks for the detailed response. I didn’t know it was targeted for connections that were 3G’ish, or even slower.
The only reason I’m even considering going to AMP is to hopefully get a minor SEO boot. The more I think about it, the more I don’t think it’s worth it. It could be a nightmare trying to remove AMP functionality if that ever became the reality.
Well, at least I know how to turn it on if I ever want to. 🙂
Heh. Yeah. I think it makes some kinds of content problematic, as we are selling services, so on our news pages, we also try to upsell people reading the news to use our services, which has diminished ‘experience’ on AMP.
I prefer a highly optimized responsive experience to AMP.
However, again, sometimes trying to read some websites like Autoweek with 50 stupid things loading, there is 30 sec delay sometimes to see first image, even on fast connection. So, there being able to just read article, see one photo, and couple of text only ads, would be preferable.
Nobody is obligated to use it, however, for some types of content on mobile, it can be beneficial.
I don’t think making the entire web ‘amp first’ is a good idea, contrary to what Google things. They do not own the web.
Awesome. thanks
Even the main menu is not there with AMP.
Oh. I didn’t know that. That pretty much is a showstopper.
Yep anything complex using a lot of javascript, custom fonts, columns, custom layouts, etc., are not intended for AMP. Again think “print friendly page” for slow mobile connection. So it comes down to basic UX think: if the “information” is most important, then AMP is great solution to not lose visitors due to page taking 30 sec to load.
This is why if *not* using AMP, it’s mission critical to “think” your post pages out as much as possible for speed with both Lighthouse check and Pagespeed check.
Thanks for the info. Really helpful.
