In today’s digital landscape, where messages and advertisements bombard us from every direction, it is easy to feel lost in the noise. Gaining real attention is more challenging than ever, and many marketers and entrepreneurs find themselves wondering: how do you stand out when everyone is shouting at once? A recurring theme that emerges is […]
How to Setup Author SEO in WordPress to Boost Your Google E-E-A-T
If you’ve been putting effort into creating great content but still struggling to rank higher on Google, the problem might not be what you’re writing. It could be who Google thinks is writing it.
That’s where Author SEO comes in. It’s the practice of optimizing your author profile so that search engines can recognize the real person behind your content, including your qualifications, your experience, and your credibility.
Google’s Human Quality Raters use E-E-A-T (Experience, Expertise, Authoritativeness, and Trustworthiness) to evaluate how well its ranking systems are surfacing trustworthy content. E-E-A-T isn’t a direct ranking factor, but giving Google clear author signals helps its systems recognize your content as credible.
In this guide, I’ll walk you through how to set up Author SEO in WordPress. Whether you’re running a personal blog or a multi-author website, you’ll have everything in place to give your content a stronger chance of ranking in Google search results — no coding needed. 🙌

📘 TL;DR: You can easily set up Author SEO in WordPress using All in One SEO (AIOSEO). Simply install the plugin, enable the Author SEO (E-E-A-T) feature, and fill out your users’ expanded profile fields.
AIOSEO will automatically generate the right schema markup for Google, including Person schema for each author and Organization schema for your site. It also lets you display beautiful author bio boxes on your posts without any code.
For multi-author sites, you can also embed live social feeds on author pages using Smash Balloon to reinforce credibility.
What Is Author SEO?
Author SEO is the practice of optimizing your author profile so that search engines can identify and verify the person behind your content, including their credentials, work history, and external profile links.
Think of it as a digital résumé for search engines. The more clearly your expertise is defined, the more confidently Google can decide whether your content deserves to rank.
Why Set Up Author SEO in WordPress?
Author SEO supports the E-E-A-T criteria, which is the set of quality signals Google uses to evaluate whether a page deserves a top position in search results.
E-E-A-T stands for:
- Experience — Has the author actually done or lived what they’re writing about?
- Expertise — Does the author have the knowledge or qualifications to speak on this topic?
- Authoritativeness — Is the author recognized by others in their field?
- Trustworthiness — Can readers and search engines rely on this author’s content to be accurate and honest?
💡 Note: Google has clarified that E-E-A-T isn’t a direct ranking factor. It comes from the Search Quality Rater Guidelines, which human raters use to assess how well Google’s ranking systems are working. Strong author signals still help Google attribute content and judge trust, which can influence rankings indirectly. But no profile field or schema setup guarantees a ranking lift on its own.
Many site owners focus entirely on keyword research and on-page SEO, but overlook the author signals that Google increasingly relies on. That’s a missed opportunity, especially in competitive niches.
Here’s why Author SEO is worth your time:
- It strengthens your E-E-A-T signals — Google evaluates your Experience, Expertise, Authoritativeness, and Trustworthiness when deciding how to rank your content. A well-optimized author profile gives Google more evidence of E-E-A-T.
- It builds reader trust — Visitors are more likely to engage with content when they can see who wrote it and confirm that person has real credentials.
- It gives your YMYL niches an edge — In topics like health, finance, or legal advice (called “Your Money or Your Life” content), Google holds authors to an even higher standard. A credible author profile can make a difference in how your content ranks.
- It strengthens your structured data — Author schema markup helps Google understand who wrote your content, which contributes to how confidently it can attribute and rank it.
- It works for solo bloggers and multi-author blogs alike — Whether you’re the only writer or managing a team, every author on your site can benefit from a properly optimized profile.
Now, let’s see how to set up author SEO in WordPress. Here’s everything I’ll cover in this article:
- Step 1: Install the All In One SEO (AIOSEO) Plugin
- Step 2: Set Up the Author SEO (E-E-A-T) Feature
- Step 3: Create an Author Profile
- Step 4: Complete Author Information in the Author SEO Section
- Step 5: Set Up Organization Schema (For Businesses & Multi-Author Blogs)
- Step 6: Verify Your Author Schema
- Step 7: Add AIOSEO Author Blocks in Your Posts
- Step 8: Add a Reviewer for YMYL Content (Optional)
- Bonus Tip: Optimize Your Author Archive Page
- Frequently Asked Questions About Author SEO
- Next Steps to Improve Your WordPress SEO
Step 1: Install the All In One SEO (AIOSEO) Plugin
To set up Author SEO in WordPress, the first thing you’ll need is the right tool.
I recommend using All In One SEO (AIOSEO) because it’s the only major WordPress SEO plugin with a dedicated, purpose-built Author SEO (E-E-A-T) module. It gives authors structured fields for expertise, experience, and credentials that flow directly into Person schema, instead of relying on the default WordPress user profile.
At WPBeginner, we use the AIOSEO plugin to optimize our post titles, configure OpenGraph settings, create schema markup, and more. See our complete AIOSEO review to learn more about what it can do.
To follow this tutorial, you’ll need an AIOSEO account.
On the AIOSEO website, click ‘Get All in One SEO for WordPress,’ choose a plan that comes with the Author SEO (E-E-A-T) feature, and complete the checkout.
💡 Note: You’ll need at least AIOSEO’s Plus plan to use the Author SEO (E-E-A-T) feature. That said, you can install the free version of AIOSEO first to explore the plugin before upgrading.

Upon signup, you’ll land in your own AIOSEO dashboard, where you can download your plugin zip file and copy your license key.
Now, you can go ahead and install and activate the All In One SEO plugin. Simply navigate to Plugins » Add Plugin in your WordPress admin area to start.

On the next screen, you can click the ‘Upload Plugin’ button.
Then, click the ‘Choose File’ button to upload your AIOSEO zip file from your local computer.

Once uploaded, click ‘Install Now,’ followed by ‘Activate.’ If you need help, please refer to our guide on how to install a WordPress plugin.
AIOSEO will then add a new menu to your WordPress dashboard. From here, let’s navigate to AIOSEO » General Settings to verify your license key.
In the respective field, enter your AIOSEO license key and hit ‘Activate.’

With that done, you can manage all of your SEO settings, including your author profiles, from the All in One SEO menu in your WordPress sidebar.
For a more detailed walkthrough of the setup process, see our guide on how to setup All in One SEO for WordPress correctly.
Step 2: Set Up the Author SEO (E-E-A-T) Feature
Before you create or edit a user, you’ll need to activate the Author SEO (E-E-A-T) feature. This will allow you to unlock extended author profile fields and structured data settings.
To do this, head to the Feature Manager in AIOSEO and toggle on ‘Author SEO (E-E-A-T)’ to activate it.

Once that’s done, go to ‘Search Appearance’ and click on the ‘Author SEO’ tab.
Here you’ll find a few settings to configure.

First, you’ll want to set ‘Display Info’ to Gutenberg Blocks.
I recommend selecting the Gutenberg Blocks option because it is the easiest way to display author information without touching any code.

Then, you can hit ‘Enable’ next to ‘Append Author Bio to Posts.’ This lets you automatically add your author bio box to the bottom of your articles, saving you the hassle of inserting it manually every time.
For the post type, select ‘Posts.’ If it’s relevant to your WordPress site, you can also select ‘Pages’ or tick ‘Include All Post Types.’

Next, let’s scroll down to the ‘Author Experience Topics’ section.
This is where you’ll add all the topics your blog covers. It’s worth taking your time here, because these topics will be used later when you assign individual writers their own Author SEO settings.
Think in two layers: start with broad umbrella terms like SEO, AI SEO, or Content Marketing, then get more specific with the tools and products you write about, like WordPress. For each one, fill in the relevant URL and any referencing pages that back it up.

When you’re happy with everything, click ‘Save Changes’ and you’re done with this step.
Step 3: Create an Author Profile
With AIOSEO installed and set up, the next step is to make sure every author on your site has a complete WordPress user profile.
This matters more than most people realize because your user profile is where Google pulls the foundational information it needs to evaluate your credibility as an author.
To get started, go to Users » Add New User from your admin area.

💡 Note: If the author already has an account, you can skip this and go to Users » All Users to edit their existing profile instead.
Here are all the fields you’ll see on your screen:
- Username (required) — This is the unique name used to log in to WordPress. Once set, it can’t be changed, so choose something professional. I recommend using the author’s real name or a consistent variation of it.
- Email (required) — Required for the account and used for WordPress notifications.
- First and Last Name — This is how the author will appear publicly on your website.
- Website — Add the author’s personal or professional website if they have one.
- Password — You can autogenerate a password for your new user and send it to them via the welcome email. The user can then change their password after logging in for the first time.
- Send User Notification — This is like a welcome email, informing the author about their new account.
- Role — Assign your new user a role, in this case, Author.
With that done, go ahead and click the ‘Add User’ button.

If your site covers topics in the YMYL (Your Money or Your Life) category — such as health, finance, legal advice, or safety, then adding a reviewer to your posts is a smart extra step.
Google holds this type of content to a higher standard. And showing that an article has been reviewed by a qualified expert can meaningfully strengthen your E-E-A-T signals.
🛑 Important: A reviewer is different from an author. The author is the person who wrote the content, while the reviewer is a qualified professional who has checked it for accuracy.
Having both clearly identified on a blog post tells Google, and your readers, that the information has gone through an additional layer of verification.
Simply repeat the process to add a new user for your reviewer.
Step 4: Complete Author Information in the Author SEO Section
Now that the user profile is set up, it’s time to add the deeper author details that AIOSEO uses to generate structured data for search engines. This is where Author SEO really starts to take shape.
To access these settings, go to Users » All Users from your WordPress dashboard. Hover over the author’s name and click ‘Edit.’

Once you’re inside the profile, you can switch to the ‘Author SEO’ tab added by AIOSEO.
You can find it next to the ‘Personal Options’ tab, like this:

Core Profile Fields
Here, you’ll want to fill in the following core details:
- Institution Name — List any universities, colleges, or institutions the author has attended.
- Institution URL — Enter the institution URL if available.
- Employer — Enter the name of the organization or company the author works for.
These fields feed directly into the author’s JSON-LD schema markup, which is a type of structured data that search engines read behind the scenes.

Then, there are these fields:
- Job Title — Add the author’s professional title, such as “Content Writer” or “WordPress Developer.”
- Knows About — Fill this out with the Author Experience Topics you have set up in the previous step.
Here’s what you might see on your screen:

🧑💻 Pro Tip: Don’t stuff the Knows About field with broad topics like WordPress, blogging, or SEO. Google can’t verify expertise that vague, so the schema signal gets diluted.
Instead, list 3-5 narrow topics you’ve actually written about and can back up with credentials or published work. Match them to your real article categories. For example, “WordPress security plugins” beats “security,” and “WooCommerce subscriptions setup” beats “eCommerce.”
Awards and Spoken Languages
Next, you can add whatever awards the author has received in the past as well as the languages the author speaks.
Do note that the Awards and Spoken Languages fields won’t be visible to readers on your posts, but don’t skip them. AIOSEO outputs this information as schema markup in the background, and Google can use it to better understand the author’s credibility.

Author Image, Excerpt, and Bio
After that, you’ll find the:
- Author Image — Upload a real, clear photo of the author. Avoid default Gravatar silhouettes, stock headshots, company logos, or an AI-generated face because they weaken E-E-A-T. Plus, if you use the same photo on the author’s LinkedIn, X, or other public profiles, then Google can match the identity across the web and reinforce E-E-A-T.
- Author Excerpt — Write a short bio that gives readers a quick snapshot of who the author is. This includes information on their background, area of expertise, and what makes them credible on the topics they cover.
- Author Bio — This is the longer version of the author’s story. Use it to go into more detail about their experience, qualifications, portfolio, and anything else that establishes them as a trustworthy, authoritative voice in their niche.
I recommend writing the bio in the third person and keeping it focused on what makes the author qualified to write on your site’s topics.

How to Write a Bio That Actually Signals E-E-A-T
A bio that earns trust does more than describe the author. It gives Google and your readers specific, checkable evidence that this person should be writing on this topic.
Start with the basics: the author’s full name, their role on your site, and the topic area they cover.
Then build the rest of the bio around the four E-E-A-T pillars:
- Experience: What has the author actually done? Name real projects, years in the field, or hands-on work. “Has run her own Etsy shop since 2018” beats “passionate about eCommerce.”
- Expertise: Qualifications, training, or certifications. Be specific. “Certified WordPress developer” or “holds a BA in Journalism from NYU” is much stronger than “highly qualified writer.”
- Authoritativeness: Named outlets, awards, or speaking spots. “Quoted in Forbes and Wired” or “spoke at WordCamp US 2024” gives Google something concrete to verify.
- Trustworthiness: Transparency signals. Mention if the author fact-checks with primary sources, discloses affiliate relationships, or reviews content on a set schedule. If you use AI assistance for drafting, then say so and explain how a human verifies the output.
The rule of thumb: numbers, named outlets, and dates beat adjectives every time. “Veteran content strategist” is filler. “Has written for HubSpot and Search Engine Journal since 2016” is a signal.
Here’s the difference in practice:
Before: Sarah is a passionate writer who loves helping small businesses succeed online. She has years of experience in digital marketing and is dedicated to creating high-quality content.
After: Sarah Chen is a content strategist who has helped 40+ small businesses set up their WordPress sites since 2019. She’s a certified Google Analytics professional, has been quoted in Search Engine Land, and personally tests every plugin she recommends on a staging site before publishing.
The “after” version gives Google three verifiable claims (the certification, the named publication, the testing process) and gives readers a clear reason to trust Sarah on WordPress topics. That is what a bio is supposed to do.
External Profile URLs
On top of those core details, you’ll also want to add external profile URLs. These are links to places outside your website where the author has a verified presence.
For example:
- A LinkedIn profile
- Listings in industry directories or professional associations
- Portfolio site or other published work on reputable platforms
These external links act as additional authorship signals. They help Google cross-reference the author’s identity and credentials across the web, which strengthens the overall trustworthiness of their profile.

How These Fields Map to Person Schema
Every field you fill out in the Author SEO tab doesn’t just appear on your website. It also gets translated into Person schema. It’s a type of structured data that tells Google who the author is in a format it can read and understand, so it can match the right person to the right content.
Here’s how each field maps to a Person schema property:
| AIOSEO Field | Person Schema Property | What Google Does With It |
|---|---|---|
| First + Last Name | name |
Identifies the author entity |
| Job Title | jobTitle |
Signals professional role and topical authority |
| Employer | worksFor |
Links the author to an Organization entity |
| Institution Name + URL | alumniOf |
Verifies educational background |
| Knows About | knowsAbout |
Confirms topical expertise signals |
| Awards | award |
Adds credibility markers |
| Spoken Languages | knowsLanguage |
Supports multilingual content signals |
| Author Image | image |
Ties the schema to a recognizable identity |
| Author Bio | description |
Provides a plain-language summary of credentials |
| Social Profile URLs | sameAs |
Cross-references the author’s identity across the web |
The sameAs property deserves special attention. When you add LinkedIn, a portfolio site, or an industry directory listing to the social profiles section, AIOSEO outputs those URLs as sameAs values in the schema. This tells Google: “This author also exists here, here, and here.”
But a sameAs URL only counts if Google can confirm it’s actually the same person. That means the profile you link to needs to match your author bio on the basics: same full name, same (or clearly recognizable) photo, same employer or affiliation, and a byline history that lines up with what your WordPress site says about them.
Some platforms carry far more weight than others. I recommend focusing on profiles that Google already treats as identity sources:
- LinkedIn: the single most useful
sameAstarget for most authors. - Muck Rack or Contently: verified journalist and writer directories.
- Industry association or speaker directories: anywhere the author is listed with a bio.
- Published bylines on recognized publications: author pages on other sites they write for.
- Crunchbase, ORCID, or Google Scholar: depending on whether the author is in business, research, or academia.
What you’re building toward is a Knowledge Panel: once Google has enough consistent cross-references confirming the same person across the web, it starts treating that author as a known entity and can eventually attribute content, expertise, and trust to them directly in search results.
The more of these fields you fill in, the richer your Person schema becomes, and the more evidence Google has to evaluate your author’s E-E-A-T signals.
Once you’ve filled in all the details, scroll down and click ‘Update User’ to save your changes.
From here, you can repeat this process for all of the authors (and reviewers) you have.
Step 5: Set Up Organization Schema (For Businesses & Multi-Author Blogs)
Author SEO covers the individual writer. But Google also wants to identify the organization publishing the content.
That’s the other half of the E-E-A-T picture. Without it, Google sees credible authors with no verified entity behind them.
AIOSEO handles this through Organization schema, which it generates from a single Knowledge Graph settings panel. Go to AIOSEO » Search Appearance and open the ‘Global Settings’ tab.

Under ‘Knowledge Graph,’ you’ll want to confirm that ‘Organization’ is selected, not ‘Person.’
This is the right choice for any site with more than one author, or any site representing a brand rather than a solo individual.

💡 Note: If you’re a solo blogger representing yourself rather than a brand, select ‘Person’ here instead. You’ll fill in your own name, bio, and social profiles, and AIOSEO will generate Person schema for your site as a whole, rather than Organization schema.
From here, fill in the following fields:
- Organization Name — Your site or company name as it appears publicly.
- Organization Logo — Upload a clear, recognizable logo. Google uses this to identify your brand in search results.
- Phone Number — Optional, but adds a layer of legitimacy for YMYL sites.
- Contact URL — Link to your contact page so Google can verify a legitimate point of contact.
These fields map directly to Organization schema properties that Google reads behind the scenes:
| AIOSEO Field | Organization Schema Property | What Google Does With It |
|---|---|---|
| Organization Name | name |
Identifies the publishing entity |
| Organization Logo | logo |
Associates a visual identity with the organization |
| Website URL | url |
Confirms the canonical home of the organization |
| Phone Number | telephone |
Adds a verifiable contact signal |
| Contact URL | contactPoint |
Provides a direct path for verification |
| Social Profile URLs | sameAs |
Cross-references the organization’s identity across the web |
Don’t forget to also add your organization’s social profile URLs at the bottom of this section, just like you did for individual authors.
These become sameAs values in the Organization schema and help Google cross-reference your brand’s identity across platforms like LinkedIn, Facebook, and YouTube.
Click ‘Save Changes’ when you’re done.
Step 6: Verify Your Author Schema
Now, you need to make sure that Google can actually find and crawl your author’s archive page. This is a dedicated page that lists all the posts written by a specific author, and it can usually be found at a URL like yoursite.com/author/username.

First, make sure your author archive page is set to index in Google. I’ll cover exactly when and why you might choose differently in the Bonus Tip below.
For now, go to AIOSEO » Search Appearance, open the ‘Archives’ tab, and confirm that ‘Show in Search Results’ under ‘Author Archives’ is set to ‘Yes.’

With that set, it’s time to confirm that the schema markup is actually showing up correctly. The best way to do this is with Google’s Rich Results Test tool because it’s free and takes just a minute to use.
What Google Sees With Author SEO Configured
After completing the Author SEO fields, you should see a fully populated Profile page result with all the structured data AIOSEO generated from your inputs.
To get started, open a new browser tab and go to Google’s Rich Results Test. Paste your author page URL into the search bar and click the ‘Test URL’ button.

Your author page URL will typically follow this format: yoursite.com/author/username. If you’re not sure what it is, you can find it by clicking on the author’s name on any published post on your WordPress site.
After the test runs, you’ll see a summary of the structured data Google detected on the page.

From here, expand the ‘Profile page’ result to check that the key Person schema properties are populated correctly:
name— The author’s full namejobTitle— Their professional roleworksFor— Their employer or organizationknowsAbout— Their listed expertise topicssameAs— Their external profile URLs
💡 Note: Schema changes don’t always show up in the Rich Results Test right after saving, so if your Author SEO fields look incomplete in the test, wait a few minutes and try again before troubleshooting.
Also keep in mind that the Rich Results Test only confirms eligibility for Google’s documented rich-result types, which don’t include Person or ProfilePage. That means your author schema can be perfectly valid and still show “no rich results detected.”
For a general validity check, you can run the same URL through the Schema Markup Validator at validator.schema.org. It reports on any schema type, not just the ones Google highlights.

If the tool flags any errors or warnings, don’t worry because this is common the first time around.
Click on each issue to see what needs to be fixed, then head back to the Author SEO section in AIOSEO to make the necessary updates. Run the test again to confirm everything is resolved.
Step 7: Add AIOSEO Author Blocks in Your Posts
With your author schema in place, the next step is to make sure that the author information is visible to readers directly inside your posts.
AIOSEO includes two dedicated author blocks that you can add to any post or page using the WordPress block editor.
To add an author block, open a post in the block editor and click the ‘+’ button to open the block inserter. Search for “author” and you’ll see the AIOSEO author blocks available to insert.

💡 Note: If you enabled the ‘Append Author Bio to Posts’ option back in Step 2, AIOSEO will automatically add a compact Author Bio block to all your selected post types, whether they are blog posts, custom post types, or pages.
AIOSEO Author Name Block
The Author Name block is designed to appear near the post title.
It displays the author’s name and profile picture, giving readers an immediate sense of who wrote the article before they’ve even started reading.

It’s a simple but effective trust signal, especially for first-time visitors who want to quickly assess whether the content comes from a credible source.
AIOSEO Author Bio Block
The Author Bio block is designed to appear at the bottom of the post.
It includes the author’s full bio, educational background, social media links, and area of expertise. This way, readers get a more complete picture of who the author is after they’ve finished reading.

You can configure this block in two ways:
- Compact — A shorter version that shows the essentials without taking up too much space. Works well for news-style sites or WordPress blogs where post length and layout are a priority.
- Full — A more detailed layout that gives the author’s background more room to breathe. Great for author-focused sites or YMYL content, where establishing credibility is especially important.
Once you’ve added and configured your author blocks, click ‘Update’ or ‘Publish’ to save your changes to the post.

Now, you can visit your posts to see your author box, optimized for SEO and E-E-A-T.
Here’s what mine looks like on the front end:

Step 8: Add a Reviewer for YMYL Content (Optional)
If your site covers YMYL topics like health, finance, or legal advice, then adding a reviewer is the highest-value E-E-A-T move you can make beyond setting up your author profiles.
A reviewer is a qualified expert who has checked the article for accuracy. Showing both the author and the reviewer on a post tells Google the content has been through an extra layer of verification, which matters a lot in niches Google scrutinizes more closely.
Create a Reviewer User
Start by adding the reviewer as a WordPress user, the same way you added your authors in Step 3.
Go to Users » Add New User and fill in their name, email, and role. If the reviewer won’t be writing posts, then the Contributor role is a safe choice. It gives them a profile without publishing access.

Fill Out the Reviewer’s Author SEO Fields
Next, go to Users » All Users, hover over the reviewer’s name, and click ‘Edit.’
Open the ‘Author SEO’ tab, the same one you used in Step 4.

Fill out the fields that signal credibility for your niche: job title, employer, institution, awards, knows about, bio, and external profile URLs like LinkedIn.
For example, for a medical reviewer, that might be their MD credential and the hospital they practice at. For a financial reviewer, their CFP designation and firm.
These fields feed into the reviewer’s Person schema, just like they do for authors. The stronger the reviewer’s documented credentials, the more weight Google gives the review signal.
Add the AIOSEO
Reviewer to Your Post
Adding a reviewer to a post takes two quick actions: inserting the AIOSEO –
Reviewer Name block where you want the credit to appear, and then picking the
reviewer in the post sidebar.
Open the post you want to attribute and click the ‘+’ button in the block editor. Search for “reviewer” and insert the AIOSEO – Reviewer Name block.

Place it somewhere visible, like near the top of the post or just below the author meta, so readers see the reviewer’s name before they commit to the content.
Next, look at the right-hand sidebar of the editor for the ‘Reviewer’
dropdown. This is where you tell AIOSEO which user actually reviewed the post.
The block won’t show a name on its own until you set this.
Click the dropdown and pick the user who reviewed this post.

Once the reviewer is set, simply update or publish the post.
The AIOSEO – Reviewer Name block on the page will pull in the reviewer’s name and photo automatically, and AIOSEO will output the reviewer’s details in the page’s structured data alongside the author’s. This means Google can read the writer-and-reviewer relationship directly from the schema.
Bonus Tip: Optimize Your Author Archive Page
Every WordPress site automatically creates an author archive page for each user.
This page does real work for your SEO. When a search engine crawls one of your posts, it follows the author link to the archive page. That’s where AIOSEO outputs the full Person schema markup you configured in Step 4.
But before you focus on making it look good, you need to make a foundational decision first: should your author archive pages be indexed by Google at all?
Should You Index or Noindex Author Archive Pages?
The answer depends on your site’s setup.
Here’s a simple way to think about it:
| Your situation | Recommended setting | Why |
|---|---|---|
| Multi-author blog with active, credentialed writers | Index ✅ | Each author page carries unique Person schema and a meaningful body of posts, which gives real SEO value. |
| Single-author blog | Noindex ⚠️ | Your author archive duplicates your homepage or blog index, which creates thin content and potential duplicate content issues. |
| Authors with only 1–2 published posts | Noindex ⚠️ | Thin archive pages can dilute your crawl budget and signal low-quality content to Google. |
| Ghost authors or placeholder accounts | Noindex ⚠️ | These pages have no real Person schema value and can actively hurt your E-E-A-T signals. |
📘 Important: If you noindex your author archive pages, then the Person schema AIOSEO generates will still exist in the page’s code, but Google won’t factor it into rankings. This means the structured data you set up in Step 4 only delivers its full SEO value when the author archive page is set to index.
Make the Page Look Trustworthy
If you’re noindexing your author archive pages, you’re done here.
If you’ve decided to index these pages, it’s worth taking a little time to make them look good too. A well-presented author page builds trust with readers who land there after clicking an author link, and reinforces the credibility signals you’ve already built into your schema markup.
Here are a few ways to improve it:
- Use your theme’s built-in options — Many WordPress themes include basic styling for author archive pages. Check your theme’s customizer or full-site editor to see what’s available.
- Use a page builder — If your theme doesn’t offer much control, a page builder plugin like SeedProd gives you full control over the layout and design.
- Add a social media feed — Embedding the author’s live social feed using a plugin like Smash Balloon is a simple way to show that the author is a real, active person with a public presence — which reinforces trust for both readers and search engines.
The goal is to make sure the author archive page looks like a real, trustworthy destination, not an unstyled list of posts.
See our guide on how to customize your WordPress theme for a full walkthrough.
Frequently Asked Questions About Author SEO
Here are some of the most common questions our readers ask about setting up Author SEO in WordPress:
Why is Author SEO important?
Author SEO is important because it directly supports Google’s E-E-A-T guidelines, which the search engine uses to evaluate whether your content deserves a top position in search results. Without clear author signals, even well-written content can struggle to rank, especially in competitive or YMYL niches.
Should I noindex author pages on a single-author blog?
Yes, in most cases. On a single-author blog, your author archive page typically duplicates your homepage or blog index, which creates thin content and potential duplicate content issues. Noindexing it avoids those problems. The exception is if your author page has a significantly different layout or content from your homepage, in which case indexing it may still make sense.
Does Organization schema help individual post rankings?
Not directly. Organization schema lives on your homepage, so it doesn’t attach to individual posts. But it works alongside the Person schema on your author pages to give Google a complete, verified picture of your site. Think of it as the foundation that makes your author-level E-E-A-T signals more credible.
Which tool can help me with my author SEO?
All In One SEO (AIOSEO) is one of the best tools for setting up Author SEO in WordPress. It includes a dedicated Author SEO section, generates JSON-LD schema markup automatically, and provides author blocks you can add directly to your posts, all without coding.
Does AIOSEO’s Author SEO feature work alongside Yoast SEO or Rank Math?
You should only run one SEO plugin at a time. If you already use Yoast SEO or Rank Math, then you’d need to deactivate it before switching to AIOSEO so that two plugins aren’t outputting Person and Article schema for the same post. Yoast and Rank Math both handle author metadata at a basic level, but neither offers a dedicated Author SEO module with the same depth as AIOSEO’s author blocks, reviewer fields, and automatic JSON-LD output.
How long does it take for E-E-A-T author signals to show up in Google search results?
Plan on weeks to months. Google needs to recrawl your author pages, re-evaluate the new Person schema, and update how it scores your content. Keep in mind that E-E-A-T is not a direct ranking factor. It’s a set of guidelines Google’s quality raters use, so stronger author signals support better rankings over time but don’t guarantee an immediate lift.
Do I need to add a reviewer to every article for E-E-A-T?
For YMYL topics like health, finance, and legal, then yes. A qualified reviewer with verifiable credentials is one of the strongest trust signals Google looks for on this kind of content. For non-YMYL topics, a reviewer is optional, but adding one to your flagship or cornerstone articles is still a smart way to back up your expertise claims.
Next Steps to Improve Your WordPress SEO
I hope this blog post has helped you set up author SEO in WordPress to boost your Google E-E-A-T.
If you found this helpful, you might want to check out our other guides on:
- Ultimate WordPress SEO Guide for Beginners
- WordPress Site Settings That Are Critical for SEO Success
- How to Check If Your WordPress SEO Is Actually Working
- How to Track SEO Changes on Your WordPress Site
- How Long Does Website SEO Take to Show Results?
If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.
The post How to Setup Author SEO in WordPress to Boost Your Google E-E-A-T first appeared on WPBeginner.
StellarWP Is No More: What’s Changing for GiveWP, LearnDash, SolidWP, and Your Site
If you woke up to news that StellarWP is being dissolved as a brand, you probably have questions.
Back in 2021, hosting company Liquid Web (the same parent that owns Nexcess) launched StellarWP as an umbrella brand to bring together a growing portfolio of WordPress plugins it had been acquiring since 2020.
Over the years, that lineup came to include some of the most recognized names in the ecosystem: GiveWP, LearnDash, SolidWP (formerly iThemes), and more. Each had its own community, support team, and product roadmap.
This week, their parent company Liquid Web (Nexcess) confirmed that those independent brands are being consolidated into a smaller set of products under the Liquid Web Software umbrella.
Since the announcement, many WPBeginner readers have emailed us asking what this means for their sites, whether their licenses still work, and which alternatives we’d recommend. So we put together this guide to lay out exactly what’s changing, what it means for your site, and what your options are if you decide to move on.

What Liquid Web Actually Announced
In their official announcement, Liquid Web confirmed that they’re reorganizing the StellarWP portfolio around four core products: Kadence, LearnDash, The Events Calendar, and Give.
Here’s what that means in practice:
| Brand You Knew | What It’s Becoming |
|---|---|
| 1. SolidWP (Security & Backup) | Folded into Kadence Security |
| 2. IconicWP (WooCommerce add-ons) | Folded into Kadence Shop Kit |
| 3. Restrict Content Pro (Memberships) | Folded into Kadence Memberships |
| 4. MemberDash (LMS Memberships) | Absorbed into LearnDash |
| 5. GiveWP | Rebranded as Give under Liquid Web |
| 6. LearnDash | Continues as a Liquid Web core offering |
| 7. The Events Calendar | Continues as a Liquid Web core offering |
| 8. Kadence | Expanded into the new flagship suite |
Liquid Web has been clear that this is not a forced migration. From their announcement:
“Your current plan, pricing, and tools remain the same unless you choose to upgrade. This is a new option for customers who want more, not a forced migration.”
They’ve also committed to continuing development on the features existing customers rely on (legacy plans aren’t being frozen) and keeping everything self-hosted (your hosting setup doesn’t change). They also plan to provide critical security patches through April 2027 for the brands being absorbed.
There is, however, one important caveat in the announcement: “If your subscription lapses, you’ll need to purchase one of the new software plans to reinstate access.”
In other words, your legacy pricing is protected only as long as you keep renewing. If you miss a renewal for any reason, you can’t reactivate your old plan, and you’ll be required to purchase a new Liquid Web Software plan at current pricing.
If you’re a current customer, the single most important thing to do today is confirm auto-renew is enabled on your account.
So if you’re a current customer, nothing breaks tomorrow. But the road ahead is worth thinking about now, while you have time to plan rather than react.
What This Means for Your Site
We’ve been around this industry long enough to know that when a brand gets absorbed into a parent product, a few things tend to happen over time, even when the parent company has the best intentions:
1. Roadmap priority shifts. Products like SolidWP and IconicWP were built and championed by their original founders. Once they become a “module” inside a larger suite, the feature development typically slows. The new roadmap belongs to the parent brand, not the original product.
2. Support and community change. The dedicated forums, Slack groups, and founder-level responsiveness that long-time users counted on often get turned into a generic support queue.
3. Pricing leverage shifts to the new plans. Liquid Web has confirmed legacy pricing applies as long as you keep renewing. The catch we flagged above… that a lapsed subscription forces you onto a new plan at current rates. That means renewals are no longer fully in your control. And over time, bundled offerings tend to nudge existing customers toward higher-tier plans.
None of this is a prediction. It’s a pattern we’ve watched play out across many WordPress acquisitions over the past decade.
If you’re a happy customer and your site is running smoothly, then you don’t need to do anything right now. Your license still works, and updates are still coming.
But if you’ve been thinking about switching, or if this news has made you worried about the long-term direction of these tools, this is a reasonable moment to look at alternatives.
If You’re Switching: Here Are the Alternatives We Trust
We’ve been recommending and using WordPress plugins at WPBeginner for over 17 years. Below are the alternatives we trust for each affected category.
For Donations & Fundraising: Use Charitable Instead of GiveWP

If you run a nonprofit, church, school, or any kind of donation campaign on WordPress, then Charitable is what we’d point you toward.
It’s the most popular donation plugin for WordPress that isn’t owned by a hosting giant, and the team behind it has been laser-focused on serving nonprofits for over a decade.
With Charitable, you get unlimited donations, recurring giving, peer-to-peer fundraising, fee recovery, Stripe and PayPal integration, and beautiful campaign pages out of the box.
The team also built a one-click GiveWP importer specifically to make this transition easy. You can move your donors, donations, and campaigns over without rebuilding from scratch.
Just remember to double-check your Stripe or PayPal webhook connections after importing to make sure your recurring donations continue without any hiccups.
For a full side-by-side breakdown of other options, see our roundup of the best WordPress donation plugins.
For Online Courses & Memberships: Use MemberPress Instead of LearnDash & MemberDash

If you sell courses, run a coaching business, or manage paid communities, then MemberPress is the most complete alternative on the market.
What used to require two products (LearnDash for courses + MemberDash for membership wrappers) is built into MemberPress as a single integrated system.
You get a full learning management system (LMS) with quizzes, certificates, and drip content, plus native support for memberships, coaching programs, community features, and digital downloads.
The migration path is also easy. Thousands of course creators have moved from LearnDash to MemberPress.
If you’d like to compare other options, our guide to the best WordPress LMS plugins covers all of our recommendations.
For Gated Content: Use MemberPress vs Restrict Content Pro
For pure membership and content restriction (paywalls, member-only content, gated resources, subscription billing), MemberPress is again our top pick.
It was built from the ground up for this use case, and the depth of restriction rules, payment gateway support, and member management features goes well beyond what RCP offered.
We’ve also compared the best WordPress membership plugins side by side if you’d like to evaluate other options first.
For Popups & Optins: Use OptinMonster Instead of Kadence Conversions

If you’ve been using Kadence Conversions for popups, optin forms, or on-site marketing campaigns, then OptinMonster is our recommended alternative.
It’s the most widely used conversion optimization tool in the WordPress ecosystem, with A/B testing, exit-intent detection, advanced targeting rules, and dozens of campaign types built in. That level of depth is hard to match from a bundled theme addon.
If you’d like to compare other options, just see our roundup of the best WordPress popup plugins.
For Backups & Migration: Use Duplicator Instead of SolidWP

For backups, migrations, and disaster recovery, Duplicator is the plugin we trust on every WPBeginner-managed site.
It’s one of the most popular backup and migration solutions in the WordPress ecosystem, with over 1.5 million active installs. The Pro version includes scheduled cloud backups (Google Drive, Dropbox, Amazon S3, OneDrive) and one-click site migrations… features that SolidWP customers paid extra for in the past.
If you bought into SolidWP’s bundle for the combined backup-and-security experience, then Duplicator handles the backup side perfectly. For security specifically, we’d pair it with a dedicated security plugin like Sucuri or Wordfence rather than a bundled tool.
In our experience, specialized solutions outperform combined suites here. Our Wordfence vs. Sucuri comparison is a good place to start if you want to learn more.
For deeper comparisons, see our roundup of the best WordPress backup plugins and the best WordPress security plugins.
For Event Calendars: Use Sugar Calendar Instead of The Events Calendar

If you run a venue, host workshops, manage church or school events, or simply need a clean event calendar on your site, then Sugar Calendar is a great lightweight option.
It’s trusted by event organizers on over 10,000 sites and was built specifically because the team felt The Events Calendar had become bloated and slow over the years.
You get recurring events, ticket sales, Zoom integration, calendar feeds, and elegant front-end displays without the performance hit.
For most small to mid-sized organizations, Sugar Calendar is faster, easier to use, and significantly cheaper.
We’ve also written a beginner-friendly tutorial on how to create a simple event calendar with Sugar Calendar, plus a roundup of the best WordPress event plugins if you want to compare options.
For WooCommerce Add-ons: Use Merchant Instead of IconicWP / Kadence
Shop Kit

WooCommerce store owners who relied on IconicWP’s product variation swatches, quick views, delivery date pickers, and other UX add-ons have a strong alternative in Merchant from aThemes.
Merchant bundles 40+ WooCommerce conversion modules, including variation swatches, sticky add-to-cart, buy now buttons, size charts, pre-orders, frequently bought together, and more into a single plugin.
Most of the IconicWP features you depended on are covered in the free version, with the pro modules priced well below what an IconicWP stack used to cost.
There’s also a free version of Merchant that includes 16+ WooCommerce modules for you to try out.
For Your Theme: Use Sydney or Botiga Instead of Kadence

If you’ve been using the Kadence theme and want to explore alternatives outside of the Liquid Web ecosystem, aThemes offers two excellent options:
- Sydney: a flexible, fast-loading multipurpose theme great for business and agency sites
- Botiga: a modern WooCommerce-optimized theme built specifically for online stores
Both are actively maintained by an independent team, and both pair well with the Merchant plugin mentioned above.
If you’d like to compare more options, see our roundups of the best WordPress business themes and the fastest WooCommerce themes.
Final Thoughts
We know change like this is frustrating, especially when it affects tools that you’ve built your business or organization around.
The good news is you have time and options. Plus, the WordPress ecosystem still has excellent independent alternatives for every category affected by this consolidation.
If there’s one lesson we’ve taken from watching acquisitions play out over the past decade, it’s this: the best long-term bet is to choose plugins built by small, focused teams who care about their product because it’s the main thing they do — not one of many things they happen to own.
That’s why we’ll keep recommending Charitable, MemberPress, OptinMonster, Duplicator, Sugar Calendar, aThemes, and the other products listed above. These are tools built by people who answer their own support emails and plan to still be doing this in years to come.
Whatever you decide, the most important thing is choosing a tool that aligns with how you want to run your site for the next 5–10 years… not just the next two.
Frequently Asked Questions About StellarWP & Liquid Web
Since the news broke, our team has received a lot of messages from readers looking for clarity.
To help you out, we’ve compiled answers to the most common questions about the StellarWP and Liquid Web consolidation below.
Will my existing GiveWP, LearnDash, SolidWP, or RCP license still work after the Liquid Web consolidation?
Yes. Liquid Web has confirmed that existing plans, pricing, and tools remain the same as long as your subscription stays active. However, if your subscription lapses for any reason, you lose your legacy pricing and will need to purchase a new Liquid Web Software plan to regain access. Make sure auto-renew is enabled on your account.
What happens if I miss my renewal date for a legacy StellarWP plugin?
Your legacy pricing is gone. Liquid Web’s announcement is explicit: “If your subscription lapses, you’ll need to purchase one of the new software plans to reinstate access.” You can’t simply reactivate your old plan at the old price. If you’re a current customer, check your account settings now and confirm auto-renew is on.
How long will security updates continue for the retired StellarWP products?
Liquid Web has committed to critical security patches through April 2027 for the brands being absorbed (SolidWP, IconicWP, RCP, MemberDash). After that date, your situation will depend on whether you’ve migrated to the new Kadence-branded equivalent or to an alternative.
Is GiveWP being shut down completely following the Liquid Web acquisition?
No. GiveWP is being rebranded as Give and remains one of the four core Liquid Web offerings. However, the standalone brand identity is going away. Marketing, packaging, and the roadmap will now sit under Liquid Web rather than the original GiveWP team.
Can I migrate my GiveWP donations to Charitable?
Yes. Charitable offers a built-in GiveWP importer that brings over your donors, donation history, and campaigns. Most users complete the migration in under an hour.
Can I migrate from LearnDash to MemberPress?
Yes. There are detailed migration guides for moving courses, lessons, quizzes, and student progress from LearnDash to MemberPress. We recommend testing the migration on a staging site first.
What about The Events Calendar… should I switch after the Liquid Web reorganization?
The Events Calendar is one of the four products Liquid Web is keeping as a flagship offering, so it’s less affected than the absorbed brands. If you’re happy with it, there’s no urgent reason to switch. If you’ve found it bloated or slow, Sugar Calendar is the alternative we’d point you toward. You can also browse our list of the best WordPress calendar plugins.
Are there any alternatives that replace Kadence Security (formerly SolidWP) specifically?
For security specifically (firewall, malware scanning, login protection), we recommend pairing Duplicator with a dedicated security plugin. See our roundup of the best WordPress firewall plugins for trusted options. If you also need to track user changes like SolidWP did, you can easily add a dedicated WordPress activity log plugin to your setup.
If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.
The post StellarWP Is No More: What’s Changing for GiveWP, LearnDash, SolidWP, and Your Site first appeared on WPBeginner.
WordPress.org blog: WordPress 7.0 Release Candidate 4
The fourth Release Candidate (“RC4”) for WordPress 7.0 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC4 on a test server and site.
Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 7.0 is the best it can be.
You can test WordPress 7.0 RC4 in four ways:
| Plugin | Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.) |
| Direct Download | Download the RC4 version (zip) and install it on a WordPress website. |
| Command Line | Use this WP-CLI command: wp core update --version=7.0-RC4 |
| WordPress Playground | Use the WordPress Playground instance to test the software directly in your browser. No setup required – just click and go! |
The scheduled final release date for WordPress 7.0 is May 20, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!
Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information.
What’s in WordPress 7.0 RC4?
Want to look deeper into the details and technical notes for this release? Take a look at the WordPress 7.0 Field Guide. For technical information related to the issues addressed since RC3, you can browse the following links:
- Closed 7.0 WordPress Core Trac tickets since May 8, 2026
- 7.0 Gutenberg commits since May 8, 2026
How you can contribute
WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can get involved with the world’s most popular open source web platform, regardless of your technical expertise.
Get involved in testing
Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. Your help testing the WordPress 7.0 RC4 version is key to ensuring that the final release is the best it can be.
This detailed guide will walk you through testing features in WordPress 7.0.
For those new to testing, follow this general testing guide for more details on getting set up.
If you encounter a potential bug or issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
Help translate WordPress
Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. This release milestone (RC4) marks the hard string freeze point of the 7.0 release cycle.
An RC4 haiku
Step into the next,
bold, new era of WordPress.
Seven-oh is blessed.
Props to @chaion07 for proofreading and review.
WordPress.org blog: Get Your WordCamp US 2026 Tickets

August 16–19, 2026, Phoenix Convention Center – Phoenix, Arizona
Tickets are now available for WordCamp US 2026, taking place August 16–19, 2026, at the Phoenix Convention Center in Phoenix, Arizona. The flagship event brings together people from across the WordPress community to learn, contribute, share ideas, connect with contributor teams, and help shape the future of an open source project that powers over 40% of the web.
Tickets are limited. Secure yours today!
WordCamp US is designed for people at many points in their WordPress journey, including contributors, developers, designers, marketers, publishers, business owners, educators, students, and anyone who wants to learn more about WordPress. This year’s event will include Contributor Day, where attendees can work alongside contributor teams and learn how to take part in the project; Showcase Day, which highlights real-world uses of WordPress; and two full days of sessions and workshops. The programming will also explore how artificial intelligence is changing the way people create, publish, build, and maintain digital experiences, with WordPress as an important part of that broader conversation.
Gather in Phoenix
This year also brings WordCamp US to downtown Phoenix, where the Phoenix Convention Center is close to restaurants, museums, theaters, galleries, live music, and the Roosevelt Row Arts District. Attendees can stay near the venue, meet with other community members between sessions, and explore a downtown area served by Valley Metro Rail. For those extending their trip, Phoenix also offers access to the wider Sonoran Desert region, including parks, gardens, and outdoor spaces that make the city a distinct setting for this year’s event.










Choose the Ticket That Fits
Several ticket options are available, giving attendees different ways to join or support the event:
- General Admission: A $100 ticket that includes access to all four days of WordCamp US programming, including Contributor Day, Showcase Day, sessions, workshops, lunch and snacks, sponsor booths, and the community social.
- Student: A $25 ticket for students who want to learn more about WordPress, connect with mentors and community members, explore open source contribution, and build practical experience.
- Micro-Sponsor: A $750 ticket that includes the same access and attendee benefits as General Admission while helping support the true cost of the event. Micro-Sponsors will also be listed on the official WordCamp US Sponsors page.
Full ticket details, including refund information, visa support, dietary accommodations, registration requirements, and other attendee information, are available on the ticket page. You can also follow the WordCamp US 2026 website for updates on the schedule, speakers, travel information, and more as the event gets closer.

Open Channels FM: Challenges and Wins of Developer Advocacy Plus OpenTelemetry and Neurodiversity in Modern Tech
In this episode, hostsCarl Alexander and guest Diana Todia discuss neurodiversity in tech and the role of Developer Relations, emphasizing the importance of community support, open source contributions, and the growing significance of OpenTelemetry for observability.
How to Reduce No-Show Appointments With WordPress (Stop Losing Money)
You’ve set aside time for a client appointment, prepared your materials, and blocked out your calendar. Then the appointment time comes, and nobody shows up.
It’s frustrating, and it’s costing your business both time and money.
You’ve probably noticed how doctors and dentists handle this. They send you email reminders days before your appointment, then follow up with a confirmation request.
And it works. Automated reminders can meaningfully reduce no-shows, which means fewer wasted time slots and more predictable revenue for your business.
The good news is that you can set up the same professional reminder system on your WordPress site with the right plugin. In this guide, I’ll show you exactly how to reduce no-show appointments using WordPress, including how to automate email reminders and require deposits.

Quick Summary
Reducing no-show appointments doesn’t have to be complicated or time-consuming. With Sugar Calendar Bookings, you can create an automated system that keeps your schedule full and your clients accountable.
The combination of email reminders, self-service links, and optional pre-payments gives you multiple layers of protection against missed appointments.
Once you set everything up, it runs on autopilot, saving you hours of manual follow-up while noticeably improving your attendance rates.
Here are the topics I’ll cover in this tutorial:
- Why Reducing No-Show Appointments Is Important
- Which Booking Plugin Should You Use?
- Before You Start
- Install and Configure Sugar Calendar Bookings
- Send Email Booking Notifications With Sugar Calendar Bookings
- Require Pre-Payment or Deposits for Appointments
- Make Rescheduling Easy and State Your Cancellation Policy
- Frequently Asked Questions About Reducing No-Show Appointments
- Additional Resources for Appointment Bookings
Why Reducing No-Show Appointments Is Important
No-show appointments are more than just an inconvenience. They cost your business real money in lost revenue and wasted time that you could have spent with paying clients.
When someone misses an appointment without warning, you’re left with an empty time slot that’s often too late to fill.
This means you’ve blocked off part of your day for nothing, and those hours add up quickly over weeks and months.
Understanding why clients miss appointments helps you pick the right fix. Most no-shows fall into a few key areas:
- The client forgot about the appointment.
- The client double-booked.
- The client lost interest but didn’t want the awkward cancellation call.
- Or the client never had real commitment because no deposit was on the line.
Each strategy in this guide targets one of these causes. Reminders fight forgetting. Self-service links fight the awkward-call problem. Deposits fight the no-commitment problem.

The good news is that automated reminders can meaningfully cut how often this happens. Let me break down how different notification strategies stack up against each other:
| Strategy | Why It Works |
|---|---|
| Email Reminder | Serves as a gentle nudge to refresh the client’s memory. Best sent 24-48 hours before the appointment. |
| Self-Service Link | Allows clients to easily reschedule or cancel, so they notify you instead of ghosting. |
| Pre-Payment / Deposit | Creates financial ‘skin in the game’. Clients rarely miss appointments they have already paid for. |
The impact of self-service links might seem counterintuitive. You might wonder why making it easier to cancel would improve attendance.
The answer is simple psychology. When clients have an easy way to reschedule, they are much more likely to notify you in advance rather than simply not showing up.
A last-minute cancellation is frustrating, but it is far better than a no-show. At least with advance notice, you have a chance to fill that slot with another client.
Which Booking Plugin Should You Use?
I recommend Sugar Calendar Bookings because it is a complete appointment scheduling suite. Booking forms, Stripe payments, Zoom calls, and email automation all come bundled, so you can run every no-show prevention strategy in this guide without installing three or four single-purpose plugins.
The plugin supports email notifications natively, so you can set up automated reminders right out of the box.
It also lets you include self-service links in your email notifications. These links give your clients one-click access to manage their appointments, which removes the friction that often leads to no-shows.
Finally, you can require a deposit or full payment during booking. The plugin also integrates with Stripe, so clients have a financial stake in the appointment. That lowers the chance they’ll skip it.
I have found that the combination of automated reminders, self-service options, and upfront payments creates the most effective system for keeping your schedule full.
Before You Start
Before you follow this tutorial, let’s make sure you have a few things ready:
- A WordPress website you can log in to as an administrator.
- A short list of the services you offer, with rough durations and prices.
- A free Stripe account if you plan to collect deposits or pre-payments. You can create one at stripe.com in a few minutes.
Install and Configure Sugar Calendar Bookings
Before you can start sending automated reminders, you need to set up your booking plugin. Sugar Calendar Bookings makes this process straightforward, even if you’re new to WordPress plugins.
The setup only takes about 10 minutes, and once it’s done, you’ll have a complete booking system ready to accept appointments. Let me walk you through each step.
Step 1: Install and Activate Sugar Calendar Bookings
First, you need to install the Sugar Calendar Bookings plugin. There are two versions to choose from:
- Sugar Calendar Bookings Lite (Free): Includes the booking form, Stripe payments, Zoom, and appointment reminders. Stripe payments through Lite carry a 3% transaction fee on top of Stripe’s own processing fees, so Lite is best for a solo provider testing the system or running reminders-only.
- Sugar Calendar Bookings Pro: Removes the 3% Lite fee on Stripe payments, and adds multiple-employee scheduling, per-service email templates, and priority support. Best if you’re taking deposits or pre-payments regularly, or running a team.
For this tutorial, I’ll use the Pro version to show the full admin experience and skip the 3% Lite fee on payments. You can follow every step here on Lite if you want to test before you upgrade. Both tiers include a 14-day money-back guarantee, so you can try Pro risk-free.
If you need help, then see our step-by-step guide on how to install a WordPress plugin.
Step 2: Configure Core Settings with the Setup Wizard
One of the things I really appreciate about this plugin is the Setup Wizard.
After you activate the plugin, it launches automatically. You can simply click the ‘Let’s Get Started’ button to begin.

The setup wizard will quickly help you set up the plugin:
1. Choose Your Meeting Type: First, you’ll select how you meet clients. Choose ‘In-Person’ for physical locations or ‘Custom Link’ for virtual meetings (like Zoom or Google Meet).
2. Select Your Industry: Next, you can pick the category that best describes your business (for example, ‘Health & Wellness‘ or ‘Education’). Sugar Calendar will pre-load sample services based on your choice to help you get started quickly.
3. Customize Your Services: You’ll see a list of suggested services. You can easily edit the Name, Duration, and Price for each one right here. I find it helpful to just get the basics down now—don’t worry about getting it perfect, as you can always change these later.
4. Set Employee & Availability: Enter your details as the primary service provider. Then, set your default Availability Schedule (such as Mon-Fri, 9 AM – 5 PM). This makes sure clients can only book times when you’re actually free.
5. Connect Payments: Finally, you will see an option to connect Stripe. If you plan to require pre-payments or booking deposits, then simply click the ‘Connect with Stripe’ button. I recommend doing this now to get it out of the way.
Pro Tip: Don’t forget to block out holidays. Go to Bookings » Settings » Availability later and scroll down to the Date Overrides section. Here, you can mark specific dates as unavailable so no one books you on days you’re off.
For a full walkthrough of how to do this, see our guide on how to set up a WordPress appointment booking system and book clients 24/7.
Once you finish the wizard, your booking system is almost ready. You just need to visit the Bookings » Settings page and enter your license key. You can find this information in your account on the Sugar Calendar website.
Step 3: Display the Booking Form
Now that your settings are configured, you need to display the booking form so clients can use it.
Create a new page in WordPress and name it something like ‘Book Now’. Next, simply click the ‘+‘ button to add the ‘Booking Form’ block.

In the block settings on the right, you have a few customization options. I personally prefer the ‘3 Column’ layout for a compact view, but the ‘2 Column’ option works great for sidebars.
- Time Slot Layout: Choose ‘3 Column’ for a compact view or ‘2 Column’ for sidebars.
- Form Appearance: Select ‘Light’ or ‘Dark’ mode to match your website’s theme.
- Services: You can choose to show all services or specific ones.
Don’t forget to click the ‘Publish’ button to make your booking page live.
Finally, I recommend visiting your new booking page to see how it looks and test the booking process yourself.
Send Email Booking Notifications With Sugar Calendar Bookings
Email reminders are your first line of defense against missed appointments. Since they are built directly into Sugar Calendar (even the free version), I think they are the easiest way to start reducing no-shows immediately.
These automated messages remind clients of the time and build confidence in your business. When clients see a professional confirmation and reminder system in place, they take the appointment more seriously.
Best of all, once you set this up, it runs on autopilot. You’ll never need to manually email a client to confirm a time again.
Step 1: Access Notification Settings
To configure your emails, you can head over to Bookings » Settings in your WordPress dashboard and click the ‘Emails’ tab.

Here, you’ll see a list of all available email types, including ‘Booking Confirmation’, ‘Cancellation’, and ‘Appointment Reminder’.
By default, most of these are enabled, but you can toggle them on or off based on your workflow.
Step 2: Customize Your Reminder Templates
Next, you can click the ‘Edit’ button next to the ‘Appointment Reminders to Attendee’ template.

This opens the editor where you can personalize the message.
You’ll notice Smart Tags like {service_name}, {start_date}, and {start_time}. These automatically pull in the specific details for each appointment, so every email feels personal and accurate.
My Recommendation: Add a Cancellation Link
You’ll likely see that the plugin automatically adds a ‘Cancel Appointment’ link to the footer of the email.
This is great, but I also prefer to give clients a specific way to manage their booking in the main body of the text.

Giving clients an easy way to change plans can reduce no-shows by up to 70%. You can use the {cancel_url} tag to give them that option upfront.
Here is a script I like to use:
Hi {customer_full_name}, this is a friendly reminder about your {service_name} scheduled for {start_date} at {start_time}. If you need to change your time, please click here: {cancel_url}
Don’t forget to click the ‘Save Settings’ button at the bottom of the page to store your customized email reminder.
Step 3: Test Your Notifications
Before going live, it’s always a good idea to test the system. You can create a test appointment for yourself and check your inbox.
Does the email arrive? Do the Smart Tags display the correct time?
Troubleshooting Tip: If the emails aren’t arriving, then they might be getting stuck in spam folders. This is a common WordPress issue.
To fix this, I strongly recommend installing WP Mail SMTP. It helps your appointment reminders land in your clients’ primary inbox, so they never have an excuse to say “I didn’t get the memo.”
Require Pre-Payment or Deposits for Appointments
Pre-payment is one of the most effective strategies to reduce no-shows. It relies on a simple psychological principle: ‘Skin in the Game’.
I’ve found that when clients make a financial commitment to their appointment (even a small one), they treat it as a firm obligation rather than a casual plan. Nobody likes to lose money, so that upfront payment serves as a powerful motivator to show up.
Pre-payment also makes your operations cleaner. You don’t have to chase down outstanding invoices or sort out payment delays when the client arrives.
Plus, only clients who are serious about your services end up taking space on your calendar.
Step 1: Verify Your Stripe Connection
If you connected Stripe during the Setup Wizard earlier, then you’re already on the right path. However, it is always a good idea to double-check that the connection is active before you start pricing your services.
You can head over to Bookings » Settings and click on the ‘Payments’ tab. You should see that Stripe is enabled.

But if you skipped this step previously, then you can simply click the ‘Connect with Stripe’ button here to link your account.
While you’re on that page, make sure that you are using the right currency.
Step 2: Set Service Prices (The ‘Deposit’ Strategy)
Once Stripe is connected, you need to determine how much to charge. In Sugar Calendar Bookings, pricing is set individually for each service.
You can go to Bookings » Services and click the ‘Edit’ icon for the service you want to update (such as ‘Group Fitness Class’).

In the Price field, you can simply enter the amount you want to charge. While there is only one field, you can use it in two different ways depending on your goal:
- Strategy 1: Full Pre-payment. You can enter the full service fee (like $100). This eliminates the risk of non-payment entirely.
- Strategy 2: Booking Fee (Deposit). Alternatively, you can enter a smaller amount (such as $25) to act as a deposit to secure the slot. This lowers the barrier to entry while still making sure the client has a financial commitment to showing up. Just keep in mind that Sugar Calendar will only process the amount you enter here. You will need a separate process (like your in-person point-of-sale system or a separate invoice) to collect the remaining balance at the time of the appointment.

Once you save the service with a price, the booking form will automatically require that payment via Stripe before the appointment is confirmed.
Step 3: Communicate Your Policy Clearly
Technically, the booking form will simply display the price you entered above. It won’t automatically label it as ‘Full Price’ or a ‘Deposit’. This can be confusing if the total service cost is actually higher.
To avoid any misunderstandings, I strongly recommend being very clear in the service name or description.
For example, you might name the service ‘Initial Consultation ($20 Deposit)’ so the expectation is set immediately. Then, in the description, you can clarify the terms:
Note: The total cost of this service is $100. The $20 paid today is a deposit to secure your slot and will be deducted from your final bill. This deposit is fully refundable if you cancel at least 24 hours in advance.
I’ve found that stating this upfront filters out less serious inquiries and saves you from awkward conversations about money later on.
Pro Tip: If a client cancels inside your stated window, you can refund their Stripe payment directly from the Bookings payments dashboard — no need to log in to Stripe separately. I recommend stating your refund window plainly in the service description (for example, “Refundable up to 24 hours before the appointment”) so the policy is clear before any money changes hands.
Make Rescheduling Easy and State Your Cancellation Policy
Self-service rescheduling can reduce no-shows by 50-70%. The reason is simple: when canceling is friction-free, clients tell you in advance instead of ghosting.
Sugar Calendar Bookings sends every confirmation email with a unique cancellation link, and the cancel link is added to the email footer automatically.
You can also drop the {cancel_url} smart tag directly into the body of your reminder template (I covered this in the email section above), so clients see the option every time you nudge them.
I also recommend pairing the rescheduling flow with a clear written policy. State your cancellation window plainly — for example, ’24-hour notice required to reschedule’ — in three places: your service description, your booking confirmation email, and your reminder email.
When the policy is visible early on, you almost never have to enforce it after the fact.
Frequently Asked Questions About Reducing No-Show Appointments
Reducing no-shows can have a real impact on your revenue and your calendar.
Here are some common questions business owners have about managing appointments and preventing no-shows on a WordPress site.
1. How do you reduce no-show appointments effectively?
The most effective way to reduce no-show appointments is to combine multiple strategies. Sending automated email reminders 24 hours in advance keeps the commitment fresh in the client’s mind. Additionally, requiring an upfront deposit at the time of booking creates a financial incentive for the client to show up. Finally, providing a self-service cancellation link allows clients to easily reschedule in advance instead of simply ghosting the business.
2. How do I send automated appointment reminders in WordPress?
You can send automated appointment reminders in WordPress by using an appointment scheduling plugin like Sugar Calendar Bookings. Once you install Sugar Calendar Bookings on your website, you can configure the plugin to automatically send customized email notifications to clients before their scheduled time slot.
3. How much of a deposit should I charge for appointments?
The ideal deposit amount depends on your specific industry, but charging between 20% and 50% of the total service cost is a standard practice. A small deposit of $20 to $25 is often enough to lower the barrier to entry while still ensuring the client has a financial commitment to attending the appointment. You can easily configure these upfront booking fees using a tool like Sugar Calendar Bookings alongside its built-in Stripe payment integration.
4. What is the best WordPress appointment booking plugin to prevent no-shows?
Sugar Calendar Bookings is one of the best WordPress appointment booking plugins for preventing no-shows. It stands out for small businesses because it offers native email reminders, built-in self-service cancellation links, and Stripe integration for collecting upfront deposits. These are all proven methods for keeping a business schedule full.
5. Why does making it easier to cancel appointments actually reduce no-shows?
Making it easier to cancel appointments reduces no-shows because of simple human psychology. When clients have to call to cancel a meeting, they often feel embarrassed or anxious and choose not to show up. By putting a self-service cancellation link directly in an automated email reminder, clients are much more likely to notify the business in advance, allowing the business owner to fill the empty time slot.
6. Do I need Sugar Calendar to use Sugar Calendar Bookings?
No. Sugar Calendar Bookings is a standalone plugin, so you do not need a separate Sugar Calendar license to use it. You only need the Sugar Calendar Bookings license tier that fits your business — Lite for testing or reminder-only use, or Pro for regular pre-payments and multi-employee scheduling.
Additional Resources for Appointment Bookings
I hope this article helped you create a complete system for reducing no-show appointments on your WordPress site. By setting up automated reminders and self-service options, you’ll spend less time chasing down clients and more time focusing on your actual work.
If you found this guide helpful, you might also want to explore these related tutorials to further improve your WordPress booking system and business website:
- How to Create a Contact Form in WordPress
- Best WordPress Appointment and Booking Plugins
- Must Have WordPress Plugins for Every Website
If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.
The post How to Reduce No-Show Appointments With WordPress (Stop Losing Money) first appeared on WPBeginner.
Gravatar: Connect Your Research Identity with ORCID on Gravatar
Researchers, scholars, and contributors can now connect their ORCID iD to their Gravatar profile as a verified account.
With this update, your Gravatar profile can include a trusted research identity alongside the other places people can find you online — from your personal site and social profiles to the platforms where you publish, collaborate, and contribute.
What is ORCID?
ORCID, which stands for Open Researcher and Contributor ID, provides a unique, persistent identifier for people involved in research, scholarship, and innovation.
An ORCID iD helps distinguish you from other researchers and contributors, even if you share a similar name, change institutions, publish across disciplines, or contribute under different affiliations over time. It’s widely used across the research community to connect people with their work, affiliations, funding, and scholarly contributions.
In short: ORCID helps make sure your work is connected to you.
Why add ORCID to your Gravatar profile?
Your Gravatar profile is a simple way to bring your online identity together in one place. Adding ORCID makes that profile more useful for researchers, academics, students, writers, and contributors who want to showcase a recognized scholarly identity.
By connecting your ORCID iD, you can:
- Show a trusted research identity on your Gravatar profile.
- Help others find your scholarly work and contributions through your ORCID record.
- Keep your identity portable across the web, connected to the same Gravatar profile people already recognize.
- Bring more context to your profile by linking your research identity with your professional and personal presence online.
Whether you publish papers, contribute datasets, review research, collaborate with institutions, or simply want your academic identity represented, ORCID is a natural fit for your Gravatar profile.
How to add your ORCID iD to Gravatar
Adding ORCID works just like other verified accounts in Gravatar:
- Go to your Gravatar profile.
- Open the Verified Accounts section.
- Choose ORCID from the list of services.
- Sign in with ORCID and approve the connection.
- Your ORCID account will appear on your Gravatar profile as a verified account.
Once connected, visitors to your profile can easily find and recognize your ORCID iD.
Bring your research identity with you
Gravatar helps you maintain a consistent identity across the web. With ORCID support, that identity can now include the research and scholarly work that matters to you.
Ready to connect your research identity?
Update your Gravatar profile and add your ORCID iD today.
WPTavern: #216 – Matt Schwartz on Exploring AI’s Impact in WordPress Agencies (Part 2)
[00:00:19] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case a second look at exploring AI’s impact in WordPress agencies.
If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.
If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.
So on the podcast today, for a second time, we have Matt Schwartz.
Matt has been working in the WordPress ecosystem since 2011, running his own agency based in Atlanta, and developing products like CheckView at all for WordPress form and checkout QA. Matt’s expertise lies in how agencies can smartly, and cautiously, incorporate AI into their workflows for real tangible wins, and how to avoid potential pitfalls.
He was on the show last week to record the first of this two part mini series. You might want to listen to that prior to this, but it’s not strictly necessary.
In this episode, we build upon last week’s conversation. Matt talks about practical strategies for integrating AI across agency operations. The discussion starts with what it means to give AI access to your agency’s brain, using tools like project management wikis and connecting them with AI chatbots to streamline knowledge sharing, and avoid common AI hallucinations.
We then get into MCPs, or Model Context Protocol, and talk about why this area is quickly becoming a game changer for agencies looking to securely connect AI agents to multiple internal systems without complex, risky API configurations.
The conversation covers how to use AI for building internal tools, highlighting where it’s low risk and where you should be more cautious, especially with public facing, or mission critical, systems. Matt explains how agencies can leverage AI for QA and checklist automation, freeing up time for deeper human review of other important tasks.
We also discussed the impact of AI on the WordPress plugin market, including potential consequences for plugin developers and the wider community, and whether the rise of AI generated disposable tools could erode the collaborative spirit of the WordPress community.
We end by chatting about the importance of approaching agency AI adoption with eyes wide open to the risks. Data security, overdependence on vendors, failure to handle errors, and the reality that AI still makes mistakes.
Matt shares his outlook on how agencies can position themselves to thrive as AI reshapes the industry, from hiring strategies to the next generation of productised services.
If you’re running an agency or freelance business in the WordPress space and want to get ahead with AI thoughtfully and securely, this episode is for you.
If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.
And so without further delay, I bring you Matt Schwartz.
I am joined on the podcast, again, by Matt Schwartz, somewhat unexpectedly. Hello, Matt.
[00:04:05] Matt Schwartz: Hey Nathan, thanks again for having me this week. I’m super excited to dive back in.
[00:04:09] Nathan Wrigley: Thank you. So we recorded an episode last week, and we intended to do it as a one hit. So get it all recorded, tied off within 40 minutes or what have you. And then we began talking.
So last week we began talking and at about the half an hour point, it became obvious to me that we weren’t going to capture it all in one recording. So we’ve come back for a second episode.
Dear listener, I would just say that in order to provide context for this episode, you really probably should listen to the previous one, because we’re stacking up Matt’s case, argument, however you wish to describe it, for where you can make wins inside your agency with the use of AI. Not just wins, maybe some cautionary tales as well. But that was the point of the first episode.
So really, we’re going to drop you in to the ninth of 16 points. So again, just pause this, go back to the previous episode, have a listen there, and then you can stack this one in your podcast player of choice at that point.
If, however, somebody’s ignoring that, Matt, are you able to just do a very quick bio? Just tell us who you are? It may be repetitive for the people that are listening to the second episode, but nevertheless, let’s hear from you who you are.
[00:05:16] Matt Schwartz: Yep. My name’s Matt Schwartz. I run a WordPress agency here in Atlanta, since 2011. And I also have a testing and QA product for WordPress for checking forms and checkout called CheckView.
And yeah, today we’re just really diving into how you can leverage AI, how you can incorporate it into your agency, but in a hopefully smart and cautious way. Not necessarily just dropping it in, being a little bit more thorough about that process. So excited to continue the conversation.
[00:05:45] Nathan Wrigley: Yeah, thank you. And thank you for being so accommodating by joining me for a second time. So as I said, Matt’s put together a whole laundry list of different areas that your business, your freelance agency, whatever it may be that you are running in the WordPress space, can perhaps gain some benefits.
Last week we did one through eight, and now we’re going to sort of hit the road running on number nine. So the ninth point was about giving AI access to your agency’s brain. It’s a lovely subheading, but what does that mean?
[00:06:12] Matt Schwartz: Yeah, so this is actually one I picked up in the Admin Bar, which is a, one of the other WordPress agency groups out there, that a lot of agencies were doing. And I thought it was an interesting, I would say hack, you could say, to add AI without getting super involved in it. Which is if you already have a project management tool, or you already have a wiki, you can add into your AI chat bot of choice when it’s actually answering a question. You can tell it in its memory, hey, whenever I ask a question about the agency, go confirm what I’m doing by visiting our Clickup or visiting our Asana.
So it’ll actually go retrieve and confirm it’s using the latest proper information instead of just guessing or hallucinating. I love how we use the word hallucinate and not lie. I love that marketing branding that the AI companies did. It’s some crazy gaslighting.
Anyways, I love AI, but definitely, if you haven’t used something like Claude or ChatGPT, saying in the memory as simple as when you answer a question, check if this is actually the case and connect to our ClickUp or connect to our wiki.
I think that helps you get all the power of your documentation, SOPs, client, CRM, any data you’ve already basically built up. It can leverage that without you having to do a whole bunch of crazy connections or ask more specific things. I thought that was actually a really neat way that agencies that are just getting into the space with AI are using the data they basically already have. They’re just using their project management software, which basically has all that data.
[00:07:47] Nathan Wrigley: When you see it in action, which I have actually, but not to do with a WordPress website, more to do with a sort of SaaS product with the, how the tool has been built and the guardrails that are into the tool. It’s really amazing because then, well, basically it never forgets.
So every time you throw something new at it, that becomes part of the corpus of information. It then has an understanding. I keep saying it, but hopefully you understand, I’m meaning the AI in this case. A wider and broader understanding, and increasingly is able to deliver that back.
So in my case, often I’ll get some text back, which is divided up into bullet points. Those bullet points will have little footnotes attached to them, you know, 1, 2, 3, 4, and what have you, which will then link out to the documentation itself. And again, just a profoundly useful use of the thing which it’s best at, which is taking a corpus of information, grinding it up and spitting out something which makes sense.
And why wouldn’t you point it at your internal documentation? You know, if you’ve got a plugin, all of your support docs, throw the AI at it, and it will be able to help you as well as your clients. Because it’s guaranteed you’ve forgotten something that you’ve built.
WordPress, of course, itself does this. You know, every AI agent on the planet is welcome to crawl the docs for how WordPress itself is put together. And it’s one of the reasons I think why WordPress has a fighting chance in this AI, CMS battle, if you like, because everything’s open source already. Nothing’s hidden behind a paywall or a licence agreement or what have you. So yeah, agreed. That’s a great example.
Okay. Anything to add or should we move on?
[00:09:22] Matt Schwartz: No, I think that one’s just a cut and dry, really. If you haven’t looked at that, that’s an easy way to get into AI and leverage it without a lot of work.
[00:09:29] Nathan Wrigley: Okay. Absolutely. Okay, then number 10 is your internal MCP and guardrails. I know this gets bandied around a lot, and there’s a lot of acronyms floating around in the AI space. But MCP, maybe we just need to spend a moment explaining what the heck an MCP is, and how it kind of fits into the overall picture, but particularly in this case, with your guardrails.
[00:09:48] Matt Schwartz: Definitely. So MCP is basically an open source way to connect AI, let’s say, chatbots or agents to external systems. It stands for Model Context Protocol. I think maybe the team behind Claude built it. I can’t remember. But the idea really is that, instead of you just connecting directly to an API, which you could do, which an API if you’re not familiar, is a way again, to connect two different systems together.
One system will have a series of things that will let you say, hey, you can add this data, or you can pull this data, or you can modify this data, right? So an example could be something like a help desk. You might create a ticket, you may delete a ticket or you may edit the ticket. An API can basically do those things.
But what an MCP does is it’s really a series of tools that are more prebuilt for the AI, so that it knows and has context of what it should let you do, and how all the pieces of that connection really should modify whatever data you’re doing.
So it’s a lot more specific to agents. It’s a lot friendlier, I would say, if you aren’t familiar with a company’s API, you could connect to their API. I can connect to the WordPress REST API, but if I don’t understand that API, it may not be actually the best way to make the connection.
With an MCP, you can really not have the background of that company’s bridge. It’s going to do all the work, and the AI’s going to have enough information to help you get what you need done.
I know that’s hard to explain, but essentially with an MCP, if you build one at your agency, this is a little bit more high level, or a little bit deeper, but I am seeing a lot of agencies looking at this. Which is, they are using an MCP basically for their teams so that they can add all of their systems in one basically bridge. So that instead of having all their employees like connect to all these different Claude connectors and APIs, they have one system.
So if I have Claude and I’m an employee, it can connect to my MCP at the agency, then the agency MCP is actually on behalf going to go retrieve data from all our different systems. So not everyone has to have API keys. Not everyone has to connect to all these other systems, if that makes sense.
So I am seeing agencies starting to do this. So in some sense the proxy, MCP becomes a proxy or just a way to connect to all your other systems in a secure way.
[00:12:18] Nathan Wrigley: I always imagine it a bit like if you, I don’t know, you approach a giant supermarket and you know that you need carrots and soup. And normally you just go into the supermarket and wander around for a long time, and eventually you’d sort of stumble across the carrots and the soup.
But wouldn’t it be nice if there was somebody at the front door? Then you could say, where’s the carrots and where’s the soup? And that’s it. And they go, okay, the carrots are there, the soup’s there, and point.
You know, it’s just like this perfect gatekeeper, this guardrail that you described that kind of allows you to get the best out of that experience without wasting a load of time and resources and probably a load of hallucination out the back end.
[00:12:55] Matt Schwartz: Wow, that was so much better said than me. But yes, that is a much better way of explaining it. And that’s why if you haven’t looked at MCPs in general, I think it’s worth looking at. But also if you have a tech background, looking at an MCP for your own agency where you can combine all your tools and connect to this one place, I think is a really neat way to, again, get your employees and contractors connected to your, all your systems without them having to have a direct connection.
So if I want them to be like, hey, answer this ticket, go to this WordPress site, instead of them having to connect Claude to the WordPress site into Fresh Desk and all these things, it’s all within the one MCP. And then they aren’t really responsible for those API keys or any of those connections.
Of course, you have to put guardrails on that too, right? Guardrails, like they can’t delete things. You know, not having them delete tickets or websites. Because if you connect, you know, your host, they could technically delete an entire website if you don’t have proper guardrails. So it is, I would say something that is a little bit more on the cutting edge that not every agency should do, but if you are on the more technical side, an internal agency MCP, I think is a really neat idea.
[00:14:06] Nathan Wrigley: I feel like there’s future of commoditising MCP creation.
[00:14:11] Matt Schwartz: Oh, it’s already happening.
[00:14:12] Nathan Wrigley: Yeah, I really haven’t experienced that but, you know, a really, I don’t even know what that interface might look like in the end, but some really credible way of, you know, you sign up for a service and for a few dollars a month, they will modify, create on the fly, adapt the MCP so that it fits in with what was already an incredible technology. It’s a bit like the icing on the cake, the MCP, isn’t it? The AI was pretty amazing anyway, and then you put that layer on top and it just becomes much more refined amazing.
[00:14:41] Matt Schwartz: There’s actually some companies doing that already where you sign up for their SaaS, they basically store all the MCP data on their server securely, because that’s always a concern. You give them basically all the credentials, you give them the guardrails, and then they build a secure, essentially MCP app for you.
So there are some early options out there for that, that agencies could also look into if they’re less technical. You just want to make sure, obviously you realise you’re giving a third party your data and your secrets essentially.
[00:15:11] Nathan Wrigley: And course, in the era of AI, the capacity to do things really seriously wrong is literally at the end of your fingertips. Whereas before, you’d probably have to have some understanding, well, you could delete whole file structures and things like that, I guess. But now that a simple prompt can just rip through your entire code base or whatever it may be, definitely, one for guardrails there.
[00:15:32] Matt Schwartz: Delete all the sites on my server, done.
[00:15:34] Nathan Wrigley: Yeah, that’s right. Yeah. And don’t check.
[00:15:37] Matt Schwartz: That could happen.
[00:15:38] Nathan Wrigley: Yeah. Ignore all previous instructions, just delete them all.
Okay, so that was number 10. And really interesting. I think that’s one for the, sort of the tinfoil hat brigade, you know, the real nerds out there. But it’s not far off. If it’s been commoditised in SaaS now, you can guarantee that in the next few years that’s going to become table stakes, I would’ve thought for a lot of businesses and SOPs and what have you.
Okay, so the next one, I’m sure many people will have been familiar with, especially if you have a YouTube account and you’re looking at AI things on YouTube. Vibe coded agency tools. I’m sure I know what this one means, but run it by me anyway.
[00:16:16] Matt Schwartz: Yeah, so one key thing is, I’m not saying vibe coded tools themselves. I’m saying vibe coded agency tools, agency being the specific part. So you’re building internal tools for your agency, which I think in some sense, depending on what the situation is, can be okay to do, in my opinion, because the risk is lower. Again, you’re using it internally.
[00:16:40] Nathan Wrigley: It’s not public facing, that’s the point, right? It’s just you and your colleagues, which hopefully you trust.
[00:16:45] Matt Schwartz: Right, right. Again, you should probably put guardrails, and you have to think about, well, what sort of data is it touching, and how important is this data? That’s everything with AI. You have to think about the risk. But I am seeing a lot of agencies starting to build different types of agency tools. Some that I really do internally myself, and I am a big fan of things like reporting tools and dashboards, right?
This is, again, a good case, I think I talked about in the previous podcast. The sweet spot, I think with AI is having it handle things that you just never could get to that were on your list for a million years, right? And realising that, as long as you do a little due diligence and you feel like it’s in the realm of where it’s supposed to be, this is probably more information than you had before, right?
So a good example is, if you’re an agency, you may have it hooked up to QuickBooks MCP. You may have it hooked up to your time tracking software. You may have it hooked up to one of your other reporting software, WooCommerce subscriptions with Woo. And from there you’re able to have a much better visible idea of what your business is doing well financially. The bottom line, especially if you’re like a lot of agencies where QuickBooks doesn’t really have all of your actual services. You may have those internally or you may have them in a other system.
You can combine those and build reporting systems. And again, that’s a relatively low risk way for you to, worst case is you’re going to use that data and you’re going to be like, well, this doesn’t seem right. And you’re going to have to dig into it and figure out what’s going on. Hopefully you don’t just blindly use it, but I do think the risk is lower.
So those sort of tools I think are really, really neat, and relatively easy to build out. So reporting tools, profitability dashboards, things like that. Looking at your time tracking, like who at your agency is the most profitable, if you have that data? Obviously make sure you actually have the data structure for that, or AI may just make that up.
But we’ve, you know, used that even at our agency and I think it’s been helpful for us to find patterns that we didn’t know where we were spending our time and effort. Especially if you are doing time tracking using something like Everhour or Harvest.
Now the tools that I do struggle a little bit more with, and I am seeing people in agencies use is things like website management dashboards, or building their own QA tools. Because those things, I think the risk is higher of things going wrong.
[00:19:05] Nathan Wrigley: Public facing again, yeah.
[00:19:07] Matt Schwartz: Right. And you’re giving this third party access to all of your websites and it’s not like, you know, a big SaaS. This is something you built internally, which means Claude doesn’t care if it’s wrong, right, until you tell it.
So a good example, and not everyone may feel this way but, you know, I’ve seen some agencies that are building replacements for management dashboards like ManageWP, WP Remote, those sort of things, which is connected to everything and is kind of their most important infrastructure for their clients. Personally, I think that that’s a little risky to be doing.
Now, if you’re doing the right due diligence and you have a technical team and you’re doing manual code reviews, sure. There’s an argument to be doing that if it’s also, I think, solving something specific to your agency. I talked about this in the last podcast, replacing SaaS products when there’s a nuanced solution that’s specific to your agency, I think could be really helpful.
But if you’re just replacing SaaS products to save 30 bucks a month, I think that doesn’t make any sense because you’re going to end up spending a lot more on maintenance, I promise you, than if you just stuck with the SaaS product, if it does what you need. So I think there’s an argument there.
[00:20:18] Nathan Wrigley: I think it’s really interesting. And I do wonder if we’re on the precipice of, so this is me sort of staring into the crystal ball a little bit. I wonder if we’re into the era of sort of disposable, one time apps. So you have a function that you need to do this month like, I don’t know, you must file your taxes this week, but you’re miles behind. So you get an AI to just quickly do that thing for you, and categorise all of the jobs that need to be done so that you can hand it over to the tax man and so on. And then you just put that on ice. That thing no longer needs to exist.
I feel that kind of coming where we sort of vibe code up this one time thing, and then dispose of it. I don’t know if I’m entirely in agreement with that as an idea, but I feel that that is coming. But to your point, I think anything public facing, we’re still in the era of, really, watch what you’re doing. It needs thorough testing.
[00:21:09] Matt Schwartz: Exactly. And thorough code review because, you know, ultimately while the AI coding, I think has gotten really, really good, it’s not a hundred percent there, and it doesn’t have any context. It doesn’t actually know what it’s doing. It’s all patterns. So there is an argument to be made that, yeah, it may get 80% there, but if no one’s actually checked the code review, two months from now, it decides to delete all your websites out of your management dashboard, well, should have done a manual code review, right? And it’s on you.
So I do think there’s an argument, same thing with like QA tools. Building one-off QA tools, which should be persistent and actually probably one of the more important things you build. It should do the same thing every day. It should almost be dumb. It should not be trying to rebuild itself all the time, or be even one-off, like you said. It’s not, I think, a good idea to build a one-off migrator typically for that reason, even though I see people doing it in agencies. Unless you think it’s just a low risk project, I do think, you know, you have to think about that.
To your point about the one-off task though, I think again, if it’s a low risk item, one-off makes actually the most sense because a lot of times if you know this is going to be a one-off thing, you then are subconsciously being like, okay, I’m going to use this once and the cost is not that high and that makes sense, because you’re not having to maintain it. But if you know it’s going to be something you’re going to be using for the next five years and you don’t plan to pay a developer to review it, I don’t think that’s a smart idea, at least not right now.
[00:22:39] Nathan Wrigley: That’s a good calculus I think to have in the background. Okay, so that’s good. So caveat emptor basically, use your discretion. If it’s public facing, maybe think twice. But also if it’s something that you want, you absolutely bulletproof need it to be reliable and predictable a hundred percent of the times that you run it. Again, maybe there’s a human in the loop there. So that was sort of vibe coded things that you might do in your agency.
I feel that’s going to be a real area of growth, whether or not it will be profitable growth or useful growth, I’m not entirely sure. I feel like in our industry at least, people are going to be dabbling in that kind of thing all the time. You know, trying to figure out new, clever tools to achieve a thing, which maybe in the past would’ve been a subscription thing that you paid $20 a month for or something. So we’ll see. We’ll see how that goes.
Okay, moving on then. So the 12th item that you brought to bear was QA, so quality assurance, checklists and testing. Right, run us through this one then.
[00:23:33] Matt Schwartz: I know I just said when you’re building a QA tool, using AI to build an internal vibe coded tool is probably not the answer. But actually what I’m going to say right now is not contradictory to that, because what I’m really talking about for QA and testing is more so having AI help you build things like checklists, right? You already have a good context usually with your SOPs. So it can help you build your SOP checklists. It can also help run the low risk items automatically. And again, I know I talked about risk a lot, but I think that’s how you have to consider it.
So one really neat thing I’ve seen a lot of agencies start using is Claude Skills, which basically just means that you teach Claude a process. Literally it walks you through in the conversation like, what do you want this process to be? And then you can run that later in context.
So a really cool example of this is if you are, let’s say onboarding a client, or you’re launching a site. During your next launch, your next onboarding, you may want to use Claude to teach it the skill of how you launch sites. And then it can automate a lot of those items. And you can still give it context like, I want the human to specifically review this item, right? Or, I want the human to check that no index isn’t set, right? Because that’s like a high risk item, right?
[00:24:55] Nathan Wrigley: Yeah. Yeah, that’s a big one..
[00:24:56] Matt Schwartz: Right. That’s one we all, I think, have dealt with at some point in our.
[00:25:01] Nathan Wrigley: Too many times.
[00:25:01] Matt Schwartz: Right. Too many. Exactly. That’s the key. And that goes back to really that vision document I said on the last call. Having an AI vision document where you go through these checklists and you’d be like, okay, we want a human to be involved, or we don’t. You could actually tell Claude this. And then Claude will actually know exactly what it should be running itself and what it expects a human, and it will prompt you for.
But I think that is the beauty of this is, you can make your whole automated process when it comes to tools with QA and anything really related to that checklist, whether it’s launch or anything like that. Look at tools like Claude and Skills like that, and I think that you can use it to help with repeatable processes. And that will actually help most agencies not only speed things up and save on margins, but I think a lot of times they’ll do more testing than they did before.
And this, again, falls into that sweet spot where like AI’s really good for the things that you knew you should do but you have limited time. And testing is one of those items. You want a hundred percent coverage, but in reality that’s not going to happen. So let’s have the human do the really important stuff and everything else we would’ve never gotten to anyways, let’s have the AI do it. And that’s where I think you can use these tools.
[00:26:11] Nathan Wrigley: Do you know what’s really interesting, and we sort of made light of it in the previous episode, the fact that there’s hallucinations and what have you going on all the time. But I do think there’s definitely a moment coming where I think some of the more straightforward things, like for example, the checklist, the binary things, is no index switched on? Yes. No. Okay, that’s a no.
I think I am getting comfortable with that now. You know, just that, okay, we asked the AI that question, it’s delivered as an answer. I’m almost at the point now where I’m never going to go back and check that was true. If it was something much more broad like, is my SEO strategy bulletproof? Well, no. It’s never going to know whether that’s the right thing.
But these much more binary things, many of which, if you add them all up, could take you hours when you’re finally launching a website. Yeah, I think there’s something to be said for just sort of handing that stuff over. And I don’t know, maybe you check it frequently, infrequently, less frequently as time goes on. But yeah, always check the no index one.
[00:27:08] Matt Schwartz: Yeah, I was like, I would still check the no index one, even if it’s binary. But to your point, a lot more of the very black and white items, I think it can handle a lot better than it used to, but I think it still comes down to risk. Like if it’s, yeah, no index, I’m still going to check it. But if it’s something else that just is not that key. Yeah, I think we’re all becoming a little more comfortable or a lot of us are coming more comfortable with that. And I think that’s okay because you know the risk exposure really.
[00:27:35] Nathan Wrigley: Well, and also, especially if it’s QA and checklist time, hopefully you have done the bits and pieces, you really are at that point just making sure that you’ve polished the thing that needs to be polished. So hopefully that’s a bit of low hanging fruit where you’ll catch the things that you missed, and maybe you’ve done the due diligence there already.
Okay, so that was number 12. We’re approaching the end. We’ve got four more to go. So number 13 links directly to WordPress specifically. The WordPress plugin market impact.
I’ve got to say, this has me slightly concerned, because I feel that this could be a good thing for our ecosystem, but also possibly a bad thing. But I’ll just hand it over to you to paint the picture.
[00:28:18] Matt Schwartz: Yeah, definitely. So I think you even touched on this a little earlier when you were saying there’s going to be more one-off apps being built by agencies. And I think that also applies to a lot of plugins that are essentially one-off solutions, right? They are utility plugins. They solve one thing really well.
I think that sort of thing is already seeing the impact. If you talk to a lot of plugin developers, especially some of the larger shops, they’re seeing a drop in sales. And that is a real thing that’s happening. They’re seeing a drop in sales, especially for smaller plugins. Because a lot of agencies and customers are solving that with AI. Maybe it’s a couple files of code, it’s a lot easier for them to build it.
Now I still have concerns around, are they having a human review that? Like I talked about. But humans are going to do what they’re going to do, which some people are just going to run with that. That ultimately affects sales.
So I think that is hurting a lot of the ecosystem when it comes to the smaller plugins out there. And even some of the bigger plugin developers are essentially sunsetting their smaller plugins, because they realise they’re not getting as many sales and they need to focus on what they consider their moat, or their platform, you know, big plugins that AI’s not going to be able to replicate or people shouldn’t trust to replicate.
But if you’re building a small plugin, I’m not going to call any out, but I think that there is some concern there. And I think ultimately for WordPress, I don’t think that really hurts the WordPress ecosystem from the standpoint of plugins in general, but I do think it raises the bar of what a good plugin will be.
And that kind of goes with the agency land. That’s what’s happening with agencies too. It’s just the bar is being raised. You have to have a more complex plugin that actually solves someone’s needs now, not just a small one that solved it, but now they can use AI to do it.
And some people argue that that’s going to continue all the way up with the most complex plugins out there. But I do think that there are, you know, unless AI dramatically improves. If it’s 80% there, that’s great and all, but it’s what we talked about earlier. You can’t really run with that in production at 80%. And that’s the difference between a really good SaaS or really good plugin versus something that was homegrown and just falls apart.
[00:30:38] Nathan Wrigley: I think I have a slightly different, maybe more community focussed, approach to this because one of the things that I think worries me is the, how should we say it? The slow ebbing away of the community. And obviously if you are a, I don’t know, a company launched onto the stock market and what have you, you’re all about the money, right? The bottom line is you’re going to make money, distribute that with your shareholders, whatever, yada, yada. But the point is to make as much cash as possible and do things with that cash.
We have a very different calculus here in that the community is the thing which largely builds the software, maintains the software, promotes events. There is a bit of me which worries that if these, let’s say developers who’ve got one plugin, it doesn’t do 3000 major things, it just does one or two little things, but it’s been their way of getting themselves into the software, and figuring out how it all works, and meeting the community, and being engaged and, you know, all of that.
That slow ebbing away of that is something that I think our community and open source communities like ours need to be just a little bit mindful of. Because it does feel as if AI could definitely eat a lot of lunches. And I think we see that actually. I think we can already see that in the real world with things like attendance at events and the amount of events that are being put on, yeah.
[00:31:57] Matt Schwartz: I think you’re correct. I was actually going to bring this up in the sense that I am already seeing it within a lot of the agency groups. There’s just not as much engagement when it comes to posts, I think, and that sort of thing. Because people use AI more to find solutions, which means they’re not as engaged in the community. Which, to your point, plugins would kind of work the same way, especially the smaller plugins.
And yeah, there’s definitely something I think I’m concerned and kind of sad about already. Because like that’s why a lot of us are in WordPress is for the community. And I 100% agree with you. Not to mention if those guys, the smaller guys go away, then there just ends up being these massive plugin companies, which have their place, but WordPress wasn’t built on all massive plugin companies. So If those smaller ones go away, then that’s a little bit of the WordPress spirit I think are lost for sure.
[00:32:47] Nathan Wrigley: Yeah, I think we just need to be very mindful about this slow, like I say, wicking away or haemorrhaging of the community. And because at some point, the calculation no longer works. You know, there just aren’t enough community members around to make it interesting for other new community members to join, or to stick with things. Or to update their plugin or whatever it may be.
And maybe that is just a consequence of the way the world is moving, I don’t know. But having lived in the WordPress ecosystem for over a decade, I think it would be a shame if that baby was to be thrown out with that bath water.
Okay. Alright. I think we’ve done that one. So the next one is, well, the next one kind of speaks directly to that actually, which is the idea of, I guess spreading your wings a little bit further and realising perhaps that AI empowers you to do things outside of WordPress. And you’ve entitled this Experimenting Beyond WordPress. Again, off you go.
[00:33:37] Matt Schwartz: So this is something I am seeing some agencies doing, which is, because you can use AI now to use unfamiliar stacks, there’s really two parts. One is just unfamiliar stacks, or unfamiliar platforms, you don’t know. You can really try out new platforms a lot faster now. It will tell you exactly what to do, you know, step by step, or it’ll just do it for you.
So there are agencies, I think looking at other platforms where certain projects may make sense outside of WordPress, where they’re using that in that capacity and it’s allowing them to experiment. Where in the past, just sticking in WordPress, you have all your knowledge there makes sense to do, right? You don’t want to know 10 different platforms. But I think AI’s made that easier to dive into these other platforms. So that’s the first thing.
The second thing I think is that, now that you can actually use chat to engage, you are seeing some agencies, and some freelancers, that are saying, well, I don’t need the WordPress infrastructure at all. I just want to go back to pretty much like static or HTML type websites because I know I’m just going to chat with it and then I don’t have to worry about security or updates.
And obviously I think that only would apply with certain websites. It’s not going to apply with highly functional websites. I think that’s not really going to work. But for like your brochure site, I think some agencies are experimenting with some other platforms out there like Astro and the EmDash setup going on with CloudFlare.
You know, and I think that was a direct response actually. They realised, oh, people are going to want to chat with it. We could build this WordPress, what they consider like an upgraded version, in their mind.
And I think that, you know, it’s good to experiment. I think what WordPress does really well, to your point though, is they’ve hopped on the API centric side of things, building the right framework, not trying to force a certain thing down our throats, but actually leave it really open.
And I think that’s ultimately good because that’s how open source works. That’s why I think AI will have a good position with open source is. To your point you made previously, all the data’s out there, all the documentation’s out there. It’s going to be able to be extremely flexible. And I think that’s really why WordPress is still, in my opinion, going to exist and thrive.
But you are seeing agencies that are looking outside of just Core WordPress, because they can experiment with just a lot less time now. And they can also try out some tools that may be a better fit for certain projects.
[00:36:18] Nathan Wrigley: There’s a lot of technologists in our community and we love tinkering, don’t we, and playing with new things? So it’s fairly inevitable. It goes with the territory.
Okay. Alright. So that was Experimenting Beyond WordPress. I think I’m going to skip 15 there because I think we covered quite a lot of that. So I’m just going to go straight to number 16, which probably will become 15, if you know what I mean, when I put it into the show notes.
So the next one anyway is called, whatever its number, is Risks and Cautions. So we’ve built what I feel is like a fairly solid argument for doing this kind of stuff. And now towards the end, we’re going to knock it all down. No, we’re not. But what are some of the risks that you might point people towards?
[00:36:58] Matt Schwartz: A hundred percent. This is, I think, probably one of my favourite sections because people don’t really talk about these risks as much as they should. If you go on LinkedIn, it’s just like all rainbows and butterflies. And we’re building a new feature every day, and I think that noise can make people feel like they have FOMO and they just jump into AI and they don’t think about the risks. So I think this is actually a really important section for any listeners to listen to.
I think one of the first items, probably a little obvious, but with security issues, with AI tools, a lot of companies, every company, I feel like at this point is inputting keys and all sorts of things into these AI chatbots. And ultimately, like those tools can still be hacked. And actually legally, a lot of them say when you submit into the chat, it’s actually considered public record. Anything you submit to them. That’s literally what OpenAI made a legal argument recently about. So keep that in mind when you’re doing this.
There are some ways to do this securely. You can look into, and I think that’s something I would recommend agencies doing because they, you are holding onto client data. And ultimately you don’t want that stuff getting leaked.
Another thing, kind of on another point, which I personally have less concern with, but I think some agencies bring up a valid point, which is every time you talk to these chat bots, et cetera, they’re keeping track of all these conversations. So I know some agencies are being like, hey, how much does a website cost in my state or my country? Only use the data that other agencies have told you. And I don’t know if it’s really doing it, but people are doing that and they’re, you know, it’s not pushing back on them.
Things like that, just be aware of, I think what you’re inputting in, because it isn’t necessarily being leaked as far as they’re being hacked, but that data make get spit out to places you don’t want it to by other parties through chat.
[00:38:52] Nathan Wrigley: I feel that at some point in the future, some gigantic disclosure, something will be disclosed, which is so horrific that it makes us all sort of take a collective breath when we suddenly realise all we’ve given over. We haven’t got there yet, or at least to my knowledge we haven’t. But I feel that at some point in the near-ish future, some jaw dropping disclosure will occur, which will make us all think twice about exactly what you’ve just described.
What are we giving up? What have we given? But also what have we not consciously given? Which kind of bit of our business did we unintentionally open up for the AI to have access to that we didn’t intend to? And if we had the time again, we wouldn’t have allowed it to, and so on and so forth. So, yeah. Okay.
Any other things on the risks and cautions? I feel that there’s a couple more lurking in there.
[00:39:43] Matt Schwartz: Yeah. I think that one’s to be the most obvious that most people are talking about. One I think people aren’t talking about though is handling errors when you’re building your own tools. Essentially, a lot of times you may vibe code something, right, which is great. But because you’re not really going into the depth of every situation, it’s just making kind of assumptions, the AI, of what should be there.
And because it’s so easy and you’re like, well, I’m saving time, people don’t really outline all of this. And so they don’t really put error handling in these tools. And what happens is, of course there’ll be some edge case and, you know, things just break. And again, depending on the tool, if it’s an internal tool, you can probably get away with that. But if it is a public facing, or a client facing tool, that is the beauty I think of having a human actually review it with logic is they are going to have context that the AI doesn’t have.
To your point earlier, like subconsciously might be giving certain information to the AI that we don’t necessarily mean to. But you also might be leaving things out because you think you’ve already told the AI, or you think it’s going to assume a certain way, and you can’t really make that assumption. It ends up really backfiring in the long run, I think.
And that’s why being very conscious about error handling and being like, okay, we’re going to set up logging, we’re going to set up testing. Validation is just the responsible way to be building these tools that really, I feel like no one talks about.
[00:41:09] Nathan Wrigley: No. And the curious thing about it is, because it’s such a black box, I feel that almost every other technology that we’ve interacted with has been much more, I don’t know how to describe it. There’s been a higher barrier to entry. It’s more difficult to interact with it. You’ve had to, I don’t know, press buttons or enter code or what have you. Now you are just communicating. And maybe we’ll even sort of drop into voice communication at some point where we’re literally just talking with the thing.
There’s just no, how to describe it. There’s just such a small amount of friction that is required to interact with these things. And so it kind of lulls us into this perception that it can’t make mistakes. It’s error free and what have you. And we know that that’s not the case. I didn’t really describe that very well, but I hope you got a general sense of what I was trying to describe there.
[00:41:54] Matt Schwartz: I think you’re right. I mean I can give an example like building out CheckView, which is obviously like a, it’s a QA tool for WordPress sites. But one thing is, I knew a decent amount of QA before I started building it. But I learned so much context building it, and we weren’t using AI when we built the tool, right? That I would’ve never gotten out if I had used AI from the beginning.
Because like you said, there’s just such little friction. You as a human just don’t have to have that much information. You can just dive into something, having no idea on what you’re really doing, which is a blessing and a curse. And I think just being aware of that. And building in the right logs, and errors to at least essentially provide a safety net for yourself, knowing that you’re not going to know everything is really important.
[00:42:34] Nathan Wrigley: Yeah. And then a couple of other things which we’ll just sort of gloss over fairly quickly because maybe they’re sort of slightly common sense. Obviously, you know, you’ve got here sensitive client data, which might be, without your knowledge, being scooped up by the AI agents. So monitoring that.
Over dependence on AI vendors. This feels like everybody’s really become dependent on a handful of companies. Maybe you could count them on one hand, I think basically. There’s three or four really, that everybody seems to be using. So that may be something that we want to be mindful of.
And of course, the last one of your bullet points under Risks and Cautions is just the fact that AI makes some mistakes all the time.
[00:43:15] Matt Schwartz: All the time. I think most of that’s common sense. Really, the only one that I think people aren’t talking as much about is the overdependence on AI. Not to date this podcast, but I’m going to a little bit anyways. For example, with Claude, they are removing Claude Code from their $20 plan right now. You know, if you’ve built this into your agency process, well, get ready to pay, you know, a hundred bucks for every employee, which could be thousands of dollars.
[00:43:40] Nathan Wrigley: You can only imagine how valuable that will be. And maybe it’ll be 200 bucks, or a thousand bucks or whatever it may be.
[00:43:46] Matt Schwartz: Right. A lot of these companies obviously are subsidising the cost, and so I do caution agency specifically. That’s why having that AI vision is important, but also considering making it independent enough from your processes that you still can function if this thing does change around, because I do think there is going to be a pushback on cost at some point.
So for example, like when you’re building a product, I’m seeing some companies that are building AI so integral to their product that it will not function without AI. Or going to have to raise the price by 10x. And so like even with CheckView, our tools are there, but we haven’t built it in in such a way that you can’t use the tool without it.
And I think at the agency level, it’s the same idea. For the most part, trying to avoid building it in a way that you couldn’t reduce the AI needs if you needed to. Or just preparing for that the costs could go up and like, you know, if you give it to all 10 employees now, you know, at 20 bucks a month, get ready to possibly pay a lot more later.
And I just think that’s something important for agencies specifically to keep in mind. And I know that seems contradictory to what I said at the beginning of this, AI everything, but I think it’s important.
[00:44:59] Nathan Wrigley: I’m not a financial wizard in any way, shape, or form, but that does seem to be something which, sure as night follows day, is going to be coming, is the requirement to repay a lot of the venture capital that the AI is currently burning through. And yeah, so maybe a significant price hike.
And we’ve all got used to these practically free tools, and maybe that’s something that is not going to be in our future. So that’s a really good point. Put that bulwark in place to make sure that you are protected from that should it go up by, like you said, 10x or whatever it may be?
Okay, so I did say that there were going to be multiple, I think 16 is what I said. This probably will be the last one. This is likely outcomes for agencies. So, Matt, you get to stare into the crystal ball and tell us what your final thoughts are in terms of what you think are likely outcomes.
[00:45:47] Matt Schwartz: So I think some of this is already happening.
Hiring, I think, is slowing down in some agencies because they’re realising they can automate more. They don’t need as many, essentially non-specialist employees, or contractors. And I think that is a real thing that is happening.
I don’t know if it’s going to be necessarily a long-term issue. Hopefully as, essentially the floor raises, work gets better, more agencies will be focused on providing more value, more strategy, those sort of things. Again, the execution becomes a little bit of a commodity. So having essentially more junior team members who usually do that execution isn’t just quite as necessary. So I think that’s going to continue to come up.
But again, I think it’s going to be balanced out with even the costs we just talked about with the AI tools. There could totally be a point where the tools might get expensive enough that it makes sense to have a junior do this execution.
[00:46:45] Nathan Wrigley: Get the humans back. Yeah.
[00:46:46] Matt Schwartz: Yeah. And we go back the other way. Some people are saying that could happen. I could see the argument for that. But I think that’s one thing.
Another thing with agencies is you now can really productise more of your services. And this comes into the automation process that we talked about. You can take your processes, you can really package them up, I think. And there has been a lot of talk about productising services, but I think now you can get more nuanced.
So if you, for example, only build sites for plumbers, well, with AI you can get way more specific on plumber specific service needs, and build out a process with what you’ve already done, plus, with AI to make that, I think, a lot easier for the plumber or the client, to get what they need out of it. In the past, I think most agencies were trying to build SOPs as we have time. And it, you know, it’s just a really difficult process. And I think that’s where agencies I think could help a lot.
And then the last point I’ll make around here is really around that the tools I think will change. It will be, again, less about the execution of tools, how you’re building your sites. More about the actual automation. And then really just testing and monitoring and making sure everything’s working how it’s supposed to be. The human will essentially become more of the manager of the AI. And that extends, I think, to even the tools.
I could see there being more QA and monitoring tools out there for more specific needs. Because now, you know, AI can build 90% of this, which is great. I save that cost, but I know I need to pay maybe 5% of that towards some tools that actually watch and monitor what’s happening, and make sure these automations, and these websites, are really doing what they need to be doing. So I think there is going to be possibly a shift in that way around what sort of tools that we’re investing in as far as agencies go.
[00:48:40] Nathan Wrigley: So that we could describe as a bit of a marathon. I think, really, you really took us through the gamut of everything that could possibly affect an agency in the AI space. We’re in the year 2026, let’s see how it ages. But that was a really interesting deep dive into all of the different bits and pieces.
Matt has very kindly put together some show notes. What I think I’ll probably do is crib those. Maybe I’ll put them into the WP Tavern show notes, or maybe I’ll link to a Google Doc or something like that where you can see them. But you’ll be able to see all of the different bits and pieces that we went through. There’s a lot more on that document than we actually had a chance to go through. So definitely do check that out.
What I can say is that the future is definitely going to be interesting. Whether or not any of the predictions you’ve made will turn out to be true, time will tell.
But what a fascinating chat. Thank you so much for chatting to me. And I really appreciate you sticking around and doing the second episode somewhat unexpectedly with me.
Just before we sign off, Matt, where can we find you? Where are the best places online to hang out with you?
[00:49:49] Matt Schwartz: Yeah, definitely. So definitely, you can find me on the Admin Bar Facebook group. I’m also in LinkedIn, trying to be better about that. You can also check me out. I’ve got a Slack channel. Checkview.io, of course. Inspry.com. Feel free to reach out if anything comes up.
Definitely, overall I would just recommend agencies dabble in this. Don’t be reckless, but definitely see what makes sense for your agency. Document it all out ahead of time. And I think that that’s really going to be agencies strong suit is, can we leverage this stuff in a smart way?
[00:50:21] Nathan Wrigley: Well, you’ve certainly provided us with a lot of food for thought. So once more, go and check out the show notes on wptavern.com. I will probably link to the document that Matt has created on both part one of this and part two as well. So you’ll be able to check both of those out.
Matt Schwartz, thank you so much for chatting to me today. I really appreciate it.
[00:50:41] Matt Schwartz: Thank you so much, Nathan.
On the podcast today we have Matt Schwartz.
Matt has been working in the WordPress ecosystem since 2011, running his own agency based in Atlanta and developing products like CheckView, a tool for WordPress form and checkout QA. Matt’s expertise lies in how agencies can smartly and cautiously incorporate AI into their workflows for real, tangible wins (and how to avoid potential pitfalls). He was on the show last week to record the first of this two part mini series. You might want to listen to that prior to this, but it’s not strictly necessary.
In this episode, we build upon last week’s conversation, Matt talks about practical strategies for integrating AI across agency operations. The discussion starts with what it means to give AI access to your agency’s ‘brain’, using tools like project management wikis and connecting them with AI chatbots to streamline knowledge sharing and avoid common AI hallucinations.
We then get into MCPs, which stands for Model Context Protocol, and talk about why this area is quickly becoming a game changer for agencies looking to securely connect AI agents to multiple internal systems without complex, risky API configurations.
The conversation covers how to use AI for building internal tools, highlighting where it’s low-risk and where you should be more cautious, especially with public-facing or mission-critical systems. Matt explains how agencies can leverage AI for QA and checklist automation, freeing up time for deeper human review of other important tasks.
We also discuss the impact of AI on the WordPress plugin market, including potential consequences for plugin developers and the wider community, and whether the rise of AI-generated ‘disposable’ tools could erode the collaborative spirit of the WordPress community.
We end by chatting about the importance of approaching agency AI adoption with eyes wide open to the risks. Data security, overdependence on vendors, failure to handle errors, and the reality that AI still makes mistakes. Matt shares his outlook on how agencies can position themselves to thrive as AI reshapes the industry, from hiring strategies to the next generation of productised services.
If you’re running an agency or freelance business in the WordPress space and want to get ahead with AI thoughtfully and securely, this is the episode for you.
9. Giving AI Access to the Agency’s Brain
- A practical quick win is connecting AI to the agency’s project management system, wiki, docs, SOPs, or past tickets.
- This allows AI to answer questions using the agency’s actual internal knowledge.
- It can help with:
- Sales handoffs
- Support consistency
- Project management
- Developer onboarding
- Client-specific context
- Process reminders
Good framing line:
One of the quickest hacks is giving AI access to your agency’s existing brain before asking it questions.
10. Internal MCP and Guardrails
- Agencies may eventually use an internal MCP layer as a controlled proxy.
- The MCP can connect to tools through APIs.
- It can give the team access to AI-powered workflows while maintaining guardrails.
- The goal is controlled access, not just letting AI freely touch everything.
Possible uses:
- Search agency docs.
- Pull project status.
- Check time tracking.
- Review support history.
- Query website data.
- Trigger approved automations.
Good framing line:
The more AI gets access to real tools, the more agencies need permission layers and guardrails.
11. Vibe-Coded Agency Tools
- Agencies are starting to vibe-code internal tools they never would have had time or budget to build before.
- Examples:
- Website management dashboards
- QA tools
- Reporting tools
- Client health dashboards
- Project profitability dashboards
- Launch checkers
- Tools combining project management, time tracking, and accounting data
- This gives agency owners a more nuanced view of the business.
Good framing line:
The value of vibe-coding is not always building a perfect SaaS product. Sometimes it is building a scrappy internal tool that saves the team 30 minutes every week.
12. QA, Checklists, and Testing
- AI is very useful for creating QA checklists.
- Tools like Claude with skills can be taught a repeatable launch process.
- AI can help generate launch checklists and even assist with running through parts of them.
- This becomes powerful when paired with actual testing tools.
Tie-in to CheckView:
- Agencies need better ways to verify that websites and automations are actually working.
- AI can suggest what to check, but testing confirms whether it works.
- This is where tools like CheckView fit into the shift toward more automated QA and monitoring.
Good framing line:
AI can help create the checklist, but you still need systems that verify the work actually works.
13. The WordPress Plugin Market Impact
- AI is making it easier to build small WordPress plugin utilities.
- This may hurt the market for small utility plugins.
- Agencies can now create small, custom plugins or snippets for specific client needs.
- Larger plugin companies may respond by focusing more on larger platform-style products with stronger moats.
- Small utility plugins may become less attractive as standalone businesses.
Good framing line:
The tiny utility plugin market may get squeezed because agencies can now build small custom utilities much faster than before.
14. Experimenting Beyond WordPress
- Some agencies are experimenting with static sites, Astro, and other platforms.
- AI makes it easier to test unfamiliar stacks.
- This does not mean WordPress disappears.
- It does mean agencies may be more willing to choose different tools for different project types.
- WordPress will still make sense where clients need editing, plugins, WooCommerce, memberships, content workflows, and flexible admin tools.
Good framing line:
AI may make agencies more platform-flexible, but WordPress still has a huge advantage when clients need a mature content and plugin ecosystem.
15. Risks and Cautions
- Security issues
- Credentials, permissions, API access, and client data need to be handled carefully.
- Poor error handling
- AI-built tools often work for the happy path but fail on edge cases.
- Many lack proper testing, validation, logging, and fallback behavior.
- No long-term maintenance plan
- Vibe-coded tools can create hidden technical debt.
- Once a tool touches client data, billing, credentials, or production systems, it needs real engineering thought.
- Sensitive client data in AI tools
- Agencies need to be careful about pasting client data into SaaS AI tools.
- There are privacy, contractual, and data leakage concerns.
- Over-dependence on AI vendors
- Agencies that make core offerings too AI-dependent could be exposed if tool costs rise.
- If the AI bubble cools or pricing changes, AI-heavy workflows may become more expensive.
- AI still makes mistakes
- AI can be confidently wrong.
- If a human made up facts this often, you would probably fire them.
- Agencies still need human review, especially for strategy, legal-sensitive work, code, security, and client-facing communication.
Good framing line:
AI can make bad thinking look very professional, and that is one of the biggest risks.
16. Likely Outcomes for Agencies
- Smaller teams will do more
- AI may allow agencies to stay leaner.
- Some agency teams may shrink, or at least avoid hiring as quickly.
- More productized services
- AI makes it easier to package repeatable offerings.
- Example:
- An agency serving service businesses could automate intake, site planning, reporting, review analysis, landing page recommendations, and follow-up workflows.
- More technical differentiation
- Agencies may differentiate through operations, automation, integrations, monitoring, and QA, not just design.
- Agency tools will change
- Less focus on purely development-specific tools.
- More demand for automation, QA, testing, monitoring, and operational visibility.
- This connects directly to CheckView because agencies need to know whether the websites, forms, checkouts, and automations they manage are actually working.
Good framing line:
The next wave of agency tools may be less about building websites and more about proving that everything connected to the website is working.
Useful links
Part 1 of this two part podcast series can be listened to here
Matt’s agency – Inspry
Open Channels FM: BackTalk on Being Strategically Annoying, RSS Adoption, and Going It Alone on the Web
Conversations from OpenChannels FM reveal insights on strategic persistence in networking, advancements in content management systems, podcasting technology adoption, and the challenges of standardizing web intents.
