does this work for "Home" and "Pages" or only posts?

Hi
you might want to read up on the purpose of AMP pages, from the amp project website. Main purpose is for news sites, and for content which gets a lot of hits on mobile. Your “about us” page won’t get 10,000 views in a week, while a story about Trump kicking a puppy would.

Per the theme docs, right now the plugin only supports posts. It should evolve into supporting pages later, but a lot of sites use shortcodes and other custom elements on “pages” which might not pass validation, whereas most news items (“posts”) will have fairly straightforward textual and image content, and not tabs, accordions, animations, etc.

Just some feedback. You might want to read the docs and the accelerated mobile project website for a quick overview.

Main purpose is for news sites, and for content which gets a lot of hits on mobile.

Really, because I read this (emphasis mine):
“The goal is for ALL published content, from news stories to videos and from blogs to photographs and GIFs, to work using Accelerated Mobile Pages”

I do see your point, but I also fear that static page business sites which don’t have AMP pages will disappear from mobile web ranking to be replaced by AMP friendly “news” sites.

Right … well, the goal is to accelerate content which gets a large amount of visits in a shorter time frame to lessen impact on mobile users who might be on a train to read something that has smaller download packet, and which doesn’t eat through bandwidth allotments.

I was answering your question “does it work with….” and right now the answer is “no.” ??

It doesn’t mean the AMP pages will rank higher than non AMP pages; content is still kind. Speed is only a factor after content and relevance to a search.

The main benefit in SERPS is the lightning bolt to ‘advise” a potential visitor that the landing page will be “speedy” as one step up from the already used “mobile friendly” identifier.

You can certainly make *any* page on your site AMP compatible, but you just need to be aware than many non-post elements may have custom code which will not pass AMP validation due to requirements for Javascript and other things.

So, the AMP plugin will eventually support “pages,” but it’s not the initial priority in the first 5 weeks of roll-out so far.

Good to plan ahead, but right now you don’t need to FEAR that non-AMP pages will be left behind. Frankly I don’t want my price list page loaded via AMP, nor my customer support pages. For example this is why even things like the Apple “reader” option doesn’t work very well with some pages — same exact concept.

ANyway … I don’t work here … just been suffering this stuff with AMP since last Oct/Nov. ??

Thanks for taking the time to reply Neotrope, I do appreciate it.
It seems that for a small local business that relies heavily on search engine ranking, and not paid advertising, the goalposts are constantly moving, which makes being proactive a necessity. In my field, I am seeing many of the local business page listings being replaced in page 1 rank by paid listings on sites like Homeadvisor, Angie’s List, Thumbtack, Yelp, and Houzz etc…