本文へ移動
cccskills
無料GitHub で公開

brand-protection

When the user faces brand impersonation, fake websites, phishing sites, or trademark infringement. Also use when the user mentions "fake site," "impersonation," "phishing site," "trademark infringement," "domain squatting," or "brand abuse." For monitoring, use brand-monitoring.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seoスター 25(GitHub 25 + cccskills 0)
連携ツールGoogle AdsCloudflare

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md9.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Strategy: Brand Protection

Guides discovery, reporting, and prevention of brand impersonation—fake websites, phishing sites, trademark infringement, and domain squatting. See domain-selection for defensive domain registration; trust-badges for official site verification signals; about-page for identity declaration.

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 it for brand name, official domain, and key assets.

Identify:

  1. Impersonation type: Fake website, phishing, trademark misuse, domain squatting
  2. Evidence available: Screenshots, URLs, WHOIS, hosting info
  3. Legal assets: Registered trademark, copyright ownership
  4. Impact: Traffic interception (fake site ranks for brand queries)? Payment fraud (users pay on fake site, then contact official support)?

Evidence Collection Checklist

ItemAction
Full URLsDocument all key pages of the fake site
ScreenshotsHomepage, product pages, logo, layout; include date/time
ComparisonSide-by-side: official vs fake (layout, logo, copy similarity)
WHOISUse ICANN Lookup for registrar, creation date, registrant
HostingIP lookup to identify hosting provider

Reporting Channels (Priority Order)

ChannelEntryUse Case
Domain registrarAbuse / Report Misuse on registrar siteBrand impersonation, trademark, fraud
Hosting providerSame; submit abuse formHosting infringing content
Google Safe BrowsingReport PhishingPhishing / impersonation risk
Google TrademarkTrademark Complaint or trademark@google.comTrademark infringement in search; requires registered trademark
Bing Content RemovalContent Moderation PlatformCopyright/trademark; content removal from Bing
Payment processorsPayPal Resolution Center, Stripe supportIf fake site accepts payments; report fraud
Social platformsX, Facebook, Instagram abuse formsIf fake site is promoted or linked there
Google Ads / Microsoft AdsPlatform trademark complaint formsIf impersonator runs brand ads
DMCATo hosting providerCopyright infringement; images, copy, design copied
ICANNDNS Abuse complaintIf registrar does not respond within reasonable time

Report content: Include full URL, clear description of fraudulent activity, and all evidence (screenshots, logs).

Reporting Best Practices

Registrar vs hosting: Use ICANN Lookup for registrar. For hosting, use IP lookup (HostingCheckerOnline, HostingDetector, ipinfo.io) to find origin server—registrar may be Cloudflare while origin host is elsewhere; report to both.

Cloudflare as registrar: Use abuse.cloudflare.com or abuse form; select "Phishing & Malware" for impersonation. Email complaints are generally not processed; use the online form. Provide specific URLs of infringing pages.

Hosting detection: Sites behind Cloudflare CDN hide origin IP. Use reverse IP lookup or hosting detection tools to identify underlying host; submit abuse to that provider as well.

Parallel reporting: Submit to registrar, host, and Google Safe Browsing simultaneously; do not wait for one before others. Google trademark review takes 1–8 weeks.

Legal Options

OptionWhenNotes
Cease and desistTrademark infringementLawyer-drafted; often first step
DMCA takedownCopyrighted material copiedImages, copy, design; hosting providers typically comply
Consumer protectionScam / fraudFTC ReportFraud.ftc.gov (US)
Law enforcementFinancial loss, identity theftIC3 (FBI) for cybercrime

Prevention Measures

Defensive Registration

  • Register brand+ai, brand+app, brand+official, etc. See domain-selection for defensive registration.
  • Redirect variants to main domain; do not deploy separate sites.

Official Site Verification

Place "Official website: [domain]" prominently:

  • Homepage (above fold or hero)
  • Sign-in / Sign-up pages
  • Pricing / Payment pages: "Only pay at [official-domain]. Do not enter payment on other domains."
  • Footer: "© [Brand]. Official site: [domain]"
  • FAQ: "How do I verify I'm on the official site?" → "The only official URL is [domain]. Any other domain is not affiliated."

Use trust-badges for verification signals. See about-page for identity declaration.

Customer Support (Payment Fraud)

When users report "can't use after payment" but no record exists—likely paid on fake site:

  1. Verify source: Ask which URL they used (request screenshot or URL).
  2. Response template: Explain that the only official site is [official-domain]; if they paid elsewhere, that site is not affiliated. Recommend: (a) dispute charge with payment provider, (b) use only [official-domain] going forward.
  3. Roll out template to support team; ensure consistent messaging.

User Education

  • Social media pinned post / announcement: "Only use [official-domain]"
  • Email signatures, support replies: link to official domain only

Traffic Recovery (When Impersonation Intercepts Search)

TacticPurpose
Brand search adsRun Google Ads and Microsoft Ads on brand terms; ensure official site appears first for brand queries
SEOStrengthen official site for branded queries; Organization schema, clear H1, meta tags. See schema-markup, title-tag
SocialPinned post: "Only use [official-domain]. Beware of impersonation."

Monitoring (Ongoing)

  • Periodic search: brand name + common variants (e.g., brand+ai, brand+app)
  • See brand-monitoring for monitoring setup, tool selection, and cadence

Timeline (Typical)

PhaseFocus
Immediate (Days 1–3)Support template; site declaration; evidence collection
Short-term (Week 1–2)Abuse reports; Google Safe Browsing; DMCA if applicable
Traffic (Week 2+)Brand ads; SEO; social announcement
OngoingMonitoring; defensive registration if feasible

Implementation Checklist

Short-term (1–2 weeks): Evidence collection; abuse reports to registrar and host; Google Safe Browsing report; DMCA if applicable; add "Official website" on site.

Medium-term: Add impersonation guidance to domain-selection; official verification to trust-badges, about-page.

Long-term: Periodic search (brand + variants); brand monitoring (BrandShield, Doppel); defensive registration of variants.

Output Format

  • Evidence package (checklist, evidence list)
  • Report templates (registrar, hosting, Google)
  • Timeline (immediate vs medium vs long-term actions)
  • Prevention (defensive registration, site verification, user education)

References

Related Skills

  • domain-selection: Defensive domain registration; brand variants
  • rebranding-strategy: When rebranding, sync brand protection checks
  • brand-monitoring: Proactive monitoring setup; tool selection; this skill = reactive takedown
  • branding: Brand asset protection; consistency
  • trust-badges: Official site verification signals
  • about-page: Official identity and domain declaration
  • homepage-generator: "Official website" placement
  • google-ads, paid-ads-strategy: Brand search ads for traffic recovery
  • schema-markup, title-tag: SEO for branded queries

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.

日本語の概要は準備中です。原文の説明を表示しています。

dalroot/agentic-seo252026年10月20日 更新

dalroot のスキルをすべて見る

このスキルの問題を報告する