How I Used Claude to Audit and Fix the SEO on My Entire Blog
Situation
I was in the middle of a brainstorm about whether this blog could ever make money. I still haven't monetized it and I'm not sure I'm going to. I just wanted to see what the options looked like.
Somewhere in that conversation, SEO came up. Not as a revenue thing exactly. More as a sequencing thing: if you ever want to do anything with this, get the SEO right now rather than retrofitting it across a hundred posts later.
I knew SEO was a thing. That was roughly the extent of it.
Everything about running this blog I taught myself. Wix, the domain, the layout, the email list, all of it figured out by clicking around until something worked. SEO was one of the panels I'd never opened.
The AI Move
I connected Claude to my Wix site through Wix's MCP connector, which lets it read and write the site directly instead of me copying fields into a chat window and copying answers back.
Then I asked it to go look at what was actually there.
Fifteen published posts, and the SEO across them was incomplete. I wasn't surprised. You can't have good SEO on something you've never once thought about.
What I didn't expect was what happened next. I asked what "good" would even look like, and instead of handing me a checklist it walked me through what each field is doing.
The SEO title is doing keyword work. It's the part search engines match against. The meta description is doing curiosity work. It's the part a human reads before deciding whether to click. And both of them still have to sound like me, or the person who clicks lands somewhere that doesn't match what they were promised.
Three jobs, stacked into two lines of text. I hadn't even been populating them!
It went and looked at what similar blogs were doing with theirs. Then it put everything into one table. Every post, what as there, the proposed changes, the focus keyword, and a note on what it would do.
Seeing all fifteen at once meant I was making decisions about the whole site instead of approving fifteen things in a row.
I reviewed everything, made a few adjustments, and told it to update all fifteen.
The Shift
Then I went and checked because it's AI and I still don't trust it (especially when running something the first time).
My descriptions were gone. All fifteen. The titles had landed but the descriptions were empty. After a moment of panic, I asked Claude to fix it and it did. I still don't know exactly what caused the problem.
What's more important though is that if I'd read the confirmation and closed the tab, my blog would have sat there with fifteen empty descriptions and I would have had no idea for months. Nothing about that would have looked broken from the outside.
The other change happened after the session ended. I have a skill that walks me through creating each blog post. Structure, voice, the checks I want run before anything goes out. I added SEO to it. The SEO title, the meta description, and the focus keyword now get drafted while I'm writing the post.
That's the part that will still matter a year from now. Fixing fifteen posts was a one-time cleanup. Putting it in the workflow means post sixteen onward never has the problem.
The Pattern
I learned SEO in the middle of doing it, and I think that's the only reason any of it stuck.
If I'd set out to learn SEO properly first, I'd have read a couple of articles, felt vaguely informed, and changed nothing.
Instead the explanation arrived attached to my own posts. When it told me what a meta description is for, it was telling me about a description it had just written for a post I wrote, about a thing I'd actually said. I had something in front of me to disagree with. A few of them I did disagree with, and the disagreeing is where I learned the most.
I still couldn't write you a guide to SEO. I can look at a description now and tell you whether it's doing its job, which turns out to be the only part I needed.
The Implication
Pick something you've been meaning to learn and never sat down to learn. Not a subject. A thing in your actual life that's half set up and you've been avoiding. For me it was the SEO panel on my own blog.
Then don't go read about it first. Open the thing, point AI at it, and ask what each part does and whether yours is doing it. Ask what you should be doing, what you shouldn't, and why it matters. It sticks because it's attached to something that's yours.
What I'm Testing Next
SEO is in my writing workflow now, so everything from here has it from the start. What I don't know is whether it does anything.
I want to review metrics every month or two and look at how people are actually finding the posts, and whether those numbers move at all. I also want to know what I'm still not filling in. There were fields we never touched, and I don't know yet whether they matter for a blog this size or whether they're for sites doing something different than mine.
I had fifteen posts up when I did this. This one is number twenty-six. That's a big enough gap that the answer should be visible, if there is one.
Setting This Up Yourself
If you're on Wix, there's an MCP connector that lets an AI read and write your site directly, so it can pull your live SEO fields and push updates back without you opening the editor. You'll find it in your AI tool's connector settings and authorize it against your site the same way you'd connect anything else. If you're on a different platform, check whether it has one.
If it doesn't, this still works. Paste your current SEO fields into a chat, run the same conversation, and do the updating by hand at the end. The audit and the drafting are where the value is. The pushing is just typing.
The Blog SEO Audit Prompt
I want you to audit and fix the SEO across my entire blog. Work in stages and stop for my approval between each one. Do not write anything to my site until I tell you to.
Stage 1: Read what's there. Pull every published post and show me, for each one, the URL slug, the post title, the current SEO title, the current meta description, and the current focus keyword. Flag anything that's empty, duplicated across posts, cut off, or just auto-generated from the post title. Then give me a short honest read on the overall state before we go further.
Stage 2: Teach me what each field does. Before you draft anything, explain what each field is actually for and who reads it. I want to know which field search engines match against, which one a human sees before deciding to click, where each one gets truncated, and what a focus keyword changes in practice. Use my real posts as the examples. Assume I know nothing about SEO and don't want a general tutorial. I want to understand my own fields.
Stage 3: Find the terms. For each post, tell me what someone would realistically type into a search box to end up there. Look at what comparable blogs in my space are using. Be honest about which of my posts have no real search demand at all, because I'd rather know that than have you invent a keyword to fill every row.
Stage 4: Draft it all into one table. One row per post. Columns: post title, current SEO title, proposed SEO title, current meta description, proposed meta description, focus keyword, and a one-line note on what you changed and why. Every proposed title has to carry the keyword and still sound like something I'd write. Every description has to give a person a reason to click that isn't just a summary of the first paragraph. Show me the whole table before touching anything.
Stage 5: Push, then verify. Once I approve the table, update the posts. Write the SEO title, meta description, and focus keyword for a given post in one operation rather than as separate sequential updates, because separate writes can silently blank fields you already set. When you're done, read the fields back off the live site and show me what's actually there now, not what you sent.
My blog is [platform] at [URL]. My audience is [who]. My writing sounds like [one line]. Start with Stage 1.
Comments