Automattic Challenges Use of Word “Automatic” for WordPress Product
Automattic challenges the use of the word “Automatic” for the WordPress product, raising questions about trademark rights and brand identity.
Automattic, the for-profit company founded by WordPress co-founder Matt Mullenweg, has formally objected to a WordPress developer’s use of the word “Automatic” in naming his CSS framework. Legal representatives of Automattic sent a trademark complaint letter to Kevin Geary, urging him to rebrand his project Automatic.css, citing potential consumer confusion due to the name’s similarity to Automattic.
Screenshot Of Mullenweg’s July 2025 Tweet To Geary
Background on Kevin Geary and His Projects
Kevin Geary is a respected figure in the WordPress development community, active since 2005. He is currently working on the WordPress page builder EtchWP (in early alpha) and is known for Automatic.css (ACSS), a CSS framework designed to streamline design consistency across websites.
ACSS integrates smoothly with popular WordPress page builders like Bricks, Gutenberg, and Oxygen.
Geary has openly criticized the WordPress Block Editor (Gutenberg), highlighting inefficiencies and usability issues in a public blog post and video.
He wrote about the Gutenberg workflow:
“Is this the “for everyone” experience? Is this the true vision of the WordPress block editor? …it’s wildly inefficient and impractical.”
He also observed that many people are unclear about Gutenberg’s purpose, referencing an informal Twitter poll of his followers that revealed disagreement over whether it should function as a page builder.
He concluded:
“It’s NOT for:
Beginner web developers who want to learn how to build websites.
Intermediate web developers who want to build custom websites.
Advanced web developers who want to build custom websites.
Most agencies & freelancers (unless they’re committed to building custom blocks).
I want to like it, I really do. As it stands now, though, the only viable way to use the block editor to build a custom site is with third-party tools. Native ain’t cutting it.”
Geary’s enthusiasm for WordPress is clear, despite his criticisms of the block editor and the community-based ‘tragedy of the commons’ support model.
Contents of Automattic’s Legal Notice
Geary shared a tweet containing the letter he received, in which Mullenweg’s lawyers requested that he rebrand his WordPress CSS framework.
Part of the content of the letter stated:
“We represent Automattic Inc. in intellectual property matters. As you know, our client owns and operates a wide range of software brands and services, including the very popular web building and hosting platform WordPress.com. Automattic is also well-known for its longtime and extensive contributions to the WordPress system.
Our client owns many trademark registrations for its Automattic mark covering those types of services and software. As a result of our client’s extensive marketing efforts and support of the WordPress system, consumers have come to closely associate Automattic with WordPress and its related offerings.
We are writing about your use of the name and mark Automatic (sometimes with a CSS or .CSS suffix) to provide a CSS framework specifically designed for WordPress page builders. As we hope you can appreciate, our client is concerned about your use of a nearly identical name and trademark to provide closely related WordPress services. Automattic and Automatic differ by only one letter, are phonetically identical, and are marketed to many of the same people. This all enhances the potential for consumer confusion and dilution of our client’s Automattic mark.
We assume you share Automattic’s interest in ensuring that consumers are not confused or misled by the use of nearly identical names and trademarks to provide related services in the WordPress ecosystem. To protect against any such confusion or dilution, Automattic requests that you rebrand away from using Automatic or anything similar to Automattic. I suggest that we schedule a time to discuss the logistics and a mutually agreeable transition timeline for the change. Please let me know some days and times when you are available.”
The letter requested a rebranding of Automatic.css to avoid dilution of the Automattic trademark and suggested discussing a transition timeline.
Matt Mullenweg’s Response and Domain Ownership Claim
Matt Mullenweg responded via tweet, mentioning ownership of the domain automatic.com to justify the trademark claim. However, Geary pointed out that domain registration does not equate to ownership of a generic term.
Mullenweg’s tweet:
“We also own http://automatic.com. You had to know this was a fraught naming area.”
To which Geary responded:
“AutomaticCSS is called “automatic” because it’s the only CSS framework that does a lot of things automatically.
Congratulations on owning the domain name for a generic term. Let me know when that fact becomes relevant.”
Community Reaction and Debate
Reactions on social media largely supported Geary, criticizing the legal challenge as excessive over a common term by tweeting:
“Why go with “AutomaticCSS” as the name though?
Options like “AutoCSS” or even “AutomatedCSS” would have been even more suitable IMHO.
It could indeed raise the question of whether there was some other motive at play. Just sharing my thoughts!”
Simon Zeimke tweeted:
“A letter from hell. How could a generic Term be IP?”
Lee Milroy responded:
“This is absurd, a product that has been around for 4 years is all of a sudden going to create “confusion”?
Really Matt needs to do some work… like the terrible WP Dashboard experience”
Industry Sentiment
Over a week since the letter leaked publicly, Geary has yet to disclose his next move. Many WordPress community members expressed a desire for the matter to de-escalate, emphasizing the importance of focusing on improving WordPress rather than engaging in trademark disputes.
