Migrating your WordPress site does not have to affect Google AdSense, because AdSense is tied to your domain and your traffic, not to WordPress. If you keep the same domain, your AdSense account and its approval carry over untouched, and nothing needs re-approving. What actually stops ad revenue is losing two things in a careless move: the ad code and ad units that were placed in your pages, and the traffic those pages earn. So the rebuild has to re-add your AdSense code, recreate your ad placements, and keep your ads.txt file at the domain root, while the migration preserves your URLs and rankings so the traffic that monetizes keeps arriving. Handled that way, ads reappear on the new site and revenue holds. WPBuildAI rebuilds the site with your ad units and ads.txt in place and maps every URL to a verified 301, so your traffic and your ad income continue.

Revenue tracks impressions, and impressions are being reshaped by AI results rather than only by your migration: Seer Interactive measured AI Overview click-through bottoming at 1.3 percent in December 2025 before recovering to 2.4 percent by February 2026, against roughly 3.3 percent where no AI Overview appears.

AdSense follows the domain, not WordPress

The thing to understand first is what AdSense is attached to. Your account and its approval are granted for a domain, and the ads are served by a snippet of code that sits in your pages. WordPress is only the software that happened to hold that code; it is not what AdSense recognizes. So when you move the same domain to a new platform, AdSense sees the same domain and treats it as the same publisher. There is nothing to re-approve and no history to rebuild, provided the domain stays the same. That reframes the worry: the platform change is not what puts your account at risk, and the real work is making sure the code and the traffic come across with you.

What actually stops ad revenue in a migration

Revenue falls in a migration for one of two concrete reasons, and both are avoidable. The first is that the new build simply does not contain the ad code and units, so there is nothing to serve; the pages look fine but earn nothing because the placements were never recreated. The second is that the migration loses traffic, by breaking URLs, dropping redirects, or shedding rankings, so even correctly placed ads have fewer people to show to. Ad income is roughly traffic multiplied by how well each visit monetizes, which means protecting your rankings is protecting your revenue. This is the same discipline as any migration that keeps its SEO, applied to the pages that happen to carry ads.

Re-adding your ad code and ad units

On the new site you place your AdSense code again and recreate each ad unit where it belonged. If you used Auto ads, you add the single Auto ads snippet to the site so Google can place ads automatically. If you used manual units, you recreate each unit in the same regions of the layout so the page earns the way it did before. A clean rebuild makes this easier than it sounds, because the layout is being reconstructed deliberately rather than inherited from a plugin, so the ad slots go exactly where you want them. Verify that ads actually render on a few live pages after launch, since a placement that exists in the editor but not on the served page earns nothing.

Two files matter as much as the ad code. Your ads.txt file, which authorizes Google to sell your inventory, must be served at the domain root, at yourdomain.com/ads.txt, on the new platform; if it stops resolving, Google can limit how your inventory is monetized. And if you have visitors in the EEA or UK, Google requires a certified consent management platform, so the consent banner has to be reconfigured on the new site rather than left behind with the old theme. Keep your placements inside Google’s policies too, since crowding a page with ads can hurt both the page experience and, in Google’s own guidance, your standing. None of this is hard, but each piece has to be deliberately brought across, because none of it travels automatically when the platform changes.

Preserve the URLs so the traffic that pays keeps arriving

The largest lever on ad revenue is the traffic, and traffic depends on keeping your addresses and rankings intact. Keep every URL the same where you can, and map any that must change to a verified 301 redirect, so the pages search has indexed and that visitors have bookmarked still resolve. Traffic concentrates on a minority of pages, as the Ahrefs study shows, so identify your highest-earning pages and make certain those URLs and their redirects are correct first. The platform itself is not a ranking factor, so a faithful rebuild at the same URLs keeps the rankings, and keeping the rankings keeps the impressions your ads are counted on, exactly as a careful site move intends.

Steps to protect AdSense through a migration

  1. Keep the same domain so your AdSense account and approval carry over with nothing to re-approve.
  2. Re-add the AdSense code and recreate every ad unit, or the Auto ads snippet, in the new build.
  3. Serve ads.txt at the root so your inventory stays authorized on the new platform.
  4. Reconfigure consent with a certified CMP for EEA and UK visitors.
  5. Keep URLs the same and 301 any that change, prioritizing your highest-earning pages.
  6. Verify ads render on live pages after launch, not just in the editor.

Worked example: a content site that kept earning

Consider a recipe site that ran Auto ads and a few manual units on its top posts, and that wanted off a slow, plugin-heavy WordPress install. Before launch, the rebuild recreated the ad placements, added the Auto ads snippet, and carried the ads.txt file and the consent banner across, all on the same domain. Every URL was mapped to a verified 301, with the ten highest-earning posts checked by hand. At launch, AdSense saw the same domain, so nothing needed re-approving; ads rendered on the new pages immediately, and because the rankings and URLs held, the traffic and therefore the revenue continued through the switch. The only visible change was a faster site, which helped rather than hurt the ads that now loaded in view.

Limitation: policy and account issues are separate from migration

It is honest to bound this. A clean migration protects the account and the revenue you already have, but it cannot fix an underlying AdSense problem: if your account carries a policy issue, a serving limit, or a pending review, moving platforms does not clear it, because those attach to the account and the domain, not to the software. Likewise, moving to a brand new domain is a bigger step, since you add the new site in AdSense and, as with any domain change, you should expect a settling period while search re-associates the content. So treat the migration as preserving what you have earned, and handle any account or policy matter through AdSense directly, in parallel.

Common mistakes

  • Rebuilding the site but forgetting to re-add the ad code, so pages load with no ads.
  • Letting ads.txt stop resolving at the domain root, which can limit monetization.
  • Leaving the consent banner behind, so EEA and UK traffic is served without a certified CMP.
  • Changing URLs without 301s and losing the traffic the ads depend on.
  • Checking ads only in the editor and never confirming they render on live pages.

Key points

Migrating will not affect your Google AdSense as long as you keep the same domain and carry the right pieces across, because AdSense is tied to your domain and your traffic, not to WordPress. Your account and approval carry over with nothing to re-approve; what you must do is re-add the ad code and units, keep ads.txt at the root, reconfigure consent for EEA and UK visitors, and above all preserve your URLs and rankings so the traffic that monetizes keeps arriving. Revenue equals traffic times how each visit earns, so the URL and redirect work is the real protection for your ad income. Account or policy problems are separate matters to handle with AdSense directly. WPBuildAI rebuilds the site with your ad units and ads.txt in place and maps every URL to a verified 301, so your traffic and your ad income continue. Send your web address for a free analysis.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.