The most reliable way to connect a WordPress site to Google AdSense is Google’s free, open-source Site Kit plugin. In WordPress, install and activate Site Kit, complete Start Setup, connect the AdSense service, and authorize Site Kit to place the AdSense code across your site. Then add the site in AdSense, complete verification, enable Auto ads if you want automatic placements, and wait until the site reaches Ready status. Code installation alone does not approve a site or make ads appear.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
A manual route is also possible: copy the code generated in your own AdSense account and place it between the page’s <head> and </head> tags on the pages where ads should run. The same approval, crawler-access, policy, and verification requirements still apply.
What you need before adding AdSense
AdSense checks the site, not just the code. Prepare the WordPress installation and the AdSense account before beginning so that verification is not blocked by a private or unfinished website.
Free tools Windows power users keep installed
One-click scans. No signup required.
A live, crawlable WordPress site
- The site must be publicly reachable on the domain you submit.
- Google’s ads crawler must be able to load the pages. A login wall, maintenance mode, an incorrect domain, or a crawler block can prevent verification.
- Publish enough original, useful content for a policy review. A nearly empty installation gives reviewers little to evaluate.
- Check that the site follows the AdSense Program policies before requesting review.
Access to the site’s HTML
You need administrator-level access to WordPress or another supported way to add code in the document head. If a developer or host manages the theme, arrange access before starting. The AdSense verification methods place different requirements on the site:
- AdSense code snippet: inserted in the page head.
- Meta tag: inserted in the page head.
- ads.txt: a text file published at the site root, normally reachable at
https://your-domain.example/ads.txt.
Use the exact method and values AdSense presents for your account. Do not copy a publisher ID from an example or another website.
Identity and account checks
Google says that, starting in June 2026, identity verification may be required before an account can show ads and receive payments. Whether it applies depends on your location and account. Where an automated check is offered, Google says most identity checks take 5–10 minutes; a manual review can take 2–3 business days. Those are estimates, not guaranteed service times, so complete any requested verification before diagnosing an ad-delivery problem.
Recommended method: connect WordPress with Site Kit
Google highly recommends Site Kit for WordPress. It is free and open source, and it can place the AdSense code across the site without requiring you to edit theme files. Site Kit can also place the appropriate code on AMP and non-AMP versions of a site. The plugin connects the site to AdSense; it does not change AdSense account settings such as Auto ads.
1. Install Site Kit
- Sign in to the WordPress dashboard.
- Open Plugins and choose Add New.
- Search for Site Kit by Google.
- Select Install Now, then choose Activate.
- Open the plugin and select Start Setup.
Complete the Google sign-in and authorization screens shown by Site Kit. Use the Google account that has access to the AdSense property you intend to connect. If the wrong account is authorized, stop and reconnect with the account that owns or manages the AdSense account instead of creating a second property.
2. Connect the AdSense service
- In Site Kit, open the service connection area and choose AdSense.
- Authorize the connection when Google asks for permission.
- Allow Site Kit to place the AdSense code across the site if you want the plugin to manage site-wide placement.
- Return to the Site Kit settings and confirm that the AdSense section reports that the code has been placed.
Site Kit’s code placement establishes the technical connection. It does not bypass AdSense’s site review, policy checks, or account verification.
3. Add the site in AdSense
Open AdSense and add the exact public domain used by WordPress. Be precise about the domain: a different subdomain, protocol, or misspelled hostname can leave the submitted site unverified even when the WordPress site is working.
AdSense will offer one or more verification methods. Follow the method shown for your account:
Recommended Free Tools
- For a code snippet, publish the complete snippet in the page head.
- For a meta tag, publish the complete tag in the page head.
- For ads.txt, publish the account-provided line in the root
ads.txtfile.
After publishing the requested verification material, return to AdSense and submit the site for review. Do not remove the verification code while the review is pending.
4. Enable Auto ads, if desired
Site Kit cannot turn Auto ads on or off in your AdSense account. If you want Google to choose automatic ad placements, open the site’s AdSense settings and enable Auto ads there. AdSense offers an optional preview during activation so you can inspect the kinds of placements it may use.
If you prefer to decide exactly where individual ads appear, leave Auto ads disabled and use individual ad units with the corresponding code. Site Kit’s connection does not force you to use automatic placements.
As an Amazon Associate I earn from qualifying purchases.
How AdSense approval works
Code placement is not approval
Installing Site Kit or inserting a snippet only gives Google a way to identify and inspect the site. Google states that ads can be served only after the site passes review and has a Ready status in AdSense. A connected service with a pending or unapproved status will not produce normal ad delivery.
Typical review timing
Google describes the usual review as taking a few days, while some reviews take 2–4 weeks. This is an estimate rather than a service-level guarantee. During that period, keep the site publicly accessible, avoid changing domains, and leave the requested verification material in place.
What to do while the review is pending
- Check that the submitted domain resolves without a login.
- Keep the main content and navigation available to crawlers.
- Confirm that the AdSense code or verification tag is still present in the rendered page source.
- Finish any identity or payment-profile prompts shown in the AdSense account.
- Do not interpret an empty ad space during review as proof that the code is broken.
Manual AdSense code installation
Manual insertion suits publishers who already manage site-wide head scripts themselves or who need a workflow independent of Site Kit. It requires more care because a theme change, caching layer, or duplicate insertion can remove or interfere with the code.
#1 Best Overall
1. Copy the code from your own AdSense account
In AdSense, use the code supplied for the site or ad configuration you are implementing. Publisher IDs and snippets shown in documentation examples are illustrative; only the values generated in your account belong on your site.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall2. Put the code in the document head
Place the complete script between <head> and </head> so it is present on every intended page. Use one site-wide head-insertion method: for example, an established theme or host mechanism, or a plugin designed to insert code globally. Do not add the same AdSense script through the theme, a header plugin, and Site Kit at the same time.
Google recommends placing AdSense code on every page across the site to get the most from AdSense. That recommendation concerns coverage, not permission to duplicate a script. After publishing, open a representative page, view its rendered source, and confirm that the expected code appears once in the head.
3. Complete AdSense verification and review
Manual code does not change the approval process. Add the domain in AdSense, complete the offered verification method, submit the site, and wait for a Ready status before expecting ads to serve.
Using ads.txt correctly
ads.txt is separate from the AdSense code in your page head. It is a plain-text file at the root of the domain that tells buyers which sellers are authorized for your inventory. Google recommends publishing it to help protect inventory from unauthorized sellers.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsCreate or update the file
- In AdSense, copy the exact ads.txt line shown for your account, including the publisher ID.
- Publish that line in a file named
ads.txtat the site root. - Open the root URL in a browser and confirm the file is publicly readable.
- If more than one monetization account legitimately sells inventory for the site, add a separate row for each account as instructed by Google.
A WordPress plugin can create or manage the file, but the plugin is only a delivery mechanism. Verify that it writes the exact account-provided entry and that another plugin or host configuration is not serving a different file.
AMP and non-AMP pages
AMP pages use a different AdSense implementation from standard HTML pages. Regular AdSense code and AMP ad code are not interchangeable. If your WordPress site publishes AMP and non-AMP versions, ensure that each version receives the code appropriate to that format.
Site Kit can place code for both AMP and non-AMP versions when the site is configured for AMP. With a manual setup, follow the AMP implementation requirements for the AMP pages rather than copying the standard head snippet into an AMP template.
Which implementation route should you choose?
| Route | Best fit | Coverage and control | Important limitation |
|---|---|---|---|
| Site Kit by Google | Most WordPress publishers, especially first-time AdSense users | Guided connection and site-wide code placement; supports AMP and non-AMP placement | Does not enable Auto ads or alter other AdSense account settings |
| Manual head insertion | Publishers with an established code-management workflow | Direct control over where the account code is inserted; can cover every page when implemented site-wide | Theme changes, caching, or duplicate scripts must be managed by the publisher |
| Other WordPress plugins | Sites already using a trusted code or ad-management workflow | Some can insert headers, manage ad units, or create ads.txt | They are third-party tools; Google does not endorse or support them, and code must not be altered |
Google mentions tools such as Insert Headers and Footers, Advanced Ads, and Ad Inserter as resources publishers may already use. None is required for AdSense, and choosing one does not remove the need for AdSense review.
Why AdSense ads are not showing
Work through the checks in order. The first goal is to determine whether the problem is approval, configuration, crawlability, or implementation.
Check the site status in AdSense
- Open the AdSense Sites list.
- Confirm the domain you connected is listed exactly as intended.
- Check whether review has completed and the status is Ready.
- If the status is pending, wait for the review window rather than repeatedly replacing the code.
A site that is not Ready cannot serve ads normally, even if its pages contain a valid snippet.
Quick Recap
Check Site Kit or the manual placement
- In Site Kit settings, confirm that the AdSense section says the code has been placed.
- For a manual setup, view the rendered page source and search for the AdSense script in the head.
- Check more than the homepage if ads are meant to run site-wide.
- Remove duplicate site-wide scripts created by overlapping installation methods.
Check Auto ads settings
If you expect automatic placements, confirm that Auto ads is enabled for the site in AdSense. Site Kit cannot change this account-level setting. If Auto ads is off, use the code for manually selected ad units instead of waiting for automatic placements.
Check crawler access and domain accuracy
- Open the site in a private browser window to confirm it does not require a login.
- Check that the submitted domain is the one actually serving the WordPress pages.
- Review security, maintenance, or robots settings that could block Google’s ads crawler.
- Confirm that HTTPS redirects and canonical-domain settings do not send Google to an unrelated hostname.
Check AMP implementation
If only AMP pages fail, inspect the AMP template separately. A standard AdSense snippet on an AMP page will not substitute for the AMP-specific implementation. Conversely, AMP code should not be pasted into ordinary non-AMP pages.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check ads.txt independently
An ads.txt problem is distinct from a missing head script. Open the root ads.txt URL, compare its contents with the exact line supplied in AdSense, and verify that each legitimate monetization account has its own row. Correct the file at the system that actually serves it; a WordPress editor may not control a host-level file.
Preventing common setup mistakes
- Submitting an unfinished site: publish substantial content and working navigation before requesting review.
- Using an example publisher ID: copy the ID and entry generated in your own AdSense account.
- Installing the same script twice: choose Site Kit or one manual site-wide route and inspect the source for duplicates.
- Editing a theme file without a maintenance plan: a theme update can remove manual code; use a persistent site-wide method or recheck after updates.
- Assuming code equals approval: monitor the AdSense status and wait for Ready.
- Expecting immediate ads: review can take a few days or, in some cases, 2–4 weeks.
- Ignoring identity prompts: account verification may be required before ads and payments are available, depending on location and account.
- Putting ads.txt in the wrong place: the file belongs at the domain root, not inside a random WordPress media directory.
- Mixing AMP and standard code: use the implementation designed for each page format.
A practical post-install checklist
- Open the public domain without signing in and confirm the main pages load.
- Verify that the AdSense site list contains the exact domain.
- Confirm the requested code, meta tag, or ads.txt entry is publicly reachable.
- Check Site Kit’s AdSense status or inspect the manual page source.
- Enable Auto ads in AdSense only if automatic placement is wanted.
- Complete identity or account prompts shown by Google.
- Wait for the site to reach Ready.
- After approval, test representative non-AMP and AMP URLs separately if both formats exist.
- Recheck code placement after WordPress, theme, caching, security, or header-management changes.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
