Favicons and your online brand: Make sure you stand out!

Favicons are those little icons you see in your browser tabs. When you have many open tabs in your browser, they help you recognize and find the page you were looking for. They are important for your branding because Google shows them in the mobile and desktop search results. So, let’s take a closer look at those little icons and your branding here!

What is a favicon?

A favicon is a tiny, square image that represents a website. You see it in your browser’s address bar, open tabs, and bookmarks. Its main job is to help users quickly identify and find a site among many open tabs or results. Often, these match a website’s logo or theme, making it instantly recognizable. For consistency, favicons follow certain size and format rules to look good on different devices and platforms.

Favicon in your browser bar

The above example is in a browser bar, but we also see these in the search results. For some time, Google has shown them in its search results.

an example of a search result with the yoast favicon located in the top left corner
The Yoast logo is an example of a favicon in Google search

If your favicon represents a trustworthy brand, it can help people recognize your brand through this little icon, boosting your site’s click-through rate. After all, a picture says more than a thousand words!

Make your favicon stand out

You should make sure your favicon stands out, whether from that long list of tabs or the search results. Check if it matches your logo and website well. Especially when you are not one of the big brands and want people to recognize this little icon. Some tips directly related to that are:

  • Avoid too many details in your icon;
  • Please use the right colors so the favicon doesn’t blend in with the gray of your browser tab;
  • Test it at various sizes to ensure it remains clear and recognizable.

Everything is about branding. Your brand should be recognizable. Proper branding ensures that people will immediately relate your favicon to your website.

Follow Google’s guidelines regarding which format and size to use for your favicon. Google’s latest guidelines require favicons to maintain a 1:1 aspect ratio and a minimum size of 8×8 pixels. While the minimum size offers a baseline, Google strongly recommends using a resolution of at least 48×48 pixels to ensure clarity and visual appeal across various devices.

You should review and adjust your favicons to align with these guidelines. Make sure that your brand remains effectively represented in search results.

an example of a site might look on google as shown in the search appearance section of yoast seo
Yoast SEO shows your favicon in the Search Appearance section

Do these have SEO benefits?

Are there real SEO benefits? The importance of these icons certainly increased since they are present in the search results. While adding a favicon won’t directly make your page rank higher, it might increase the click-through rate to your page when it is shown next to your URL in the search results. It adds professionalism to your site, enhancing user perception and trust. This might indirectly contribute to better engagement metrics.

Of course, this only works if people feel positively about your brand or website. In practice, you should invest time in holistic SEO: making your website (and product/service) awesome in every way!

Favicons in WordPress

If you use WordPress, you might know that there’s a favicon functionality in WordPress. You can use this default functionality without hassle. It’s located in the General Settings and is called Site Icon. Here, you can read step-by-step instructions on how to change your site’s favicon in WordPress.

Set your favicon in the WordPress General Settings

These icons are small powerhouses

Favicons might be small, but they impact how people see your website. Your favicon can represent your brand by keeping your design simple and following the latest guidelines. It helps attract attention and makes your site look more professional. While they don’t directly boost search rankings, they can lead to higher click-through rates and better brand recognition. These benefits can support your overall SEO strategy. Spending a little time on a great icon can strengthen your connection with visitors.

Read more: 5 tips on branding »

Coming up next!

The SEO Agency Guide To Efficient WordPress Hosting & Management via @sejournal, @kinsta

This post was sponsored by Kinsta. The opinions expressed in this article are the sponsor’s own.

Managing client sites can quickly become costly in terms of time, money, and expertise, especially as your agency grows.

You’re constantly busy fixing slow WordPress performance, handling downtime, or regularly updating and backing up ecommerce sites and small blogs.

The solution to these challenges might lie in fully managed hosting for WordPress sites.

Opting for a fully managed hosting provider that specializes in WordPress and understands agency needs can save you both time and money. By making the switch, you can focus on what truly matters: serving your current clients and driving new business into your sales funnel.

WordPress Worries & How To Keep Clients Happy

For SEO agencies managing multiple client sites, ensuring consistently fast performance across the board is essential. Websites with poor performance metrics are more likely to see a dip in traffic, increased bounce rates, and lost conversion opportunities.

Managed hosting, especially hosting that specializes and is optimized for WordPress, offers agencies a way to deliver high-speed, well-performing sites without constantly battling technical issues.

Clients expect seamless performance, but handling these technical requirements for numerous websites can be a time-consuming process. While WordPress is versatile and user-friendly, it does come with performance challenges.

SEO agencies must deal with frequent updates, plugin management, security vulnerabilities, and optimization issues.

Challenges like bloated themes, inefficient plugins, and poor hosting infrastructure can lead to slow load times. You also need to ensure that client WordPress sites are secured against malware and hackers, which requires regular monitoring and updates.

With managed hosting, many of these tasks are automated, significantly reducing the workload on your team.

Managed hosting for WordPress simplifies the process by providing a full suite of performance, security, and maintenance services.

Instead of spending valuable time on manual updates, backups, and troubleshooting, you can rely on your hosting provider to handle these tasks automatically, resulting in reduced downtime, improved site performance, and a more efficient use of resources.

Ultimately, you can focus your energy on SEO strategies that drive results for your clients.

Basics Of Managed Hosting For WordPress

Managed hosting providers like Kinsta take care of all the technical aspects of running WordPress websites, including performance optimization, security, updates, backups, and server management.

We take over the responsibilities ensure the platform runs smoothly and securely without the constant need for manual intervention.

Kinsta also eliminates common performance bottlenecks in WordPress include slow-loading themes, outdated plugins, inefficient database queries, and suboptimal server configurations.

Key Benefits Of Efficient Managed Hosting For SEO

1. Performance & Speed

Core Web Vitals, Google’s user experience metrics, play a significant role in determining search rankings. Managed hosting improves metrics like LCP, FID, and CLS by offering high-performance servers and built-in caching solutions.

CDNs reduce latency by serving your website’s static files from servers closest to the user, significantly improving load times.

Kinsta, for example, uses Google Cloud’s premium tier network and C2 virtual machines, ensuring the fastest possible load times for WordPress sites. We also provide integrated CDN services, along with advanced caching configurations, which ensure that even resource-heavy WordPress sites load quickly.

And the benefits are instantly noticeable.

Before the switch, Torro Media faced performance issues, frequent downtimes, and difficulties scaling their websites to handle traffic growth. These issues negatively affected their clients’ user experience and SEO results.

After migrating to Kinsta, Torro Media saw noteable improvements:

  • Faster website performance – Site load times significantly improved, contributing to better SEO rankings and overall user experience.
  • Reduced downtime – Kinsta’s reliable infrastructure ensured that Torro Media’s websites experienced minimal downtime, keeping client websites accessible.
  • Expert support – Our support team helped Torro Media resolve technical issues efficiently, allowing the agency to focus on growth rather than troubleshooting.

As a result, Torro was able to scale its operations and deliver better results for its clients.

2. WP-Specific Security

Security is a critical component of managed hosting. Platforms like Kinsta offer automatic security patches, malware scanning, and firewalls tailored specifically for WordPress.

These features are vital to protecting your clients’ sites from cyber threats, which, if left unchecked, can lead to ranking drops due to blacklisting by search engines.

Downtime and security breaches negatively impact SEO. Google devalues sites that experience frequent downtime or security vulnerabilities.

Managed hosting providers minimize these risks by maintaining secure, stable environments with 24/7 monitoring, helping ensure that your clients’ sites remain online and safe from attacks.

3. Automatic Backups & Recovery

Automatic daily backups are a standard feature of managed hosting, protecting against data loss due to server crashes or website errors. For agencies, this means peace of mind, knowing that they can restore their clients’ sites quickly in case of a problem. The ability to quickly recover from an issue helps maintain SEO rankings, as prolonged downtime can hurt search performance.

Managed hosting providers often include advanced tools such as one-click restore points and robust disaster recovery systems. Additionally, having specialized support means that you have access to experts who understand WordPress and can help troubleshoot complex issues that affect performance and SEO.

Importance Of An Agency-Focused Managed WordPress Hosting Provider

For SEO agencies, uptime guarantees are essential to maintaining site availability. Managed hosting providers, like Kinsta, who specialize in serving agencies, offer a 99.9% uptime SLA and multiple data center locations, ensuring that websites remain accessible to users across the globe.

Scalability and flexibility matter, too. As your agency grows, your clients’ hosting needs may evolve. Managed hosting platforms designed for agencies offer scalability, allowing you to easily add resources as your client portfolio expands.

With scalable solutions, you can handle traffic surges without worrying about site downtime or slowdowns.

Agency Dashboard - Managed Hosting for WordPress

1. The Right Dashboards

A user-friendly dashboard is crucial for managing multiple client sites efficiently. Kinsta’s MyKinsta dashboard, for example, allows agencies to monitor performance, uptime, and traffic across all sites in one centralized location, providing full visibility into each client’s website performance.

Hosting dashboards like Kinsta’s MyKinsta provide real-time insights into key performance metrics such as server response times, resource usage, and traffic spikes. These metrics are essential for ensuring that sites remain optimized for SEO.

2. Balance Costs With Performance Benefits

For agencies, managing hosting costs is always a consideration. While managed hosting may come with a higher price tag than traditional shared hosting, the benefits, such as faster performance, reduced downtime, and enhanced security, translate into better client results and long-term cost savings.

Kinsta offers flexible pricing based on traffic, resources, and features, making it easier for agencies to align their hosting solutions with client budgets.

By automating tasks like backups, updates, and security management, managed hosting allows agencies to significantly reduce the time and resources spent on day-to-day maintenance. This frees up your team to focus on delivering SEO results, ultimately improving efficiency and client satisfaction.

Don’t think it makes that big of a difference? Think again.

After migrating to Kinsta, 5Tales experienced:

  • Improved site speed – Load times dropped by over 50%, which enhanced user experience and SEO performance.
  • Better support – Kinsta’s specialized support team helped troubleshoot issues quickly and provided expert-level advice.
  • Streamlined management – With our user-friendly dashboard and automated features, 5Tales reduced the time spent on maintenance and troubleshooting.

Overall, 5Tales saw an increase in both client satisfaction and SEO rankings after moving to Kinsta.

3. Managed Hosting & Page Speed Optimization

Tools like Kinsta’s Application Performance Monitoring (APM) provide detailed insights into website performance, helping agencies identify slow-loading elements and optimize them. This level of transparency enables faster troubleshooting and more precise optimization efforts, which are critical for maintaining fast page speeds.

It’s also easy to integrate managed hosting platforms with your existing tech stack. Kinsta works seamlessly with SEO tools like Google Analytics, DebugBear, and others, allowing agencies to track site performance, analyze traffic patterns, and ensure sites are running at peak efficiency.

Conclusion

Managed hosting is not just a convenience. It’s a critical component of success for SEO agencies managing WordPress sites.

By leveraging the performance, security, and time-saving benefits of a managed hosting provider like Kinsta, agencies can improve client results, enhance their relationships, and streamline their operations.

When it comes to SEO, every second counts. A fast, secure, and well-maintained website will always perform better in search rankings. For agencies looking to deliver maximum value to their clients, investing in managed hosting is a smart, long-term decision.

Ready to make the switch?

Kinsta offers a guarantee of no-shared hosting, 99.99% uptime guarantee, and 24/7/365 support, so we’re here when you need us. Plus, we makes it easy, effortless, and free to move to Kinsta.

Our team of migration experts have experience switching from all web hosts. And when you make the switch to Kinsta, we’ll give you up to $10,000 in free hosting to ensure you avoid paying double hosting bills.


Image Credits

Featured Image: Image by Kinsta. Used with permission.

In-Post Image: Images by Kinsta. Used with permission.

Mullenweg Criticized for 1st Amendment Claims via @sejournal, @martinibuster

Matt Mullenweg portrayed himself as a victim in his dispute with WP Engine, claiming in a tweet and blog post that they are ‘trying to curtail’ his free speech. Social media responses ranged from polite debunking of his First Amendment claim to accusations of hypocrisy.

TL/DR Of Dispute With WP Engine

Matt Mullenweg, co-creator of WordPress and CEO of Automattic ignited a dispute with managed WordPress web host WP Engine (WPE), using a Q&A at the WordCamp WordPress conference to denounce WP for not giving enough back to the WordPress open source project. He followed that statement with a post on WordPress.org that called WPE a cancer to WordPress, writing:

“This is one of the many reasons they are a cancer to WordPress, and it’s important to remember that unchecked, cancer will spread. WP Engine is setting a poor standard that others may look at and think is ok to replicate. We must set a higher standard to ensure WordPress is here for the next 100 years.”

He next banned thousands of WP Engine customers, cutting them off from updating their websites. Mullenweg later offered a temporary “reprieve” to prevent further inconvenience by WordPress publishers caught in the middle of the dispute and allow WP Engine to create a workaround.

Banning WP Engine elicited a negative response from WordPress developers and businesses. A tweet by the CEO of Ruby Media Group was representative of the general sentiment:

“My dev team can’t update my plugins because of this. You are destroying people’s lives.”

WP Engine responded with a Cease and Desist letter against Mullenweg and Automattic, followed by a federal lawsuit by WP Engine against Mullenweg and Automattic seeking relief from what they allege is an attempt by Mullenweg to extort millions of dollars from WPE.

Claim Of Attempt To Curtail First Amendment Rights

Mullenweg on Sunday published a blog post claiming that WP Engine’s lawsuit against him and Automattic is an attempt to “curtail” his “First Amendment rights.”

He wrote:

“WP Engine has filed hundreds pages of legal documents seeking an injunction against me and Automattic. They say this about community or some nonsense, but if you look at the core, what they’re trying to do is ask a judge to curtail my First Amendment rights.”

Mullenweg ended the post by stating he will no longer comment on the lawsuit filed by WP Engine but encouraged others to speak up in support of his side of the dispute.

Mullenweg Mocked On Social Media

The First Amendment is a guarantee that the United States government shall not create a law that infringes on a person’s free speech. Many on social media were quick to point out that WP Engine cannot curtain is First Amendment rights because they’re not the government.

A WordPress software developer tweeted:

“You have no first amendment rights in this context. WP Engine is not the government trying to curtail your 1A rights. 1A only applies to government entities.”

Another person followed up with:

“Please reread what the first amendment is, dum dum”

Another developer went further, calling Mullenweg “moronic”:

“WPEngine isn’t the government, how moronic can one man be?”

Another web developer advised Mullenweg to seek legal counsel to explain to him how the First Amendment works:

“Please go talk to your big expensive lawyer. I am sure they can break it down into small words for you.”

Accused Of Hypocrisy

Others on social media accused Mullenweg of hypocrisy for curtailing the free speech of others in the official WordPress Slack channel and banning WP Engine users from accessing plugins from the official repository.

A tweet by a WordPress and open source enthusiast captured the general feeling:

“Yes, “freedom of speech” is so important. I assume you now will be unblocking everyone that was exercising their right to freedom of speech in the WordPress Slack and here on X. Or, did you just mean literally “my freedom of speech” only.”

A WordPress developer from Denver tweeted:

“How many people have you banned from the WP slack channel over the past couple weeks?”

And another tweet:

“This coming from the guy cancelling anyone’s account/ access that disagrees with him. Really?”

Not Much Sympathy For Mullenweg

The overwhelming response to Matt Mullenweg’s post about his First Amendment rights was not sympathetic to his side of the story. A web applications developer’s tweet captured the lack of support:

“Maybe, maybe. But you probably won’t be getting a lot of sympathy from the crowd right now due to this thing the kids these days call “consequences.””

Read the original tweet by Mullenweg:

Matt Mullenweg’s blog post:

My Freedom of Speech

Featured Image by Shutterstock/Wirestock Creators

WordPress Announces New Executive Director via @sejournal, @martinibuster

Automattic CEO and WordPress co-creator Matt Mullenweg announced a new Executive Director for WordPress.org after the previous director’s resignation. Social media reactions, while generally positive, were notably subdued, with many comments focused on the recent WordPress controversy.

New Executive Director

Mullenweg announced that Mary Hubbard, was hired as the new Executive Director. Hubbard was formerly the Chief Product Officer for WordPress.com from 2020 and will begin her new position on October 21st. She recently resigned as the Head of TikTok Americas, Governance and Experience.

The Executive Director position at WordPress.org opened up after the resignation of 8.4% of Automattic employees, including the previous Executive Director Josepha Haden Chomphosy. Mullenweg offered employees who wished to leave $30,000 or the equivalent of six months pay, whichever was higher. The severance package was offered after the recent issues between Automattic, Mullenweg and WP Engine (WPE) which resulted in WPE filing a federal lawsuit against Mullenweg and Automattic, alleging attempted extortion.

Muted Response To Announcement

A post in the popular Dynamic WordPress Facebook Group generated 21 responses within seven hours, with most of the comments a discussion about the recent drama and the Mullenweg’s ownership of WordPress.org and other similar topics (view the discussion here, must join the private group to view).

The response to the official WordPress.org announcement on X was muted, with about equal amounts of people posting welcomes as those who were taking the opportunity to post their displeasure and opinions about recent events.

Seven hours after posting the announcement there were only 15 responses, 21 retweets, and 117 likes.

Screenshot Of Tweet

Typical Expressions Of Welcome

Typical Other Responses

Read the official announcement on WordPress.org

Please Welcome Mary Hubbard

Featured Image by Shutterstock/michaelheim

Executive Director Of WordPress Resigns via @sejournal, @martinibuster

Josepha Haden Chomphosy, Executive Director of the WordPress Project, officially announced her resignation, ending a nine-year tenure. This comes just two weeks after Matt Mullenweg launched a controversial campaign against a managed WordPress host, which responded by filing a federal lawsuit against him and Automattic.

She posted an upbeat notice on her personal blog, reaffirming her belief in the open source community as  positive economic force as well as the importance of strong opinions that are “loosely  held.”

She wrote:

“This week marks my last as the Executive Director of the WordPress project. My time with WordPress has transformed me, both as a leader and an advocate. There’s still more to do in our shared quest to secure a self-sustaining future of the open source project that we all love, and my belief in our global community of contributors remains unchanged.

…I still believe that open source is an idea that can transform generations. I believe in the power of a good-hearted group of people. I believe in the importance of strong opinions, loosely held. And I believe the world will always need the more equitable opportunities that well-maintained open source can provide: access to knowledge and learning, easy-to-join peer and business networks, the amplification of unheard voices, and a chance to tap into economic opportunity for those who weren’t born into it.”

Turmoil At WordPress

The resignation comes amidst the backdrop of a conflict between WordPress co-founder Matt Mullenweg and the managed WordPress web host WP Engine, which has brought unprecedented turmoil within the WordPress community, including a federal lawsuit filed by WP Engine accusing Mullenweg of attempted extortion.

Resignation News Was Leaked

The news about the resignation was leaked on October 2nd by the founder of the WordPress news site WP Tavern (now owned by Matt Mullenweg), who tweeted that he had spoken with Josepha that evening, who announced her resignation.

He posted:

“I spoke with Josepha tonight. I can confirm that she’s no longer at Automattic.

She’s working on a statement for the community. She’s in good spirits despite the turmoil.”

Screenshot Of Deleted Tweet

Josepha tweeted the following response the next day:

“Ok, this is not how I expected that news to come to y’all. I apologize that this is the first many of you heard of it. Please don’t speculate about anything.”

Rocky Period For WordPress

While her resignation was somewhat of an open secret it’s still a significant event because of recent events at WordPress, including the resignations of 8.4% of Automattic employees as a result of an offer of a generous severance package to all employees who no longer wished to work  there.

Read the official announcement:

Thank you, WordPress

Featured Image by Shutterstock/Wirestock Creators

8% Of Automattic Employees Choose To Resign via @sejournal, @martinibuster

WordPress co-founder and Automattic CEO announced today that he offered Automattic employees the chance to resign with a severance pay and a total of 8.4 percent. Mullenweg offered $30,000 or six months of salary, whichever one is higher, with a total of 159 people taking his offer.

Reactions Of Automattic Employees

Given the recent controversies created by Mullenweg, one might be tempted to view the walkout as a vote of no-confidence in Mullenweg. But that would be a mistake because some of the employees announcing their resignations either praised Mullenweg or simply announced their resignation while many others tweeted how happy they are to stay at Automattic.

One former employee tweeted that he was sad about recent developments but also praised Mullenweg and Automattic as an employer.

He shared:

“Today was my last day at Automattic. I spent the last 2 years building large scale ML and generative AI infra and products, and a lot of time on robotics at night and on weekends.

I’m going to spend the next month taking a break, getting married, and visiting family in Australia.

I have some really fun ideas of things to build that I’ve been storing up for a while. Now I get to build them. Get in touch if you’d like to build AI products together.”

Another former employee, Naoko Takano, is a 14 year employee, an organizer of WordCamp conferences in Asia, a full-time WordPress contributor and Open Source Project Manager at Automattic announced on X (formerly Twitter) that today was her last day at Automattic with no additional comment.

She tweeted:

“Today was my last day at Automattic.

I’m actively exploring new career opportunities. If you know of any positions that align with my skills and experience!”

Naoko’s role at at WordPress was working with the global WordPress community to improve contributor experiences through the Five for the Future and Mentorship programs. Five for the Future is an important WordPress program that encourages organizations to donate 5% of their resources back into WordPress. Five for the Future is one of the issues Mullenweg had against WP Engine, asserting that they didn’t donate enough back into the community.

Mullenweg himself was bittersweet to see those employees go, writing in a blog post:

“It was an emotional roller coaster of a week. The day you hire someone you aren’t expecting them to resign or be fired, you’re hoping for a long and mutually beneficial relationship. Every resignation stings a bit.

However now, I feel much lighter. I’m grateful and thankful for all the people who took the offer, and even more excited to work with those who turned down $126M to stay. As the kids say, LFG!”

Read the entire announcement on Mullenweg’s blog:

Automattic Alignment

Featured Image by Shutterstock/sdx15

WordPress Co-Founder & Automattic Sued For Attempted Extortion via @sejournal, @martinibuster

WP Engine, the managed web host recently banned from WordPress.org, has filed a federal lawsuit against WordPress co-founder Matt Mullenweg and Automattic, alleging attempted extortion as well as seeking relief from trademark infringement claims.

The goal of the federal lawsuit is to stop Mullenweg from continuing to “harm” WP Engine and the WordPress ecosystem as well as to hold Mullenweg and Automattic accountable for their “broken promises and malfeasance.” Malfeasance refers to wrongful or illegal conduct that may involve violations of the law or unethical actions, particularly by someone in a position of authority.

What The 98 Page Lawsuit Is About

The TL/DR of the lawsuit is that it’s “about abuse of power, extortion, and greed.” It states that the open source WordPress ecosystem was built on the promise of the freedom to create with WordPress without any constraints but that those promises were not kept and that the failure to keep those promises constituted wrongful acts, including making false statements to the IRS, among many other accusations backed up with evidence.

WP Engine made the following statement to Search Engine Journal:

“Matt Mullenweg and Automattic’s self-proclaimed scorched earth campaign against WP Engine has harmed not just our company, but the entire WordPress ecosystem. The symbiotic relationship between WordPress, its community and the businesses that invest millions to support WordPress users, and advance the ecosystem, is based on trust in the promises of openness and freedom.

Matt Mullenweg’s conduct over the last ten days has exposed significant conflicts of interests and governance issues that, if left unchecked, threaten to destroy that trust. WP Engine has no choice but to pursue these claims to protect its people, agency partners, customers, and the broader WordPress community.”

WP Engine’s lawsuit asks for judgment on these eleven points:

(1) Intentional Interference with Contractual Relations;
(2) Intentional Interference with Prospective Economic Relations;
(3) Computer Fraud and Abuse Act, 18 U.S.C. § 1030 et seq.;
(4) Attempted Extortion;
(5) Unfair Competition, Cal. Bus. Prof. Code § 17200, et seq.;
(6) Promissory Estoppel;
(7) Declaratory Judgment of Non-Infringement;
(8) Declaratory Judgment of Non-Dilution;
(9) Libel;
(10) Trade Libel; and
(11) Slander

Denial Of Trademark Infringement

The lawsuit filed by WP Engine denies the assertion by Mullenweg that the use of the word “WordPress” to refer to the open source project is subject to licensing fees, asserting that not only is the use of the name of the project legal and necessary in order to communicate information that consumers need, WP Engine asserts that the use of the name WordPress is freely used by the entire WordPress community and that said use has been condoned by the defendant Mullenweg.

Many times, lawsuits are won or lost based on the evidence provided and WP Engine’s lawsuit offers evidence to back up every allegation made against Mullenweg and Automattic.

For example, the lawsuit provides evidence that WP Engine was not misusing or infringing on the trademarks and that Mullenweg had been fully aware of WPE’s use of the challenged terms.

  • WP Engine’s membership in the ‘Five for the Future’ program is an acknowledgment that WPE was not infringing because one of the requirements of membership is to not currently be infringing on trademarks
  • Matt Mullenweg praised WP Engine on March 21, 2023 at the DE{CODE} developer conference, despite the fact that WPE used the challenged terms on their website at the time. The lawsuit quotes Mullenweg’s public statement: “vote with your wallet. So when you support companies like WPE, who don’t just provide a commercial service, but are also part of a wider open source community, you’re saying, hey, I want more of this in the world.”
  • Matt Mullenweg publicly acknowledged in an X livestream on September 26, 2024 that he knew WP Engine used the terms “for years” but that he had chosen not to take action.

Accusation Of False Statements To State Of California

The lawsuit also accuses that following the official incorporation of WordPress.org as a non-profit that Mullenweg of publicly transferred the WordPress trademark from Automattic to the non-profit WordPress Foundation but then secretly transferred it right back to Automattic through an exclusive sublicensable license which allowed Automattic to control the WordPress trademark. This contract between the WordPress Foundation and Automattic is the basis of their accusation that Mullenweg had made false statements to the state of California.

The lawsuit asserts:

“Mullenweg failed to disclose this exclusive licensing arrangement between his nonprofit (the WordPress Foundation) and his for-profit (Automattic) in the WordPress Foundation’s tax filings with the California government, claiming that there were no ‘contracts . . . between [WordPress Foundation] and any officer, director or trustee . . . or with an entity in which any such officer, director or trustee had any financial interest’ …This statement was false, given that Mullenweg was a director of the WordPress Foundation while also having a financial interest in Automattic, the entity with which the Foundation entered into a trademark license agreement—an apparent self-dealing transaction constituting inurement under federal tax law.”

Allegation: Mullenweg Made False Statements To IRS

WP Engine also states that Mullenweg has made false statements to the IRS.

The lawsuit documents the following:

“It appears Mullenweg also did not disclose the license agreement in the WordPress Foundation’s filings with the IRS, and none of WordPress Foundation’s fourteen years of publicly available federal reporting to the IRS indicates that the WordPress Foundation was compensated in any form for granting an exclusive, fully-paid, royalty-free, perpetual, irrevocable, worldwide, sublicensable license for trademarks Defendants now claim are incredibly valuable. Indeed, while the Foundation has failed to ever disclose to the IRS its ownership of the trademarks or existence of the exclusive royalty-free license to Automattic, for the past seven years Mullenweg himself executed the IRS forms on behalf of the Foundation under penalties of perjury, an apparent false certification to the IRS and public that the Foundation’s Forms 990 were true, correct, and complete.”

Additionally, the lawsuit shows that in 2011 Mullenweg filed IRS forms claiming that the non-profit WordPress Foundation only had assets of $14,071 and made no mention of assets like trademarks or other IP (intellectual property).

False Statements About Trademark Ownership

Another of the accusations made in the lawsuits is that Mullenweg had made misleading public statements asserting that the trademarks had been transferred to the non-profit WordPress foundation, even though he had secretly transferred the trademark back to Automattic through an exclusive sublicensable license. A sublicensable license is an agreement in which the original license holder (the licensor) grants a second party (the licensee) the right to grant a license to a third party (the sublicensee).

The lawsuit states:

“In 2010, in response to mounting public concern, the WordPress source code and trademarks were placed into the nonprofit WordPress Foundation (which Mullenweg created), with Mullenweg and Automattic making sweeping promises of open access for all: “Automattic has transferred the WordPress trademark to the WordPress Foundation, the nonprofit dedicated to promoting and ensuring access to WordPress and related open source projects in perpetuity. This means that the most central piece of WordPress’s identity, its name, is now fully independent from any company.” Mullenweg and Automattic reiterated this promise later, in even more forceful terms: ‘What’s important is that [] longer than I’m alive, longer than Automattic is alive, longer than any of us are alive, there is something that holds the WordPress code and trademark for the free access for the world.”

What Defendants’ statements and assurances did not disclose is that while they were publicly touting their purported good deed of moving this intellectual property away from a private company, and into the safe hands of a nonprofit, Defendants in fact had quietly transferred irrevocable, exclusive, royalty-free rights in the WordPress trademarks right back to Automattic that very same day in 2010. This meant that far from being “independent of any company” as Defendants had promised, control over the WordPress trademarks effectively never left Automattic’s hands. “

WP Engine writes that it relied on the promises made when it was founded in 2010 as a business built around WordPress, investing hundreds of millions of dollars over the past 14 years only to see WordPress turned against it by the “petulant whims” of Automattic’s CEO, Matt Mullenweg to “inflict harm” to WP Engine’s business.

Further claims are made that the request for payment of tens of millions of dollars for a trademark license (that WPE claims is not needed) came “without warning” and that they were given only 48 hours to make the decision to pay or face being banned and “publicly smeared.”

Alleges Mullenweg Controls WordPress Foundation For Self-Interest

The lawsuit also claims that the recent events at WordCamp and the days thereafter exposes that the non-profit WordPress Foundation is an entity that Mullenweg personally controls for his own and Automattic’s commercial interest.

“Mullenweg’s recent actions have exposed and highlighted his long history of obfuscating the true facts about his control and manipulation of the WordPress Foundation and wordpress.org—which he presents as a not-for-profit ‘dot-org’ enterprise, but which in fact he solely owns and directs with an iron fist to further his own commercial interests in Automattic and associated commercial businesses, to the detriment of Defendants’ competitors.”

Fallout From Lawsuit

The lawsuit was filed October 2nd and there is already a credible report that the WordPress Executive Director/General Manager, Open Source Division; Automattic, Josepha Haden Chomphosy, has resigned and will be making an announcement today October 3rd. The statement about this was posted on X by WP Tavern journalist Jeff Chandler who has been involved with WordPress since 2007.

He tweeted:

“I spoke with Josepha tonight. I can confirm that she’s no longer at Automattic.

She’s working on a statement for the community. She’s in good spirits despite the turmoil.”

Read the 98 page federal lawsuit here: (PDF)

Featured Image by Shutterstock/Billion Photos

WordPress Gives WP Engine Users A Reprieve via @sejournal, @martinibuster

Matt Mullenweg posted on WordPress.org that WP Engine users have been granted a reprieve from the block on the WordPress plugin and theme repository until October 1st, allowing them to access updates as usual.

WordPress Versus WP Engine

Matt Mullenweg and popular web host WP Engine have been locked in a conflict for the past week over a commercial licensing fee that other web hosts pay but WP Engine does not. The issue between them stems from the frustrations on Mullenweg’s side with the perception that WP Engine is not giving back enough to WordPress in the way that they should. Prominent figures in the WordPress industry like Joost de Valk agree with Mullenweg that companies, including WP Engine, should give back more to WordPress.

WP Engine has offered their side of the story have gone as far as to send a formal cease and desist letter for what they perceive as an unfair attack on their business.

Regardless of who is right or wrong, WordPress users on WP Engine are caught in the middle of this conflict, with their businesses disrupted by Mullenweg’s decision to block WP Engine from accessing the WordPress.org plugin and theme repository, preventing them from updating plugins and themes.

Temporary Reprieve

Mullenweg posted on WordPress.org that he has heard from WordPress users and has decided to give the WordPress users a chance for WP Engine to set up a solution so that they won’t be inconvenienced. WP Engine has until October 1st to engineer a workaround.

He wrote:

“I’ve heard from WP Engine customers that they are frustrated that WP Engine hasn’t been able to make updates, plugin directory, theme directory, and Openverse work on their sites. It saddens me that they’ve been negatively impacted by Silver Lake‘s commercial decisions.

WP Engine was well aware that we could remove access when they chose to ignore our efforts to resolve our differences and enter into a commercial licensing agreement. Heather Brunner, Lee Wittlinger, and their Board chose to take this risk.

…We have lifted the blocks of their servers from accessing ours, until October 1, UTC 00:00. Hopefully this helps them spin up their mirrors of all of WordPress.org’s resources that they were using for free while not paying, and making legal threats against us.”

Read more at WordPress.org:

WP Engine Reprieve

Featured Image by Shutterstock/Vladimka production

Yoast Co-Founder Suggests A WordPress Contributor Board via @sejournal, @martinibuster

Joost de Valk, co-founder of the Yoast SEO plugin, published an article calling for more equitable contributions from large WordPress companies, greater financial transparency, and a new board that represents the voices of contributors and companies.

Joost de Valk Supports Matt Mullenweg

Joost de Valk’s article is supportive of WordPress and agrees with Automattic’s CEO Matt Mullenweg that WP Engine should contribute more to WordPress. He praises Mullenweg and Automattic for the amount of contributions they make to WordPress, contrasting Mullenweg’s example against those who are financially benefiting the most from WordPress but don’t contribute on a level that’s reflective of their rewards.

He writes:

“I agree with Matt about his opinion that a big hosting company such as WPEngine should contribute more. It is the right thing to do.”

Joost writes that these aren’t just words to him, that they reflect his values and actions, sharing that his organization contributed so much time to the Gutenberg Project that it was literally at the expense of his own for-profit venture in that, while they “still made a lot of money” their revenue did experience a dip.

He thus envisions creating a board that’s representative of stakeholders as a way to encourage a healthy sustainable open source ecosystem with greater transparency and community representation.

Business Success Informs His Opinion

His idea for cultivating a health self-perpetuating open source community has been his guiding principle and is what he credits for his business success. In a 2013 WordCamp presentation he shared his experience of spending many years contributing to WordPress and creating a wildly popular plugin while not yet making any money. He reached a point where he had a day job to support his WordPress hobby and had to decide how to flip that so that they hobby became his day job.

In that presentation (The Victory Of The Commons) he described two ways of thinking about his situation, one in which he just goes all-in and focuses on doing what’s best for him and another path where he does what’s best for him and the WordPress community.

Joost credits his wife with suggesting to solve his problem by looking at it within the framework of the Tragedy Of The Commons. The Tragedy Of The Commons is a concept of how individuals can decide to either manage a shared resource to create a sustainable living for the community or behave in self-interest and eventually deplete the resource, thus harming the entire community.

He shared the following in that 2013 WordCamp presentation:

“So, if everyone in the WordPress community, if we all looked at it like this, we can make money and make sure that we reinvest that money, we’d grow.”

He said that creating something and giving it away is not necessarily good. He said it’s better for everyone to make “piles and piles of money” with the work but giving some of that back supports you and the community in a self-sustaining circle. He insisted that reinvesting “in the pasture” was paramount to working within the WordPress open source community.

“Reinvest some of that profit into all of our main pasture, WordPress. We all benefit.”

New WordPress Foundation Board

One of the solutions that Joost suggests is the creation of a board that provides representation to those who contribute to WordPress. Joost uses the analogy of taxation with representation as the basis for a WordPress Foundation board so that those who contribute can also be heard as part of the decision making process.

What he envisions isn’t a governing board with decision making power but one that serves in an advisory position that can participate as part of a dialogue within the decision-making structure.

He writes:

“I think this could actually help Matt, as I do understand that it’s very lonely at the top.

With such a group, we could also discuss how to better highlight companies that are contributing and how to encourage others to do so.”

The three main points he makes are:

1. Representation Of Stakeholders

“In my opinion, we all should get a say in how we spend those contributions. I understand that core contributors are very important, but so are the organizers of our (flagship) events, the leadership of hosting companies, etc. We need to find a way to have a group of people who represent the community and the contributing corporations.”

2. Facilitation Of Transparent Discussions

“Now I don’t mean to say that Matt should no longer be project leader. I just think that we should more transparently discuss with a ‘board’ of some sorts, about the roadmap and the future of WordPress as many people and companies depend on it.”

3. Encouragement And Recognition Of Contributions

“With such a group, we could also discuss how to better highlight companies that are contributing and how to encourage others to do so.”

Transparency With Money

One of the points that Joost brings up is somewhat separate from the creation of a contributor board and it’s about the payments made to Automattic for trademark deals.  He says that thing mingling of money creates a situation where it’s uncertain how much of it is used by Automattic as contributions to WordPress.

He writes:

“…let everybody see how the money flows.

Currently the way it works is that the money for trademark deals flows to Automattic, but we don’t know how much of the contributions Automattic does are paid for by Newfold, whom we now all know are paying for the use of the trademark. Maybe the money should go directly into the foundation? If not, I think we should at least see how many of the hours contributed by Automattic are actually contributed by Newfold.”

WordPress May Be At A Crossroad

WordPress may be at a historic crossroad that could lead to different outcomes. Joost suggests doubling down on open source by engaging with the entire WordPress community, returning to the ideal of reinvesting in “the pasture” to create a sustainable system that allows everyone to make “piles and piles of money” and achieve the goals users are working toward.

Featured Image by Shutterstock/Shutterstock AI Generator

WordPress Bans Thousands Of WP Engine Customers via @sejournal, @martinibuster

WordPress banned WP Engine, a managed WordPress web host, blocking thousands of websites from adding or updating plugins and themes. Technology writer Robert Scoble described the decision as “universally hated in tech” and that out of hundreds of posts on the subject almost none was on Mullenweg’s side on the issue.

What Happened

Matt Mullenweg, co-creator of WordPress, accused WP Engine of infringing on their trademarks and demanded tens of millions of dollars in compensation. Things came to a head on the last day of the recent WordCamp WordPress conference when Mullenweg gave WP Engine until 4:30 PM that day to comply with his demands. Failure to agree to those demands led to a public shaming of WP Engine by Mullenweg and the subsequent ban of WP Engine.

WordPress.org Bans WP Engine

In a post titled WP Engine is banned from WordPress.org, Mullenweg announced that WP Engine was banned and cut off from their plugin and theme repository.

He wrote:

“Any WP Engine customers having trouble with their sites should contact WP Engine support and ask them to fix it.”

WP Engine posted an incident report on their website that offered a workaround:

“WordPress.org has blocked WP Engine customers from updating and installing plugins and themes via WP Admin. There is currently no impact on the performance, reliability or security of your site nor does it impact your ability to make updates to your code or content. We know how important this is for you and we are actively developing a remediation for this issue. We will update you as soon as we have a fix.

If you need to install or update a plugin or theme, manual instructions can be found at https://wpengine.com/support/manage-plugins-and-themes-manually

If you have any questions or need assistance, do not hesitate to reach out to our technical support team.”

WordPress Core Contributor Sentiment

WordPress core contributors are apparently not liking the current situation. A post on Reddit by an anonymous code contributor to WordPress indicated that that the core developer community is not rallying around Mullenweg.

The WordPress core contributor wrote:

“WordPress core dev here.

All contributors, Automattic and non Automattic, are watching very closely. We’re also thinking very carefully about our contributions. This is a community project and contributors are part of the community. No matter who is listed as project leadership, we’ll continue to be here for the community.

I’ve said this in other comments, but whether Matt has been accurate doesn’t even come into it for plenty of us. The way this has been done, and is continuing to be done, is such a significant problem to address before even looking at whether he’s been accurate or not.

The community, which includes us at WordPress core, are not rallying around in support of this action. Everyone I’ve spoken to at WordPress core had no prior notice of this action being taken. Given the lack of notice about this latest action, it raises concerns about whether more is to come. Right now, there’s an almost deafening public silence in contributor-to-contributor communication. We’re still trying to regulate our reactions to recent events and hopefully avoid adding more of the kinds of kneejerk actions our whole community have been subjected to in recent days.

Ceasing our own contributions would have further impact on the community. We definitely don’t want that. Even with that at the forefront of my mind, if a decision is made to engage in a collective withdrawal of contributions, with a clearly communicated desired outcome to break that withdrawal, I’d join that action. Regretfully.”

The core contributor related that aside from the warning about legal action, Mullenweg has not discussed his plans or course of action with the WordPress contributors. They also confirmed that none of the core contributors have made a change to “facilitate his actions”.

The core contributor posted a follow up to their comments to say that they’re not seeing anything positive yet.

It should be crystal clear in Matt’s mind that what’s happening right now can’t continue. How he chooses to act on that knowledge is anyone’s guess. Unfortunately, what I’m seeing in his messages through all communication channels so far doesn’t show signs of anything positive, yet (as I said in my earlier comment, we’re all watching very, very closely).”

Social Media Reaction

An overwhelming number of the posts on X (formerly Twitter) express disappointment with Mullenweg’s actions and are supportive of WP Engine.

Technology writer Robert Scoble posted:

“WordPress at war. So sad.

I was one of the first to use WordPress. I didn’t see this coming. I read hundreds of posts about what @photomatt did and almost none of them are on his side.

Never seen a decision so universally hated in tech. Lots of my old friends are in pain tonight.”

Typical reaction on X:

“This is absolutely insane and such a disgusting abuse of power by @photomatt. I have clients using @wpengine and now they can’t easily install plugins or update themes. #WordPress”

Another WordPress user posted:

“Gotta say, I’m with WP Engine on this. Not saying they are the “good guys” but if we all have to pay Automattic for using the word “WordPress” in our marketing, then we’re all in trouble. This sets a dangerous precedent.”

Read Mullenweg’s post on WordPress.org

WP Engine is banned from WordPress.org

Read the WP Engine Incident Report:

Plugin and Theme Update Restrictions

Featured Image by Shutterstock/Wirestock Creators