Skip to content

Feature Request: Add Name-Quality Checker for Plugin Trademarks & Confusing Similarity #1124

@davidperezgar

Description

@davidperezgar

I would like to propose a new feature for the Plugin Check Plugin (PCP): a name-quality checker that helps plugin authors choose appropriate, non-problematic names before submitting to the Plugin Directory.

Problem

Plugin authors often unintentionally choose names that:

  • Contain protected trademarks (e.g., “WordPress,” “WooCommerce,” major brand names)
  • Are confusingly similar to existing plugin names in the directory
  • Do not follow the WordPress plugin naming guidelines
  • Could create brand conflicts or user confusion

These issues frequently lead to time during plugin review, which could be prevented early with automated guidance.

Proposal: Name-Quality Checker

Add a module or function in PCP that analyzes the plugin name defined in the main plugin file and reports:

1. Trademark Conflicts

  • Detect use of known restricted trademarks (WordPress, WooCommerce, Jetpack, etc.).
  • Optionally allow a configurable list of additional trademarks.

2. Similarity Check Against Existing Plugins

  • Compare the declared plugin name with existing names in the Plugin Directory API.
  • Warn when a name is overly similar (e.g., "SEO Booster Pro" vs. "SEO Booster").

3. Compliance with Naming Guidelines

Check for:

  • Use of “WordPress” instead of “WP”
  • Use of brand names as prefixes
  • Overly generic names
  • Excessive keyword stuffing

4. Actionable Suggestions

  • Recommend alternative naming approaches.
  • Highlight conflicts with links to relevant guidelines.

Benefits

  • Reduces plugin review rejection rate
  • Helps developers choose clear, unique, policy-compliant names
  • Improves the overall quality and clarity of the Plugin Directory

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions