Search stopped being ten blue links. A growing share of discovery now happens inside ChatGPT, Perplexity, Claude, Gemini, and Google's AI Overviews — engines that don't rank your page, they cite it or they don't. I had 500+ posts live across my brands that were built for the old game. So I rebuilt them for the new one, using Claude Code agents, without hiring anyone.
This is how a full-blog GEO/SEO overhaul actually works — the workflow, not the theory.
Why "GEO" is a different job than SEO
Generative Engine Optimization is optimizing to be cited by AI engines, not just ranked by Google. The two overlap heavily — clean structure, real expertise, crawlable pages help both — but GEO adds its own requirements: passage-level answerability (can an engine lift a self-contained, correct answer from your page?), machine-readable structure, and the blunt prerequisite that AI crawlers can reach your site at all.
One thing I learned the hard way: AI-search parameters change monthly. My working framework for this has a mandatory step — do fresh research on the current per-engine rules before every batch, then apply. A GEO playbook frozen in time quietly rots.
The problem with 500+ posts
You cannot hand-edit 500+ posts. You also cannot run a dumb find-and-replace, because each post needs judgment: does this claim need a source, does this heading answer the question it implies, which sibling posts should this link to. That combination — high volume plus per-item judgment — is exactly the shape of problem AI agent fleets are built for.
The architecture is the same one I described in how one person runs five brands with agent fleets: a written framework the agents must follow, batch execution, and a verification pass separate from the generation pass.
The per-post framework
I encoded the entire per-post standard as a Claude Code skill — a written procedure every agent loads before touching a post. That single move is what makes 500 posts come out consistent instead of 500 flavors of drift. The framework covers:
Structure. A direct answer to the core question near the top, in a liftable self-contained passage. Question-shaped H2/H3 headings. Lists and tables where the content is genuinely list- or table-shaped — AI engines quote structured passages far more readily than walls of prose. An FAQ block for the queries people actually ask.
Schema. JSON-LD structured data on every post — Article markup with a real author entity, FAQPage where there's an FAQ, breadcrumbs. Schema is how you tell machines what a page is instead of hoping they infer it.
E-E-A-T. Experience, Expertise, Authoritativeness, Trust — demonstrated, not claimed. Real author attribution with a real bio. First-hand operational detail that a content mill couldn't fake. Claims backed by sources. Dates that are honest. For my brands this part is natural, because the posts describe systems I actually run; the overhaul's job was making that experience visible to engines.
Internal links. Every post links to its siblings in the topic cluster, with descriptive anchor text, so both crawlers and AI engines see a connected body of expertise instead of orphan pages. (You're inside one of those clusters right now — this post, the pillar post, and the GEO citation checklist all point at each other on purpose.)
The infrastructure half
On-page work is wasted if machines can't reach or hear about your pages.
AI-crawler access. Many sites block GPTBot, ClaudeBot, PerplexityBot and friends at the firewall or robots.txt level — sometimes by default, without anyone deciding to. Step zero of a GEO overhaul is auditing that and unblocking the AI crawlers you want citations from. You cannot be cited by an engine that has never read you.
IndexNow. Instead of waiting for crawlers to rediscover changed pages, IndexNow lets you push every new and updated URL to participating search engines the moment it changes. When you're touching 500+ posts, active notification versus passive waiting is the difference between weeks and days.
Fast, static delivery. My blogs run on Astro deployed to Cloudflare Pages — static HTML, globally cached. Crawl budget goes further and every fetch is cheap, which matters when you've just invalidated your entire archive.
The workflow, step by step
Here's the actual sequence for overhauling an existing blog of any size:
- Inventory. Crawl your own site. Build a list of every post with its URL, title, word count, existing schema, and internal links. This becomes the work queue and the progress tracker.
- Fresh rules research. Research the current citation behavior and requirements of each target engine. This step is mandatory per batch, because the rules move.
- Write the per-post framework as an executable procedure. Structure, schema, E-E-A-T, linking rules — one document the agent loads for every post. No improvisation.
- Unblock the crawlers. Audit robots.txt, firewall rules, and bot-protection settings. Fix before rewriting anything.
- Batch through the queue. Agents process posts in batches: restructure headings, add the liftable answer passage, inject schema, add sourced claims, wire internal links. Each post is a small, reviewable diff.
- Verify separately. A second pass validates schema, checks links resolve, confirms the framework was actually followed. Generation and verification are never the same step.
- Push via IndexNow and sitemap. Notify engines about every changed URL; regenerate the sitemap.
- Track and iterate. Watch indexation and AI-engine citations, and feed what you learn back into the framework for the next batch.
What it took
The honest resource summary: one operator, Claude Code agent fleets, and a written framework — applied across brands until 500+ AI-generated, GEO-optimized articles were live. The related authority engine now publishes on a 2-hour scheduled loop with zero manual steps, so the archive keeps growing under the same standard without me in the loop per-post. How that scheduling layer works — and how to make sure it's actually running — is its own post: Scheduled AI Agents That Work While You Sleep.
The meta-lesson is bigger than blogging. Any large archive of anything — docs, product pages, help centers — built for yesterday's discovery layer can be systematically rebuilt for today's, if you turn the standard into an executable procedure and put an agent fleet behind it.
FAQ
Is 500+ AI-generated posts just spam at scale?
Volume without a standard is spam. Volume under an enforced framework — real structure, real schema, demonstrated first-hand experience, verified claims, human-reviewed output — is a content operation. The framework is the difference, and it's written down and executed identically on every post.
Do I need to do all of this, or is there a minimum viable version?
Minimum viable GEO: unblock AI crawlers, add a direct liftable answer near the top of your key pages, add Article/FAQ schema, and set up IndexNow. That's a weekend of work and covers the largest gaps most sites have.
How do you know if it's working?
Three signals, in order of speed: indexation and crawl activity from AI bots in your logs; classic search impressions on the rebuilt pages; and actual citations — your domain appearing as a source in ChatGPT, Perplexity, and AI Overviews answers for your target queries. Check the citations manually with real queries; that's the scoreboard that matters.
— Italo Campilii. If you're building something that needs this kind of operator, get in touch.