Expired Domains and AdSense: Risks to Check Before You Buy

Yes, a site on a previously owned domain can be approved for AdSense; there is no rule against buying a dropped or auctioned name. What Google prohibits is using an expired domain mainly to ride its old reputation with low-value content, and a domain can also carry baggage from its previous life (spam, malware flags, an old ads.txt) that you need to clear first.

What Google actually says about expired domains

The relevant text is in the Search spam policies, which the AdSense Publisher Policies make binding for any page with Google ads (answer/11035931). The expired domain abuse section reads:

"Expired domain abuse is where an expired domain name is purchased and repurposed primarily to manipulate search rankings by hosting content that provides little to no value to users."

Two words carry the weight: primarily and little to no value. Google's own examples include affiliate content on a domain that used to belong to a government agency, commercial medical products on a former non-profit's domain, and casino content on an old school site. Buying oldbakery.com to run a genuine bakery blog is not the target. Buying it to host 300 casino reviews because it has backlinks from local newspapers is.

The AdSense side has no separate "expired domain" rule. A rejection on a reused domain will come back under the familiar labels: low value content, policy violations, or site down.

The four kinds of baggage a used domain can carry

1. A spam or hacked history

If the previous owner ran a pharma spam farm, or the site was hacked and filled with injected pages, those URLs can still be in Google's memory and in backlink profiles. Worse, old URLs sometimes keep receiving traffic and links that point to topics you would never want associated with your new site.

2. Safe Browsing or malware flags

A domain that served malware may still be listed. Ads will not run on screens that "contain malicious software", and a flagged domain shows a red warning in Chrome, which also kills your traffic. Check the Safe Browsing site status before you pay.

3. A leftover ads.txt or ad code

This is the most overlooked problem. If you restore an old site from a backup or a Wayback copy, you may also restore /ads.txt with the previous owner's publisher ID:

google.com, pub-4512987730012345, DIRECT, f08c47fec0942fa0

Google's rule is that ads.txt is optional, but if the file exists it must list you: you must not "place Google-served ads on a domain that uses ads.txt where you are not included as an authorized seller" (answer/11128498). Replace the old line with your own ID, or delete the file until you have one. The ads.txt setup guide shows the exact format.

4. A previous AdSense relationship

People often ask whether a domain that was once "banned" from AdSense can be approved again. Google does not publish a domain blacklist, and there is no official statement that a domain inherits the previous account's status. Community reports go both ways. Treat it as an unknown risk factor rather than a rule, and focus on what you control: the content and policy state of the site as it is today.

How to research a domain's past

Before buying, or right after, spend an hour on this. It is cheap insurance.

Check	Where	What you want to see
Archive history	web.archive.org/web/*/example.com	Same or neutral topic, no casino/pharma/adult phases
Registration events	RDAP lookup (e.g. rdap.org/domain/example.com)	When it was created, when it dropped, when re-registered
Safe Browsing	transparencyreport.google.com/safe-browsing	"No unsafe content found"
Search footprint	site:example.com in Google	No foreign-language spam pages still indexed
Backlinks	Any backlink tool's free tier	Links from real sites, no obvious link-farm anchors
Manual actions	Search Console → Security & Manual actions	Nothing listed after you verify

When reading the Wayback history, look for topic jumps. A domain that was a gardening blog from 2012 to 2021, then a Japanese casino directory in 2023, then dropped, is a domain where someone has already tried the abuse pattern. That does not make it unusable, but you will be starting with cleanup work.

Building on a used domain without triggering the policy

The safe pattern is simple: build a site that would make sense on a brand-new domain.

1. Pick a topic you can actually cover. If it happens to match the old site, good. If it doesn't, that is fine too; what matters is that the new content stands on its own. See niche focus for AdSense.
2. Don't resurrect old content you didn't write. Copying the previous owner's articles from the Wayback Machine is replicated content and, unless you own the rights, a copyright problem.
3. Handle old URLs honestly. If old URLs get traffic, either return 410 Gone or redirect them to a genuinely related new page. Mass-redirecting 2,000 old URLs to your homepage just recreates soft-404 noise.
4. Don't build to the backlinks. Writing a "payday loans" section because the domain has links from a finance forum is exactly the "primarily to manipulate search rankings" pattern.
5. Show who runs the site now. An About page that explains the site is new under new ownership costs nothing and removes ambiguity for reviewers. See about and contact pages.

Old URL handling example

A quick way to retire old paths in nginx:

location ~ ^/(casino|bonus|slots)/ { return 410; }
location = /old-garden-tips/ { return 301 /guides/winter-pruning/; }

Only redirect where the target genuinely answers what the old page was about.

Does domain age from the old registration help?

Probably not in the way people hope. There is no current official minimum domain age for AdSense (see the domain age myth), so an old registration date does not unlock anything. And for Search, Google representatives have said publicly over the years that Search can recognise when a domain changes hands and treat it as a new site. The value of a good used domain is mostly a memorable name and perhaps some type-in traffic, not a shortcut through review.

Before you apply

Run through this short list on a reused domain:

• /ads.txt lists your publisher ID only, or does not exist
• No old ad scripts, analytics IDs or verification meta tags from the previous owner
• Safe Browsing shows no warnings
• site: search shows only your pages
• Old spam URLs return 404 or 410, not 200
• New content is substantial enough for a reviewer to evaluate

The rest of the pre-application work is the same as for any site; our checklist covers it.

Scan before you submit

A free scan checks your ads.txt against your ad code and flags leftover scripts and off-topic sections from a domain's earlier life.

FAQ

Is buying an expired domain against AdSense rules?

No. The spam policy targets repurposing an expired domain primarily to manipulate rankings with low-value content. A real site with original content on a used domain is not that.

The domain had AdSense before. Will my application be rejected automatically?

Google has not published any rule that a domain inherits a previous account's status. Community experiences vary. Clean the site, remove the old publisher ID everywhere and apply with your own content.

Should I restore the old site from the Wayback Machine?

Only content you own the rights to. Republishing someone else's archived articles is copied content and can lead to a low value or policy rejection.

Do I need to wait some months after buying a used domain?

There is no official waiting period. Apply when the site has enough original content to evaluate and the history checks above come back clean.