Skip to content
Approvalens

Guides7 min read

AdSense on WordPress: Setup, Plugins and Rejection Traps

Getting WordPress ready for AdSense: where the code goes, Site Kit, WordPress.com plans, settings that hide your site, and thin auto-made pages.

Fixes these report findings

  • AdSense code and meta tag
  • Homepage is indexable
  • Googlebot allowed in robots.txt
  • Placeholder homepage
  • Default CMS content
  • Archive and utility pages in the index
  • Good pages marked noindex
  • Required privacy statements
  • +2

A self-hosted WordPress site applies for AdSense like any other site. You put the AdSense code in the <head> (by hand or with a plugin such as Site Kit by Google), make sure Google's crawlers can reach the pages, and submit the domain. Most WordPress rejections don't come from WordPress. They come from leftovers and settings: a "Hello world!" post, a "Discourage search engines" box nobody unticked, a security plugin that blocks bots, or hundreds of near-empty tag pages that WordPress generated on its own.

WordPress.org or WordPress.com?

These are different situations.

  • WordPress.org (self-hosted). You control the theme, plugins and server, so you can add code to <head> and upload ads.txt to the root. AdSense requires exactly that: "you must have access to the HTML source code of your site. You need to be able to place AdSense code between the tags of your pages" (owning the site).
  • WordPress.com (hosted). Adding header code is available on the Personal, Premium, Business and Commerce plans, using the Insert Headers and Footers plugin by WPCode (adding code to headers). WordPress.com notes that script tags need a plugin-enabled plan with hosting features activated (code on WordPress.com). The free plan can't do it. WordPress.com also has its own ad program, WordAds, from Premium upward, and recommends running "only one ad program at a time" (WordAds).

The rest of this guide is about self-hosted WordPress. Most of it applies to WordPress.com plugin-enabled plans too.

Where the code goes

AdSense accepts three ways to verify a site: the AdSense code snippet, an ads.txt snippet, or a meta tag (connect your site). On WordPress, pick one way to place the code:

Method Good for Watch out for
Site Kit by Google Official, connects your account. With "Let Site Kit place AdSense code on your site" enabled, it inserts the Auto ads snippet (Site Kit AdSense) Site Kit recommends removing other AdSense snippets, or "you may run into errors due to duplicate codes"
A header-code plugin (e.g. WPCode) Survives theme changes Make sure the snippet is placed in the header, not the footer
header.php in a child theme No extra plugin Editing the parent theme is lost on the next update
An ad-management plugin Also handles placements and often ads.txt Don't let it add "Click here" style labels next to ads

The snippet, with your own ID:

<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1234567890123456" crossorigin="anonymous"></script>

Check it yourself

Open your home page and one post with view-source: in the address bar (not the DevTools inspector) and search for adsbygoogle. It should appear once, inside <head>, with your ID. Caching and optimisation plugins sometimes delay or merge scripts. That usually doesn't matter for verification, but if verification fails, exclude adsbygoogle.js from "delay JavaScript" features.

ads.txt

ads.txt is optional, but if it exists it must list you. AdSense's own FAQ suggests: "Consider using a plugin to create your ads.txt file in WordPress. If you already use a plugin to place ads, it might include a feature to create your ads.txt file" (ads.txt FAQ). The full how-to, including the physical-file-versus-plugin conflict and WordPress in a subfolder, is in how to add ads.txt on WordPress.

Settings that quietly hide your site

  1. Settings → Reading → Search engine visibility. When "Discourage search engines from indexing this site" is ticked, WordPress (5.3 and later) prints <meta name='robots' content='noindex,nofollow' /> in the head of every page (Reading Settings). Since 5.3 it no longer adds Disallow: / to robots.txt, so robots.txt looks fine while every page says noindex. Untick it.
  2. Settings → General → WordPress Address and Site Address. Both should use the version of your domain you submit to AdSense (https://, with or without www). A mismatch with your server's redirect causes loops. The cPanel www guide shows how to make them agree.
  3. Maintenance or "coming soon" plugins. They often return HTTP 503 to everyone who isn't logged in, including AdSense's crawler, so the site looks down. Turn them off before you submit.
  4. Security and firewall plugins. Rate limits, country blocks and "block unknown bots" rules can send 403 to Google. Allow verified Google crawlers, and check your host's firewall too. If Cloudflare sits in front of WordPress, see Cloudflare and AdSense.
  5. A physical robots.txt. WordPress's virtual robots.txt only works "if WordPress is installed in the site root and no robots.txt exists". An old file left by an SEO plugin overrides it. Open example.com/robots.txt and read every line, or paste it into the robots.txt tester.
  6. Login walls. Membership plugins that hide all posts behind a login leave the reviewer with nothing. AdSense asks you to "consider temporarily removing the login so that we can reach your site" (site not ready).

The thin pages WordPress creates for you

WordPress generates many URLs you never wrote. Google doesn't allow ads on screens "without publisher-content or with low-value content" (publisher policy), and reviewers look at the whole site.

A WordPress site's URL inventory drawn as a case file: posts and pages you wrote marked keep; Hello world, Sample Page and the draft privacy policy marked delete or rewrite; tag, author and date archives marked merge or noindex; attachment pages marked redirect
What WordPress publishes besides your posts, and what to do with each type before you apply.
URL type Example What to do
Default content /hello-world/, /sample-page/ Delete the post, the page and the sample comment. Approvalens flags them because they're a reliable sign of an unfinished site
Draft privacy page /privacy-policy/ WordPress's template is generic. Rewrite it with the AdSense statements, publish it and link it in the footer (privacy policy guide)
Tag archives /tag/recipes-2/ Fifty tags with one post each are fifty near-empty lists. Merge tags, or set tag archives to noindex in your SEO plugin
Author and date archives /author/admin/, /2026/10/ On a one-author blog they duplicate the main list. Most SEO plugins can turn them off
Attachment pages /my-post/image-1/ "As of WordPress 6.4, attachment pages for new WordPress installations are fully disabled", but on older sites "attachment pages continue to work as is" (WordPress 6.4 note). Redirect them with your SEO plugin
"Uncategorized" /category/uncategorized/ Rename it and sort your posts into real categories

Comments, forms and other plugins

  • Comment spam. You're responsible for user content on pages with ads. Google asks you to moderate comments (site pages ready). Hold first comments for moderation and use an anti-spam plugin.
  • Pop-up plugins. A full-screen newsletter modal in the first second of a mobile visit gets in the way of reading. Delay it or use a slide-in.
  • Other ad networks. If you run a network with pop-unders or push notifications, remove it before applying. Pop-unders aren't allowed on pages with Google ads.
  • Consent. If you serve visitors in the EEA, UK or Switzerland, Google requires a certified CMP that supports IAB TCF (consent requirements). Cookie plugins differ here, so check their TCF support. See the CMP guide.

WordPress pre-application checklist

  • AdSense code appears once in <head> in the page source
  • "Discourage search engines" is unticked and no page carries noindex by accident
  • WordPress Address and Site Address match the domain you submit
  • No maintenance or coming-soon mode
  • robots.txt has no Disallow: / for *, Googlebot or Mediapartners-Google
  • ads.txt (if used) is at the root, served as plain text, with your pub- line
  • "Hello world!", "Sample Page" and the sample comment are gone
  • The privacy policy is rewritten, published and linked (check it)
  • Thin tag, date, author and attachment pages are merged, redirected or noindexed
  • Comments are moderated

Scan your WordPress site

The free Approvalens scan crawls your site from the home page and flags WordPress leftovers, blocked crawlers, noindex tags and thin archives. Run it after you've worked through the list above, so the report shows what's really left.

FAQ

Is Site Kit required to get AdSense on WordPress?

No. It's a convenient official plugin, but any method that puts the code in <head>, or the meta tag, works for verification.

Should I install an ad-placement plugin before approval?

You only need the verification code before approval. Placement plugins become useful once your site is marked Ready.

My theme has a demo homepage. Is that a problem?

Yes, if demo text, "Lorem ipsum" sections or fake testimonials are still visible. AdSense says not to apply while a site "only consists of a site template" (not approved).

Can I keep my tag pages?

Yes, if they're useful (several posts each) or set to noindex. Hundreds of one-post tag pages add nothing for readers.

Does WordPress.com's free plan work with AdSense?

No. You can't add header code on the free plan. Paid plans from Personal upward can, through a plugin.

Spotted something out of date or wrong? Tell us and we'll correct it.

Read this guide in Turkish →

Check it on your own site. Free, no sign-up.

Free tools for this

Free scan

Check your own site

The free scan reads your first 50 pages and checks them for AdSense code and meta tag, Homepage is indexable, and Googlebot allowed in robots.txt, along with everything else in the report.

First 50 pages free · no sign-up · no card