mesotu

Hi @devnihil
I can confirm I am getting this same marketing message for Ryte. There is absolutely nothing wrong with my site being indexed by Google. In fact, everything is confirmed in my Google Search Console and I am appearing just fine on Google page 1, position 1 for many of my main keyword phrases.

To be honest, I really love Yoast and have been using the plugin for years, but I would strongly recommend cutting this marketing rubbish out of your plugin. It’s just an annoying warning message, but it still doesn’t change the fact that it’s false and appears mainly geared to generate sales for Ryte.

Thanks for your understanding ??

Hi @obsidianurbex and @clorith

This was VERY helpful! As it turns out, this is something of an obscure issue and there was not much online to solve this.

I had the EXACT same issue with the .htaccess code forcing the trailing slash. I had even put out my own ticket for it looking for answers, but then came across your post.

The only problem I’m having is that when I use the modified .htaccess code, the problem repeats itself. The ONLY way I’m able to publish or modify posts is by deleting the code from .htaccess.

Did you find a code that worked for the trailing slash and also allowed you to publish and update posts?

Edit:
I was able to find this code which worked just fine and allowed me to force the trailing slashes and still be able to post

# Force trailing slash
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_METHOD} GET
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteCond %{REQUEST_FILENAME} !\.(gif|jpg|png|jpeg|css|xml|txt|js|php|scss|webp|mp3|avi|wav|mp4|mov)$ [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1/ [L,R=301]

I found it here: https://docs.wp-rocket.me/article/131-redirection-to-enforce-trailing-slash-on-urls

Cheers

• This reply was modified 5 years, 10 months ago by mesotu.
• This reply was modified 5 years, 10 months ago by mesotu.

Hi all,
I have resolved the issue, but I wanted to leave an update here for anyone else having the same issue.

The problem was in my .htaccess file. I had some code to force the trailing slash at the end of my URLs.

# BEGIN redirect to trailing slash
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*[^/])$ /$1/ [L,R=301]
# END redirect to trailing slash

It was working fine on my old site but for some reason when I just overhauled the site with a new theme, it was causing problems.

Hope this helps someone out there because it’s kind of an obscure issue.

Cheers

• This reply was modified 5 years, 10 months ago by mesotu.

Thanks for your reply @sterndata Yep, always learning. I figured it was due to the nested comments maybe (?). A friend of mine has an article with 1400 comments on it but has 1756 DOM elements on the page compared to my 3800 DOM elements for 235 comments.

Then as I thought about it, what if I changed the number of comments that appear on a page in the Discussion Settings. I did that and voila, problem solved. If people want to read the comments, then they just need to click on “older” and “newer” comments in the navigation.

Screenshot here:
https://imgur.com/XgqNgxR

For anyone getting dinged for excessive DOM elements on Google Page Speed Insights or GT Metrix, this will probably help you.

Thanks @sterndata

@vlado89rj Same thing here. Google AMP auto ads stopped working all of a sudden.

Did you ever get this resolved? I noticed that two days ago all of a sudden my revenue dropped significantly and I found that despite my analytics showing 2000 daily page views, my page views from Adsense are down way below that. When I looked into it, I saw that none of my AMP pages are rendering Google ads anymore.

I’m reasonably tech savvy so have checked all the usual suspects.
1) I have auto ads enabled.
2) I have both the head and body auto amp code installed correctly
3) I have the amp-auto-ads tag in my code as well.

When I go to the amp page in desktop view, ads appear, but they are not appearing when in mobile view. Very odd that this was working fine then all of a sudden it’s not. I’d welcome any suggestions from other people who may have had the same thing happen.

• This reply was modified 6 years, 4 months ago by mesotu.

I’m having the same issue. How can I change where the plugin pulls the information from? I see this thread is a couple months old and the developer has not yet responded. Is anyone going to respond to @musicforte and this query? Cheers

Hi @ampforwp,

I’m just following up to see if you were able to investigate further Google Tag Manager issues as per my above post (https://imgur.com/RUXHjHC). I’m working at the CDN and hosting level to see if there is something happening there, but so far no luck. My CDN and hosting provider were unable to locate anything on their end and suggested to speak with the plugin developer to further troubleshoot.

I have disabled GTM in my settings and only activated the normal analytics. This fixed the problem, so I can confirm with reasonable confidence that something is still not right with the GTM configuration within the AMP plugin (or seems to be the case).

I’d welcome your input and possible solutions for this issue. Thanks in advance.

There appear to be two main issues related to GTM:
1) Failed to load https://www.googletagmanager.com/amp.json?id=GTM-KLHBNS&gtm.url=https%3A%2F%2Fwww.my-domain-name.com.au%2post-name%2Famp%2F&__amp_source_origin=https%3A%2F%2Fwww.my-domain-name.com.au: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘https://www.my-domain-name.com.au’ is therefore not allowed access. The response had HTTP status code 403. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.

2) Error loading remote config: https://www.googletagmanager.com/amp.json?id=GTM-KLHBNS&gtm.url=https%3A%2F%2Fwww.my-domain-name.com.au%2Fpost-name%2Famp%2F Error: XHR Failed fetching (https://www.googletagmanager.com/…): Failed to fetch???
at sa (log.js:505)
at qa.f.createExpectedError (log.js:274)
at custom-element.js:1380

• This reply was modified 6 years, 9 months ago by mesotu. Reason: added more details

Hi @ampforwp, just adding to my last post, check out this link here related to this issue with the GTM: https://github.com/ampproject/amphtml/issues/13005
Cheers

Hi @ampforwp and Chico (@blogginglife), I have just updated to 0.9.96 and can also confirm that the duplicate entries have cleared up. Thanks for this.

However, I am still seeing a GTM issue on my end but I do not know for sure if this is something associated with the AMP plugin or if it is something else unrelated (i.e., my CDN or something). You can see the error message here: https://imgur.com/RUXHjHC

Thanks again for the good work on the other duplicate amp entries.

I’m thinking I’d have to dig into the bowels of the plugin files to make changes to the source code. This plugin was working fine for me up until the most recent updates. I’m seeing a lot of other people having this same problem all of a sudden, so it’s not an isolated incident. I don’t have any other plugins which would be adding AMP coding to my posts. When I disable this plugin and go to an AMP page (i.e., domain.com/post-title/amp) all error messages are gone. It there was another plugin introducing these duplicate entries, then I would assume I’d still be able to find the scripts in the source code, but I don’t. I’d welcome any insights on how to fix this.

I’m having the same issue since my last plugin update. Up until now, everything was fine but the issue just appeared in my Google Search Console.

Here is the error message(s) in Firefox Developer Edition console: https://imgur.com/g2cvf4H

Here it is as a cut and paste:
amp-ad is already registered. The script tag for amp-ad is likely included twice in the page.
v0.js:80:428
ie
https://cdn.ampproject.org/v0.js:80:428
<anonymous>
viewer-impl.js:272:15
f.assert
log.js:325:6
Mh
custom-element.js:845:8
Nl
vsync-impl.js:302:26
Ml/<
log.js:622:16
Qd
document-register-element.node.js:1244:17
Ml
vsync-impl.js:301:9
f.addElement/<
vsync-impl.js:285:13
f.addDocFactory
vsync-impl.js:355:12
f.addElement
vsync-impl.js:285:13
f/<
amp-ad.js:124:2
f
https://cdn.ampproject.org/v0/amp-ad-latest.js:106:2
f.registerExtension
viewport-impl.js:1127
c/<
viewer-impl.js:360:10
[Show/hide message details.] Error: Doc factory failed: amp-ad: amp-ad is already registered. The script tag for amp-ad is likely included twice in the page.??? log.js:319:20
f.assert
log.js:319:20
Mh
custom-element.js:845:8
Nl
vsync-impl.js:302:26
Ml/<
log.js:622:16
Qd
document-register-element.node.js:1244:17
Ml
vsync-impl.js:301:9
f.addElement/<
vsync-impl.js:285:13
Kl/</<
vsync-impl.js:403:18
forEach self-hosted:268:13 Kl/<
vsync-impl.js:399:8
Error loading remote config: https://www.googletagmanager.com/amp.json?id=GTM-KLHBNS&gtm.url=https%3A%2F%2Fwww.drbillsukala.com.au%2Fexercise%2Fslendertone-review%2Famp%2F Error: “XHR Failed fetching (https://www.googletagmanager.com/&#8230;): NetworkError when attempting to fetch resource.???”
sahttps://cdn.ampproject.org/v0.js:8:169createExpectedErrorhttps://cdn.ampproject.org/v0.js:4:119fihttps://cdn.ampproject.org/v0.js:262:303 log.js:164:6
ra
log.js:164:6
f.Ga
log.js:219:6
f.error
log.js:234:18
f/g.Xb/<
amp-analytics.js:509:10

• This reply was modified 6 years, 9 months ago by mesotu. Reason: added screenshot for clarity

Hi all,
I’m so glad I found this page. It confirms that I’ve not lost my mind. I also did some troubleshooting on this and agree with the above.

As of today (5 June 2017) this issue is still ongoing. My Cart and Checkout pages are not rendering correctly and I’ve whittled it down to a conflict between WP Rocket with CDN activated and WooCommerce. If I turn off the CDN (I use Stackpath), it goes away. Turn it back on, problem comes back.

Until this is resolved, a poor man’s workaround is using the plugin called “Plugin Organizer.” I was able to deactivate the WP Rocket plugin ONLY on the affected pages and then the pages were able to render correctly. Again, not a pretty “solution” since it’s not a solution, but at least something to get your site going to make sales without looking like a back alley operator.

If anyone found a proper fix to this, I’m all ears.
Cheers

@pampfelimetten, perhaps look in your error logs and see if you can locate the issue and post here for Jordy.

If you’re running WP Rocket, you might have issues (as I did this morning).

Thanks Jordy,
I’ll try it out in a little while and see if I can get it to work. If not, then I’ll throw in a prayer on top of that just for good measure!

Hi Jordy,
I can easily do a deactivate/delete from the WP dashboard, but to do a complete fresh install, can you advise me on the best way to do this? I could delete from the cPanel side, but just curious to know if there’s anything else I’d need to know to make sure there are no residual files which might conflict with a fresh re-install. Thanks amigo. ??