Forum Moderators: martinibuster

Message Too Old, No Replies

Earnings at risk - You need to fix some ads.txt file issues.

         

puente

4:24 pm on May 3, 2020 (gmt 0)

5+ Year Member Top Contributors Of The Month



hi all,

"Earnings at risk - You need to fix some ads.txt file issues to avoid severe impact to your revenue."

i'm sure this topic has been discussed ad nauseam. but i've had this message for my sites for a few weeks now while nothing was changed. all tests are showing good access and valid setting and content.

i do have a list of abusive ip's blocked at f/w level for years and wonder if google is using one of those to access ads.txt now. don't want to open that up and give access to the parasites while waiting weeks to see the results.

would you nice people dig into your logs and reply with google ip addresses that crawl your ads.txt files?

of course the addresses would be different for different sites but it may give me a clue.

not2easy

5:24 pm on May 3, 2020 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



"Earnings at risk - You need to fix some ads.txt file issues to avoid severe impact to your revenue."
Do they not offer any more information than that? Nowhere to click to find out what action they want you to take?

Sorry, but looking through my logs could not help you. What IPs do you see in your logs, those would be the ones to check to make sure they are who they say they are. Lots of requests for ads.txt claiming to be Media Partners are clearly not from any Google ranges. If you know which ranges you are blocking, just compare those IPs to Google's bot ranges. Unlike some major bots, Google has been transparent on where they come from and what user agents they use.

From a quick search here for Googlebot IPs I see: at [webmasterworld.com...]
@lucy24:
Are they all legitimate Google IPs? Within the US, it should only be 66.249.64.0/20 for crawling. (The adjacent 66.249.80.0/20, like the other Google addresses in the US, is for various Googloid functions of varying legitimacy.) It's a widely spoofed UA, so I hope you're blocking anything that claims to be the Googlebot but comes from elsewhere.

Rumor has it they're also using non-US ranges, but only if you've got non-US-targeted content. Has anyone worked up a list of legitimate Google IPs outside the US? I don't remember seeing one.


Other more recent information regarding the AdSense "Mediapartners-Google" bots: [webmasterworld.com...]
and [webmasterworld.com...]

OR- you can visit Google's information pages where they list the UA's as "Mediapartners-Google" (only) for the desktop bot and (Various mobile device types) plus (compatible; Mediapartners-Google/2.1; +http://www.google.com/bot.html) for mobile.

How to verify? [googlewebmastercentral.blogspot.com...]

puente

3:18 pm on May 4, 2020 (gmt 0)

5+ Year Member Top Contributors Of The Month



thanks for the reply.

adsense gives no other info. just a link to download ads.txt file which is already the same exact file on my sites.

also dug into as15169 which has google's ip prefixes. not much luck there.

and sent a message to adsense but not really expecting a response.

well, will keep investigating.

CommandDork

2:20 am on May 6, 2020 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I've had this same msg on my account going on four weeks now. Nothing's changed on my end. The file has been there for years so I dont know what Adsense's prob is.

Have no clue why it triggered all of a sudden. I'm monitoring things and revenue hasn't been impacted as far as I can tell.

And, ya, the only help is the download link. Which isn't helpful at all.

Seems it's always something doesn't it?

I've had this happen before on another domain and ignored it. It went away on it's own eventually.

puente

2:22 pm on May 8, 2020 (gmt 0)

5+ Year Member Top Contributors Of The Month



the stupid pink error notice has finally gone away. commanddork, is yours gone too?

on closer look, one of my adsense registered sites had a subdomain that was an alias to a classic google sites website. like abc.example.com aliased to sites.google.com/sites/account.

this had been there for over a decade and apparently google sites changed something or adsense decided it no longer liked google sites and that triggered the notice.

i removed the subdomain from the list and after a couple of days the notice is gone. i'd also sent a feedback request on this to adsense so maybe that helped, though doubt it.

now was this really a google sites issue? who knows. adsense was no help. it wouldn't even point out which subdomain was the culprit, if in fact that was the cause.

maybe the error notice was just a fluke and was going away by itself anyways. or maybe it'll come back again. it's all a big G mystery.

in case anyone's interested, i got access to the logs of another domain and below is a partial list of ip's that were hitting /ads.txt.
they all seem to be aws hosts and possibly belong to Interactive Advertising Bureau (IAB), but can't confirm. some could be spoofs.

100.25.43.200 AdsTxtCrawler/1.0.2
18.204.201.59 AdsTxtCrawler/1.0.2
18.205.21.0 AdsTxtCrawler/1.0.2
18.232.105.109 AdsTxtCrawler/1.0.2
3.220.230.179 AdsTxtCrawler/1.0.2
3.233.232.237 AdsTxtCrawler/1.0.2
3.234.239.74 AdsTxtCrawler/1.0.2
3.235.15.240 AdsTxtCrawler/1.0.2
34.237.145.104 AdsTxtCrawler/1.0.2
34.239.156.175 AdsTxtCrawler/1.0.2
3.80.207.167 AdsTxtCrawler/1.0.2
3.86.5.61 AdsTxtCrawler/1.0.2
3.92.61.99 AdsTxtCrawler/1.0.2
3.93.57.2 AdsTxtCrawler/1.0.2
3.94.29.5 AdsTxtCrawler/1.0.2
54.157.114.219 AdsTxtCrawler/1.0.2
54.159.94.151 AdsTxtCrawler/1.0.2
54.174.75.191 AdsTxtCrawler/1.0.2
54.198.89.245 AdsTxtCrawler/1.0.2
54.80.121.21 AdsTxtCrawler/1.0.2
54.87.185.19 AdsTxtCrawler/1.0.2
54.90.216.182 AdsTxtCrawler/1.0.2