
Disclosure Page Generator
- 758 installs
- 787 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
disclosure-page-generator is a marketing skill that drafts FTC-aligned affiliate and sponsored-content disclosure pages for developers who monetize blogs, docs, or product sites with paid partnerships.
About
disclosure-page-generator is a Claude Code skill from kostja94/marketing-skills that produces compliant affiliate and sponsored-content disclosure pages aligned with FTC guidelines. The skill guides an agent through trust-building copy, placement notes, and page structure so developers can publish monetized content without hand-writing legal boilerplate. Developers reach for disclosure-page-generator when launching affiliate programs, adding sponsorship banners, or auditing existing disclosure pages on marketing sites, documentation portals, or content-heavy SaaS properties. It fits content and SaaS builds where transparency requirements apply before traffic or revenue scales.
- Generates full disclosure pages for affiliate, sponsored, and paid partnership content
- Automatically adapts to US (FTC), EU, and multi-region legal requirements
- Creates standalone pages or footer-linked components with proper headline, summary, and legal details
- Reads project-context.md to understand your specific affiliate or partnership model on first use
- Reduces legal risk while building visitor trust through transparent language
Disclosure Page Generator by the numbers
- 758 all-time installs (skills.sh)
- +6 installs in the week ending Jul 25, 2026 (Skillselion tracking)
- Ranked #612 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill disclosure-page-generatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 758 |
|---|---|
| repo stars | ★ 787 |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
How do you write FTC-compliant affiliate disclosure pages?
Instantly generate compliant, trust-building affiliate and sponsored-content disclosure pages that meet FTC guidelines.
Who is it for?
Developers publishing affiliate links, sponsored posts, or partner content who need a compliant disclosure page without legal drafting from scratch.
Skip if: Developers who only need general privacy policies, cookie banners, or GDPR consent flows unrelated to affiliate monetization.
When should I use this skill?
The user mentions affiliate disclosure, FTC compliance, sponsored content labels, or asks to generate or audit a disclosure page.
What you get
A publish-ready disclosure page with FTC-aligned affiliate and sponsorship language, placement guidance, and trust-building copy blocks.
- Disclosure page copy
- Placement guidance
- Audit notes for existing pages
Files
SEO: Local
Guides local SEO: Google Business Profile, NAP consistency, and citation building. Businesses with accurate NAP across 40+ authoritative sites see ~19% higher visibility in Google Maps. Use this skill when optimizing for local search, setting up GBP, or auditing citations.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 4 (Audience), 5 (Website).
Identify: 1. Business type: Storefront vs service-area 2. Location: Single or multiple 3. Current listings: Existing GBP, directories
NAP Consistency
NAP = Name, Address, Phone. Critical for local rankings.
| Rule | Guideline |
|---|---|
| Exact match | "Street" vs "St." or "LLC" inconsistency = Google may treat as different entities |
| Fix first | Audit and fix inconsistencies before adding new citations |
| Tools | BrightLocal, Whitespark, Moz Local for audit |
Google Business Profile
| Element | Guideline |
|---|---|
| Address | Physical address; no P.O. boxes |
| Description | 750 chars; primary keywords in first 100 |
| Hours | Accurate; seasonal availability |
| Category | Primary category matches business type |
| Service-area | Hide address if no storefront; define service areas |
Citation Building
Targeted precision over submitting to every directory.
Priority order: 1. Google Business Profile 2. Apple Maps 3. Yelp, Bing Places, Facebook 4. Better Business Bureau, Foursquare, Nextdoor 5. Niche directories (Healthgrades, Angi, etc.)
Citation Audit
- Incorrect or outdated data
- Duplicate entries
- Missing listings on key directories
Fix before adding; compounding errors harm rankings.
Output Format
- NAP (exact format for consistency)
- GBP optimization checklist
- Citation priority list
- Audit findings (if applicable)
Related Skills
- geo: GEO for AI search; local + AI overlap
- localization-strategy: Multilingual; local + i18n
- directory-submission: Directory listings; different from local citations
Related skills
How it compares
Pick disclosure-page-generator for FTC affiliate and sponsorship copy; use privacy-policy or cookie-consent skills for GDPR, data collection, or general legal pages.
FAQ
What does disclosure-page-generator produce?
disclosure-page-generator produces FTC-aligned affiliate and sponsored-content disclosure pages with trust-building copy and placement guidance. Developers use the output as a publish-ready page or section before monetized content goes live.
When should developers use disclosure-page-generator?
disclosure-page-generator fits when a site publishes affiliate links, paid partnerships, or sponsored posts and needs transparent disclosure language. The skill targets FTC guideline alignment rather than general privacy or cookie consent.
Is Disclosure Page Generator safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.