Yoast SEO WordPress Plugin Adds Support For LLMs.Txt via @sejournal, @martinibuster

Yoast announced the addition of llms.txt capability to both the premium and free versions of their SEO plugin. Users can now add llms.txt files to their sites to future-proof them for AI search engines.

LLMS.Txt

llms.txt is a proposal for a new standard that will enable large language models (LLMs) to access a publisher’s content in a way that is easy for LLMs. The main content is presented to LLMs without advertising and other page elements that target humans.

The proposed standard uses markdown in pages with the .md file name, duplicates of existing pages that only contain the main content. Google’s John Mueller has alluded to the inherently untrustworthiness of the proposed standard because there’s nothing to stop unscrupulous SEOs from adding whatever they want to the LLMs.txt web pages.

It simply makes more sense to just grab the content from the normal web pages. Additionally, LLMs aren’t currently looking for those pages and it’s quite likely that they will continue to use the normal web pages.

Yoast’s announcement states:

  • “Helps AI tools understand your site better: Guides large language models like ChatGPT and Gemini to your most relevant content.
  • Highlights your key content automatically: No need to decide what to include. Yoast SEO detects your most important and recently updated pages.
  • No technical setup required: The file is generated and refreshed weekly, no coding or manual work needed.
  • Future-proof your website for AI search: Make sure your site is ready for how people find information today, and tomorrow.
  • Built into Yoast SEO, free for everyone: Available in one click, no upgrade needed.”

Read the Yoast SEO announcement here:

Future proof your site for LLMs llms.txt

Featured Image by Shutterstock/Cagkan Sayin

WordPress Co-Founder Mullenweg’s Reaction To FAIR Project via @sejournal, @martinibuster

The Linux Foundation recently announced the FAIR Package Manager project, an open-source, distributed WordPress plugin and theme repository that decentralizes control of the repository. A distributed theme and plugin repository became a priority for many in the WordPress community after Matt Mullenweg took control of certain paid premium plugins and created free versions from them, in addition to removing access to the free versions of the original plugins.

The Linux announcement, made on Friday, June 6, came during the middle of WordCamp Europe, all but assuring that it would be a topic of discussion at the three-day conference.

According to the Linus foundation announcement:

“…The FAIR Package Manager project paves the way for the stability and growth of open source content management, giving contributors and businesses additional options governed by a neutral community…”

It was inevitable that Matt Mullenweg would be asked about it and that’s what happened, twice. Mullenweg was gracious about answering the questions but he was also understandably cautious about it, given that it had only been less than 24 hours since the FAIR project had been announced.

Initial Reaction To Project FAIR

The first question was asked early in the question and answer period, where Mullenweg was asked how he sees such initiatives coexisting with WordPress and asking what he sees as the ideal outcome.

Mullenweg expressed cautious optimism, praising the open source nature of WordPress by saying that that’s the point of open source, that it can coexist with everything. But he also was reluctant to say much more. He did seem a little annoyed that the FAIR project was created “in secret.” I don’t know the extent of whether the FAIR project was created in secret but it did seem as if the Linux foundation essentially ambushed WordPress and WordCampe with their announcement.

Mullenweg answered:

“…I think that’s part of the beauty that something like this can be written with the APIs that WordPress has. I don’t know if I want to comment too much further on it just because kind of just found out about it last night, there hasn’t been that much time. There’s a lot of code and uh and complexities.

You know, I do wish if the team did want to collaborate or the team says we want to be transparent and everything. But it did sort of drop as a surprise. It was worked on in secret for six months. But we can work past that and look at it. “

Do Users Want A Federated Repository?

Mullenweg next turned the question away from what he might think about it and asked if this is something that WordPress users would want. He also explained the immensity of the undertaking a decentralized system for the repository.

He continued his answer:

“I do think things we need to keep in mind are, you know, what are users asking for?

What are the challenges they’re facing around finding the right things, knowing it’s secure, getting updates? You know the stats around how many sites that are hacked are from out of date plugins. Those are things that are top of my mind for the plugin directory and so the trust and safety elements of that for the.org directory.

…So we’re now up to 72,000 plugins and themes. This is about 3.2 terabytes, like zip files. That’s not counting all the SVN history and everything like that. So there’s a there’s a lot of data there, which also we need to make sure, like if 500 mirrors are set up and they’re all sucking down the directory like, that could DDOS us.”

About twenty minutes later someone else stepped up and asked the question again, sharing about her long history with WordPress and her opinion of why the FAIR project may be useful.

She said:

“I’ve been contributing to the communication team for 14 years and contributing to plug in review team for a couple of years and my whole work in documentation was serving the user every decision we made we made was to serve user. And in plugin review team we also include plugin authors So everything we do we do for plugin authors and users to make their lives easier and better.”

Next she offered an explanation of why she thinks the FAIR project is good for plugin authors and users:

“So the Fair project is actually federated and independent repository of trusted plugins and teams. And it is under the Linux Foundation. So that means a lot when it’s under the Linux foundation.

And what it means for users and plugin authors and team authors is actually making their lives easier and better, more secure. It makes all the products more discoverable and also developers can choose their source. Where are they using their supply chain from.

But also, it is helping WordPress.org because these are mirrors so it will reduce the load from WordPress.org for every update and all of that.

…I don’t know if you trust me, but it seemed to me that this aligns with the idea of having users and developers first in mind. Would you as wordpress.org consider collaborating with this project?”

Mullenweg’s answer was cautious in tone, giving the impression that he didn’t know much about the FAIR project aside from the public announcement made by the Linux Foundation.

He answered:

“Of course we consider everything, but even in what you said, I think there’s a lot of challenges to it. So for example, right now, a supply chain attack needs to breach wordpress.org which has never been hacked.”

At this point loud laughter rang out in the hall, catching Mullenweg by surprise.

He then continued, offering an idea of the complexity of a federated theme and plugin repository:

“The… now all of a sudden there is N places that could potentially be compromised that you know there’s ways to do that, many ways. There’s N places with uptime issues.

And… it makes it much more difficult for, I don’t know if it’s actually better for WordPress.org, because it makes it much more difficult to do things like rollouts, phased rollouts, or let’s say we get plugin authors the ability to ship to 5% of users and then see what happens, which means we also need things being checked back and then we can roll out to the rest, which is something that I’ve heard a ton of plugin authors ask for.

It will break all the analytics and stats that we provide and also that we internally …use to make decisions, for example which versions of PHP we support…

So I think that it’s uh a big part of why WordPress is where it is today is because of the infrastructure and the sort of feedback loop that we get from wordpress.org.

Also, the trust that we’re able to engender by having that be a resource. When you look at marketplaces, people aren’t asking necessarily for I want it to be downloaded from more locations.

  • They’re asking for how do I know this is trustworthy?
  • How do I know these reviews are real?
  • Who’s moderating?
  • Who’s checking the IP’s on these different reviews?
  • What’s the plug in rating?
  • What’s the compatibility for it?
  • How does it, compatible with my other plugins?

These are things I’m hearing from users, not I need it hosted in a different place. This is one example.

And again, I don’t want to get too far into it because I want to read the code. I want to dive more into it. I want colleagues to look at it. So, I think it’s kind of premature, less than 24 hours in to say like we’re going to …this or not.”

At this point Mullenweg praised the fact that people were being constructive rather than arguing.

He continued:

“But I do think it’s awesome that people are shipping code versus just arguing or talking or writing blog posts. I think that’s a pretty productive way to sort of channel possible disagreements or anything, and then we can see how it looks. Might be a super niche thing that a few people use, maybe one or two hosts or it might be something that maybe there’s something in there that becomes …popular.”

Then he returned to listing things that still need to be looked into, trying to give an idea of how complex creating a decentralized repository is.

Mullenweg continued:

“Like something that we probably need to do in the plug and review is something about these admin banners right, now how is that enforced in a distributed FAIR system?”

Mullenweg then asked the person asking the question how she would solve all of those problems to which she answered that she’s not the smartest person in the room but that this is something to be collaborated on and then she tossed off a joking remark that maybe they can ask ChatGPT, which drew laughter and applause, breaking the tension of the moment and ending the question on a light note.

Watch the question and answer session in about the 8 hour mark of the video:

WordPress Plugin Platform Offers Proactive Security Scanning via @sejournal, @martinibuster

WordPress security company Patchstack announced a new security tier called managed Vulnerability Disclosure Program platform (mVDP), which offers both human and advanced AI plugin reviews to help plugin developers keep their software resistant to vulnerabilities and provide greater trustworthiness.

One of the biggest problems with WordPress is vulnerabilities from third-party plugins. An enormous amount of plugins are discovered with vulnerabilities every day and it doesn’t matter if the developer is a one-person shop or a large multinational organization, vulnerabilities happen and when they do user trust goes down, especially if it happens on an ongoing basis.

PatchStack offers a way for software developers to build trust with their users with two tiers of protection, a free and a paid tier that help plugin developers focus on creating high quality plugins that are free from vulnerabilities.

With more and more software being generated by AI, we’re seeing a significant increase in new vulnerabilities and an equal increase in AI-generated security reports, which makes managing the security of plugins more important than ever.

Patchstack offers a standard managed VDP and a new Security Suite that costs $70/month.

According to the announcement, the new paid tier comes with the following benefits:

“$40 worth of AI tokens for code security reviews per month

Team management feature with 5 seats included

Discussion board for direct communication with the reporting researchers

AI code review and human research
The new Security Suite tier combines the best of both worlds. Your plugins will receive boosted visibility (100% AXP bonus) in the Patchstack Alliance ethical hackers community, which encourages security researchers to report significantly more bugs and help plugins fix more vulnerabilities faster.

Additionally, our AI code review tool can scan through your entire codebase to find WordPress-specific security issues and highlight potential improvements. We are currently launching this in beta, but we’ll have much many releases to share in the coming months.”

Security Suite customers will receive security recommendations from their internal security experts, helping developers be proactive about building safe to use WordPress plugins.

Read more at Patchstack:

NEW: Patchstack AI code review tool and Security Suite for plugin vendors

Featured Image by Shutterstock/STILLFX

WordPress Shares How AI May Play Stronger Role In Web Publishing via @sejournal, @martinibuster

WordPress interviewed a member of the newly formed WordPress AI Team who shared how AI can be integrated into WordPress, outlining a future in which the platform supports AI agents and content consumption while enabling new kinds of functionality. To achieve this, the team is focusing on developer tools that allow third-party developers and services to connect AI systems to WordPress without embedding generative features directly into core.

The interview was with James LaPage, the AI engineering lead at Automattic and one of the leaders of the newly announced WordPress AI Team.

Screenshot of James LaPage of WordPress AI Team

Timing Of AI Team Announcement

Many competitors, from private closed systems like Wix, Duda, and Shopify to open-source platforms like Drupal CMS, have various AI integrations built in. Third-party WordPress plugins such as Yoast, Rank Math, and Elementor also feature AI integration. WordPress hosts including Bluehost, 10Web, and Automattic’s commercial WordPress.com platform offer AI-powered site builder functionality. A case could be made that WordPress is late to the AI party.

James LaPage of the WordPress AI Team argues that a cautious approach was necessary due to the fast rate of changes within AI. This makes sense given that Agentic AI (AI agents that research the web on behalf of humans), is just beginning to gain adoption.

LaPage explains these realities early in the interview:

” I’ve wanted an AI team for a long time. I think right now actually was the perfect time to launch it because the …generative AI boom and the technology running and powering that boom is actually like pretty recent, and it’s changing so rapidly and only recently have we seen a lot of centralization around, for example, how these models work, how they consume information, how you interact with them, how you connect them to software.

So we’ve come to a point right now where a project like WordPress, which is massive and humongous and incredibly important on the web, is able to begin actually exploring this type of stuff because it isn’t changing from under our feet in the way that it was a year ago or two years ago.

And a good way to point that out is there was a Make WordPress post about AI two years ago that Ann published, and a lot of us had commented on it and it was really like, Yeah, this is awesome.

And as you read through those comments, you can kind of see everybody being excited but not really knowing where to push that excitement and point and say do this or do this or do this and we finally get to the point now where this team can say this is what we want to be doing and there can be real understanding of why we’re doing that and prior art in terms of how things actually work.”

WordPress As A Fully AI-Accessible System

LaPage was asked what an AI-friendly WordPress might look like in three years. He share a vision of WordPress as a foundational framework for AI agents, like a platform where tools, content, and interactivity are natively exposed to be dynamically interacted with and consumed.

He explained:

“I think if WordPress is able to become something that we can use AI to consume information from and build functionality for, that is a lovely spot and position it can be in. And it’s already almost in that spot. And if we can make it more accessible to AI, then I think that we are able to maintain its position on the open web as this place that you express yourself digitally.

…What I would love to see is WordPress be this platform where people continue to digitally express themselves. And I think that expression becomes more important in this era where more and more stuff will be consumed by chatbots and you’ll be speaking with AI and you’ll be doing all these different things.

Having the ability to express yourself and also be able to express yourself in ways where you couldn’t before because you couldn’t develop this crazy idea that you have in your head, or you have a crazy idea in your head, you don’t even know how to do it… Like, that type of stuff I would love to enable through the work that we do on this AI team.

So maintaining the position of yes, it’s really important to have this digital presence on the Internet. It’s very important not to subscribe only to these walled gardens, like the social media platforms and the AI chatbots, but instead have this lovely blossoming of expression on the web as WordPress enabled in its beginnings as well.

Like, this was something that it was very difficult to publish your thoughts and then it wasn’t. Let’s do it again. But let’s do it with AI.”

Technical Description Of Future Of AI Innovation With WordPress

James LaPage went into a description of what MCP Model Context Protocol is and the role it plays with how AI can interact with and transform WordPress into like a framework for being able to accomplish a wider range of things on the web.

“So MCP is model context protocol. This is an open protocol and standard. So it’s important to focus on that. It’s a standard. It’s not a technology package that’s built in Python that you go and install. You can build things around this standard and what the standard does is define how software can expose functionality to AI, in the simplest definition.

So you have the ability to define tools which are ways that you expose, hey, you can do this or you can read this on my piece of software. You can look at the piece of software as WordPress and then you also have the method of providing those tools to the client, which is something like Claude or Cursor or another AI agent for example, that can then read those tools and use them however they want, and it’s up to the folks building the actual systems to implement the protocol properly and to build the actual agents and the tools and everything that comes with it through MCP.

So when you look at how we enable AI within WordPress and outside of WordPress, we’ve had similar needs at Automatic …and other folks in the industry have had needs to define how AI speaks to specifically in WordPress different plugins and different functionality within the core software and the Feature API is the answer to exposed features of WordPress and features of plugins in a WordPress specific way to AI.

And this is intended to almost be something that goes into WordPress core, allows plug-in developers to expose this functionality to AI within WordPress in this unified way, similar to how I explained MCP. But do it in the WordPress way allows you to plug into the capabilities and the permission callbacks and the REST API aliases and all of these different WordPress-focused things, which means you’re not reinventing the wheel on WordPress, you’re simply exposing functionality in this unified way, which then it’s up to a developer to say well, now I have this list of functionality, list of things I can do with WordPress resources, I can read with WordPress, let’s build an agent or let’s build a media generation playground or let’s build a single shot, single click button that generates a whole bunch of stuff and use that features API to do so.

And when you think about how WordPress can speak with software outside of itself and almost become that framework for the functionality that plugins bring in, the data that the database stores and custom post types and posts, then you kind of start infusing the ideas behind Feature API and MCP.”

You Can Become Involved

Something that many WordPress users might not be aware of is that every user and interested party can contribute to WordPress to help shape it to be what they need it to be. Even a user who doesn’t know how to program can still influence WordPress by expressing their opinions to WordPress.

LaPage invited the wider WordPress community to get involved with providing feedback to the AI Team.

He said:

“Immediately, the way to get involved is through the make.wordpress.org/AI blog. There are several posts popping out. The most recent one as we’re recording being the hallway hangout. This probably best way to be plugged in is through the Core AI Slack, in the Make WordPress Slack. Both of those things are linked throughout the make.wordpress.org/AI site and the news announcements and everything else, so that’s how you can get involved right now in terms of contributing into the future.

A big focus of the group is to get to a very solid road map with explicit instructions and directions on how you can contribute that are likely going to be several projects that work together that we build and maintain. There’s likely going to be many other focuses around AI that we want to address, and we’re going to try to make it as clear as possible as to how you can get involved and how you can actually go and help make WordPress what it needs to be in in this AI era.

So right now, join the the core AI Slack, check out the blog posts and join the hallway hang out on Monday to really get in on the ground floor.”

Watch the WordPress interview with James LaPage here:

Featured image/Screenshot by author

WordPress Performance Team Releases New Plugin via @sejournal, @martinibuster

The WordPress Performance Team has released an experimental plugin that increases the perceived loading speed of web pages without the performance issues and accessibility tradeoffs associated with Single Page Applications (SPAs). The announcement was made by Felix Arntz, a member of the WordPress Performance Team and a Google software engineer.

Plugins released by the WordPress Performance Team are released so that users can play around and test with a new performance enhancement before the new feature is considered for inclusion into the WordPress core. Using these plugins provides a way to receive advanced performance improvements before a decision is made as to whether to integrate the improvements into WordPress itself.

The View Transitions plugin brings smooth, native browser-powered animations to WordPress page loads, mimicking the feel of Single Page Applications (SPAs) without requiring a full rebuild or custom JavaScript. Once the WordPress plugin is activated, it replaces the default hard reload between pages with a fluid animated transition effect, like a fade or slide, depending on how you configure it. This improves the visual flow of navigation across the site and increases the perceived loading speed for site visitors.

The plugin works out of the box with most themes, and users can customize the behavior through the admin user interface under Settings > Reading. Animations can be set using selectors and presets, with support for things like headers, post titles, and featured images to persist or animate across views.

According to the announcement:

“You can customize the default animation, and the selectors for the default view transition names for both global and post-specific elements. While this means the customization options are limited via the UI, it still allows you to play around with different configurations via UI, and likely for the majority of sites these are the most relevant parameters to customize anyways.

Keep in mind that this UI is only supplemental, and it only exists for easy exploration in the plugin. The recommended way to customize is via add_theme_support in your site’s WordPress theme.

…For the default-animation, a few animations are available by default. Additionally, the plugin provides an API to register additional animations, each of which encompasses a unique identifier, some configuration values, a CSS stylesheet, and optional aliases.”

The new WordPress plugin is optimized for block themes but designed to work broadly across all WordPress sites.

The page transitions are supported by all modern browsers, however it will degrade gracefully in older unsupported browsers by falling back to standard navigation without breaking anything.

The main point is that the plugin makes WordPress sites feel more modern and app-like—without the complexity or downsides of SPAs.

Read the announcement on Felix Arntz’s blog:

Introducing the View Transitions Plugin for WordPress

Download the experimental WordPress Performance Team plugin here:

View Transitions WordPress Plugin

Featured Image by Shutterstock/Krakenimages.com

Custom Vs. Template Website Design: Making The Right Choice via @sejournal, @atuljindal01

When launching your business online you are faced with many decisions. One of these is whether to go with a template website such as WordPress, or invest in a custom design.

This decision is critical because what you choose can define your business’s performance. It can also influence how your business grows online.

Of course, it may also define your profit margins and affect your bottom line.

Understanding the pros and cons of each option can help you make an informed decision – one that will benefit your business in the long run.

Understanding Custom Vs. Template Web Design

A custom website is one you build from scratch. You hire professional web designers and developers who generate mockups before coding all the features, aspects, and elements of your website from the ground up.

In contrast, a template website comes with many features and elements pre-coded into the design.

It’s more of a drag-and-drop option where, in most cases, you can simply download a theme, make a few changes, and quickly have your site go live.

Custom Vs. Template Web Design: A Comparison

Website templates are built using website builders and aim to make web building easier for people with no coding experience or knowledge.

However, as simple as these websites may be, they have their limitations. It is because of these limitations that many established businesses often choose custom-built websites, even if that means investing a large sum of money upfront.

Here’s a quick rundown of how custom and template design websites compare against each other to empower you to make the right choice:

Uniqueness

The online world is saturated with businesses, which are vying for one thing and one thing alone: customer attention.

The only way your business can stand out and win that fleeting customer attention is if it appears unique in a sea of businesses that all seem to be selling the same thing.

Using a pre-built website does little to help your business stand out.

Website design templates are built for a larger audience. Therefore, most websites that use a design template tend to look the same.

In some cases, using a web design template can make your website look exactly like that of the competitor you so want to stand apart from. This is not the case with custom web design.

When building a custom website, everything is designed and added to the website from scratch. From color to layout, navigation, and design, everything is coded according to your business’s requirements and preferences.

This helps you ensure that your business can stand out and have a more identifiable and unique digital footprint.

Customization

Website templates allow for customization, but the level of customization comes nowhere near that of a custom-designed website.

You can edit the header, change the color theme, and even add some graphics that you like. However, the layout and a lot of the backend features remain the same.

This limits the degree of personalization your business can incorporate in its online user experience.

With 61% of consumers more likely to purchase from brands that offer personalized experiences, customization is not an area you want to slack off on.

When building a custom website, you can work alongside professional developers who can code highly personalized features into the website.

You can implement a design that aligns with your target audience’s unique needs and challenges to offer an unmatched and intuitive user experience.

Going the custom-built route can help you launch a website that is designed to help make your users’ journey easier.

Design templates are more generic and meant to serve larger, more general audiences, so it can be hard to hone in on a particular audience group’s preferences.

SEO

While there are many ways you can get traffic to your site, currently 53% of all web traffic comes from organic search. Although, more traffic from LLMs is to be anticipated as search changes.

SEO is essential for visibility across organic search and potential inclusion in LLMs

While website templates, especially the ones using WordPress, have excellent plugins to help SEO, they work well only if the website is small and has a limited number of pages and functionality.

If your website grows with your business, its SEO requirements may get more complex. Most website template builders limit access to a website’s HTML, JavaScript, and other backend functionalities.

These limitations restrict the level to which you can optimize your website.

As a result, a website template may struggle to achieve any sustained visibility and custom-built websites can be better optimized, especially for bigger, more established businesses.

When building a custom website, you can work with the developer to apply SEO best practices to the site.

As the website grows, you can continue to monitor optimization to achieve and maintain the visibility in search engines and LLMs.

Performance

A slow-loading website can drive users away. Not just that, decreased website load speeds can also drag a website down in the search results and reduce organic traffic.

Website templates are often notorious for poorer performance and slower load speeds. This is because they use various plugins to deliver all the functionality that the business needs.

These plugins add more code to the website’s backend. With bloated code, the website struggles to load fast and is more likely to deliver a poorer experience.

With a custom website, you have the liberty to only code features your business truly needs and use speed optimization tactics like code minification to make sure the bloated code does not impact the site’s load speed.

Website Security

Websites can store sensitive data and crucial assets. So, website security remains a priority you don’t want to compromise on.

Website templates often offer poorer security compared to custom-designed websites.

The reason? Plugins. Again.

96% of WordPress vulnerabilities are related to plugins.

Plugins often have security vulnerabilities that offer backdoor pathways for malicious actors to exploit.

Moreover, most of the website templates are built using popular website builders and leverage popular plugins. This in itself makes the site an easy target for hackers.

As a comparison, if you use a reputable and experienced coder, a custom website is usually safer if the developer writes good code covering all necessary security measures to mitigate any security vulnerabilities.

Custom-coded websites are also unique in terms of code. This uniqueness also makes them more secure and harder to hack.

Scalability

Every business that intends to grow requires a website that can grow when the business does.

Website templates may not have the flexibility to grow with your business. As your business grows, its needs may evolve.

With a website template, you may struggle to integrate new APIs, add new features, and offer better functionalities on the website.

Custom-designed websites are more scalable since all the features and elements can be coded into the website to accommodate a business’s growing needs.

Your business may do just fine with a website template in the beginning, but as it grows, you may have to shift to a custom website. Transitioning to a new website may then be time and resource-intensive.

Budget

As amazing as custom websites are, they are expensive. You need to hire professional designers, developers, and quality assurance specialists – the entire team – to take your project from concept to launch.

This can be expensive and require a huge upfront cost.

Forking out a sizable amount upfront can be challenging for small business owners and start-up founders. In this case, going for a website template may make more sense.

Website templates do not require a huge budget. They can be built and launched easily, even if you are bootstrapped for cash and can invest only a couple of hundred dollars.

Time To Go Live

A custom website is built in phases. Therefore, it can take from several weeks to even months before your custom-designed website is ready to go live.

In contrast, website templates can be built and launched within hours. You don’t have to spend so much time working on the concept, design, navigation, etc.

Technical Expertise

Building and maintaining a custom-designed website requires coding knowledge and technical expertise. You cannot just DIY it.

Because of this, having a custom-coded website requires that you regularly work with professional web developers to keep your website up to date, backed up, and maintained.

Website templates are no-code solutions for people with little to no technical expertise. You can easily build and update a templated website even if you have never written a single line of code in your life.

Making The Right Choice

There is no one-size-fits-all answer to whether you should choose a templated website or invest in a custom-designed website.

Your choice depends on a lot of factors, including your business goals, budget, available resources, etc.

You can choose a custom website if you:

  • Have the money for the upfront cost of custom web development.
  • Don’t mind putting in a few weeks or months into the project.
  • Can hire or work with web developers for regular maintenance and updates.
  • Need a scalable solution that accommodates your business’s growing needs without compromising on performance.
  • Want a website that helps reinforce your brand identity and allows your business to stand out from the crowd.

A website template can work for you if you:

  • Are working with a limited budget.
  • Don’t mind your website looking similar to the competitors.
  • Can make regular updates and install all the patches to avoid security vulnerabilities.
  • Don’t need too many plugins for added features and functionalities.
  • Want to go live quickly.
  • Are not expecting your business to scale beyond a few pages and some very basic features.

If you run an ecommerce store, a job board, a flight directory, or anything with advanced features and more than 10 pages, a custom solution may work best for you.

However, if you only need a website for your blog, portfolio, or to maintain a basic online presence, then a template web design may make the most sense, given its cost-effectiveness and simplicity.

More Resources:


Featured Image: N Universe/Shutterstock

New AI-Assisted Managed WordPress Hosting For Ecommerce via @sejournal, @martinibuster

Bluehost announced two competitively priced managed WordPress ecommerce hosting solutions that make it easy for content creators and ecommerce stores to get online with WordPress and start accepting orders.

Both plans feature AI site migration tools that help users switch web hosting providers, free content delivery networks to speed up web page downloads, AI-assisted site creation tools and NVMe (Non-Volatile Memory Express) solid state storage which provides faster speeds than traditional web hosting storage.

The new plans enable users to sell products with WooCommerce and even offer paid courses online, all within a managed WordPress hosting environment that’s optimized for WordPress websites.

According to Bluehost:

“Bluehost’s eCommerce Essentials equips content creators with an intuitive, all‑in‑one toolkit—complete with AI‑powered site building, seamless payment integrations, paid courses and memberships, social logins, email templates and SEO tools—to effortlessly engage audiences and turn their passion into profit.”

There are two plans, eCommerce Essentials and eCommerce Premium, with the premium version offering more ecommerce features built-in. Both plans are surprisingly affordable considering the many features offered.

Satish Hemachandran, Chief Product Officer at Bluehost commented:

“At Bluehost, we understand the unique needs of today’s content creators and entrepreneurs who are building personal brands or online stores and turning their passion into profit.

With Bluehost WordPress eCommerce hosting plans, creators get a streamlined platform to easily develop personalized commerce experiences. From launching a store to engaging an audience and monetizing content, our purpose-built tools are designed to simplify the process and support long-term growth. Our mission is to empower creators with the right resources to strengthen their brand, increase their income, and succeed in the digital economy.”

Read more about the new ecommerce WordPress hosting here:

WooCommerce Online Stores – The future of online selling is here.

WordPress Takes Steps To Integrate AI via @sejournal, @martinibuster

WordPress announced the formation of an AI Team that will focus on coordinating the development and integration of AI within the WordPress core. The team is to function similarly to the Performance Team, focusing on developing canonical plugins that users can install to test new functionality before a decision is made about whether or how to integrate new functionalities into the WordPress core itself.

The goal for the team is to help create a strategic focus, rapid testing to deployment and to provide a centralized location for collaborating on ideas and projects.

The team will include two Google employees, Felix Arntz and Pascal Birchler. Arntz is a Senior Software Engineer at Google who contributes to the WordPress core and to other WordPress plugins and has worked as a lead for the Performance Team.

Pascal Birchler, a Developer Relations Engineer and WordPress core committer, recently led a project to integrate the Model Context Protocol (MCP) with WordPress via WP-CLI.

The WordPress announcement called it an important step:

“This is an exciting and important step in WordPress’s evolution. I look forward to seeing what we’ll create together and in the open.”

WordPress First Steps On Path Blazed By Competitors

The formation of an AI team is long overdue, as even the new open source Drupal CMS designed to provide an easy to use interface for marketers and creators has AI-powered features built-in. Third-party proprietary CMS provider Wix already and shopping platform Shopify have both integrated AI into their user’s workflows.

Read the official WordPress announcement:

Announcing the Formation of the WordPress AI Team

Featured Image by Shutterstock/Hananeko_Studio

WordPress Unpauses Development But Has It Run Out Of Time? via @sejournal, @martinibuster

Automattic announced that it is reversing its four-month pause in WordPress development and will return to focusing on the WordPress core, Gutenberg, and other projects. The pause in contributions came at a critical moment, as competitors outpaced WordPress in ease of use and technological innovation left the platform behind.

Did WordPress Need A Four-Month Pause?

Automattic’s return to normal levels of contributions were initially contingent on WP Engine withdrawing their lawsuit against Automattic and Mullenweg, with the announcement stating:

“We’re excited to return to active contributions to WordPress core, Gutenberg, Playground, Openverse, and WordPress.org when the legal attacks have stopped.”

WP Engine and Automattic are still locked in litigation, so what changed?

Automattic suggests that it has reconsidered its place as the future of content management:

“After pausing our contributions to regroup, rethink, and plan strategically, we’re ready to press play again and return fully to the WordPress project.

…We’ve learned a lot from this pause that we can bring back to the project, including a greater awareness of the many ways WordPress is used and how we can shape the future of the web alongside so many passionate contributors. We’re committed to helping it grow and thrive…”

Automattic’s announcement suggests that they realized moving forward with WordPress is important despite continued litigation.

But did Automattic really need a four-month pause to come to that realization?

Where Did The WordPress Money Go?

And it’s not like Automattic was hurting for money to throw at WordPress. Salesforce Ventures invested $300 million dollars into Automattic in 2019 and an elated Mullenweg wrote that this would enable them to almost double the pace of innovation for WP.com, their enterprise offering WordPress VIP, WooCommerce, Jetpack, and increase resources to WordPress.org and Gutenberg.

Mullenweg wrote:

“For Automattic, the funding will allow us to accelerate our roadmap (perhaps by double) and scale up our existing products—including WordPress.com, WordPress VIP, WooCommerce, Jetpack, and (in a few days when it closes) Tumblr. It will also allow us to increase investing our time and energy into the future of the open source WordPress and Gutenberg.”

In the years immediately following the $300 million investment, updates to WooCommerce increased by 47.62% and as high as 80.95% and just a little bit higher for the year 2024. Jetpack continued at an average release schedule of 7 updates per year although it shot up to 22 updates in 2024. The enterprise level WordPress VIP premium service may have also benefited (changelog here).

Updates to the WordPress Core remained fairly unchanged according to the official release announcements and the pace of Gutenberg releases also followed a steady pace, with no significant increases.

List of number of WordPress release announcements per year:

  • 2019 – 29 announcements
  • 2020 28 announcements
  • 2021 26 announcements
  • 2022 27 announcements
  • 2023 26 announcements
  • 2024 30 announcements
  • 2025 9 announcements

All the millions of dollars invested in Automattic, along with any other income earned, had no apparent effect on the pace of innovation in the WordPress core.

Survival Of The Fittest CMS

A positive development from Automattic’s pause to rethink is the announcement of a new AI group, modeled after their Performance group. The new team is tasked with coordinating AI initiatives within WordPress’ core development. Like their Performance group, the new AI group was formed after their competitors had outpaced them, so WordPress is once again late in adapting to user needs and the fast pace of technology.

Matt Mullenweg struggled to answer where WordPress would be in five years when asked at the February 2025 WordCamp Asia event. He asked someone from Automattic to join him on stage to answer the question, but that other person also couldn’t answer because there was, in fact, no plan or idea other than the short-term roadmap focused on the immediate future.

Mullenweg explained the lack of a long-term vision as a strategic decision to remain adaptable to the fast pace of technology:

“Outside of Gutenberg, we haven’t had a roadmap that goes six months or a year, or a couple versions, because the world changes in ways you can’t predict.

But being responsive is, I think, really is how organisms survive.

You know, Darwin, said it’s not the fittest of the species that survives. It’s the one that’s most adaptable to change. I think that’s true for software as well.”

That’s a somewhat surprising statement, given that WordPress has a history of being years late to prioritizing website performance and AI integration. Divi, Elementor, Beaver Builder, and other WordPress editing environments had already cracked the code on democratizing web design in 2017 with block-based, point-and-click editors when WordPress began their effort to develop their own block-based editor.

Eight years later, Gutenberg is so difficult for many users that the official Classic Editor plugin has over ten million installations, and advanced web developers prefer other, more advanced web builders.

Takeaways:

  • Automattic’s Strategic Reversal
    Automattic reversed its pause on WordPress contributions despite unresolved litigation with WP Engine, perhaps signaling a change in internal priorities or external pressures.
  • Delayed Response to AI Trends
    A new AI group has been formed within WordPress core development, but this move comes years after competitors embraced AI—suggesting a reactive rather than proactive strategy.
  • Lack of Long-Term Vision
    WordPress leadership admits to having no roadmap beyond the short term, framing adaptability as a strength even as the platform lags in addressing user needs and keeping up with technological trends.
  • Minimal Impact from Major Investments
    Despite receiving hundreds of millions in funding, core WordPress and Gutenberg development showed no significant acceleration, raising questions about where investment actually went.
  • Usability and Competitive Lag
    Gutenberg arguably struggles with usability, as shown by the popularity of the Classic Editor plugin and user preference for third-party builders.
  • WordPress at a Competitive Disadvantage
    WordPress now finds itself needing to catch up in a CMS market that has evolved rapidly in both ease of use and innovation.

The bottom line is that the pace of development for the WordPress core and Gutenberg remained steady after the 2019 investment, and after all of the millions of dollars that Automattic received from companies like Newfold Digital, sponsored contributions, and volunteer contributions from individuals themselves, the effect on the speed of development and innovation maintained the same follow-the-competitors-from-behind pace.

Automattic’s return to WordPress core development inadvertently calls attention to how far the platform has fallen behind competitors like Wix in usability and innovation, despite major investments and years of community support. For users and developers, this means that WordPress must now work to regain trust by proving it can adapt quickly and deliver the tools that modern site developers, businesses, and content creators actually need.

Automattic has a legitimate dispute with WP Engine, but the way it was approached became a major distraction that resulted in an arguably unnecessary four-month pause to WordPress development. The platform might have been in danger of losing relevance if not for the work of third-party innovators, and it still arguably lags behind competitors.

Future-Proofing WordPress SEO: How To Optimize For AI-Driven Search Features via @sejournal, @cshel

Search is changing. I hate saying that (again) because it feels cliche at this point. But, cliche or not, it is true and it is seismic.

With the rollout of AI Overviews, Bing Copilot, and conversational search interfaces like ChatGPT and Perplexity, SEO is no longer just about traditional rankings; it’s about representation and visibility.

Instead of obsessing over page 1 and traffic numbers, WordPress site owners need to start focusing on whether they’re represented in the answers users actually see and if that visibility is resulting in revenue.

The old rankings system itself is mattering less and less because AI-driven search features aren’t just scraping a list of URLs. They’re synthesizing content, extracting key insights, and delivering summary answers.

If your content isn’t built for that kind of visibility, it may as well not exist.

Google doesn’t even look like Google anymore. Since the March core update, AI Overviews have more than doubled in appearance, and this trend shows no signs of slowing. This is our new reality, and it’s only going to accelerate.

WordPress is already a flexible, powerful platform, but out of the box, it’s not optimized for how AI-driven search works today.

In this guide, I’ll show you how to future-proof your WordPress site by aligning your structure, content, and technical setup with what large language models actually understand and cite.

Don’t Build Trash Content

Before we talk about how to do it right, let’s talk about the strategy that’s finally running out of road.

For literal decades, site owners have spun up content sites that were never designed for people, only for ad revenue. These sites weren’t meant to inform or help – just rank well enough to earn the click and display the ad.

Unfortunately, WordPress made this model wildly scalable. It almost instantly became the go-to tool for anyone who wanted to launch dozens (or hundreds) of sites fast, slap on some AdSense, and rake in passive income – money for nothing and your clicks for free.

That model worked very well for a very long time. But (thankfully), that time has come to an end.

AI Overviews and answer engines aren’t surfacing this kind of content anymore. Traffic is drying up. Cost per mille (CPM) is down. And trust – not volume – is the currency that search engines now prioritize.

Even if you’re trying to brute-force the model with paid placements or “citation strategies,” you’re competing with brands that have earned their authority over the years.

To be clear, WordPress is not and was never the problem. The problem is that people use it to scale the wrong kind of content.

If your content is created for algorithms instead of actual people, AI is going to pass you by. This new era of search doesn’t reward valueless content factories. It rewards clarity, “usefulness,” and trust.

Nothing in the rest of this article is going to fix that dying business model. If that’s what you’re here for, you’re already too late.

If, however, you’re focused on publishing something valuable – something worth reading, referencing, or citing – then please, keep reading.

Use WordPress Like You Mean It

WordPress is the most widely used content management system (CMS) for a reason. It’s flexible, extensible, and powerful when you use it right.

However, default settings and bloated themes won’t cut it in an AI-first environment. You have to optimize with clarity in mind.

Let’s start with your theme. Choose one that uses semantic HTML properly:

,

,
, and a clear heading hierarchy.

Avoid themes and builders that generate “div soup.” Large language models rely on clean HTML to interpret relationships between elements. If your layout is a maze of

s and JavaScript, the model may miss the point entirely.

If the theme you love isn’t perfect, that’s fine. You can usually fix the markup with a child theme, custom template, or a little dev help. It’s worth the investment.

A Checklist For Optimizing WordPress Fundamentals

  • Use lightweight themes: e.g., GeneratePress, Astra, or Blocksy are all well-regarded by developers for their performance and clean markup.
  • Optimize image delivery: Large, uncompressed images are one of the biggest culprits behind slow load times. Reducing file sizes improves speed, performance scores, and user experience, especially on mobile.
  • Use caching and CDNs: These reduce server load and speed up delivery by storing content closer to your users. Better performance means faster indexing, higher satisfaction, and improved Core Web Vitals.
  • Delete unused plugins: Seriously. If it’s deactivated and collecting dust, it’s a liability. Every inactive plugin is an unpatched attack vector just waiting to be exploited.
  • Delete unused themes: Same issue as above. They can still pose security risks and bloat your site’s file structure. Keep only your active theme and a fallback default, like Twenty Twenty-Four.

Declutter Hidden Or Fragmented Content

Pop-ups, tabs, and accordions might be fine for user experience, but they can obscure content from LLMs and crawlers.

If the content isn’t easily accessible in the rendered HTML – without requiring clicks, hovers, or JavaScript triggers to reveal – it may not be indexed or understood properly.

This can mean key product specs, FAQs, or long-form content go unnoticed by AI-driven search systems.

Compounding the problem is clutter in the Document Object Model (DOM).

Even if something is visually hidden from users, it might still pollute your document structure with unnecessary markup.

Minimize noisy widgets, auto-playing carousels, script-heavy embeds, or bloated third-party integrations that distract from your core content.

These can dilute the signal-to-noise ratio for both search engines and users.

If your theme or page builder leans too heavily on these elements, consider simplifying the layout or reworking how key content is presented.

Replacing JavaScript-heavy tabs with inline content or anchor-linked jump sections is one simple, crawler-friendly improvement that preserves UX while supporting AI discoverability.

Use WordPress SEO Plugins That Help Structure For LLMs

WordPress SEO plugins are most often associated with schema, and schema markup is helpful, but its value has shifted in the era of AI-driven search.

Today’s large language models don’t need schema to understand your content. But that doesn’t mean schema is obsolete.

In fact, it can act as a helpful guidepost – especially on sites with less-than-perfect HTML structure (which, let’s be honest, describes most websites).

It helps surface key facts and relationships more reliably, and in some cases, makes the difference between getting cited and getting skipped.

Modern SEO tools do more than just generate structured data. They help you manage metadata, highlight cornerstone content, and surface author information – all of which play a role in how AI systems assess trust and authority.

Just don’t make the mistake of thinking you can “add E-E-A-T” with a plugin toggle. John Mueller has said as much at Search Central Live NYC in March of this year.

What author schema can do, however, is help search engines and LLMs connect your content to your wider body of work. That continuity is where E-E-A-T becomes real.

Finally, consider adding a WordPress SEO plugin that can generate a Table of Contents.

While it’s useful for readers, it also gives LLMs a clearer understanding of your page’s hierarchy, helping them extract, summarize, and cite your content more accurately.

Structure Your Content So AI Uses It

Whether you’re creating posts in the Block Editor, Classic Editor, or using a visual page builder like Elementor or Beaver Builder, the way you structure your content matters more than ever.

AI doesn’t crawl content like a bot. It digests it like a reader. To get cited in an AI Overview or answer box, your content needs to be easy to parse and ready to lift.

Start by using clear section headings (your H2s and H3s) and keeping each paragraph focused on a single idea.

If you’re explaining steps, use numbered lists. If you’re comparing options, try a table. The more predictable your structure, the easier it is for a language model to extract and summarize it.

And don’t bury your best insight in paragraph seven – put your core point near the top. LLMs are just like people: They get distracted. Leading with a clear summary or TL;DR increases your odds of inclusion.

Finally, don’t forget language cues. Words like “Step 1,” “Key takeaway,” or “In summary” help AI interpret your structure and purpose. These phrases aren’t just good writing; they’re machine-readable signals that highlight what matters.

Show AI You’re A Trusted Source

WordPress gives you powerful tools to communicate credibility – if you’re taking advantage of them.

E-E-A-T (which stands for experience, expertise, authoritativeness, and trustworthiness) isn’t just an acronym; it’s the bar AI systems use to decide whether your content is worth citing.

WordPress gives you plenty of opportunities to show you’re the real deal.

Start by making your authors visible. Include a bio, credentials, and a link to an author archive.

If your theme doesn’t support it, add a plugin or customize the layout.

Schema markup for authors helps, too, but remember, it doesn’t magically give you E-E-A-T. What it does is help LLMs connect your byline to your broader body of work across the web.

From there, build out internal signals of authority. Link your content together in meaningful ways.

Surface cornerstone pieces that demonstrate depth on a topic. These internal relationships show both users and machines that your site knows what it’s talking about.

Finally, keep it fresh. Outdated content is less likely to be included in AI answers.

Regular content audits, scheduled refreshes, and clear update timestamps all help signal to LLMs (and humans) that you’re active and credible.

Final Thoughts: Build For Understanding, Not Just Ranking

At this point, it should be clear that WordPress can absolutely thrive in an AI-first search environment – but only if you treat it like a platform, not a shortcut.

Success with AI Overviews, answer engines, and conversational search doesn’t come from tricking algorithms. It comes from helping language models truly understand what your content is about – and why you’re the one worth citing.

That means focusing on structure. On clarity. On authorship. On consistency. That means building not just for Google’s crawler, but for the models that generate answers people actually read.

So, yes, SEO has changed. If you’re using WordPress, you’re already holding the right tool. Now, it’s just a matter of wielding it well.

More Resources:


Featured Image: Roman Samborskyi/Shutterstock