huifer/adsense-readiness-benchmark · Archived

geo-localization-compliance

Audit regional compliance requirements for publisher monetization across privacy law, disclosure expectations, language coverage, and restricted verticals.

First seen Jul 16, 2026

Installation

$ npx skills add huifer/adsense-readiness-benchmark --skill geo-localization-compliance

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from huifer/adsense-readiness-benchmark · top by installs.

npx skills add huifer/adsense-readiness-benchmark

Browse all from huifer/adsense-readiness-benchmark

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,737 B
  • docs SUMMARY.md 190 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Geo Localization Compliance

Assess whether a site is ready to monetize across multiple jurisdictions with differing privacy, disclosure, consent, and restricted-content requirements.

Quick Start

Input: Website URL, target countries, languages, consent setup, site type Output: Regional compliance matrix + localization gap list + priority fixes Time: 20-40 minutes

Regions Covered

  • European Union / EEA
  • United States (state-level privacy emphasis)
  • United Kingdom
  • India
  • Brazil
  • Southeast Asia
  • Other markets as applicable

Review Areas

  1. Privacy policy localization
  2. Cookie consent and CMP implementation
  3. Data rights disclosures
  4. Language coverage and consistency
  5. Region-specific restricted categories
  6. Legal pages for commerce or subscriptions where applicable

Output Contract

Return:

  • regions_reviewed
  • compliancestatusby_region
  • missing_requirements
  • highrisklocales
  • priority_fixes
  • relatedarbitems

Typical Risk Signals

  • English-only legal pages on multi-language sites
  • No consent mechanism for EEA traffic
  • Weak disclosures for affiliate or sponsored content in localized pages
  • Different language versions with inconsistent policies
  • Region-specific restricted products promoted without controls

Routing

  • If trust/legal pages are incomplete → trust-credibility-strategy
  • If affiliate disclosures vary by locale → affiliate-link-compliance
  • If the site spans premium networks → multi-network-readiness