Google Accelerated Mobile Pages

[lesliekirk]

In case anyone is interested, here's a post where I run down the AMP for Miva Merchant module. Includes basic AMP page info and many of the features of the module: http://scotsscripts.com/blog/amp-for-miva-merchant.html

I've had the opportunity to beta test this and I will say, it's a pretty slick module. Scot has been able to take Miva Merchant and bring it to the strict requirements of AMP. Good job!

[lesliekirk]

ps... https://webmasters.googleblog.com/20...-indexing.html

[jsdva]

This is why I like bootstrap/responsive sites. Not as much need for Google to intervene in what I am doing.

[lesliekirk]

This is why I like bootstrap/responsive sites. Not as much need for Google to intervene in what I am doing.

AMP is something very different from bootstrap/responsive design. It's a whole new game for Google to play.

[jsdva]

AMP is something very different from bootstrap/responsive design. It's a whole new game for Google to play.

Should have been clearer which I was responding to. Google's recommendation: "where the primary content and markup is equivalent across mobile and desktop, you shouldn’t have to change anything." (https://webmasters.googleblog.com/20...-indexing.html), so for the time being at least mobile is covered with bootstrap/responsive sites, no need for a mobile and desktop version.

[Scot - ScotsScripts.com]

AMP (Accelerated Mobile Pages) pages are a different beast than the mobile/desktop versions of pages that bootstrap and other responsive CSS frameworks offer and are indexed and displayed uniquely from those mobile and desktop pages. Most of the articles/news/products you see in film strips at the top of search engine results pages are AMP pages, not mobile indexed pages - no data on this, just my own observations.

Since AMP pages have to follow strict validation rules regarding changes to HTML tags and how (and what) CSS and JS are loaded, and since currently it doesn't appear any of the large CSS frameworks support AMP pages yet, site owners must create them manually or use plugins (wordpress has several) or modules (see above!)

2016 is the year everyone needed to have a responsive website for SEO relevancy, 2017 is going to be the same thing for AMP. People who don't serve up AMP pages will be on the second tier of SEO as their competitors data is displayed in AMP film strips and clicked on first, before mobile or desktop indexed pages for a simple reason: AMP page pics and links are at the top off the results and displayed perfectly for mobile devices.

[lesliekirk]

In case anyone is interested, here's a post where I run down the AMP for Miva Merchant module. Includes basic AMP page info and many of the features of the module: http://scotsscripts.com/blog/amp-for-miva-merchant.html

Coming back here with a few additional questions. The AMP for Miva Merchant module does a great job with the category and product pages. Now what about the SFNT, especially if it's the landing page? I've got a store owner inquiring if it will help with the Google Page Speed mobile issues being reported. If not, remind me how the customer will go from the SFNT to one of the AMP pages?

[Scot - ScotsScripts.com]

Activate the AMP item on the SFNT page then basically create a dumbed-down version of the important store content- no tags, just content. There's really no way for the AMP module to figure out what content is important and what is not important when it comes to the SFNT and other singular pages in the store (ABUS, CTUS, etc...) We don't need sidebar stuff,or the majority of head/foot material in the AMP page, so I leave it up to the store admin to create the AMP content that includes links to the main site and perhaps important categories and/or products.

[lesliekirk]

Understood. I probably should go look at what some of the case studies to see how one would land on their sites. It sounds like it's more of a search engine landing page, than a pared down mobile site. So what ever demons are in the current site, should still be resolved.

[Scot - ScotsScripts.com]

Oh, I forgot to comment on your question about how a customer goes from the SFNT to an AMP page: they don't. Amp pages are only there for search engines and other AMP page indexers. The only time a customer goes to the AMP page is when they click on it in the search ribbon on google or whatever, then after that, all the other links on the amp page should go to the regular store pages. It's purely for search recognition.

[lesliekirk]

I'm finally starting to wrap my head around the usage of AMP Pages (thank you Scot!) and I've learned to equate them to mobile landing pages just for Google. Now with that in mind, should links within the AMP pages go to other AMP pages? In other words when building any sort of category tree in the slideout menu (using Scot's Accelerated Mobile Pages for Miva Merchant module) should the links go to the standard category pages or the AMP category pages?

[Scot - ScotsScripts.com]

Make the links on the AMP pages go to regular store pages, especially now that responsive CSS is the norm.

I think of AMP pages as SEO landing pages. They show up in the film strip (or whatever) in search engines, people click on them and read the article or get interested in the product, then any other click should go to the regular site because AMP pages are fairly sparse in nature by design- the idea is speed.

Blog posts are another thing, I think AMP blog post pages can link to other AMP blog post pages. The Blogger module's 2.0 update (soon) includes full AMP blog post support and blog post links will go to other AMP pages (but other store links will go to the normal store.)