Blogger ads.txt: Add Your Publisher Record and Verify Its Status

If you use Google AdSense or another advertising partner on a Blogger site, an ads.txt file can help buyers identify which companies are authorised to sell your ad inventory. It is a small text file, but a missing or incorrect entry can lead to warnings in an advertising dashboard or reduce the number of eligible ad buyers.

The good news is that Blogger hosts the file for you. You do not need FTP, a separate hosting account, or a plugin. You only need the exact seller record supplied by your advertising provider and access to the correct Blogger blog.

What ads.txt does

Ads.txt means "Authorized Digital Sellers." It is an IAB Tech Lab standard that publishes a list of companies allowed to sell advertising for a website. It does not guarantee approval for AdSense, increase traffic, or raise revenue by itself. It simply makes your advertising relationships more transparent and helps reduce counterfeit inventory.

The typical AdSense line looks like this:

google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0

Replace the X characters with your own AdSense publisher ID. Keep the pub- prefix and required comma-separated fields; copy the provider’s record exactly. Never copy a publisher ID from another site. If you use another network, ask that network for its official ads.txt record and add it only if you actually work with that provider.

Add ads.txt in Blogger

1. Sign in to Blogger with the Google account that manages your site.
2. In the Blogger dashboard, choose the blog you want to edit. Double-check the blog name before changing settings.
3. Open Settings in the left-hand menu.
4. Scroll to the Monetization section.
5. Turn on Enable custom ads.txt.
6. Select Custom ads.txt.
7. Paste the exact line or lines supplied by AdSense and your other legitimate ad partners.
8. Click Save.

If several providers are authorised to sell your inventory, put each record on its own line. Do not add random networks, affiliate programs, or "recommended" lines from an online template. An ads.txt record should describe a real business relationship.

For AdSense, you can usually find the suggested record in the AdSense notification or in the ads.txt area of your account. Your publisher ID is also shown in AdSense under account information. Treat it as business information, not as a password; your password, two-factor codes, and recovery details must never be pasted into ads.txt.

Check that the file is live

After saving, open this address in a browser, replacing the example domain with your own:

https://yourblog.blogspot.com/ads.txt

If you use a custom domain, check the custom-domain version as well. The page should show plain text containing the record you added. If it still returns an error or an old version, wait and try again: Blogger, caches, and advertising crawlers may not update at exactly the same time.

You can also return to AdSense and use its option to check for updates, when available. Detection is not always immediate, so do not repeatedly edit the file or paste duplicate lines while waiting. Keep a copy of the exact records you approved for your site.

Common mistakes to avoid

Using the wrong publisher ID: AdSense IDs are tied to an account. Copy yours carefully, including pub- and all digits.

Putting the code in a post: Ads.txt belongs at the site-level /ads.txt address. A blog post, HTML gadget, or robots.txt entry is not a substitute.

Overwriting a provider's record: If an existing file contains a legitimate line, preserve it unless the provider tells you to remove it. Add new lines separately.

Expecting instant earnings: Ads.txt is not a monetization switch. You still need an eligible site, a valid AdSense setup, policy compliance, and ad placements that work for readers.

Ignoring policy requirements: Do not click your own ads, encourage others to click them, or publish prohibited content to chase impressions. Follow the current Blogger and AdSense publisher policies.

Saved, public and recognized are different checks

Keep these observations separate when troubleshooting:

• Saved: reopen Blogger’s custom ads.txt setting and compare it with the provider’s record. This checks the saved value, not crawler access.
• Public: open the site’s /ads.txt address and compare the actual text. If the browser reports that an extension or client blocked the request, that observation alone cannot establish whether Google can fetch the file. Do not change publisher IDs to solve a local viewing error.
• Recognized: inspect the site’s ads.txt status in AdSense, including when it was last checked. A correct-looking public file is useful evidence, but is not the same as an updated authorization status.

Google says AdSense updates can take a few days, or up to a month for sites with few ad requests. Use Sites → select the site → Check for updates when appropriate. Record the change and check times rather than repeatedly replacing identical lines.

Final checklist

Confirm that custom ads.txt is enabled, your publisher ID is yours, every line came from a real provider, and /ads.txt displays the expected text. Recheck after changing domains, switching ad partners, or closing an account. Keep the saved record and the date of your last check so a later account or domain change can be investigated.

Links and dashboard labels can change. Always follow the latest instructions from Blogger, AdSense, and your advertising provider.

Sources: Google Blogger Help: advertise on your blog, including custom ads.txt setup and Google AdSense Help: ads.txt guide and update timing, checked October 9, 2026.

Prepared with AI assistance. The troubleshooting distinctions are editorial guidance, not a claim that Advice Me has verified authorization for every reader’s site.