Major Google Search Console Errors (Hundreds)

Support
#1

So I’ve been dealing with this problem for a long time and I don’t know why I haven’t really tried addressing it until now.

Honestly I don’t have a clue to fix any of it and it just seemed crippling.

But I’ve continued to get new Google Search Console error emails and the Yoast SEO plugin was always giving me this error:

It says to go here and run my url:

https://search.google.com/test/mobile-friendly?utm_source=mft&utm_medium=redirect&utm_campaign=mft-redirect

Here’s a few screenshots, seems like its a combination of a few things, Java/jquery being a big part of it and I really have no idea about any of that really.

I can follow directions quite well though, so if it’s possible for me to fix this with someones help, well then that would be awesome.

Here are a few more screenshots of the results:

Does anyone have an idea what caused this total disaster and how I can make sure this never happens again?

Does anyone have an idea on if this is going to be an easy fix or is this a really big deal?

Thank you, as always the Apex team is great!!

I’ll add some login details to a secure note so you can poke around.

I know my google rankings & SEO has just been absolutely destroyed by this for probably over a year now. This is an absolute top priority for me to completely fix 100% ASAP!

#2

Hey John,

Thank you for your kind words about our Apex team.

I checked the errors though and they’re not caused by our theme. The issues stem from your server and robot.txt setup.

Just checking the console, I see that there’s a CORS related issue. Please contact your web host to fix that.

For the robots.txt, please contact a SEO expert to configure the robots.txt for you as this is not a service we offer or included in our product support.

Thank you for understanding.

#3

Ok so for the web host/server issues related to CORS

I spoke to hostgator and they gave me this thread to read:

Can you tell me if that is indeed the fix I need?

Basically it says:

Add the following line to the .htaccess file:

Header set Access-Control-Allow-Origin "*"

The instructions to enable CORS say to put it into the apache configuration but considering this would get overwritten, I would add it to the .htaccess.

Does that seem right?

And I see a lot of the errors are related to the RevSlider, is this widget/plugin not functioning properly on it’s own?

Or it’s all related to the CORS issue?

Any idea what would my make robots.txt be so out of whack that it needs an SEO specialist to fix it?

#4

Hello John,

Your are experiencing CORS. The file resources of your site were loaded coming from this 3rd party site: https://i1.wp.com/. This usually happens when you enable the site accelerator feature in Jetpack plugin. Please temporarily disable this feature or temporarily deactivate Jetpack plugin and test your site again.

Kindly let us know how it goes.

#5

Ok so most definetly Jetpack Site Accelerator was enabled:

I know I enabled this because my website & specifically the Home page is very image-rich, so I wanted the best & fastest loading times for visitors.

But that seems to have actually made it worse this entire time and it really doesn’t load as fast as it should!

Does this feature of theirs actually work and is beneficial? Should I setup this CORS properly so that I can re-enable this feature?

Or would Users actually see better performance if I kept this feature disabled?

What about the other Lazy Load option of theirs, can I enable it to help only load pics only as viewers are scrolling for faster page loading - does this actually work?

Would enabling this feature also conflict with with this CORS issue?

If CORS is setup properly, can I run the Site Accelorator & Lazy Load together for the best/fastest user experience?

I feel that with so many images, some of they on the larger size that my websites home page loads very slow and optimizing it’s speed is something I’m really trying to do.

Thank you!

#6

Ok so i disabled the Site Accelerator feature and re-ran the Mobile Friendly URL test from my first post within about 5 minutes and it seemed to help clear up part of the errors:

It seemed to have cleared up almost all of the Javascript issues, and some of the other errors, however, there are still 200 various errors.

Did I give the website enough time to “re-configure” itself after disabling Site Accelerator & re-running that mobile test?

What are my next steps to clear the rest of these errors up?

Thank you.

#7

Hello John,

Your intentions to use the Jetpack’s Site Accelerator is to make the site load faster. The problem is that your server does not allow CORS or Cross Origin Resource Sharing. How this works? Now that the Site Accelerator were disabled, your images were load from the same domain, eg http://www.example.com/wp-content/uploads/2010/9/the-image-file.jpg. When the Site Accelerator were enabled, the images were loaded from a caching server like https://i1.wp.com/www.example.com/wp-content/uploads/2010/9/the-image-file.jpg and this is the CORS issue happens. So you will either fix the CORS issue in your server and continue using Site Accelerator or just disable the feature to get rid of those errors.

And for the remaining issues, it is actually a warning that some of the resources were not loaded. Please check out this article to resolve that:

And so far your site is a mobile-friendly site.

#8

Ok so is the Jetpack Site Accelorator & Lazy Load both good options that really work and benefit the website load time?

If so I will enable CORS properly.

If they really don’t work that good, I won’t bother.

Also, I’ve re-ran that mobile test a few times and not only does it come back as “Page is Not mobile friendly”, it also keeps getting varying results of errors, including additional javascript errors.

Why is this?

#9

Hey John,

Please forward all Jetpack related questions to Jetpack support. We do not cover support for third-party plugins.

Regarding the mobile responsive test, I previously said that it’s because of your robots.txt setup. I’d just add that Google could not reach your CSS so it thinks your site is not mobile responsive.

Sliders could also cause that error. The mobile friendly test might think that the content of sliders expand outside the container but it really doesn’t.

Though the mobile responsive text could be useful, the most important thing is the real output in mobile devices. If you don’t see content overflowing, your site is generally mobile responsive.

Please understand that our themes are mobile responsive and they alone won’t cause such an issue. This is not an issue with our theme so we could not cover this case as part of our product support.

Thank you for understanding.

#10

I’m having trouble finding my robots.txt file - where is it located within X Theme install?

#11

According to Yoast SEO, I don’t even have a robots.txt

Is this normal?

The Yoast plugin gives me the option to create one, but I’m not quite sure what info it needs.

Also, if I go to www.ohiocannabis.com/robots.txt, I get this:

Sitemap: https://www.ohiocannabis.com/sitemap.xml
Sitemap: https://www.ohiocannabis.com/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

#12

Hi John,

Please see the following link for more details about robots.txt file.

https://www.robotstxt.org/robotstxt.html

Please also check the Discourage search engines from indexing this site option on the Settings > Reading and make sure it is not enabled.

Thanks,

#13

Ok thank you, I’m working on getting this taken care of properly.

The Discourage Search Engines From indexing this site was NOT enabled, so I was ok there.

I guess the next step is to have the Yoast plugin create a robot.txt file for me and get it setup properly.

Also, in regards to the Jetpack plugin, I understand you said you do not cover support for third party plugins

But I was asking you as a ThemeCo rep if the Jetpack Site Accelorator & Lazy Load are both good options that really work and benefit the website load time

Or if I should ignore them because they aren’t as beneficial as they claim and conflict with X Theme Pro setup?

#14

Hi John,

You’re always welcome!

There are confirm cases that modules has conflict with the theme specially on displaying images. As stated you have to consult the jetpack developer to fix it disable it.

#15

Ok you mean to have the jetpack developer fix it OR just disable it right?

I’ll post on their support forum, but as of now I’m keeping it disabled.

Does the Site Accelerator and the Lazy Load BOTH have module problems with X Theme Pro?

#16

Hello John,

It is best that you temporarily disable the plugin while awaiting reply from the developers. And yes, the Site Accelerator and Lazy Load has conflicts with the editor. It prevents the editor or preview from loading.

Hope this helps.

#17

Ok so taking the Jetpack problem out of this equation, I’d like to focus on the problem with the robots.txt

I tried posting all of this over on the Google Search Console support forums, however they deleted my thread because of the word cannabis in it. So I won’t be able to get any help from them at all it seems. Hopefully someone here can help me get this figured out, it’s a total mess.

First off, I don’t understand why the robots.txt is even having a problem, which seems to be since I initially installed wordpress & X Theme Pro.

Why wasn’t this file automatically setup properly upon install?

Even my main Home Page hasn’t been Indexing this entire time, which according to google means it’s never showing up for any searches - which is obviously a major problem since I have a lot of pertinent info on my Home Page.

This is currently my new robots.txt file I created with Yoast SEO:

​​​User-agent: *
Allow: /wp-content/uploads/
Disallow: /wp-content/plugins/
Disallow: /wp-admin/
Disallow: /readme.html
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.ohiocannabis.com/sitemap.xml
Sitemap: https://www.ohiocannabis.com/news-sitemap.xml

It seems all of my crawl issues are related to images for the most part:

Which I’m really confused how the ability of the images to be crawled/featured/populate on my wordpress site has been messed up since install?

And even with adding this new Allow: /wp-content/uploads

The robots.txt is still blocked:

Shouldn’t the Allow: /wp-content/uploads/ clear up all of these image crawl issues now that I’ve added that specific Allow to the robots.txt file?

Also, is it necessary to have both of those Sitemaps? Is the news-sitemap.xml really needed? It was auto-generated by Yoast SEO when I had it create the robots.txt file.

I hope someone can help me get this fixed already, I’ve been getting destroyed with this terrible Indexing for over a year. I even get errors that my Home page isn’t Indexed!

Finally, when it comes to “Properties” in Google Search Console, I was originally told to add the following 4 Properties by someone:

https://www.ohiocannabis.comm



I’ve come to realize only the https://www.ohiocannabis.com had any real stats, the other 3 Properties literally had 4 crawls on them.

I also noticed that my new Yoast SEO robots.txt file was only updated on the https://www.ohiocannabis.com URL, for some reason the other 3 kept the old/default robots.txt file

I just deleted the other 3 as I didn’t think they were doing anything based on their stats and clearly seemed to be negatively affecting Indexing with the old/default robots.txt file

Should I add them back?

Sorry this is so long, but I’m really in a bad place with SEO & Indexing and it’s really been devastating to my business this last year by having very low traffic.

I’m not sure if this robots.txts affects the mobile-friendly test coming back with a bunch of resources errors or not still or is this a separate problem still?

I’ve added some updated login credentials.

Thank you.

#18

Hey John,

We understand that you’re having a hard time with your robots.txt setup but, as I’ve said previously:

None of our products generate robots.txt therefore none of them could cause the issue you’re experiencing with Google Search Console.

robots.txt is usually exists out of the box with your hosting setup. If not, it must be setup manually or generated by SEO plugins. Please contact an expert that can fix your robots.txt for you.

If you are interested to try fixing this yourself, try reading this: https://moz.com/blog/why-all-seos-should-unblock-js-css.

Please just remember that we will not fix your robots.txt as that is not a part of our product support.

I kindly ask that you understand our position.

Thank you.

#20

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.