Policy history
Ask for screenshots of the Policy center in the seller's account and ask about old warnings that were already resolved.
Use case · Buying and selling sites
A site with ads carries a history: policy warnings, condemned formats, forgotten subdomains and traffic sources that do not always show up in the sale listing. This guide shows what to check before closing the deal, from both sides of the table.
Why check
Whoever buys a monetized site buys content, traffic and a reputation with Google's systems. The Ad Experience Report, for example, is tied to the site in Search Console and counts repeated failures over the last 365 days.
On the other side, whoever sells gains trust by showing a site in order. An audit report with screenshots and completed tasks answers at once many of the questions the buyer would ask.
Remember that the publisher is always responsible for the traffic and content where their ad code appears. From the day the buyer's code goes on the site, whatever is there becomes their problem.
What to look at
Each one can change the price or the plan after the purchase.
Ask for screenshots of the Policy center in the seller's account and ask about old warnings that were already resolved.
Ask for access to Search Console and check the mobile and desktop status and the history of changes.
Look for old, test or abandoned subdomains. Some end up showing spam or another site's content.
Check where the visits come from. Purchased traffic needs to be explained, with channels and landing pages.
Read random posts, not just the most visited ones. Look for short, repeated or unreviewed translated texts.
Check who is authorized to sell the inventory and which ad codes are on the site today.
Checklist
Common errors
All of these cases show up after the purchase, when it is too late to renegotiate.
The showcase posts are fine. The problem is usually in the hundreds of old pages nobody opens.
A forgotten subdomain can show sexual content, spam or serve another site, and it is still tied to the domain you bought.
High revenue from low-quality purchased traffic may not last when the source changes or is paused.
Lines for the seller's networks that stay in the file authorize other companies to sell the inventory.
Changing the theme, code and ads.txt all at once makes it hard to tell later what caused a drop.
Without a dated report of the site's state at purchase, it is hard to prove what already existed beforehand.
On both sides
The same audit serves both, with different goals.
Wants to know what they are getting and how much it costs to fix.
Wants to show the site is in order and speed up the sale.
In ConsentMode
No. The audit reads the site as a visitor, without logging in. For the account side, such as the Policy center, ask the seller for screenshots.
AdSense says it can take a few days and, on sites with few ad requests, up to a month. There is a button to request a new check on the Sites page.
It lists sites with a violation that made ad requests in the last 7 to 10 days. Old warnings that were already resolved may not appear, so it is worth asking.
They can show the audit report and, if they want, publish a public profile for the domain, which anyone can check on the Check badge page. Audits stay private if they are not published.
No. It shows risks and fixes. The value of the deal is for the buyer and the seller to decide.
Library
This guide was written from these official pages. Read them directly at the source:
The audit reads the whole site and its subdomains like a visitor and delivers a dated report for the negotiation.