Home/Blog/Connecting WordPress to AI: From Listing Products to Fixing SEO, One Person Runs the Whole Store

AI 运营

Connecting WordPress to AI: From Listing Products to Fixing SEO, One Person Runs the Whole Store

Once WordPress and WooCommerce are wired to AI, products, content, SEO and operations can all be handled by saying what you want. Here's what becomes possible, and how to connect it.

2026-07-16 4 min read AI 运营
Connecting WordPress to AI: From Listing Products to Fixing SEO, One Person Runs the Whole Store

My last piece, "Connecting Your Store to AI," was read by 100,000 people, and the most common question in the comments was: what if I'm on WordPress? This post answers that properly. Once WordPress (plus WooCommerce, if you sell) is wired to AI, the four things that eat your time every day — products, content, SEO and operations — can mostly be handled by saying what you want. First what's possible, then the full setup at the end.

The conclusion up front: connecting it isn't hard. What's hard is realising how much AI can take off your plate once it's connected.

1. Products: listing and optimising, both by conversation

Listing — hand the AI a product URL and let it analyse the page and turn it into a product in your store; or send over the copy and images you've prepared and let it list them against your template. No more filling in fields one at a time.

Optimising — tell it to "optimise product X" and it will research comparable best-sellers, look at how others write their selling points, then come back and rewrite your title, description and bullets. It's like having an operator who does competitive research for you.

2. Content: from topic to publish, in one pass

The blog is the easiest win. Give it a topic, or let it research one itself; when the draft is done it can push the article straight into your WordPress admin — no copy-paste. Editing existing pages and posts works the same way: explain what you want and it generates the new copy and swaps it into place. It does the work; you review once.

My own rule: drafts automatic, publishing manual. Let the AI carry it all the way to a draft, and keep that final "publish" click for yourself.

3. Pages and SEO: what used to need a developer now needs a sentence

Adding a page or adjusting a layout used to mean finding someone technical. Now you describe the page you want and it builds it.

More useful still is SEO: have it run a full-site audit and fix what it finds along the way. The classic case is images missing alt text — hundreds of images, none of which you have to touch by hand (the WordPress REST API's media endpoint carries an alt_text field, which is exactly what you want for a batch write).

I built a dedicated site SEO audit Skill for this and open-sourced it. It checks three layers — page, site technical, structured data — and works out of the box: SEO Audit Skill →

A word on why structured data (JSON-LD) matters so much right now: it is the most direct way to get ChatGPT, Gemini and similar systems to understand and cite your pages accurately. One study found that adding structured data lifted model accuracy from 16% to 54%. In the AI era, whether you get cited depends heavily on how complete that layer is.

4. Marketing and operations: the daily chores, all of them

If you run WooCommerce, day-to-day operations can go to it as well:

(On a content-only site without WooCommerce, skip this section — the other three still apply.)

5. How to connect: three steps, ten minutes

Connecting is really just handing the AI a set of keys:

  1. Generate an application password: WordPress admin → Users → your profile, scroll to "Application Passwords" at the bottom, give it a name and generate. You get a 24-character key (like xxxx xxxx xxxx xxxx xxxx xxxx) that is shown only once — save it.
  2. Put it in your project's .env: the key, your login email, and your site domain.
  3. WooCommerce users, one more step: admin → WooCommerce → Settings → Advanced → REST API, create a key, and put the Consumer Key and Secret in .env too.

Then have the AI run a connectivity check. If it passes, you're connected. Your .env ends up looking roughly like this:

WORDPRESS_SITE_URL=https://yourstore.com
WORDPRESS_USERNAME=your@email.com
WORDPRESS_APP_PASSWORD=xxxx xxxx xxxx xxxx xxxx xxxx
# add these two if you run WooCommerce
WC_CONSUMER_KEY=ck_xxxxxxxxxxxxxxxx
WC_CONSUMER_SECRET=cs_xxxxxxxxxxxxxxxx

Three traps to know before you start

On MCP: WordPress is also pushing a more native path (the Abilities API in 6.9 plus an MCP Adapter), but the ecosystem has only just landed and it has version requirements. The most stable, host-agnostic option today is still the application password plus REST API setup above — start there and get the work moving.

These are just the patterns I use most; you'll find more once you're connected. I'll keep sharing on stores and AI — follow along if it's useful.