Brand Protection

作者 kostja948dd89c57395e無授權條款1K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫2 天前更新

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.

AI 產生的概覽

指導發現、蒐證、檢舉與預防品牌冒充、釣魚網站及商標侵權。

功能
此技能提供一套結構化流程,用於處理品牌冒充,例如假網站、釣魚網站、商標濫用與網域搶註。內容涵蓋初步評估、證據蒐集清單、依優先順序排列的檢舉管道、法律選項、預防措施、流量回復與監控。產出包括證據包、檢舉範本、行動時程表與預防建議。
適用情境
當品牌遭遇冒充、假網站或釣魚網站、商標侵權、網域搶註或品牌濫用時使用。此技能著重於被動處置與檢舉工作;持續監控由另一個技能負責。
執行需求
除代理程式外不需要指令碼或特殊工具。部分步驟涉及外部服務與查詢,例如 WHOIS 與主機偵測,以及註冊商濫用表單、Google Safe Browsing 和 DMCA 通知等檢舉管道。

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

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

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 [email protected]Trademark 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

來源與署名

來源:kostja94/marketing-skills位於skills/strategies/brand/brand-protection提交8dd89c5

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架