Using the WordPress name can help explain what a product does. It can also make a third-party product sound official. That’s the distinction I want to explain here.

What is Trademark Infringement?

Suppose someone sells a cake called “Wonder Cake.” Another bakery using the same name could confuse customers about who made it. That’s the kind of problem trademark law addresses.

In the WordPress world, trademark infringement occurs when someone uses the WordPress name or logo in a way that might confuse people about whether their product or service is officially associated with WordPress.

Nominative fair use

If you review Wonder Cake, you need to use its name to identify it. That’s where nominative fair use comes in.

Nominative fair use allows you to use someone else’s trademark to refer to their product or service, as long as you’re not suggesting a false association or endorsement.

In the context of WordPress, nominative fair use means you can use the WordPress name to accurately describe or refer to WordPress-related products or services, without implying that you’re officially associated with or endorsed by WordPress.

The WordPress trademark policy

WordPress has a trademark policy covering use of its name and logo. The distinction this post focuses on is whether:

  1. You’re referring to the WordPress software itself.
  2. You’re describing how your product works with WordPress.
  3. You’re not implying an official association or endorsement.

Naming examples

Here are some names that could cause confusion and alternatives that make the relationship clearer:

  1. Name: “WordPressHosting.com”
    Fix: “FastHost: Optimized for WordPress”
    Why: The original could imply official WordPress hosting. The fix clearly separates the host name from WordPress.
  2. Name: “WordPress Experts, Inc.”
    Fix: “Web Dev Pros: Specializing in WordPress Solutions”
    Why: The original might suggest official WordPress endorsement. The fix shows expertise without claiming official status.
  3. Name: “The Ultimate WordPress Theme”
    Fix: “Flex Theme: Compatible with WordPress”
    Why: Giving the theme its own name makes the distinction clearer.
  4. Name: “WordPress Certified Training”
    Fix: “Comprehensive WordPress Development Course”
    Why: WordPress doesn’t have an official certification program. The fix describes the service without implying official status.
  5. Name: “WordPress Security Plugin”
    Fix: “SecurePress: A Security Plugin for WordPress”
    Why: The original might be mistaken for an official WordPress product. The fix clearly separates the product name from WordPress.

The goal is to explain how your product relates to WordPress without making it sound officially associated or endorsed.