Matt Magi

I see that thanks, but would I check off “Media” I was worried that would stop images themselves from being indexed. Would that just apply to the media attachment URL?

Thanks @foomagoo

@redsand do you have any solutions on your end to make your plugin work with plugin organizer? I emailed you guys as well. Thanks!

Oh you two…lets all be friends. Thanks guys.

Yes I am actually!

Jacob,

Great thanks, some documentation for newbies would be great to have. Including things on facebook’s end.

Thanks for your responses.

Jacob,

Thanks! So if I want to use ViewContent on page, and target those people what do I need to fill into the “Value 1” fields? And what will it show up like on my facebook pixel stats page? Will it have ViewContent there?

Thanks again!

Its not a google or wp bug.

Apparently google just started sending out the JS/CSS warnings today (even though they have been using this method for some time) which would explain why we all are just finding out:
https://www.thesempost.com/new-google-search-console-warning-for-googlebot-cannot-access-css-and-js-files/

More info above.

I guess its OK to allow all now. As google is smart enough apparently not to index wp core files. They started targeting css/js a while back on their last update, but are now just sending out warnings. Here are some articles:
https://yoast.com/google-panda-robots-css-js/
https://yoast.com/wordpress-robots-txt-example/

Some of mine do, for example:

/wp-content/plugins/custom-contact-forms/css/jquery-ui.css?ver=3.3.1

This is VERY common in wp themes.

Exactly, but if your super cautious you could always disallow as usual (wp- or wp-admin, wp-includes) and follow the method mlepisto posted.

mlepisto that looks like a solid solution as well ?? so I suppose if you feel safer or better by disallowing wp-admin, wp-functions you can add those lines to allow the JS/CSS.

So what do you have in your robots.text exactly so others can see how you feel its best structured?

User-Agent: *
Disallow: /wp-*

User-Agent: Googlebot
Allow: /*.js*
Allow: /*.css*

Looks like a good robots.txt to me that will solve this problem. Thats the way I’d personally go, I was just stating that according to yoast (who are very well known for WP SEO) they are saying there is no longer any reason to block wp- directories.

bsaverino, those lines will allow ANY JS or CSS file so it shouldn’t matter.

Dont ignore it, its not a bug. I clearly stated why its happening and the solution.

Its happening now because google just started notifying people about the access issues today.

pbensin, if you read above I posted the solution and the reason everyone is getting these messages.

sfeatherston, see my message above, remove /wp-admin/ and you will be OK.

Apparently google just started sending out the JS/CSS warnings today (even though they have been using this method for some time) which would explain why we all are just finding out:
https://www.thesempost.com/new-google-search-console-warning-for-googlebot-cannot-access-css-and-js-files/

More info above.

I guess its OK to allow all now. As google is smart enough apparently not to index wp core files. They started targeting css/js a while back on their last update, but are now just sending out warnings. Here are some articles:
https://yoast.com/google-panda-robots-css-js/
https://yoast.com/wordpress-robots-txt-example/

********************************
******THE SOLUTION******
********************************

We should just keep all our robots.txt files blank from now on. There is no longer a need to block core wp directories.

I just updated my robots.txt. I removed my disallow of wp-includes, wp-admin etc. and now google is rendering my websites properly.

To test it, login to webmaster tools, and simply fetch and render as google. If your site appears in the screenshot to not be loading CSS then your robots.txt is blocking it somehow.