Schedule
Choose daily, weekly, every-15-days or monthly audits, or a custom frequency.
Product · Monitoring
Did the site change? You see it in the next audit
An updated plugin, a new Ad Inserter block or a series of posts published in a rush can bring back a problem that was already fixed. Monitoring repeats the audit at the pace you choose and alerts you when something new appears.
- ✓Daily, weekly, every 15 days, monthly or custom
- ✓Bell and email notification
- ✓Comparison between audits
5frequency options: daily, weekly, every 15 days, monthly or custom
2ways to be notified: the dashboard bell and email
3severity levels to separate the urgent from what can wait
0changes made to the site: every scheduled audit is read-only
Why monitor
A site with ads never stands still
Fixing everything once is a great start, but the site keeps changing. Plugins update on their own, the theme changes the layout on mobile, someone on the team creates a new block in Ad Inserter or publishes a series of short posts.
Each of these changes can bring back a banner stuck to the menu, high density or a consent message in the wrong place. Without follow-up, you only find out when a policy warning arrives or when revenue drops.
Monitoring repeats the full audit at the pace you choose and compares it with the previous one. When a new problem appears, you get a notification, and the comparison shows what was resolved and what stays the same.
How it works
Four parts of monitoring
Everything is in the same dashboard where the reports are.
History
All audits are saved. You can go back and see how the site looked on any date.
Comparison
Two audits side by side show what appeared, what was resolved and what stays the same.
Alerts
The dashboard bell tells you when an audit finishes or when a new problem appears, and the notification also arrives by email.
Configure
How to set up monitoring in 4 steps
- Run a full auditIt becomes the baseline. Fix what is critical and serious before you start tracking.
- Choose the frequencySites that publish every day or change ads often need a faster pace. Stable sites can go from weekly to monthly.
- Turn on notificationsCheck that the notification email reaches the right person, whether you, someone on the team or the client.
- Compare after every changeChanged the theme, Ad Inserter or the CMP? Compare the next audit with the previous one to see the effect.
One-off or continuous
Audit now and then, or monitoring
Both read the site the same way. The difference is the time between a problem appearing and you knowing about it.
One-off audit
You run it when you remember or when something goes wrong.
- Good before asking for approval or review
- Good for purchase due diligence
- A problem can stay live for weeks without anyone seeing it
- No recent baseline to compare against
Monitoring
The audit runs on its own at the chosen frequency and tells you what changed.
- A new problem shows up on the bell and by email
- History ready for comparison
- Shows whether a fix is still holding
- Needs a frequency thought out for each site
What comes back
Problems that tend to reappear
These are the cases where monitoring usually makes a difference.
Theme update
The spacing changes on mobile and the banner touches the menu again.
New block in Ad Inserter
A new position adds ads on short posts and density goes over the limit.
CMP switch
The new tool comes with the region set to the whole world and the European message appears in Brazil.
New subdomain
Someone creates a subdomain for a test or a campaign and it stays live afterward.
Best practices
How to get the most from monitoring
Monitoring works best when it becomes part of the team's routine, not just an alarm.
Allowed
- Open the comparison whenever you change the theme, the CMP or Ad Inserter
- Handle what arrives as critical or serious first
- Mark tasks as done as the team fixes them
- Adjust the frequency when the publishing pace changes
- Keep the history to show progress to the client or partner
Not allowed
- Ignore the bell notification because the last audit was clean
- Leave the notification email going to a mailbox nobody reads
- Change several parts of the site at once without comparing afterward
- Wait for a revenue drop before looking at the report
- Schedule all sites at the same frequency without thinking about each one's pace
In practice
A plugin update at three in the morning
Before
A job portal had passed the audit clean. Two weeks later, an automatic plugin update changed the position of an ad block.
After
The weekly audit found the banner stuck to the next-page button on every post in the series and sent a notification on the bell and by email.
The comparison with the previous audit showed exactly what had changed and since when. The team fixed the block the same day, before any warning from Google.
In ConsentMode
What you see in each scheduled audit
- The full audit, with all URLs, subdomains and both screen widths
- What is new since the last audit, separated from what was already known
- Findings by severity, with the same screenshot, explanation and fix path
- Tasks per URL that the team marks as done as they fix them
- Automatic resume if the audit is interrupted by a restart or a network drop
Frequently asked questions
Which frequency should I choose?
It depends on how much the site changes. People who publish every day or change ads often usually choose daily or weekly. Stable sites can go between every 15 days and monthly.
Do scheduled audits change anything on the site?
No. Each one is read-only, with ad requests blocked and nothing clicked.
Who gets the notifications?
Notifications appear on the dashboard bell and arrive by email. In client workspaces, the team with access to the workspace follows the same history.
Can I compare two old audits?
Yes. The history keeps all audits, and the comparison shows what changed between them.
Let the audit keep watch for you
Choose the frequency and get notified when a new problem appears.