GSC / Google Search is not the same as Adsense / Adsense bot.

What you are seeing is obviously a consequence of the Brand safety thing. From an adsense point of view, your pages are new, and so, for a while, Adsense will not serve ads, until the Adsense bot visits these pages, and verify the content.

That's so helpful. Thank you Travis. Unfortunately, It makes sense except that almost all my pages have some ads except the home page. Is there a way to check on whether the adsense bot has crawled?

Sorry, I didn't understand it was only the homepage missing ads. In that case, I don't know.

About checking adsense' bot, you should see it in your logs.

Thanks for trying. I have an email into the adsense help team so maybe they'll have some answers.

Just a couple points to check...

• If you have any security warnings on a page, Adsense will automatically not server ads.

• In your Adsense code, none of the paths should be HTTP. Either add the "S" or remove the protocol altogether.

• The Brand Safety impact could be kicking in since you are now using HTTPS. This removes ads until the Adsense bot verifies your page is safe. To speed this process up, it helps to visit your pages with the Chrome browser.

Here's something weird. Today, I got this message: "Googlebot couldn't get all resources for this page. Here's a list: " And then it lists

https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js It says that my robot.txt files says:

User-Agent: *
Allow: /ads/preferences/
Allow: /gpt/
Disallow: /
Noindex: /

This is false as I've checked and my web host tech support checked and my robot.txt is:
User-agent: *
Disallow:

What's up with this false robots.txt?

[edited by: not2easy at 1:36 am (utc) on May 7, 2018]
[edit reason] delinked javascript [/edit]

What's up with this false robots.txt?

Double check this by going to GSC > Crawl > robots.txt Tester

Google may in fact have a *false* robots.txt for your site. If it does, submit your *correct* one.

Now, where did this *false* robots.txt come from? That's an important question.

I did the crawl and got:
User-agent: *
Disallow:

This is what my webhost techs verified as my robots.txt also. Do you know how I submit a robots.txt to google?

Yes, this false robots has come up before.

Do you know how I submit a robots.txt to google?

I just told you

GSC > Crawl > robots.txt Tester

Use the button that says "Submit"

[added]
Regarding "this false robots has come up before."

You need to find out where it's coming from. Googlebot is getting it from somewhere. It's possible your site has been copied, code and all. Do a few web searches for short phrases found on your pages. See if in fact someone has duplicated your pages... if so, there are a few steps you can take.

The robots.txt they are referring to is probably their own. Read about Blocked Resources here: [webmasterworld.com...]

I've gone through the trouble of clicking through to see the source of the problem and it is almost always their own .js and robots.txt files that are the Blocked Resources. They tell you there that the importance is "Low". Not your problem.

Google's tools are irony at its best. Several of them give you errors when it's Google itself causing the error.

Thanks everyone. Very helpful.

This is false as I've checked and my web host tech support checked and my robot.txt is:

And what do YOU see when you access your own robots.txt (by typing the URL in the address bar of your browser).

User-agent: *
Disallow:

That's what I see . I still have no adsense showing up on my home page but it's on other pages of my site. Huge drop in revenue. I know I have to be patient but it's my main source of income for my kids and I so makes me a bit worried .

When you added the "new" https domain to GSC did you validate it in GSC?

Did you also add the "new" domain to your AdSense account as an authorized domain?

When you redirected via htaccess, did you ensure that it is only accessible via https and that the rewrite is via 301? Did you ensure that the resources are also secure (an example would be an image or .js script from http)?

I did validate my new domain in gsc. I have tried to add the new domain to adsense but it doesn't show the "new" domain...just the domain minus the "https://www". I don't think it matters in adsense. My web host did the redirect for me via my .htaccess file. Looks like this but with my domain in there:

RewriteEngine On
#RewriteCond %{HTTP_HOST} ^example\.com [NC]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]

I did replace all my http code with https via "Dreamweaver find and replace" and have rechecked. The weird thing is that I have another website that was redirected to https also and that home page is showing ads just fine, but it's considered a subdomain. I don't know if that would matter. But my home page on my main website isn't showing the ads. Maybe I have to wait until Google crawls it because in google search, it's still showing up some places as just www instead of https://www. Not sure why other pages are showing ads just fine though.

[edited by: not2easy at 2:22 pm (utc) on May 7, 2018]
[edit reason] unlinked for readability [/edit]

I just noticed that in google search, some pages are showing up as https and some aren't. My home page isn't.

The code that your host provided has a few issues, I'd suggest asking around in the Apache [webmasterworld.com] forum because it is not a 301 rewrite. That first line is commented out (with #). Google sees this as temporary, not permanent. That "[R,L] " part would need to have a 301 in the flag because Apache's default is a 302 Temporary status.

Thank you so much. I will ask the tech guys about this. Dang it.

I figured it out. I had taken off a piece of js called the "global tracking snippet" along with my google analytics code. When I put this back on my home page, the ads showed up again. Weird. I'm on the fence about Analytics because I don't ever use it. I like statcounter. What do you guys think?

Good to hear you're seeing ads again, but that rewrite 302 is something you should fix as soon as possible.

BTW - I also dislike GA.

Thank you not2easy. I had the tech guys at my inmotion check the .htaccess file. When he tried to rewrite it with a "301" instead of the "RL", he got a "too many redirects" error message. that's what my site showed when I checked it and the site was down. I had him put the old code back because it's prime time for me and I can't afford to have my site down. He didn't understand why the 301 would prompt a "too many redirects" message and was going to ask a superior, except that my site would have to be down the whole time and I said no for now. Any clues?

I'll bet it is related to the order of the rules. Is this a WordPress site? If so, that WP code needs to be AFTER the https redirect. If not, then the 301 needs to be the last rule.
Also important is if you have rewrite rules using mod_rewrite and redirects using mod_alias mixed in there, it will cause a problem. This is why I suggested taking it to the Apache forum where you can get correct answers. This is the AdSense forum, we don't do Apache here, sorry.

I will take it to the Apache forum for sure. Thanks a bunch. It's not a WP site. I use Dreamweaver. The order of rules does make some sense, though. Thank you so much for your input. So helpful!