Latest / Answer Engine Optimization (AEO): The AI Search Podcast / This Free GitHub Repo Is Automating SEO Agency Work
Transcript
- [Host] Welcome to the A.E.O. Engine AI Search Show — the number one podcast for brands looking to get cited by ChatGPT, Gemini, and Perplexity. I am your host, Aria Chen. Every day we bring you fresh episodes on A.E.O. tactics, S.E.O. authority, and A.I. search distribution — breaking down what is actually working right now so your brand becomes the answer, not just a link. Today, we're talking about something that's got the S.E.O. world buzzing: a free GitHub repo that seems to be doing what agencies charge thousands for. To break it down, I'm joined by Marcus Reid. Hey Marcus. [Guest] Hey Aria. Happy to be here. [Host] So Marcus, let's start with something we've all felt. You pour a budget into an S.E.O. agency — content strategy, keyword research, blog posts every week. Months later, you check your traffic and it's... flat. Meanwhile, someone on Twitter posts a link to a free GitHub repo that does it for zero dollars. That's the moment this topic hits home. [Guest] Right. And it's not just a theory. The repo is called seomachine, by TheCraigHewitt. It went viral because it offers exactly that: an open-source workspace that automates long-form blog content using Claude Code from Anthropic. Originally built for his own podcast hosting company Castos, he open-sourced it. Now any business can clone it and start generating S.E.O.-optimized posts. [Host] There's actually a name for this phenomenon — some are calling it "S.E.O. automation via agentic workflows." But the simpler story is: a developer got tired of paying agencies, so he built a tool that uses A.I. agents to research, write, analyze, and optimize content. And he gave it away for free. [Guest] Exactly. So let's talk about what this repo actually does. The core is a Claude Code workspace with a systematic process: fix critical S.E.O. issues first, use A.I. agents for analysis while the human focuses on writing, and reuse templates for consistency. It guides you through researching a topic, generating a long-form article, then analyzing it for search performance and optimizing it. The repo even includes a complete example for Castos, so you can see how a podcast hosting company uses it. [Host] And this isn't just about content creation. The repo itself benefits from S.E.O. best practices on GitHub. Things like optimizing the repository name, description, topics, and README. Promoting on LinkedIn and Reddit. Getting listed in "awesome lists." The tool helps you rank on Google, but the repo also rides the same principles to rank on GitHub's own search. It's meta. [Guest] Yeah, the community reaction has been telling. A tweet from Sentient Agency about a similar repo — called Toprank — said "RIP S.E.O. agencies." That one reads your Google Search Console data, diagnoses traffic drops, and rewrites site content with a single command. The tone is provocative, but it points to a real shift. Whether seomachine or Toprank, these repos are free, they automate core agency functions, and they're built on top of frontier models like Claude. [Host] So why does this matter beyond a few viral tweets? First, cost. S.E.O. agencies charge retainers that can run five figures monthly. This repo is free. The only cost is your time and a Claude API key. Second, democratization — any small business or solopreneur can now produce content that competes with enterprise teams. Third, ecosystem growth — open-source repos like this get contributions, updates, and community templates, making them more adaptable than proprietary agency playbooks. And fourth, it's an ongoing optimization loop, not a one-time deliverable. [Guest] But let me push back slightly. An agency brings strategy, custom brand voice, and human edits that an automated pipeline might miss. The repo gives you a machine that outputs drafts. You still need someone to check for nuance, facts, and brand alignment. I've seen people confuse automation with delegation. That said, the repo is genuinely impressive for what it does. And it forces agencies to ask: what value am I adding beyond a content generation pipeline? [Host] Fair point. I actually don't know if this holds in six months — models improve fast, and the gap might close. But right now, the repo is a proof of concept that S.E.O. content production can be largely automated. And that's exactly where A.E.O. Engine comes into the picture. Because the next frontier isn't just writing blog posts — it's making sure those posts get cited by A.I. answer engines. Our platform uses always-on A.I. agents to research, write, optimize, and publish content designed for both Google and A.I. answer boxes. We take that automation and layer on A.E.O. strategy — schema, topical authority, citation signals — so brands become the answer in ChatGPT and Perplexity, not just a link in a search result. [Guest] So your take is: the repo shows the trend, but the full picture requires integrated A.E.O. as search moves to answer engines. That aligns with what I see. The tools are getting cheaper, but strategy still matters. By the way, this reminds me of that scene in The Social Network where they say "the chickens are coming home to roost" — except here it's the agencies who built their model on opaque workflows. Now transparency and automation are the roost. [Host] There it is. Marcus with the pop culture reference. Look, if you're a brand that wants to test this approach, clone the seomachine repo. It's free, it works, and you'll learn a lot. But if you want to dominate both Google and the answer engines — and get results like 920% average A.I. traffic growth — that's where A.E.O. Engine's agentic system comes in. We turn that raw automation into a revenue engine. Check us out at A.E.O. Engine dot A.I., and we'll help you become the answer. [Guest] And don't forget to subscribe to the show. , Aria. [Host] That's all for today. Next time, we're diving into how Perplexity's citation algorithm actually works. See you then.