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:
  • [Translate]
  • [Translate]
  • [Translate]
  • [Translate]
  • [Translate]
  • [Translate]
  • [Cache/Archive]
  • [Translate]
  • [Proxy]
  • [Translate]
  • [Admin Configuration of Apps on Cloudflare]
  • [Translate and Cache]
  • [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.


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:, 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, 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.

Adsense Auto Ads with Regular Ads

After seeing Adsense Auto Ads beta feature pop up on my account, I was excited to jump right in. I did, however, worry adsense would be too conservative in placing ads or just not place the right type of ads for my site. In an effort to not have a couple day drop of a good chunk of revenue, I simply placed the auto-ad code in along with the existing ads on my site.

Auto Ads Setup Screen

I will be monitoring the performance closely and may remove the hard-coded ads to see if performance keeps up.

Set up Auto ads on your site

Copy and paste this code in between the <head> tags of your site. It’s the same code for all your pages. You don’t need to change it even if you change your global preferences. See our code implementation guide for more details.
For those of you looking to get started with auto-ads, you may be able to place the following code onto your site (with your own publisher-id).
<script async src="//"></script>
 (adsbygoogle = window.adsbygoogle || []).push({
 google_ad_client: "ca-pub-0545639743190253",
 enable_page_level_ads: true

The auto-ads management page can be found at:

but since the program is still in beta, many users don’t have access yet.


Google also has the Auto Ads for AMP pages, in their documentation for the AMP implementation,  things are set out more clearly:


Google Custom Search Results Not Loading [results on own domain]

A big problem with Google’s Custom Search engine is the code is not formatted for users on https websites:

You can see the two urls and are both insecure. This is even after providing Google with the secure version of the site where the ad-code would be displayed. When implementing the code and the results page, most users see a blank page or a search box missing the google custom search logo.

The simple fix for this issue is to change the http in the urls to https. This will stop any mixed content errors and users over your http and https site alike will have no trouble loading the searchbox or search results.

Hope this helps anyone! Ask any questions in the comments!