diff --git a/anti-patterns.md b/anti-patterns.md
index b67e063..8d52f27 100644
--- a/anti-patterns.md
+++ b/anti-patterns.md
@@ -33,6 +33,10 @@ Framework adapted from professional naming agencies. If a name has any of these,
 
 Driven by fear of standing out. "WordPress Site Monitor" is a description, not a name. "Cloud-Based Team Collaboration Platform" is a sentence, not a brand.
 
+ **WordPress Trademark:**  Using **"WordPress"** inside a product name is not only generic — it can violate the WordPress Foundation trademark policy.
+- **Acceptable pattern:** *"[Product Name] for WordPress"* (descriptor).
+- **Risky / disallowed pattern:** *"WordPressBackup", "WordPressMonitor", "WPWordPressTool".*
+
 **Why it happens:** Stakeholders feel safe with descriptions because they're immediately clear. But clarity without memorability is useless — people understand what the product does for 5 seconds, then forget its name forever.
 
 **The fix:** Use the description as your tagline, not your name. The name creates recall; the tagline creates clarity.
diff --git a/availability.md b/availability.md
index a6c46d2..c46bf74 100644
--- a/availability.md
+++ b/availability.md
@@ -128,6 +128,17 @@ For serious products, do a basic trademark search. You don't need a lawyer for i
 
 ---
 
+### WordPress Naming Restrictions
+
+The WordPress Foundation enforces trademark rules that affect plugin and theme naming:
+
+- **"WordPress" cannot be used** in commercial product names (plugin, theme, SaaS)
+- **"WP" is allowed** but discouraged — signals commodity, not premium
+- **"for WordPress" is acceptable** as a descriptor, not a name component
+- **Check:** [WordPress Trademark Policy](https://wordpressfoundation.org/trademark-policy/)
+
+---
+
 ## Availability Decision Framework
 
 Not every platform needs to be available. Prioritize based on your product type: