GoogleInitIc – Google Adsense Experiencing a loading issue

Google Adsense / Double click seems to be experiencing some occasional loading issues across domains. Users are seeing the text “GoogleInitIc(document.body,’10,10,10,10′)” followed by a blank space in place of an advertisement. These issues appear widespread and could be impacting ad revenue.

GoogleInitIc loading error with blank ad space

Bulk IP-Address / Reverse DNS Lookup Tool

I’ve created this simple little Google Sheet for conducting reverse DNS / IP address lookup via Google Sheets.

I primarily use this tool for auditing the top IP addresses connecting to my site. If you use this API for your own products, please include your website/contact in the URL.

The sheet works off of an API hosted by me so if you have any requests or if you just enjoy using the free tool, please leave me a comment below.

Google-Certificates-Bridge User Agent .well-known/acme-challenge Requests

I recently have been having many requests coming from Google IPv4 and IPv6 addresses with the user agent “Google-Certificates-Bridge” accessing unique files within /.well-known/acme-challenge/XXXX.
A snippet from my Apache Log
64.233.172.141 - - [25/Dec/2018:23:30:30 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
64.233.172.145 - - [25/Dec/2018:23:30:40 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
64.233.172.143 - - [25/Dec/2018:23:30:50 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
64.233.172.146 - - [25/Dec/2018:23:31:00 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
2001:4860:4801:400a::35 - - [25/Dec/2018:23:31:10 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
64.233.172.144 - - [25/Dec/2018:23:31:20 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
2001:4860:4801:400a::19 - - [25/Dec/2018:23:31:30 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
66.102.8.40 - - [25/Dec/2018:23:31:39 +0000] "GET /.well-known/acme-challenge/XXXXXXXXXXXXX-XXXXXXXXXXXXX HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"
64.233.172.143 - - [25/Dec/2018:23:31:40 +0000] "GET /.well-known/acme-challenge/LjaR-XXXXXXXXXXXXX-lgf6-QW8 HTTP/1.1" 404 - "-" "Google-Certificates-Bridge"

These requests are used by Cpanel, Google and some other services for the purpose of verifying SSL certificates issued to the domain. No need to worry, as long as the requests are coming from a familiar IP, this is not likely attack traffic.

Adsense: Is this your site? We’ve detected your ad code on the site below…

Is this your site? We’ve detected your ad code on the site below. If it’s your site, click Yes to add it to your Sites.
Web caches, proxies, and translation services often appear as sites where Google Adsense has detected your ad code. Here is a list of services I’ve seen on my account:
  • translatoruser-int.com [Translate]
  • translate.google.com [Translate]
  • translate.google.ru [Translate]
  • translate.google.com.br [Translate]
  • translatoruser.net [Translate]
  • www.microsofttranslator.com [Translate]
  • web.archive.org [Cache/Archive]
  • www.translate.ru [Translate]
  • www.proxyit.cc [Proxy]
  • www.s-translation.jp [Translate]
  • cloudflare.works [Admin Configuration of Apps on Cloudflare]
  • yandex.ru [Translate and Cache]
  • dakwak.com [Translate]
  • Web caches and other [Google “Cache:”, other]

For my properties, I primarily receive this message from the Adsense console due to translation services accessing the site and pulling my Adsense code through to their front-end.  Generally, it is not a good idea to add translation services, caches, and proxies to your Adsense account. Although depending on the number of readers you have translating your site, you could gain a few extra percent of ad revenue. This does, however, come with some major risks which may outweigh the small percentage of revenue gain you could see from these new domains.

Within the Adsense Sites configuration [Adsense > Sites > Overview] you can control the list of sites your code appears on. 

This feature was added as a way to protect your account from “malicious use of your ad code by others”. The sites in your sites list are the only sites that are permitted to use your ad code. If a site displaying your ad code is not on your list of sites, then no ads will show on that site.

Malicious use of your ad code could include generating false clicks on your site for the purpose of harming your Adsense account, revenue, and reputation. A malicious actor might include a competitor or someone else looking to harm your site for their own financial gain.

By enabling translation sites, caches,  and proxies to display your ad code, you open your account be displayed alongside content you might not control. Malicious actors could serve up your ad code alongside restricted content creating negative marks on your Adsense account.  Because Proxies are known to be couriers of less desirable internet content (and thus are disallowed by Adsense ToS), I would never risk adding a proxy domain to my AdSense account. Auto-translating sites are a risk as well due to the poor quality of the translations. In most cases, auto-translated content is considered low-quality by Adsesnse. Because caches are often a direct mirror of your content they carry a smaller risk of being low-quality or malicious, but for most, the risk likely doesn’t outweigh the payoff.

 

/h/8913147.html in Google Analytics Spam

The page “/h/8913147.html” is part of a Google Analytics Spam campaign published by get-seo-help.com
It is likely the uniqueness of the url is utilized to avoid being filted by Google.

I’ve also seen the same html page being used for referrer spam from  free-seo-consultation.com

 

Verification methods used: Unknown [Google Search Console]

If you purchased a domain via domains.google, you can add it to your Google Webmaster Tools / Search Console without performing any further verification (no Google Analytics / DNS / HTML file required).

It makes adding domains and subdomains to WMT / GSC super easy, but it also comes with a confusing “Unknown” domain verification information tag.

Verification Method Unknown

Using pandas.DataFrame.to_sql to UPDATE/REPLACE data

It’s pretty simple. You’ll have to first create a temporary table that matches your destination table. Then, use the pandads dataframe to replace the data in the temporary table with your new data (if_exists=’replace’).
dataframe.to_sql(‘mydatatable_temp’, conn, if_exists=’replace’, index=False)

From there you will use this little bit of SQL to update your destination data table with the newly loaded temp table data
conn.execute(‘REPLACE INTO mydatatable (SELECT * FROM mydatatable_temp);’)

If you found this at all useful, please comment and I will come back and make this a much better walkthrough. I also routinely answer questions and comments below.

Google Adsense ads.txt

Dear Publisher,
We’ve noticed that one or more of the sites listed in the ‘My sites’ tab in your AdSense account doesn’t have an ads.txt file.
Ads.txt helps ensure your ad space is only sold through sellers (e.g., AdSense) who you’ve identified as authorized. This gives you control over who’s allowed to sell ads on your site and prevents unauthorized sellers from potentially falsifying your domain to sell their inventory to prospective advertisers. You can learn more about ads.txt in our Help Center.
Soon advertisers who use some of our ads products to buy ad space on publisher sites will have the option to only bid on inventory from sellers that are classified as authorized through ads.txt. To ensure that prospective advertisers can continue to bid on your ad space, it’s important to create and publish an ads.txt file on all your sites.
To post an ads.txt file on your sites, here’s what you need to do:
1. Create a blank text (.txt) file
2. Include the following line:
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
(Important: Make sure you replace pub-0000000000000000 with your own publisher ID which can be found at the top of this email)
3. Save it as ads.txt and upload to the root domain for every site in your My sites list (for example, https://example.com/ads.txt). It may take up to 24 hours for AdSense to process your updated ads.txt files. Please work with your webmaster to ensure that they can be crawled by Google
If you find sites in your My sites list that you don’t own or monetize on, please do the following:
1. Turn on site authorization
2. Make sure only your owned sites are marked as verified
Site authorization ensures your ad code only works on the sites that you mark as verified, which means it’s protected from malicious or accidental use by others. When site authorization is turned on, information in your AdSense account is restricted to your verified sites, including any ads.txt issues you may have. You can learn more about how to authorize your verified sites to display ads in our Help Center.

Disable: This file is dangerous, so Chrome has blocked it.

If you are experiencing this error when trying to download a file, you will need to disable your file download protection in Chrome.

This file is dangerous, so Chrome has blocked it.

Answer To Solve: Copy this URL and disable “Protect you and your device from dangerous sites”
chrome://settings/?search=Protect+you+and+your+device

Protect you and your device from dangerous sites

Google Search Console Crawl Rate Settings

Your site is being crawled at a rate calculated as optimal by Google. You can change the crawl rate only by filing a special request using the form mentioned in the “learn more” documentation.

For some sites, Google will allow users to adjust the crawl rate and thus manually limit the amount of traffic Google has on your servers. This customization option is only available to some sites. I’ve been unable to determine what metric limits users to adjusting this option. Sites with high and low traffic have the option both available and not available (replaced by the above message).

Google tries to crawl as many of your site’s pages as we can without overwhelming your server’s bandwidth. If Google’s crawlers are slowing your site, you can change the crawl rate (the speed of Google’s requests). This feature is only available for sites at the root or subdomain level.

If you think Googlebot is crawling your site too quickly, and you want to slow it down but cannot (because the WMT option is disabled), you can file a request here to report Googlebot issues with crawling. You’ll need to know the following information before you submit a crawl-issue request.

  1. From what IP addresses are you seeing Googlebot activity?
  2. For which user-agent are you seeing Googlebot activity?
  3. How many times a day does Googlebot access your site?
  4. Additional details (Please also include a portion of the weblog that shows Google accesses so we can track down the problem quickly):

Report a problem with how Googlebot crawls your site.
You can report problems only for domain-level properties (for example, “www.example.com/”)

The rate at which Google crawls your page depends on many factors:

  • The URLs we already know about
  • Links from other web pages (within your site and on other sites)
  • URLs listed in your Sitemap.

For most sites, Googlebot shouldn’t access your site more than once every few seconds on average. However, due to network delays, it’s possible that the rate will appear to be slightly higher over short periods. If you are seeing a particular issue with the Googlebot, please share it in the comments!