WordPress SEO with AI: Let Claude or ChatGPT Fix Your Whole Site (Step by Step)

Watch the video tutorial

The video runs ten minutes and some parts are sped up. The written guide covers the same steps, with the prompts and results in full.

What you need

• A WordPress site where you are an administrator.
• The free GoBuildWP plugin. You can download the latest version or install it from WordPress admin.
• An SEO plugin. We use Rank Math, free version. Yoast SEO, All in One SEO, SEOPress, The SEO Framework, Slim SEO and SmartCrawl work too.
• An AI app that supports MCP connectors, such as Claude, ChatGPT, Cursor or Claude Code.
• GoBuildWP Pro, only for the steps marked Pro below.

GoBuildWP turns your site into an MCP server, so the AI gets a list of clear actions it may take, such as "update the SEO title of this page". It never gets your password. Our connect an AI client guide shows the connection for each app, and the Claude setup page, ChatGPT setup page and Cursor guide show each screen.

Setup: plugin, connector and Rank Math

In Rank Math, open Dashboard and switch on the Redirections and 404 Monitor modules. Plugin settings like these stay in wp-admin on purpose: you decide which features are on, not the AI.

Then start a chat with the GoBuildWP connector on and ask:

On demo.gobuildwp.com, which SEO plugin is installed and active? Tell me which SEO tools you have for this site now, and which of them need GoBuildWP Pro.

Claude found Rank Math 1.0.281 active, with no second SEO plugin to fight it. It listed three groups of tools: Rank Math's own tools, the GoBuildWP Rank Math tools, and GoBuildWP's bulk SEO, content fix and page check tools, each marked free or Pro. This first question is worth asking on any site, because two active SEO plugins are a common cause of duplicate tags.

Step 1: Run a full-site SEO audit

Run a full SEO content audit of demo.gobuildwp.com: broken links, orphan pages, thin content, SEO titles and descriptions, and schema. Don't change anything yet. Give me the results as a short table, worst problems first.

The audit only reads. It checks every published page and returns a ranked list, with the evidence for each problem. On our site the worst items were missing SEO descriptions, a thin Solutions page and an indexing problem we look at next. The audit reads Elementor content as well, so page builder pages aren't reported as empty, although it can still count fewer words than a visitor sees on long Elementor layouts.

Always start here. An audit costs nothing and tells you which of the steps below matter for your site.

Step 2: Find the indexing problem

The most expensive SEO mistake is a page Google isn't allowed to index. Nothing else you do matters while it's there.

Check whether Google is allowed to index the homepage of demo.gobuildwp.com. Look at the robots meta tag on the live page and the "Search engine visibility" setting. Then run a PageSpeed check on the homepage and show me the SEO score.

Claude loaded the live homepage and found noindex, nofollow in the robots meta tag. The cause was the WordPress setting Settings, Reading, Discourage search engines from indexing this site, which was switched on. robots.txt was fine: it blocked only /wp-admin/. PageSpeed gave the homepage an SEO score of 63, held down by that noindex.

On our demo site this is on purpose. On a live site it hides everything, so untick the box. Google's own page on blocking indexing with noindex explains how the tag works.

Step 3: Get keyword ideas and search intent

Read the five pages on demo.gobuildwp.com. For each page, suggest one main keyword and two or three related phrases, and the search intent behind each (informational, commercial, transactional, navigational). Make sure no two pages target the same keyword. Be honest: you don't have search volume data, so mark these as ideas to check.

Claude returned one main keyword per page, a few related phrases and the intent behind each, with no two pages chasing the same term. It also said plainly that it had no search volume data. That honesty matters. Treat AI keyword lists as ideas, then check them in a keyword tool or in your Search Console queries before you build pages around them.

Step 4: Write and save SEO titles and meta descriptions

Using those keywords, write an SEO title (50-60 characters) and a meta description (140-160 characters) for each of the five pages. Make every one different, write for people, not for robots, and don't stuff keywords. Show me the list first. Don't save anything until I say yes.

Claude drafted a title and description for all five pages, built from what each page actually says, with the character count beside each one. Titles came in at 52 to 59 characters and descriptions at 141 to 146. Nothing was saved yet.

Read the drafts the way a searcher would. We changed one thing:

Yes. One change first: start the Pricing description with the free plan, so people see it costs nothing to try. Then save all five to Rank Math, and read them back from Rank Math so I can see they saved.

Claude rewrote the Pricing description to lead with the free Starter plan and "no card needed", saved all five into Rank Math's own fields, and read them back. The read back is the part copy and paste never gives you.

In wp-admin, the Rank Math snippet editor on each page now holds the approved title and description.

Titles, descriptions and robots settings work in the free plugin, for all seven SEO plugins listed above.

Step 5: Focus keywords, canonicals, social previews and bulk edits (Pro)

With GoBuildWP Pro, the AI can set the rest of the SEO fields:

Now set the Rank Math focus keyword on each page to the main keyword we picked. Also check each page's canonical URL points to itself, and add an Open Graph title and description for social sharing. Do a dry run first and show me what would change.

The dry run listed every field it would write, page by page. We applied it with the canonical fields left blank, because Rank Math already points each page at itself when the field is empty. We skipped the social image too: our pages use SVG images, which social networks don't show, so a proper PNG is a job for later.

Bulk meta updates work the same way on bigger sites. Up to 100 posts per run, a dry run first, and a check for duplicate titles before anything is written.

Step 6: Change a URL with a 301 redirect

Changing a URL is where many sites lose traffic. The old address keeps its links and rankings unless it redirects to the new one.

Change the slug of the Solutions page from /solutions/ to /workflow-solutions/, make sure a 301 redirect is created from the old URL, then open the old URL and confirm it redirects.

With Pro, Claude checked that automatic redirects on slug change were on and which redirect store was used, then changed the slug. Rank Math created redirect #1, a 301 from /solutions/ to /workflow-solutions/, and the old URL landed on the new page.

A redirect alone still leaves your own pages pointing at the old address. So:

Yes, point the internal links and the menu at the new URL. Show me a preview of what will change first, then apply it and confirm no page still links to /solutions/.

Claude previewed the changes, then updated 36 links across five pages and the header and footer templates, and confirmed nothing still linked to /solutions/. Google's guide to 301 redirects explains why this pair of steps keeps rankings intact.

Step 7: Check headings and fix thin content

Show me the heading outline (H1, H2, H3) of the Features page as visitors see it. Is there exactly one H1? Are the levels in order?

Claude reads the page as it renders, not the raw editor data, so you see the outline a visitor and a search engine see. Features had one H1 and the levels in order. The Solutions page was the problem: a sentence or two per team section.

Thin pages are where AI content goes wrong most often, so the prompt sets clear rules:

The Solutions page is the thin one: each team section is only a sentence or two. Make a draft working copy of it and expand each team section into a genuinely helpful paragraph: what the team struggles with, how FlowPilot helps, and a short example, under clear headings. Only use facts already on the site. Where you need a fact you don't have, leave a [CHECK] note for me instead of making it up. Don't touch the live page. Show me the preview link.

With Pro, Claude made a working copy, a private draft of the live page, and wrote five team sections from facts already on the site. Where it needed something it didn't know, such as a customer number, it left a [CHECK] note instead of inventing one.

We didn't have those answers, so we asked Claude to remove every [CHECK] note and any sentence that depended on one, label the examples as illustrative, and publish. It published the working copy over the live page and checked the new heading outline and word count. If you don't like the result, it is one undo.

This is the pattern to copy: let AI expand from your facts, make it flag what it doesn't know, and never let it fill gaps with made up numbers.

Step 8: Fix image alt text, titles and captions

Audit image alt text on demo.gobuildwp.com. How many images are missing alt text, and which look decorative?

Then:

Look at each image and write short, specific alt text that describes what it shows and why it's on the page. Use an empty alt for decorative images. Skip images that aren't used on the site. Show me the list, then save them in one go.

Claude viewed each image, wrote alt text, left decorative images empty on purpose and saved 24 alt texts in one batch. That runs in the free plugin, up to 100 images per run. Alt text helps people using screen readers first and image search second; Google's image SEO guide covers both.

Alt text isn't the only field. For the homepage hero image, Claude also set a title, a one line caption and a short description in the Media Library.

Step 9: Internal links, broken links and 404s

Check internal links across the site: broken links, orphan pages with no links pointing to them, and the 404 log. Then make a fix plan. Don't apply anything.

Claude checked 186 links on five pages. All returned 200 and no page was an orphan. The 404 log had one entry, an old blog URL. The fix plan was more interesting than the broken link count: Privacy and Terms links pointed at the contact form (10 links), and the Pricing signup buttons (7) and Sign In links (10) did too. Nothing was broken, but those links promised one thing and delivered another.

We left those alone, since it's a demo, and asked for three natural internal links with descriptive anchor text, not "click here". Claude suggested three and added the one from Home to Pricing.

Step 10: Duplicates and keyword cannibalization

Check for duplicate SEO titles and descriptions across the site. Then explain how I'd find keyword cannibalization, and whether you can detect it for me.

No duplicates. The closest pair was Features and Pricing, whose titles both opened with the same three words, which is fine but worth watching.

On cannibalization, Claude was honest. Two pages compete for one search only if Google actually shows both for it, and that shows up in real data. The method is to open Search Console's performance report, filter by query, and look for queries where two of your URLs take turns ranking. The AI can compare your titles and topics, but it can't see that data on its own.

Step 11: Schema, sitemap and robots.txt

What schema is on each page now? Should the homepage keep its FAQ schema? Is there an XML sitemap, and is robots.txt blocking anything important? Tell me which of these you can change and which I should do in Rank Math.

All five pages printed Organization, WebSite, WebPage, Person and Article schema, with FAQPage on three of them. Claude flagged two cleanups: Article is a poor fit for a pricing page, and the Person type exposed the author's name. On FAQ schema it was clear: Google now shows FAQ rich results only for well known government and health sites (Google's 2023 announcement), so keeping it is a choice, not a ranking trick.

The XML sitemap index listed the page sitemap with the new Solutions URL, and robots.txt blocked only /wp-admin/ and pointed to the sitemap. Schema types and sitemap settings are Rank Math settings, so Claude told us where to change them rather than changing them itself.

In the page source you can see the end result: Rank Math's title, robots tags, and the Open Graph and X tags.

Step 12: PageSpeed and accessibility

Run PageSpeed on the homepage and the Features page, mobile. Then run an accessibility audit on the Features page. Give me the top three fixes for each, in plain English.

Main content showed after 1.7 seconds. The top fix was render-blocking files (28 on Home, 25 on Features), worth about 1.4 seconds. The SEO score stays at 63 until the noindex from Step 2 goes. For deeper speed work, see our WordPress AI speed optimization page.

What Google says about AI and AI search

A short note before we check our work, because it shapes how you should use all of the above.

• No special AI markup. Google's guide to AI features in Search says normal SEO best practice is what counts for AI Overviews and AI Mode. You don't need llms.txt or special AI schema to appear there.
• AI content is fine when it helps. Google's guidance on AI-generated content judges content by quality, not by how it was made.
• Mass pages are spam. Generating pages for every search variation is "scaled content abuse" under the spam policies.
• Show experience. Google's helpful content guide rewards first hand experience. That's why our thin page prompt banned invented facts.

Fact check every title, description and alt text before you approve it. The AI is fast; you are the editor.

Prove it saved, and keep undo close

List every change you made to demo.gobuildwp.com in this session. Then check the live Pricing and Features pages: confirm the SEO title, meta description and image alt text in the actual page HTML, not just the database. Tell me if any page prints two meta descriptions.

This is the step that copy and paste never gets you. Claude loaded the pages as a visitor and found a real problem: every page printed two meta descriptions. The second came from the Hello Elementor theme, which adds its own description tag built from the page excerpt.

That's a theme setting, so Claude told us exactly where to click. In the Hello theme settings we switched on Disable description meta tag, saved, and asked Claude to check again. Every page then printed exactly one meta description, the one we approved.

If you use Hello Elementor with any SEO plugin, check this on your own site. It's an easy duplicate to miss.

Then undo:

Undo the Pricing meta description change only, then read it back.

Claude rolled back that one change and read the old description back. A second prompt put the approved version back again. In wp-admin, GoBuildWP, Changes lists every AI session with the number of changes. Ours had 65 changes, 62 of which could be undone, and you can undo a whole session or a single change. Our undo and rollback guide explains how it works.

What the free plugin does for SEO

Everything below works with the free GoBuildWP plugin:

• SEO titles, meta descriptions and robots settings in Rank Math, Yoast SEO, All in One SEO, SEOPress, The SEO Framework, Slim SEO and SmartCrawl.
• Content audits for thin content, missing titles and descriptions, broken links and schema, with Elementor content counted.
• Image alt text audits and bulk updates, up to 100 images per run, plus media title, caption and description.
• Live page checks that read the page as a visitor sees it, which is how we caught the duplicate description.
• PageSpeed checks and accessibility audits.
• The 404 log and search and replace across content.
• Post and page edits, so the AI can add an internal link or fix a heading.
• Changes, the log of every AI session with undo and redo.

What GoBuildWP Pro adds for SEO

• Focus keywords, canonical URLs, Open Graph and X fields and schema settings for Rank Math and Yoast.
• Bulk SEO meta reads and updates with a dry run, up to 100 posts per run, and duplicate title checks.
• Redirects, including automatic 301s when a slug changes.
• Content fix plans that list problems with before and after views, then apply the ones you approve.
• Working copies, so the AI edits a private draft of a live page and you preview it before it publishes.
• Read access to SEO plugin settings, so the AI can tell you exactly which setting to change.

The Free vs Pro comparison breaks every ability down by area, and the SEO reference and Rank Math reference list the SEO actions one by one.

What to keep manual

Some SEO jobs need data or decisions the AI doesn't have:

• Keyword volume and difficulty. Use a keyword tool.
• Cannibalization. Use Search Console queries, as in Step 10.
• Sitemap, schema type and robots.txt settings. Change them in your SEO plugin.
• Plugin installs and module switches. Do these in wp-admin.
• Social images. Make proper PNG or JPG images yourself.
• Requesting indexing after big changes, in Search Console.

Limits worth knowing

• Audits miss things. Word counts on long page builder layouts can come in low, and the sitemap can still list pages set to noindex. Read the evidence, not just the score.
• AI can misread a request. That's why every step above shows a draft, a dry run or a preview first.
• Some changes can't be undone. The change log marks them. Ours had two.
• No ranking promises. Clean titles, redirects and alt text remove problems. Rankings still depend on content people want and links from other sites.

Wrapping up

WordPress SEO with AI works best when the AI works inside WordPress: it reads the real pages, saves to your SEO plugin's real fields, and checks the live result. Start with the audit, which only reads. Fix indexing first. Write unique titles and descriptions and read them back. Change URLs only with a redirect and updated links. Expand thin pages from your own facts. Fix alt text and links, then verify the live HTML and keep undo close.

Want the bigger picture? Our WordPress AI SEO automation page covers the whole feature set, and fixing WordPress SEO with Claude shows a shorter use case. If you're building pages too, see how to build an Elementor website with Claude or ChatGPT, and before approving many title changes at once, read how to review bulk WordPress SEO title changes.