From arb
Sets up automated monitoring for AdSense compliance post-approval, configuring rules, alert thresholds, and workflows to detect content policy violations, performance issues, and ad code problems.
npx claudepluginhub huifer/adsense-readiness-benchmark --plugin arbThis skill uses the workspace's default tool permissions.
Establish ongoing monitoring system for post-approval compliance. Detects violations early and triggers remediation workflows before Google enforcement action.
Suggests manual /compact at logical task boundaries in long Claude Code sessions and multi-phase tasks to avoid arbitrary auto-compaction losses.
Share bugs, ideas, or general feedback.
Establish ongoing monitoring system for post-approval compliance. Detects violations early and triggers remediation workflows before Google enforcement action.
Post-approval continuous monitoring layer. Re-runs audit skills on a schedule.
| Field | Value |
|---|---|
| Phase | Post-approval monitoring |
| Recommended scope | Core 79 + Profile for regular checks; Full 105 for quarterly deep scans |
| Monitored pillars | All 6 (CI, PC, TH, UX, TD, SI) |
| Score mode | Declared per run; stored in monitoring log alongside timestamp |
Each monitoring run should record:
score_mode used for that runtriggered_items: ARB item IDs that flagged violationsseverity: Critical / High / Medium / LowMaintain compliance after AdSense approval:
1. Content Policy Monitoring
Monitor for prohibited content:
Keywords to flag (daily scan):
- Health misinformation: "cures cancer", "anti-vaccine"
- Adult content: [explicit terms]
- Illegal: "credit card numbers", "buy drugs"
- Hateful: [slurs and threats]
2. Configuration
Create .monitoring/config.json:
{
"monitors": [
{
"name": "Policy Violations",
"frequency": "daily",
"severity": "critical",
"alert_to": ["admin@example.com"],
"threshold": 1
},
{
"name": "Performance Issues",
"frequency": "weekly",
"severity": "high",
"alert_to": ["admin@example.com"],
"threshold": 5
}
]
}
3. Alert Channels
Setup notifications:
Monitor:
Implementation:
# Daily content quality check
00 06 * * * /usr/local/bin/quality-monitor.sh > /tmp/quality.log
Monitor:
Implementation:
// Check ad code health
window.addEventListener('load', function() {
if (!window.adsbygoogle) {
console.error('AdSense code not loaded');
alert_monitoring_system({
issue: 'Ad code missing',
severity: 'critical'
});
}
});
Monitor:
# Compliance Monitoring Checklist
## Daily (Automated)
- [ ] Scan new content for policy violations
- [ ] Check ad code errors
- [ ] Monitor server uptime
- [ ] Review analytics anomalies
## Weekly (Manual Review)
- [ ] Review flagged content
- [ ] Check click-through rates
- [ ] Verify affiliate disclosures still present
- [ ] Test page load speeds (5 random pages)
## Monthly (Full Audit)
- [ ] Content quality review (sample 20 pages)
- [ ] Affiliate disclosure audit
- [ ] Ad placement verification
- [ ] Performance metrics review
- [ ] Policy compliance spot-check
## Quarterly (Full Reassessment)
- [ ] Re-run ads-readiness-assessment
- [ ] Compare to baseline scores
- [ ] Identify improvement areas
- [ ] Update monitoring thresholds
IF policy violation detected
THEN email + Slack + block publication
IF ad code broken
THEN email + SMS
IF revenue drops >30%
THEN email + investigation flag
IF new content has thin pages
THEN email alert
IF duplicate content detected
THEN email alert
IF site goes down for >5 minutes
THEN email + SMS
Related Skills:
health-check-automationalert-rules-setup