Skip to content
All posts
WordPress7 min read

The Future of Artificial Intelligence

AI is everywhere right now, and WordPress is not exempt. Here's my honest take, as a plugin developer, on what's actually changing, what's hype, and where I'd start building.

On this page
  1. It's not a button anymore
  2. Why WordPress is a good place for this
  3. The part most people skip
  4. Be careful with other people's data
  5. If I were starting from scratch
  6. Where I think this is going
  7. So, will AI replace WordPress developers?

I'll be upfront: I was skeptical about AI for a long time. Every other week there was a new tool that promised to change everything, and most of them changed nothing. But somewhere along the way it stopped being a toy. I now use it to untangle bugs, draft boring emails and sanity-check my own ideas, and I'd be lying if I said I wanted to go back.

So I've been thinking a lot about what it means for those of us who build on WordPress. This isn't a prediction piece. Nobody knows exactly where this is going. It's just my honest read on what's real, what's noise, and what I'd do if I were starting a plugin today.

It's not a button anymore

The first AI features everyone shipped were basically a button. "Generate with AI." Click, wait, get a paragraph. Cool for a demo, but not something you really build a habit around.

What's happening now is quieter, and I think more interesting. AI is slipping into the background. It helps search understand what someone actually meant. It suggests alt text so you don't skip it. It answers a customer's question using your own documentation instead of a canned reply. Nobody calls spell check "an AI feature" anymore, it's just part of writing. I think a lot of this will end up the same way.

For a WordPress site, that could look like:

  • Helping you write and edit inside the editor, without leaving it
  • Better on-site search that gets the intent, not just the keywords
  • Support answers pulled from your own docs and FAQs
  • Alt text, captions and summaries done in seconds instead of never
  • Small maintenance help, like explaining a weird error in plain English

None of that is science fiction. Most of it is possible today. The hard part isn't the AI, it's making it feel natural and trustworthy.

Why WordPress is a good place for this

A few things work in our favor. WordPress already stores content as structured data, and the block editor made that even more true. A paragraph is a block, a heading is a block, so it's easy to imagine an assistant suggesting a change to one block while you stay in control of the rest.

We also have hooks, filters and the REST API. That means a plugin can plug into almost anything without hacking core. And since most site owners are not going to wire up an AI provider on their own, they'll rely on plugins to do it for them. That puts plugin developers in a pretty interesting spot.

There's a flip side, though. WordPress is everywhere, so a sloppy mistake in a popular plugin doesn't hurt one site, it hurts thousands. That's worth keeping in the back of your mind.

The part most people skip

Here's where I'd slow down. It's very easy to wrap an AI API in a settings page and call it a product. You can do it in an afternoon. Which also means anyone else can, and many already have.

If I were building something today, I'd care much less about "which model" and much more about the stuff around it:

Does it solve one real problem well? Not ten problems badly. One thing that a real person is tired of doing by hand.

Does it know the site? Generic output is easy to get from anywhere. Output that understands your products, your tone and your existing content is where the value is.

Can the owner stay in charge? I'm a big believer in suggestions over automation. Let the AI propose, let the human decide. The moment a plugin rewrites someone's content without asking, trust is gone, and it's very hard to win back.

What happens when it fails? It will. Requests time out, providers have bad days, and models sometimes say confident nonsense. A good plugin handles that calmly instead of leaving a half-saved mess.

Can people switch providers? Prices and terms change fast. Locking users into one provider is a risky bet.

Be careful with other people's data

This is the boring section, and it's the one that matters most.

When you add AI to a site, you're probably sending content somewhere else. Tell people clearly what leaves their site and where it goes. Don't send personal data unless you truly need to. And give them an easy way to turn it all off.

The other thing I keep reminding myself: treat whatever a model returns the same way you'd treat any input from a stranger. Sanitize it before you save it, escape it when you show it, and check permissions on every endpoint that triggers a request. A model's answer is not trusted just because it sounds polite. There's also something called prompt injection, where text inside a post, comment or web page tries to give the model new instructions. It's a real thing, so never let model output trigger something powerful without a check in between.

Here's a tiny example of the mindset. It's not a full plugin, just the shape of a safe request:

add_action( 'wp_ajax_myplugin_suggest_title', 'myplugin_suggest_title' );

function myplugin_suggest_title() {
    check_ajax_referer( 'myplugin_suggest_title', 'nonce' );

    $post_id = isset( $_POST['post_id'] ) ? absint( $_POST['post_id'] ) : 0;

    if ( ! $post_id || ! current_user_can( 'edit_post', $post_id ) ) {
        wp_send_json_error( array( 'message' => __( 'Not allowed.', 'myplugin' ) ), 403 );
    }

    // Placeholder: swap in your own provider call here.
    $response_text = myplugin_call_ai_provider( get_post_field( 'post_content', $post_id ) );

    if ( is_wp_error( $response_text ) ) {
        wp_send_json_error( array( 'message' => $response_text->get_error_message() ), 502 );
    }

    // Treat the answer like any other untrusted input.
    $suggestion = sanitize_text_field( $response_text );

    // Save it as a suggestion. The editor decides what to do with it.
    update_post_meta( $post_id, '_myplugin_suggested_title', $suggestion );

    wp_send_json_success( array( 'suggestion' => $suggestion ) );
}

Notice it never overwrites the real title. It just offers a suggestion. That one small choice keeps the person in control, and honestly it's a good rule for most AI features.

If I were starting from scratch

I wouldn't try to build a giant "AI platform." I'd pick one annoying, repetitive job. Writing alt text, summarizing long posts and suggesting categories are all good candidates because they're small, useful and easy to check.

Then I'd make it optional, label it clearly, and show the result as a suggestion. I'd add the boring safety stuff from day one: permissions, sanitizing, rate limits, a clear error message. After that I'd watch what people actually do. Do they accept the suggestions? Do they ignore them? What does it cost per use? The answers to those questions are worth more than any roadmap I could write today.

Only once that first thing works would I add more. Better context, more providers, maybe something smarter.

Where I think this is going

I'm not going to pretend I can see the future. But a few things feel likely to me.

Assistants will get better at doing small multi-step jobs, like checking a post for broken links and preparing a fix for you to approve. They'll get better at using a site's own content, so answers are specific instead of generic. Smaller models that run closer to the user will make sense when privacy or cost matters. And people will simply start expecting a site to be smart, the same way they now expect it to work on a phone.

So, will AI replace WordPress developers?

I don't think so. What I do think is that it will quietly take over a lot of the repetitive stuff, and that's a good thing. It leaves more room for the parts that need taste, judgment and a bit of care. Those are the parts people actually remember.

If you build for WordPress, my advice is simple. Try it, keep it small, and build the thing you'd be happy to use yourself. Be honest with your users about what it does. And don't be afraid to change your mind, because with something moving this fast, all of us will.

If you're experimenting with AI in your own plugins, I'd genuinely like to hear what's working and what isn't.