Hi
AMP pages were visible on my iPhone 7.
There are multiple ways to enable AMP on a site:
1 - the "normal" way is: each page has a regular HTML version and an AMP version. Inside the regular HTML version is a link (rel="amphtml") that tells search engines or other possible services using AMP what's the URL of the AMP version. So you get 2 URLs for a page:
/my-article.html: regular HTML, has a rel=amphtml (hidden) link pointing to /my-article.amp.html
/my-article.amp.html: AMP version of the page, has a rel=canonical link pointing back at /my-article.html (to avoid duplicate content).
Here you get either the regular or the AMP version simply depending on which URL you try to load in your browser. Wether you're on a mobile device or desktop is not relevant: your WP site renders one version or the other depending on which URL you request in your browser address bar.
99.9% of websites on the planet are configured that way and this is 100% what we recommend (back to why later). This is the operation mode you get with weeblrAMP when you select "Normal"
chrome should deliver AMP pages to the cell phone since it is a mobile device
It's technically possible to do that but it definitely not recommended and very, very hard to do properly. I am not aware of any site that does this, just because it's so hard to get full content and interactivity of pages on AMP versions.
I think the confusion here comes from the fact that [b]Google and Bing (and others) shows you the AMP version of the page when you click on a link in their search results. This is exactly how AMP is designed to work:
- If you load a page from your site (ie type the URL in your browser) you get whichever version you requested, regardless of the device you use
- if you click on a link in a search results page (or linkedin link, or twitter link,...) then the search engines will show you the regular page if you are on a desktop and the AMP version when you are on a mobile.[/b]
2 - "Standalone" mode is: your entire site is AMP. There's not regular HTML version. EAch page gets a single URL, /my-article.html. This page does have a rel=amphtml but it points to itself, telling search engines that /my-article.html is an AMP version but also that it is the only version of that page the exists.
Once again, whether you load the URL /my-article.html in your browser from a mobile device or desktop does not matter, you'll always get the AMP version.
This mode is rarely used (although promoted by Google) again because it's hard to get feature parity between regular HTML and AMP. Sites with simpler design/features or good development team can pull this.
3 - When using "normal mode", it is possible to force the display of the AMP version of a page for mobile users
even if they requested the /my-article.html URL, that is the regular HTML URL.
This seems to be what you are asking for. We decided to not implement this because we've done it on our AMP plugin for other CMS and it's bad. The main reason is again that it's hard to get the same page content and features on AMP than on regular HTML pages.
Now that Google is using
mobile-first indexing, if you force the AMP version of your page to all mobile users, then Google will index your site content based on the AMP version only. You better be sure to have all the content and all the features your site require on the AMP version or else you'll loose big in terms of SEO instead of winning.
Hope this clarify the AMP operation. The key point is that " I launch my website via Chrome on my iPhone 7, chrome should deliver AMP pages to the cell phone since it is a mobile device.", although technically possible is not something you want to do. Nobody is doing it and for good reasons.
My main reason for consider switching to Weeblr is your support for Elementor.
Elementor support means that we can read Elementor content and we will render it on the page. I'm under the impression that you may think "Elementor support" means that an Elementor page will render with the same aspect and the same features (ie tabs, carousels, etc) that you have on the regular HTML page.
This is not so. We will render the
content. But all of Elementor visual design and features will not pass through to the AMP version and it will require some custom CSS to achieve a similar look. It is important to understand that none of the style and features (javascript based) do not transfer to AMP pages (this is forbidden by the AMP specification) and most AMP implementations require custom CSS and custom template overrides to achieve a similar look and feel as your regular HTML page. This is the exact reason why nobody forces the AMP version onto all mobile users.
The same apply to forms: we have good support for CF7/WPForm. Any form that does not require javascript will be converted automatically and display fairly well. Complex forms with multi-page for instance will not convert automatically. They won't convert at all actually and will need to be coded again manually following the AMP specification.
Hope this gives you a better picture, implementing AMP on your site requires some work, it's only going to be a install-plugin-and-forget about it for fairly simple sites. Others will definitely require some develoment capability, CSS-wise and possibly more. Using Elementor, CF7, WPForms totally smells like dev work will be needed.
I am confused by the suggestion that Google techs may not understand the difference between regular pages and AMP pages and may be confusing the two.
Google is not confused at all. They strictly follow the rules exposed above, that is the rel=amphtml tag being present on a page to indicate whether a page is amp or not. So what the error above suggest is that a regular HTML page contains a rel=amphtml pointing at itself.
So Google has been told to consider a given page as AMP while the page is actually a regular HTML page, hence the errors.
One thing that pops to my mind is that maybe you have other AMP related plugins. YOu should not. You should disable absolutely any other AMP-related plugin that exists on your site when enabling weeblrAMP. What
could be happening is that other plugin incorrectly insert the rel=amphtml tag in the wrong place.
Best regards
