Tag: WordPress

Tech Insight : WordPress Telex Uses AI To Turn Plain Language Into Working Blocks

Posted on by Paul Stradling

WordPress has introduced Telex, an AI powered tool that turns simple written prompts into working WordPress blocks, opening up custom development to people who cannot write code.

What Is Telex?

Telex is an experimental system that converts natural language instructions into functional Gutenberg blocks, which are the modular elements that make up WordPress sites. The WordPress team describes it as a tool that lets users “simply describe what you want, and Telex generates the block”. It is designed to remove much of the technical complexity that usually surrounds block development, which has traditionally required experience with WordPress internals, React, JavaScript, PHP and various build tools.

The official announcement explains that even modern AI code editors only reduce part of that workload because developers still need to provide WordPress specific context and wire everything together themselves. Telex aims to remove that barrier entirely by handling the scaffolding, packaging and previewing work automatically in the browser.

How Does Telex Work?

Telex runs in a browser based environment powered by WordPress Playground, which is a sandboxed version of WordPress that allows safe testing. Users simply type a written description of the block they want, covering functionality, controls, layout and styling. Telex then interprets the prompt, generates the block’s code, registers it as a plugin and displays it running inside Playground.

That allows users to refine the result through short follow up prompts. Also, Telex can adjust styles, fix errors or add extra features, or users can switch to the Code view to edit the PHP, JavaScript or CSS manually. When the block is ready, it can be downloaded as a zip file and installed on any WordPress site that accepts plugins. There is also a Share option that produces a link so others can preview and download the block without logging in.

Early Demonstrations Of The Tool

The announcement about Telex on the WordPress blog gives quite a detailed example aimed at food bloggers. In this example, the author asked Telex to build an Ingredient List block that displays ingredients in a table, allows readers to tick items off, includes a copy to clipboard button and adds a built in recipe scaler. The editor view for the block required columns for quantity, unit and ingredient, along with buttons to reorder or remove items.

WordPress says the result appeared in about two minutes. The first version worked but needed visual refinements, so the author asked Telex to simplify styling so it inherited the current theme, apply a strikethrough to checked ingredients, convert quantities to whole numbers or fractions rather than decimals and add a confetti animation when all items were ticked. After four short iterations the block met all requirements. The author noted that the whole process “took about 10 minutes to build in total”.

WordPress says this example was created entirely in the browser without local setup, thereby demonstrating the kind of functional utility blocks Telex is intended to handle.

Real-World Uses Revealed At State Of The Word

At WordPress’s recent State of the Word event in San Francisco, project co-founder Matt Mullenweg shared some further examples that had already been created using Telex. These included price comparison elements, price calculators, real time store hours with a map link, partner logo carousels, Google Calendar integrations and post grids with consistent card heights.

Mullenweg made the point that such components used to require custom development work that could cost “thousands, tens of thousands of dollars to build, even just years ago” but Telex now allows developers and non developers to produce them in a browser in a matter of seconds before refining them with prompts or manual edits.

Who Is Telex Designed For?

The WordPress team stresses that Telex is not only for experienced developers but that “everyone can use Telex”, such as site owners, agencies, freelancers, developers and aspiring developers as target users.

Example Uses

For site owners, Telex could offer a really quick way to create small features that might otherwise be too costly to commission. Agencies and freelancers could use it to test ideas, build prototypes or generate custom utility blocks for client projects. Developers could use the fast scaffolding tool to produce standard block plugins that can be refined or integrated into larger systems. Also, aspiring developers could generate blocks and then study the source code to understand how WordPress handles structure, behaviour and styling.

Access And Cost

The good news is that Telex is currently free to use and allows unlimited block creation. Anyone can visit the Telex interface, log in with a WordPress.com account and begin generating blocks without paying for a WordPress.com plan. WordPress is essentially providing a low-risk way for teams to experiment with AI assisted development without needing to commit budget.

Limitations And Known Issues

Although it all sounds very promising, it’s worth noting here that Telex remains an experimental tool. In fact, WordPress warns that results vary and users may encounter bugs, incorrect assumptions or code that fails to run. The guidance suggests asking Telex to fix the problem directly, restating the requirement, or starting a fresh session.

There are also some technical gaps to consider. For example, blocks that rely on inner blocks, such as a slideshow with separate slide elements, are not yet supported. Complex systems involving e-commerce, membership logic or extensive backend integrations may also require manual adjustments to ensure reliable behaviour, security and responsiveness.

Not An AI Website Builder – More Of An Assistant

WordPress also makes it clear that Telex “is also not an AI website builder”. Instead, it is described as an AI system that helps users create “small functional tools as blocks”, thereby positioning it as an assistant rather than a replacement for full site builders or human developers.

Part Of A Wider AI Direction For WordPress

Telex actually forms part of a broader strategy to make WordPress more compatible with AI systems. For example, Mullenweg highlighted the development of an Abilities API, which defines what WordPress can do in a structured way that AI models can interpret, and an MCP adapter that lets AI agents use those abilities without requiring dedicated integrations for each platform.

This means WordPress sites can now be connected to AI tools like Claude or Copilot in a more consistent and predictable way. Mullenweg also noted that developers are already using AI in their daily workflows through tools such as Cursor and Claude Code. WordPress plans to introduce benchmarks and evaluations in 2026 that will allow AI models to be tested on specific WordPress tasks, including plugin changes, text editing and navigating the interface via browser agents.

Why It Matters For Organisations And Developers

Telex offers a new route for building and iterating on small functional blocks that would once have required dedicated developer time. Marketing and content teams could describe a pricing tool, a custom callout block or a simple event feature and have a working prototype ready within minutes. Agencies may find it useful for workshops or early client engagement, where quick prototypes help clarify requirements.

Also, the sandboxed environment, zip based packaging and editable code provide clear boundaries for testing and refinement. At the same time, Telex’s experimental nature and its known gaps emphasise the need for cautious review before deploying blocks that handle sensitive data or important business processes.

The overall picture is essentially of a tool designed to make WordPress development faster, more accessible and easier to experiment with, while still leaving space for developer oversight, theme alignment and long term maintenance.

What Does This Mean For Your Business?

Telex shows how AI can compress development cycles, reduce manual effort and give teams an easier starting point for experimenting with new ideas. The fact that it can turn a short prompt into a working block in minutes could really help the testing and refining of features, particularly for organisations that rely on WordPress for day to day marketing and content work. It also means non technical users can really contribute, i.e., a wider group of users can now generate early versions of components that would once have required a developer to build from scratch.

Despite this democratising element, it should be noted that it doesn’t remove the need for experienced developers, especially where security, performance and integration work are concerned. The experimental label is important because Telex still introduces errors, makes incorrect assumptions and struggles with more advanced structures. Developers will remain central to reviewing outputs, hardening code and ensuring long term maintainability. That balance highlights where Telex currently sits in the WordPress ecosystem, i.e., it speeds up the early stages of building small functional tools, but it still relies on human expertise to take those tools into production safely.

The implications for UK businesses are notable. For example, teams that have previously avoided commissioning custom work because of cost or time pressures may now have a practical way to prototype new functionality. Agencies can offer quicker turnarounds during discovery work, and in house teams can test new components without waiting for formal development cycles. Telex also seems to fit quite neatly into the broader move toward AI assisted workflows, which many UK organisations are now exploring as part of wider digital transformation plans.

There is also an equal significance for the wider WordPress community. For example, the Abilities API and MCP adapter show that Telex is only one part of a longer term strategy to make WordPress more interoperable with AI systems. As AI agents become more capable of understanding and manipulating the platform, new opportunities will emerge for automation, testing and collaborative development. Telex is, therefore, an early look at how WordPress may evolve, giving users a practical tool today while pointing towards a much broader set of capabilities in the years ahead.

News : ‘Telex’ Builds WordPress Blocks With Prompts

Posted on by Paul Stradling

WordPress used WordCamp US 2025 in Portland to debut ‘Telex’, an experimental AI tool that turns plain English prompts into downloadable website blocks, making it faster and easier to build custom WordPress features without coding.

What Telex Is And Why It Matters

Telex is a prototype that generates custom Gutenberg blocks (the modular sections that make up WordPress pages) from a typed prompt, then packages the result as a downloadable .zip. The .zip file can then be uploaded as a plugin to a WordPress site or tested in WordPress Playground. In his keynote, WordPress co-founder and Automattic CEO Matt Mullenweg described it as “V0 or Lovable, but specifically for WordPress,” referencing the rise of prompt-based “vibe coding” tools (vibe coding is using AI to generate code from natural language prompts). He showed how a developer used it to create a simple marketing animation, underscoring the aim to lower the barrier to building bespoke site elements.

The service is currently available at telex.automattic.ai and is marked as experimental, to show users that it’s still a work in progress. Early testers have reported that there have been projects that failed outright or needed manual fixes before working properly, which is consistent with the current prototype label. “At the core of it, there is a seed of something, which is so enabling,” Mullenweg said, while also acknowledging concerns about the hype cycle around AI.

Who Is Behind It?

Telex follows WordPress’s formation of a formal AI Team in May 2025, which was set up to coordinate AI features across the ecosystem using a plugin-first approach. The initial team includes contributors from Automattic, Google, and 10up, the apparent brief being to “accelerate and coordinate artificial intelligence projects” in line with WordPress values. This is the governance backdrop for Telex and other experiments.

How It Works In Practice

The idea of how Telex is used is simple, i.e. users describe the block they want (for example, a hero section with animated text and a call to action) and Telex generates code that the user can install as a plugin. WordPress Playground, which runs full WordPress instances in the browser, provides a safe place to try outputs without touching a live site. For many users, especially small teams, this should reduce the set-up overhead of traditional development and encourage and speed up layout or interaction ideas.

What’s So Special About Telex (Compared With Other AI Builders)?

There are, of course, plenty of AI website builders that generate whole sites in one go, including Wix’s AI Website Builder and Squarespace’s Blueprint AI. However, Telex is different because it targets WordPress’s modular architecture and outputs discrete Gutenberg blocks that can slot into existing sites, themes, and workflows. For teams invested in WordPress, that is a more natural fit than moving to a closed, hosted builder. Wix and Squarespace are pitching all-in-one creation and hosting, often with paid plans and platform lock-in, whereas Telex sticks to WordPress’s open approach and lets users host sites wherever they choose.

Benefits Businesses Might Notice

If Telex matures, the immediate benefit is likely to be time saved due to speed. For example, routine front-end building blocks such as hero sections, testimonial carousels, or animated counters could be generated in just minutes, then refined by a developer rather than built from scratch. Since the output is a standard plugin zip, teams can check the code, keep track of changes, and remove it easily if needed, which suits organisations that follow strict approval processes.

For non-technical teams that still prefer WordPress, Telex simplifies things. WordPress powers 43.4 percent of all websites (according to W3Techs , so any step that makes customisation easier is likely to have an outsized impact. If prompt-to-block works well, agencies could prototype options live with clients, then hand over code that slots into existing repos and CI pipelines.

Playground is also useful because it allows developers to test Telex-generated blocks in a browser without needing a live site. They can install the plugin, check it works as expected, and export the result as a .zip file when ready.

Where It Fits In The Competitive Landscape

WordPress remains the most widely used content management system. Other platforms such as Wix and Squarespace have recently introduced AI features that build entire sites in minutes, aimed at first-time users and small businesses.

Telex takes a different approach. Instead of generating whole websites, it focuses on creating individual WordPress blocks that can be added to existing themes and layouts. It stays within the open WordPress system and gives users the freedom to host their websites anywhere, which is often a priority for businesses that want more control over their data and setup.

This could help WordPress hold onto small businesses that might otherwise switch to closed, hosted platforms. If Telex proves reliable, it may also speed up work for agencies and internal teams who already build with WordPress.

There may also be knock-on effects across the WordPress ecosystem. If businesses can generate standard blocks themselves, this could reduce demand for some paid plugins and themes. At the same time, it could create new opportunities for agencies to offer reviewed prompt templates, support services, or curated collections of AI-generated blocks for clients in regulated industries.

Key Challenges And Early Criticism

It seems that Telex has already faced some questions about reliability, e.g. there have been reports that several early test projects failed or needed extra work before they could run properly. For now, it’s likely that businesses will still need developers to review, test, and secure any blocks before using them on a live site. How well Telex handles different themes, and whether it supports accessibility and good performance by default, will make a big difference to how useful it becomes.

There’s also the wider legal backdrop. For example, WordPress and Automattic (the company behind WordPress.com and a major contributor to the platform) have spent the past year in a legal dispute with hosting provider WP Engine. That case led to a court-ordered injunction in December 2024 and remains ongoing. Although it has nothing to do with Telex, the dispute has raised concerns about how decisions are made in the WordPress ecosystem and who holds the influence. At WordCamp, Mullenweg said only that the case was moving through the legal system.

Security is another area that will need close attention because like any AI tool that writes code, Telex can produce weak or incomplete results if the prompts are unclear. As WordPress runs in so many different environments, even small errors can lead to problems. WordPress Playground (the browser-based version of WordPress used for safe testing) may help lower the risk during development, but once in production, businesses will still need to carry out proper checks, just as they would with any third-party plugin.

What It Could Mean For WordPress

Telex is part of WordPress’s ongoing move to introduce AI in a way that’s open and easy to test. The AI Team set up in May 2025 has said it will use a plugin-first approach, meaning features like Telex will be released separately at first, not baked into WordPress Core. If Telex becomes more widely used, it could start to shape WordPress development practices, training materials, and support tools.

It could also lead to more conversational features in WordPress itself, such as tools that help users build blocks by describing what they want in plain English. Mullenweg made clear that this ties directly into WordPress’s long-standing goal of making publishing accessible to everyone. “We’ve taken things that were difficult to do, that required knowledge of coding or anything else, and made it accessible to people,” he said.

If AI can continue that trend without lowering code quality or reducing choice, Telex could help keep more creators on the WordPress platform rather than losing them to simpler, hosted services.

What About Business Users of WordPress?

For small and medium-sized UK businesses already using WordPress, Telex could speed up common tasks such as adding new sections to a homepage, updating layouts, or testing different calls to action. Also, marketing teams could test ideas quickly and agencies could deliver small custom features faster and at lower cost. Developers could spend less time writing basic layout code and more time on integrations, security, and performance.

For companies in regulated sectors, the fact that Telex generates installable plugins, not hosted code or external widgets, is also important because it makes it easier to track changes, review code, and remove features if needed, which fits well with internal approval processes.

Hosted platforms like Wix and Squarespace now offer strong AI tools for beginners, but they also limit flexibility and hosting choices. Telex offers an alternative that works within WordPress and still gives users full control over where and how their site is hosted.

For developers, Telex essentially changes the way some work gets done but doesn’t remove the need for human input (it still needs the AI prompts). Early feedback shows that AI-generated blocks often still need testing and refinement and, therefore, agencies with strong technical teams may be best advised to combine effective prompting with proper review, offering clients speed without sacrificing quality.

How To Try It Safely Today

Telex is still experimental, and the safest way to try it is through WordPress Playground (a browser-based version of WordPress for safe testing). This lets developers test blocks directly in the browser, without affecting any live sites. For now, users may want to keep the scope simple, such as generating a hero section or a testimonial layout, and then review the code before installing it on a development site. That will give teams a chance to see how Telex works while keeping control over what goes into production.

Where Things Stand for Now

Telex is still in its early stages, and some outputs may not yet be reliable enough for complex sites. However, the tool sits within a wider AI development effort at WordPress, supported by a new AI Team and a plugin-first approach. For now, therefore, Telex appears to offer a way for developers and businesses to explore how prompt-based tools could be used inside existing WordPress workflows, without relying on external platforms or hosted AI builders.

What Does This Mean For Your Business?

Telex essentially gives users a faster way to create modular WordPress features using natural language prompts. By generating standard plugin files that can be tested, reviewed, and installed like any other block, it offers a practical route to exploring AI-assisted development without changing platform or setup.

For UK businesses already using WordPress, this could simplify everyday site updates and reduce the time spent on routine layout tasks. It may also allow smaller teams to create and test new features without relying on external developers, provided there is still a review process in place to catch errors or security issues. Larger organisations, especially those in regulated sectors, are likely to value the ability to track changes and control what gets deployed.

Telex also points to wider changes across the WordPress ecosystem. Agencies may begin using it to accelerate early design work, freeing up developer time for more complex builds. At the same time, plugin developers may face new pressure to show the added value of their products if standard blocks become easier to generate on demand.

The real test will be how well Telex performs in production environments, across different themes and hosting setups. Its usefulness will depend not just on speed but on consistency, security, and whether it can meet accessibility standards. For now, it gives WordPress users a way to experiment with AI-driven development using familiar tools, while keeping full control over hosting and site management.

Tech News : Court Orders Restoration Of WordPress.org Access

Posted on by Paul Stradling

A California district court has ruled that Automattic, the parent company of WordPress.com, along with its CEO, Matt Mullenweg, must immediately restore WP Engine’s access to WordPress.org.

Follows Power Struggles in WordPress Community

This decision follows a heated legal battle that has pitted two prominent players in the WordPress ecosystem against each other, raising critical questions about the dynamics of power, open-source contributions, and fairness within the community.

Who Are The Parties Involved?

Automattic was founded by Matt Mullenweg in 2005 to commercialise WordPress, the open-source content management system (CMS) he co-created in 2003. Today, WordPress powers more than 40 per cent of websites globally, making Automattic a dominant force in the CMS industry. The company manages WordPress.com and is intricately linked to WordPress.org, which hosts a vast repository of themes and plugins essential to WordPress users.

Despite the ‘WP’ in the name WP Engine, it is, in fact, a third-party hosting provider that specialises in managed WordPress solutions. Established in 2010, the company supports developers and businesses by offering optimised hosting services and technical expertise. A central part of WP Engine’s appeal lies in its popular Advanced Custom Fields (ACF) plugin, which has become a staple for developers seeking to customise WordPress websites efficiently.

What Is The Legal Battle About?

The dispute between the two erupted publicly in September this year when Automattic’s Mullenweg accused WP Engine of undermining the WordPress community, reportedly calling the company a “cancer to WordPress” at an event. Shortly after this, Automattic banned WP Engine from accessing WordPress.org, effectively blocking its ability to manage and update the ACF plugin. To further complicate the situation, Automattic created a separate version of ACF, called Secure Custom Fields (SCF), by copying and modifying its code. At the same time, Automattic continued its campaign against WP Engine.

WP Engine responded by filing a lawsuit, accusing Automattic and Mullenweg of extortion and abuse of power. The company argued that the ban inflicted immediate and irreparable harm, disrupting business operations and tarnishing relationships within the WordPress ecosystem.

The Court’s Ruling

In the recent ruling, Judge Araceli Martínez-Olguín granted a preliminary injunction ordering Automattic to reinstate WP Engine’s access to WordPress.org and its associated resources. The injunction essentially compels Automattic to restore WP Engine’s control over the ACF plugin, take down a webpage tracking departing WP Engine customers, and remove a controversial checkbox requiring WordPress.org users to declare non-affiliation with WP Engine.

In her ruling, Judge Martínez-Olguín noted that Automattic’s actions were designed to disrupt WP Engine’s business relationships, citing the “Defendants’ role in helping that harm materialise through their recent targeted actions toward WP Engine, and no other competitor, cannot be ignored.” The judge dismissed Automattic’s argument that WP Engine’s reliance on WordPress.org was self-imposed, emphasising the deliberate nature of Automattic’s actions.

What the Ruling Means

For WP Engine, the decision is a significant win, as it restores critical access to the tools and platforms integral to its services. The company has, therefore, welcomed the ruling, expressing gratitude to the court for ensuring “stability and security” within the WordPress ecosystem. WP Engine has also highlighted the broader implications, stating that the ruling benefits not only WP Engine but also its customers and the developer community reliant on WordPress.org.

The reinstatement of ACF access allows WP Engine to resume updates and maintain the plugin’s reputation among users. This move is expected to strengthen WP Engine’s position in the competitive hosting market.

Automattic, on the other hand, has vowed to continue its legal battle, with a spokesperson asserting that the ruling is merely a temporary measure to preserve the status quo. The company has stated that it intends to file counterclaims and is confident of achieving a favourable outcome at trial. Automattic also appears to have framed its actions as a defence of the open-source ecosystem, a stance that could resonate with some segments of the WordPress community.

However, the injunction places immediate constraints on Automattic’s ability to unilaterally enforce policies against competitors. The removal of its anti-WP Engine checkbox and customer-tracking webpage is really a setback in its campaign against the hosting provider.

What About The WordPress Community?

The case has highlighted tensions within the WordPress ecosystem, particularly around the balance of power and the responsibilities of for-profit entities contributing to open-source projects. Mullenweg’s criticism of WP Engine centred on what he perceived as insufficient contributions to WordPress development, a claim WP Engine disputes.

The ruling could, in fact, set a precedent for how disputes are handled within the WordPress community and shows the importance of fair play and collaboration among stakeholders, particularly in an ecosystem that thrives on collective contributions.

The Broader Implications

This legal battle has also attracted attention from competitors and industry analysts. This is because, for competitors, the outcome could redefine the rules of engagement in the WordPress ecosystem, and may require a reassessment of relationships with Automattic and WordPress.org. For the broader market, the ruling highlights the vulnerabilities inherent in relying heavily on a single platform or ecosystem.

Also, the case raises questions about the governance of open-source projects. For example, critics have argued that Automattic’s close association with WordPress.org creates a conflict of interest, while supporters maintain that its stewardship is vital to WordPress’s continued success.

The Road Ahead

As the legal proceedings continue, the tech industry will be closely watching the next steps from both parties. Automattic’s counterclaims and the broader trial could reshape perceptions of leadership and collaboration within the WordPress community. Meanwhile, WP Engine’s focus will likely remain on strengthening its position and rebuilding trust with its users and partners. This evolving saga, therefore, serves as a reminder of the complexities in navigating open-source ecosystems where commercial and communal interests intersect.

What Does This Mean For Your Business?

The court’s decision is a pivotal moment for the WordPress ecosystem, and highlights the tensions that can arise when commercial interests collide with the principles of open-source collaboration. For WP Engine, the ruling represents not just a legal victory but also a reaffirmation of its role within the WordPress community. By regaining access to WordPress.org and control over the ACF plugin, the company can focus on rebuilding its reputation and continuing to serve its users and developers effectively. This will undoubtedly strengthen its standing in a competitive hosting market.

For businesses relying on WordPress websites, the ruling highlights the fragility of relationships within the WordPress ecosystem and the potential risks of platform dependencies. If disputes like this escalate further or lead to service disruptions, it could impact website functionality, updates, and security – i.e. issues that are critical for businesses operating in competitive online environments. Businesses may now decide to be more cautious in selecting hosting providers and plugins, favouring those with stable access to WordPress.org resources. The case also shows the importance of diversifying digital strategies and reducing reliance on single ecosystems to mitigate such risks.

For Automattic, the injunction poses a challenge to its authority within the ecosystem and raises questions about its stewardship of WordPress.org. While the company maintains that its actions were aimed at protecting the open-source project, the ruling casts doubt on its methods and intentions. The removal of public-facing measures targeting WP Engine may signal a need for a recalibration of its approach, but Automattic’s commitment to contesting the case suggests that this battle is far from over.

The implications of this case extend well beyond the immediate parties involved. For the wider WordPress community, the dispute has brought to light critical issues regarding fairness, governance, and the responsibilities of key players in an open-source environment. The ruling also serves as a reminder that dominance within an ecosystem comes with the obligation to foster collaboration and maintain balance, rather than exert unchecked influence.

As the legal proceedings continue, this case will likely serve as a precedent for how disputes within open-source projects are managed. It has already sparked broader discussions about the vulnerabilities of relying on centralised platforms and the need for clear governance structures in ecosystems where commercial entities play significant roles.

Featured Article : WordPress At War!

Posted on by Paul Stradling

Following a (very public) recent spat between WordPress founder and Automattic CEO Matt Mullenweg, and WP Engine, we look at what’s happened and why, and what the effects have been WordPress users.

WordPress and WP Engine 

To better understand the story, it may be a good idea to first look at the two sides in the dispute – who (and what) they are, and why they’re different.

WordPress

Most people are likely to be familiar with WordPress, the open-source content management system (CMS) that now powers over 40 per cent of websites globally. It was founded in 2003 by Matt Mullenweg and Mike Little as a fork of another blogging tool called b2/cafelog. Since its blogging platform beginnings, it has evolved into a versatile CMS and is used for everything from personal blogs to large corporate websites. WordPress.org is the official website where the open-source version of WordPress can be downloaded and is maintained by the broader WordPress community. WordPress’s co-founder Matt Mullenweg is also now the CEO of Automattic, the company behind WordPress.com, a commercial arm that provides hosting services for WordPress users. Mullenweg also founded (in 2010) the WordPress Foundation, which is a non-profit organisation to promote and protect the WordPress brand and support the open-source project’s development.

WP Engine 

WP Engine, on the other hand, is a managed hosting service specifically designed for WordPress websites. Founded in 2010 by Jason Cohen, and currently led by Heather Brunner (the company’s CEO and chairperson), WP Engine offers specialised hosting services, focusing on performance, security, and support for WordPress-based websites.

The key distinction between the two is that WordPress is an open-source software project managed by a community, while WP Engine is a commercial entity offering specialised hosting for WordPress sites, i.e. it is distinct from (and not officially associated with) WordPress – the brand is not part of WordPress. Automattic, led by Mullenweg, is closely tied to the development of WordPress, whereas WP Engine builds its business upon optimising the WordPress experience for its customers without contributing significantly to its core development.

Other Players 

One other player mentioned in the recent dispute is Silver Lake, a global private equity firm that specialises in technology investments. Silver Lake invested $250 million in WP Engine back in 2018, significantly boosting WP Engine’s financial capacity to grow its hosting business within the WordPress ecosystem. However, Silverlake doesn’t have a direct relationship with WordPress, but has been criticised (as detailed below) by WordPress’s Matt Mullenweg.

The Recent Conflict – A Quick Blow-By-Blow Breakdown

The current, ongoing feud between Matt Mullenweg, CEO of Automattic, and WP Engine has taken the WordPress community by storm. The dispute began on September 20 when Mullenweg publicly lambasted WP Engine, accusing the company of profiteering from WordPress while contributing little to its open-source ecosystem. What followed has been a series of escalating accusations, legal actions, and heated exchanges, leaving WordPress users and businesses concerned about the impact on their websites and the future of the platform.

September 2024 – Mullenweg Calls Out WP Engine 

The feud came to light when Mullenweg, during his keynote address at the WordCamp US event in September 2024, sharply criticised WP Engine. He labelled the company a “cancer” within the WordPress ecosystem, accusing them of using the open-source platform for commercial gain without giving back in a meaningful way. Specifically, Mullenweg pointed out that WP Engine only contributes around 40 hours per week towards WordPress development, compared to Automattic’s substantial 4,000 hours. His most significant grievance was that WP Engine had allegedly disabled core WordPress features, such as post revisions, to reduce their hosting costs, thus compromising user experience for profit.

WP Engine’s Response 

In response, WP Engine released a blog post defending its track record, highlighting over a decade of contributions to the WordPress community. They pointed to innovations such as their headless WordPress solution and their support for modern web frameworks like Faust.js and WPGraphQL, emphasising their role in expanding the platform’s capabilities.

Cease-and-Desist Letters 

The situation worsened when WP Engine sent a cease-and-desist letter to Automattic, accusing Mullenweg of making false claims and threatening the company with legal action. WP Engine argued that Mullenweg’s statements were defamatory and could damage their business. They also stated that Mullenweg’s criticism was rooted in their refusal to pay Automattic a significant sum of money, which Mullenweg had allegedly demanded for the use of WordPress trademarks. According to WP Engine, they were operating within the guidelines of the WordPress Foundation’s trademark policy and did not require such a licence.

Automattic responded by issuing its own cease-and-desist letter, accusing WP Engine of trademark misuse and unfair competition. Automattic claimed that WP Engine had been benefiting from the WordPress brand without proper authorisation and that their use of terms like “WordPress” and “WooCommerce” in their marketing was misleading to customers.

Statements 

Throughout the conflict, both Mullenweg and WP Engine have been vocal in defending their positions. Mullenweg, in a blog post titled “WP Engine is Not WordPress,” accused the company of butchering the platform for profit. “What WP Engine gives you is not WordPress,” Mullenweg wrote, emphasising that WP Engine’s practices were misrepresenting the platform and harming users by removing essential features like post revisions. He reiterated this during his WordCamp US speech, where he criticised private equity involvement in the WordPress ecosystem (referring to Silverlake – the company that invested in WP Engine in 2018), stating, “Silver Lake doesn’t care about your open-source ideals, it just wants a return on capital.” In short, Mullenweg’s criticism of WP Engine, particularly about its focus on profits over open-source contributions, also targets Silver Lake, implying that their primary interest is financial returns, rather than supporting the open-source community.

In contrast, WP Engine pushed back against these claims, arguing that their investments in the WordPress ecosystem go beyond contributing to the core software. WP Engine has highlighted its efforts to support the wider WordPress developer community and create innovative tools for businesses, noting that their business model is entirely compatible with the platform’s open-source ethos.

The Impact on WordPress Users 

For businesses that rely on WP Engine for hosting, the dispute has raised several concerns. One immediate consequence was WP Engine’s temporary ban (September 25) from accessing WordPress.org resources, including essential software updates. This move (by Automattic) led to some operational challenges for users, who were unable to receive timely updates for their websites – sites using WP Engine’s solutions couldn’t install plug-ins or update their themes. Also, WP Engine customers couldn’t access security updates, thereby potentially leaving them vulnerable. WP Engine has reassured customers that they are working to resolve the issue and continue providing a stable service. WordPress.org has since lifted the ban on hosting provider WP Engine (until October 1).

Trademark A Key Issue 

Shortly after banning WP Engine from WordPress.org, Mullenweg stated (in a blog post) that trademarks are the main issue. Automattic alleged that WP Engine has built its $400 million+ revenue business upon unauthorised use of its WordPress trademark (Automattic says it has the exclusive commercial rights for from the WordPress Foundation for this trademark). Automattic says, for example, it has been trying to sign a licensing deal with WP Engine and has offered WP Engine the option to pay a direct licensing fee or make in-kind contributions to the open-source project.

Divided Opinion 

Meanwhile, the broader WordPress community has been left divided. Some developers and users have voiced support for Mullenweg’s stance, arguing that WP Engine’s commercial approach undermines the open-source principles on which WordPress was founded. Others, however, believe that Mullenweg’s comments were unnecessarily inflammatory and that WP Engine’s contributions to the platform, particularly in the area of headless WordPress solutions, have been valuable for the community.

So, Where Are We Now? 

As of late September 2024, the situation remains unresolved, with both parties engaging in a public and legal back-and-forth. While no lawsuits have yet been filed, WP Engine’s legal team has hinted at potential claims of tortious interference and unfair business practices. The WordPress Foundation, which manages the platform’s trademarks, has also updated its policies, seemingly targeting WP Engine’s business practices. Mullenweg, for his part, continues to stand by his comments, reinforcing his belief that WP Engine is not operating in the best interests of the WordPress community.

What Does This Mean For Your Business? 

For UK businesses that rely on WordPress, this conflict brings several important considerations. Firstly, if you are using WP Engine as your hosting provider, it’s essential to stay updated on the potential legal outcomes and any changes to the service that may result from this dispute. The ban from WordPress.org resources, even though temporary, affected site performance and security for some users, so keeping an eye on WP Engine’s communication with customers going forward may be critical.

From a broader perspective, this feud highlights the tension between open-source ideals and commercialisation. While WordPress remains free and open-source, hosting providers like WP Engine have built profitable businesses on top of it. Mullenweg’s criticism raises questions about how much companies should contribute back to the ecosystem from which they benefit.

For competitors, this may create an opportunity. Hosting providers who are more aligned with WordPress’s open-source principles could attract users disillusioned with WP Engine’s business practices. For businesses looking to build or maintain WordPress sites, it may be worth exploring alternatives that contribute more significantly to the platform’s long-term sustainability.

This dispute, therefore, serves as a reminder that even in the open-source world, commercial interests can sometimes lead to conflict. Whether you are a developer, a business owner, or simply a WordPress user, keeping an eye on these developments is crucial for making informed decisions about your website’s future.

Tech News : Yoast Gets AI Optimize (Yes, with a ‘Z’)

Posted on by Paul Stradling

Yoast, the company behind the popular SEO plugin for WordPress, has announced the introduction of ‘Yoast AI Optimize’ feature which is designed to simplify SEO tasks by providing AI-powered optimisation suggestions for content at the click of a button.

Helps With Essential SEO Factors 

Specifically, ‘Yoast AI Optimize’, which is only available to Yoast SEO Premium customers, focuses on enhancing ‘Keyphrase in Introduction’, ‘Keyphrase Density’, and ‘Keyphrase Distribution’, which are essential SEO factors.

How It Works 

To use the new feature within the WordPress editor, users open their post or page and go to the Yoast SEO sidebar. For assessments like ‘Keyphrase in Introduction’, ‘Keyphrase Density’, and ‘Keyphrase Distribution’, there’s a sparkly icon next to them in the SEO analysis section. Clicking this icon triggers the AI to generate optimisation suggestions for the selected content. Users can then choose to either apply the AI’s suggestions to the content or dismiss them.

The Benefits 

Whereas the popular (regular) Yoast plugin, which currently has more than 13 million active installations, requires the user (who may not be knowledgeable about SEO) to manually make SEO adjustments, the new feature does it all with just a few clicks, and the changes are made automatically throughout the text. This saves time, streamlines the SEO process, removes complexity, and democratises effective SEO – i.e. making it accessible for all content creators, freelancers, and marketers.

Kimberley Cole, General Manager Europe at Newfold Digital, parent company of Yoast, said of the new feature: “With Yoast AI Optimize, users can save time and energy by tapping into SEO powered by AI and unlocking the full potential of their website, blog, online store and more.” 

In terms of how the new feature may improve Yoast’s market position, Kimberly Cole said: “As AI-infused technology evolves, Yoast, the world’s largest SEO plugin, remains at the forefront by combining our in-house SEO expertise with the technology of today to provide the highest quality SEO tools that simplify and elevate the user experience for all website owners. By improving search rankings, SEO drives targeted traffic, boosts credibility and helps businesses market their products and services more effectively in an increasingly competitive digital landscape.”   

Drawbacks 

With something that sounds this good, there must some drawbacks! Some of these include :

– It is currently only available for texts up to 1000 words, thereby restricting its usability, especially for users with longer content or those using different editors.

– Users cannot accept just part of a suggestion but must accept ‘all … or none’. This reduces flexibility and customisation options and may force users to accept changes they don’t fully agree with.

– The feature is only available for the Block editor and users can only optimise content in the Paragraph, Heading, List, and Table blocks. Content from other blocks can’t be optimised.

– ‘Yoast AI Optimize’ is currently only available for the following SEO checks: Keyphrase in Introduction, Keyphrase Density, and Keyphrase Distribution. For Keyphrase Density, it can only support the case in which the key phrase is underused. If the key phrase is overused, the ‘Yoast AI Optimize’ feature can’t be provided.

Currently in Beta 

‘Yoast AI Optimize’ is currently in Beta and to access it, (Yoast SEO Premium) customers must have updated to the most recent version, 23.2, and granted consent to use AI.

What About Yoast’s Competitors? 

Yoast faces several strong competitors in the SEO plugin market, many of which have AI-powered features similar to (or even more advanced than) Yoast’s AI offerings. For example:

– Rank Math is a highly recommended alternative with robust automation, allowing users to optimise content for multiple keywords and perform full SEO audits. It integrates AI to assist with schema markups and offers a content analysis tool that automates SEO tasks like generating meta titles and descriptions.

– All in One SEO (AIOSEO), another major competitor, provides AI-powered keyword ranking and content decay analysis, helping users track and optimise older posts. Its AI features also extend to automated link suggestions and meta generation, making it highly efficient for content creators.

– SEOPress includes AI capabilities for generating SEO metadata (like meta descriptions) based on the content. It also offers white-label options, making it popular among agencies. SEOPress provides a clean, user-friendly interface while handling complex tasks like generating sitemaps and managing structured data.

– SEMRush, although broader in scope, includes AI-powered tools like its SEO Writing Assistant that helps optimise content for readability and search engine performance. It offers AI-driven content suggestions and meta generation, making it a comprehensive tool for both SEO and content creation.

What Does This Mean For Your Business? 

The introduction of ‘Yoast AI Optimize’ could prove to become very helpful to businesses aiming to improve their website’s SEO, particularly those that lack technical expertise in this area. With AI taking over many of the manual and time-consuming SEO tasks, businesses can now streamline their optimisation processes. This means that even small businesses and individual content creators may now be able to implement sophisticated SEO practices without having to invest heavily in SEO expertise or tools. This AI feature could enable them to optimise content quickly and more effectively, which could result in better search rankings, increased traffic, and ultimately, higher conversions and sales.

For existing Yoast SEO Premium users, this new feature could enhance the value of their subscription. It simplifies SEO further by automating tasks like keyphrase management, allowing users to focus more on content creation rather than manual optimisation. However, while the feature is currently limited in terms of functionality and word count, its potential is clear. As the AI develops, users can perhaps expect greater flexibility and wider applications, which would only enhance its appeal.

For Yoast, this innovation strengthens its competitive edge in a rapidly evolving market. By incorporating AI, Yoast is hoping to position itself as a forward-thinking leader in SEO, and ensure it adds value and retains users by staying at the forefront of search engine optimisation trends. However, the competition is fierce. Competitors like Rank Math and AIOSEO are also leveraging AI to offer advanced features, and the race to provide the most user-friendly, efficient, and powerful SEO tools is heating up.

More broadly, this is just another example of how AI is transforming the digital landscape. From content generation to SEO optimisation, the integration of AI across digital tools is changing how businesses manage their online presence. The growing influence of AI within SEO can now empower businesses to hopefully achieve better results faster, and it raises the bar for SEO tools in general. That said, ultimately, search engine algorithms (especially Google’s), control how effective SEO efforts are, and if all users started using effective AI-powered SEO tools, this would perhaps require another algorithm change. Therefore, how well Yoast (and other SEO tools) keep up with changes made by search engines (which use AI themselves) will have a bearing on how effective they are.

That said, with AI SEO tools like Yoast offering a good chance to improve ranking, for businesses, this means staying informed about the latest AI-powered tools may now be essential to maintaining a competitive edge in their digital marketing efforts.