Most conversations about “AI in SEO” start with the same idea: use AI to write more content. I tried that version first, and it failed. Anyone who has actually run a multi-region site knows the real bottleneck is clarity, structure, and consistency. The site I ran spanned North America, Europe, and Southeast Asia. Three regions, one editorial brain (mine), and never enough hours. That's where ChatGPT earned a place in my workflow, as a tool that works on the layer above the page.
The version that didn't work
My first attempt was the obvious one. I pasted an underperforming page into ChatGPT and asked for an “SEO-optimized rewrite.” The output was grammatical, confident, and interchangeable with every competitor page on the same query. It kept the keywords and dropped the substance, the compliance phrasing EU readers need, the payment-terms detail SEA buyers actually search for. I shipped none of it.
One rule survived that experiment: the model never writes the page. It works on intent, structure, metadata, and diagnosis. Those are the four jobs below.
Start with intent
When I optimize an existing page, my first step is almost never rewriting. I ask the model one question: what is the user behind this query actually trying to accomplish? That doesn't magically solve SEO, but it forces alignment, and misalignment is a more common failure than bad prose. The pattern I keep finding: a page written as a product announcement sitting under a query where people are asking “how do I.” The page is simply answering a different question than the one being asked.
Fixing that alignment alone often lifts a page without adding a single extra paragraph. Cheapest optimization there is.
A structural editor
Long-form content usually fails on logic: transitions break, arguments repeat, the page never delivers what the headline promised. I use the model to surface these issues early, where a concept jumps too quickly, where a claim needs grounding, where the story lacks a closing loop.
I still rewrite everything myself. But I rewrite with a clearer map, which is the difference between editing and guessing.
Metadata across three regions
Metadata was my biggest time sink, and the arithmetic explains why: every page needs a title and a meta description tailored per region. 3 regions × 2 fields = 6 pieces of metadata per page, before a word of body copy. I used to write each one from scratch, from a blank cursor. The fix: I defined the structure once, then had the model draft inside it. This is the actual title pattern from my framework:
The model fills the slots; I fix the nuance by hand. The output reads like it came from one unified editorial brain instead of scattered contributors. Speed was a bonus. I built it for consistency.
Diagnosis: the content auditor
The audit habit started with a dip I misdiagnosed. An EU page slid, my first theory was links, and I spent a week looking in the wrong place. When I finally pasted the page plus its target queries into the model and asked where reader expectations weren't met, the answer was more boring: the H1 promised a comparison and the page never delivered one. Readers bounced; rankings followed.
That's the routine now. Traffic dips, the model flags the suspects, user questions left unanswered, depth missing, logic going repetitive, and I verify which suspect is real. None of this replaces judgment. It shortens the distance between noticing a problem and understanding its root cause, which is where most audit time actually goes.
Systems are the compounding asset
The biggest long-term advantage was the libraries of reusable assets I designed with the model's help: outline frameworks, metadata patterns (above), region-specific language variations, internal linking logic, and editorial rules for tone and clarity. Two examples, so this isn't abstract:
- The internal-linking logic is 3 rules the model applies as a checklist: every new post links up to 1 pillar page, sideways to 2 siblings on the same intent, and never to a page targeting the same query. It is mechanical, which is exactly why it gets skipped at volume unless something enforces it.
- The most-reused prompt in the library: “Here is the page and the query. List every question a reader with this query expects answered, then mark which ones the page answers, partially answers, or ignores.” That one prompt is most of the audit.
SEO only scales when structure scales. My part was the structure; the writers owned the words. These assets let a whole team produce content that stays aligned as volume grows, without flattening the nuance each market needs.
The model shortens the audit loop; matching reader intent is what moves the rankings.
What stays human
Positioning, market context, compliance-sensitive wording, final editorial quality, and any claim that needs business validation, that's mine. The model drafts and flags; it is never the final authority on what a page should say.
If you want to try this on your own site, skip the rewrite prompt. That's the version that failed. Pick 1 underperforming page. Ask the model what the user behind the query is trying to accomplish, compare that against what the page actually delivers, and fix the mismatch before touching anything else. Then write your metadata framework down and make the model draft inside it. Only after that, decide whether the body copy needs work. Most of the time it needs less than you think.