Changing Your Site URL in AdSense After Approval

Your AdSense account can stay approved while earnings flatline—because the public URL moved and the program still thinks in terms of site objects, verification, and root-domain seller files. A theme swap on the same hostname is annoying; a new domain, HTTPS host change, or platform migration is a different checklist.

Cluster owners: Add a new site after approval, Connected sites vs account status, Host vs subdomain when adding a site, and ads.txt authorized meaning.

Pick one public host → redirect everything else → add the new domain on Sites → verify → fix ads.txt on the new root → wait for Ready before you treat ads as supposed to work.

Disclosure: Educational overview of AdSense site management after a URL change. We do not guarantee review speed, approval, or earnings. Confirm steps in official Google AdSense Help—UI labels change. CashPilot may earn from some links at no extra cost to you.

Table of contents

1. Why a URL change breaks the old setup
2. Redirects before you touch AdSense
3. Add and verify the new site
4. ads.txt must match the crawled host
5. Account vs site status during a move
6. Mistakes that extend downtime
7. FAQ
8. Ship the new hostname cleanly

Why a URL change breaks the old setup

AdSense separates publisher account approval from each connected site. Google's site management Help is clear: you add a site to the Sites list if you want site-related actions on that domain, verify ownership, then request review so the site can reach a status that allows serving.

So when oldblog.com earned and you relaunch on newblog.com, the account badge can still say approved while the new hostname is missing, unverified, or stuck at Requires review. That is normal layering—not proof the account was "closed."

If you need the mental model first, read connected sites vs account status before you debug ad code on the new theme.

Redirects before you touch AdSense

Search engines and AdSense both prefer one canonical host. Before you add the new domain on Sites:

1. Decide apex vs www (or the single host your SEO stack uses).
2. Publish 301 redirects from every old URL pattern to the matching page on the new host.
3. Update internal links, sitemap entries, and Search Console property strategy if you use it.
4. Confirm HTTPS works on the chosen host without redirect loops.

Hostname typing rules when you add the site belong with host vs subdomain when adding a site—enter the domain AdSense accepts, not a path or query string.

If I were migrating a small blog, I would test one old post URL in a private window and watch it land on exactly one HTTPS destination before I request AdSense review on the new name.

Add and verify the new site

Official sequence (confirm live Help):

1. Sign in → Sites → add the new site URL → save. Help: Add a new site to your AdSense sites list.
2. Choose a verification method AdSense offers—common paths include the AdSense code snippet, ads.txt line, or meta tag. Help: Connect your site to AdSense.
3. Publish the verification asset on the new host and click verify.
4. Request review when prompted and watch status move toward Ready. Help: AdSense site management and Check the status of your AdSense sites.

Google's Help notes checks often take a few days and can take two to four weeks in some cases—treat that as a range, not a promise.

The deep click-path for site two lives on add a new site after approval. This migration page assumes you already understand why a fresh Sites row exists.

ads.txt must match the crawled host

ads.txt is a root-domain seller declaration—not a plugin setting buried under /blog/. After a domain move, buyers look at https://yournewdomain.com/ads.txt.

Minimum hygiene:

• File returns plain text at the site root
• Includes the google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0 line Google documents (verify the live Help example)
• Hostname in AdSense Sites matches the domain serving the file

Status words—Authorized, Not found, Unauthorized—are their own topic on ads.txt for AdSense what authorized means. During migration, fetch the new URL yourself before you blame "AdSense lag."

ads.txt can also be a verification path when adding a site—do not delete the old file until redirects and the new file both make sense for your cutover plan.

Account vs site status during a move

Blank ads on the new domain usually mean the site row or seller file is stuck—not that Google "removed" your account. Fix the layer that is red before you reinstall plugins.

Mistakes that extend downtime

Adding the wrong hostname string. Paths, tracking parameters, or disallowed subdomain patterns waste a review cycle—see the host guide first.

Removing and re-adding the new site every day. Help warns that churn delays review. Stabilize redirects and verification, then wait.

Leaving ads.txt on the old domain only. Redirects do not replace a root seller file on the new property.

Serving ad code only on URLs that still 404. Migration QA belongs in your CMS checklist, not only in AdSense.

Assuming Ready on site A auto-Ready site B. Each domain earns its own Sites status.

FAQ

Do I need a new AdSense account when I change domains?

Usually no—add and verify the new site on your existing account.

Should I edit the old site URL in AdSense to the new one?

Follow add-site and verification Help; treat it as a new site object plus redirects.

How long until the new site shows Ready?

Help cites a few days up to two to four weeks in some cases—watch Sites status.

What happens to ads.txt after a domain change?

Publish a correct root file on the new domain Google crawls.

Can I remove the old site immediately?

Avoid remove/resubmit cycles that delay review; keep redirects stable.

Is this the same as adding a second blog?

Mechanics overlap; this page focuses on migration and hostname alignment.

Will 301 redirects carry ad code automatically?

Redirects help users; you still need Sites verification and Ready on the new host.

Where is official Help for site moves?

Add a new site · Site management · Connect your site · Check site status.

Ship the new hostname cleanly

A domain move is three jobs at once: public redirects, a verified Sites row on the new hostname, and ads.txt on the root buyers fetch. Account approval got you into the program; the new URL still has to earn its own Ready badge.