lancecarr

Hi Spiros,
The developers are looking into this but it is not as easy as it looks.
The plugin would have to determine whether adding /amp to any link in the content would actually go to an amp page.

e.g. If a website owner has links on a page that are affiliate links and the page it points to doesn’t have amp then it would throw a 404 error.

Even if they only add /amp to links of the same domain this would still create problems if the website owner was using a plugin like Pretty Links to redirect to external sites.

It’s OK now I just used a CSS rule to block it… carry on.

AMP in the WordPress sidebar then choose Settings and then General.
Use the little button to turn on support for pages.

• This reply was modified 7 years, 4 months ago by lancecarr.

You seem to have proven that the loss of traffic had nothing to do with the implementation of AMP because after removing AMP and redirecting, the losses continued.

You need to look elsewhere for the reason.

This has never been right.
This is a site that has a “Blog” category and a staic page for the Homepage.

It is the reason (still) why I have never deployed AMP for WP on money sites.

https://singleserve.net.au/
<title>Single Serve Louise Harper – Cooking for One</title>
<meta name=”description” content=”The Single Serve series is a collection of books, recipes and tips for the single person wanting to just cook for one.” />

https://singleserve.net.au/amp/
<title>Single Serve – Cooking for One | Delicious meals for one in under 20 minutes.</title>
<meta name=”description” content=”While you are baking those potatoes I wrote about in my Lamb with Red Beet Sauce post, take five minutes to whip up this dessert and bake it with them.” />

When you create the the Instant Article feed with AMP for WP the latest article goes to the top of the feed, FaceBook detects it and adds it to your Instant Articles.

When you then publish another article the new one goes to the top and all the rest move down one position.

This repeats on and on. Eventually an older article will drop off the bottom RSS feed making way for new ones.

If you update an article that has already dropped off the feed then FB may not detect the changes and update.

When you update a post or page on your site you may want to also update the publishing date as well.

This forces that updated version back to the top of the feed resulting in (hopefully) an updated version in Instant Articles.

Hi jd1234,
The whole basis of the AMP Project from Google’s perspective is that in order to serve your amp page in the fastest possible way, they cache the amp page and serve it from their own data centers.

You are right that it is a bit of a pain when you update or change a page because they may take some time to update their cache.

The only way you can speed that up is to employ some old SEO types tricks to try to force Google to come and visit!

You can try this:
When you update the page make sure you update the publishing date at the same time.
Take the AMP url and share it on a few social media sites especially Google Plus.
Take the post/page RSS feed and ping it.

Well who knows!
I just put that AMP url into both the AMP project validator AND the google one and both times got a pass!

Actually it is quite common which is why I have answered you here so you don’t go off trying to fix something that is not broken.

The Google bot that crawls websites sometimes may hit a problem, it could be a server problem, a packet of info gets lost in transfer… it could be anything.

The REAL test is whether the AMP page in question can pass the Validator test.

If it does then the page is fully compliant per the requirements of the latest AMP project settings and it is Google’s problem, not yours.

This is all entirely up to Google as to what they DO with the AMP versions of pages once they are detected.

You do NOT have to enable the Mobile Redirection if you already have another mobile friendly solution in place. This is completely separate to how Google will deal with your AMP pages.

Relax!
Just grab a few of the pages that Google says have a problem and test them here:
https://validator.ampproject.org/

I just tested the URL you posted and it’s fine.

Sometimes when Googly is crawling pages (especially amp ones) some kind of glitch occurs and it reports all sorts of errors that are false positives.

If your pages are passing in the AMP Validator above then eventually Google will re-crawl and the errors will disappear.

Once you have removed the AMP pages from the site it is then entirely up to Google as to what they do about it.
You can go to Google Webmaster Tools and under the Google Index tab choose Remove URLs.
You can enter the AMP URLs there and hope that Google gets around to removing them.

There is absolutely NO reason why removing the AMP plugin from Automattic should result in you getting more “hits.”

If you are using the latest version of AMPforWP then your pages should be AMP compliant.

Once that is done from there it is entirely up to Google as to whether they index your AMP pages or serve those pages to Google users searching.

Try this free add-on they offer:
https://ampforwp.com/amp-category-base-remove-support/

@lukefive
Regarding your question about installing the Automattic AMP plugin.

Currently there are two types of AMP plugin available.
Those that require the Automattic plugin to be installed and ones that do not.

AMPforWP in the past required the Automattic plugin to be installed and like the ones similar to it added functionality to that base plugin.

Recently Automattic (finally!) issued an update to the base AMP plugin and promptly broke a whole bunch of sites on their own as well as another whole bunch of sites that used their plugin as a base.

The guys at AMPfor WP at that time decided to change the plugin so that now you do not need to install the Automattic plugin.

That plugin has been incorporated into the AMPforWP plugin so they can control the situation better and more importantly thoroughly test any updates Automattic make before releasing them into the wild.