You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**What is the motivation / use case for changing the behavior or adding new
AMP version of the site can bring lot of improvements to the eCommerce SEO discover ability and performance.
However, there is no external JS allowed in AMplified pages. So probably we need to add the alternative renderer to generate just the AMP product and category pages and then distribute the traffic to existing VS pages
Regarding the docs:
In order for Google (and other technologies supporting the AMP Project) to detect the AMP version of your article, you will need to modify the original version of the article page. The original article page must include the following tag, essentially a canonical tag for AMP pages:
when there is a query parameter ?amp=1 we should use different index.html template and render the plain amp html version of the Product and Category pages
The text was updated successfully, but these errors were encountered:
pkarw
added
the
feature request
Requests for new features. Please be as specific as possible and provide proposal API if it you can
label
Sep 8, 2018
AMP version of the site can bring lot of improvements to the eCommerce SEO discover ability and performance.
However, there is no external JS allowed in AMplified pages. So probably we need to add the alternative renderer to generate just the AMP product and category pages and then distribute the traffic to existing VS pages
Regarding the docs:
In order for Google (and other technologies supporting the AMP Project) to detect the AMP version of your article, you will need to modify the original version of the article page. The original article page must include the following tag, essentially a canonical tag for AMP pages:
link rel="amphtml" href="http://www.example.com/blog-post/amp/"
This is how Wordpress official AMP plugin works
The text was updated successfully, but these errors were encountered: