My AI employee runs my SEO while I sleep, Google has no idea (full system, free) 🔥

I did SEO by hand for 16 years and it ate the hours I wanted to spend building products. So two months ago I stopped writing completely and gave the job to an AI employee that lives on my Mac. In 2 months it has drafted 70 articles and 65 pages across my 4 websites, picked every keyword from real search data, generated every image, and sent me a report on Telegram every morning at 7:45. It runs on a normal Claude subscription, the one you might already pay for, with no API bill for the writing. This is the full setup with every file and every rule, so you can build the same thing this weekend. Quick context so you know I'm not selling a course. I'm a French developer, I built OceanWP, a WordPress theme that passed 500,000 installs, and today I build my products in public, like Amabrik, which scans any site for security holes and leaked keys, tells you if ChatGPT can see you, and keeps cookie banners compliant worldwide. The agent you're about to copy runs my actual sites 6 nights a week. And this is not a ChatGPT wrapper that spits out generic posts. The agent follows written rules that took me two months of failures to learn, and you're getting all of them below, right after the shopping list. What you need A computer that stays on, meaning any Mac or Linux machine, and an old laptop is fine. Mine is a regular Mac, no GPU needed, because the intelligence runs in the cloud through your subscription. A Claude subscription with Claude Code. Claude Code is Anthropic's terminal agent, and it's included in the Pro plan at $20 a month, which is enough to start with one site. I run 4 sites daily on the Max plan, which starts at $100 a month. Still no API key for the writing, the subscription covers it. Everyone assumes agents mean huge API bills, and mine costs a flat monthly price. A DataForSEO account, where real keyword data comes from (volume, difficulty, CPC). It's pay as you go and a small deposit lasts months. You'll see why it's non-negotiable in the failure section. Google Search Console, which is free, connected to your site. This is how the agent sees what you already rank for. A Gemini API key for images, costing cents per image with the model people call Banana Pro. A blog the agent can write into. A git repo works best (Astro, Next.js, anything file-based), WordPress works through its REST API. A free Telegram bot, so the agent reports every morning and asks approval instead of publishing alone. How the machine works The clock comes first, with six scheduled jobs, one per night. Monday, Wednesday and Friday are article nights (informational keywords, people asking questions). Tuesday, Thursday and Saturday are page nights (commercial keywords, people ready to buy). Sunday at 2am is the optimization run, my favorite, I'll explain it last. A seventh small job runs daily and submits every newly published page to Google and Bing instead of waiting weeks to be discovered. On a Mac you schedule all of this with launchd, on Linux with cron. Each job runs one command, claude -p followed by the run prompt, which tells Claude Code to work alone, headless, no questions allowed. The brain files are where the magic actually lives. The agent's knowledge sits in plain markdown files called skills. One engine file holds the method, meaning how to pick keywords, how to write, and how to make images. One small config file per site holds the identity, so the domain, audience, tone, topic clusters, and what the agent may publish alone (pages yes, articles never, in my case). When the agent makes a mistake, I don't retrain anything, I edit a text file. That's the whole trick, and my engine file today contains every lesson from every failed run. Keyword selection decides if you rank. My agent is forbidden from inventing keywords, so every night it builds a brief from two sources only, DataForSEO and Search Console. Then every candidate keyword has to survive five gates before a single word gets written. Gate 1, relevance: would someone searching this plausibly become a customer? A plumber site doesn't write about pipe history, it writes about emergency repair costs. Gate 2, verified volume: the keyword must have real, confirmed search volume in DataForSEO. Zero volume means zero article, no matter how good it sounds. Gate 3, intent: question keywords become articles and buying keywords become pages, confirmed by reading the live top 10 (a page full of guides means questions, a page full of agencies means buyers). Gate 4, winnability, is the one that changed everything for me, because a new site must only target low-difficulty long-tail keywords, difficulty 25 or under. My rule, written word for word in the engine file: a difficulty-9 keyword at 300 searches beats a difficulty-60 keyword at 5,000, because you'll actually rank for the first one. The agent checks the live top 10, and if it's wall-to-wall famous brands, it walks away and logs the term for later. Gate 5, anti-cannibalization: before locking a keyword, the agent scans the sitemap, the unpublished drafts and Search Console to make sure no existing page already targets it. Two of your own pages fighting for one keyword is how you rank for nothing. Once a keyword survives the gates, the agent reads the top 3 ranking pages and writes down a coverage map of everything they explain, a gap list of what they miss, and one sentence answering "why would someone read mine instead of the current top 3?". If it can't write that sentence, it drops the keyword. The piece then has to cover everything the top 3 cover and add what they miss, so nothing ever ships thinner than what already ranks. Quick wins are the fastest results you'll get. Search Console shows keywords where you sit at position 5 to 20, and those pages almost rank, so a targeted improvement pushes them into the top 3 within weeks. The agent hunts these first, because it's ranking you already earned and just haven't collected. The writing rules matter more than people think, because this is where most AI content dies. Readers and Google both smell machine text. My engine file bans the em dash, bans the "not just X, but Y" pattern, bans a whole list of AI words, caps the statistics per article, forces a direct answer in the first four sentences, forces H2 headings phrased as real questions, and forces an FAQ that matches what people actually ask. Those structural rules are not decoration, they are AEO, meaning answer engine optimization. The quick answer is the exact block ChatGPT and Perplexity love to quote, the question headings and the FAQ mirror how people ask AI assistants, and the agent adds the matching schema markup so machines know exactly what the page answers. Google ranks you and the AI engines start citing you with the same piece. Then two dedicated skills run on every draft, and this part is not optional: an anti-slop skill holding all those bans, and a humanizer skill that rewrites anything still sounding like a robot, built from Wikipedia's public Signs of AI writing list. And the biggest rule of all is that every price, date and number gets verified against a live source during the run, or it gets deleted. An article with 3 verified facts beats one with 10 plausible guesses. The images get the same discipline. Each piece gets a hero image and section images from the Gemini image model, and the prompts are the opposite of "a nice blog image". Mine are 500 words minimum, they describe the literal subject, the composition, the light, the exact brand colors of the site, and they end with a list of what's forbidden (no glowing orbs, no padlocks, no metaphor junk). Long prompts are the difference between images that look AI-generated and images that look art-directed. An autonomous agent with write access deserves respect, so four rules keep mine harmless. First, articles are always saved as drafts, a human presses publish. Second, every secret lives in one .env file the scripts load at runtime, and the agent's instructions forbid printing, copying or committing any of it, so no key ever ends up inside an article or a git commit. Third, every run has a hard timeout and writes one status line to a log file, and if a run fails I get a Telegram alert instead of silence. Fourth, the agent runs with limited permissions, not god mode, and the funny proof that these layers work: Claude Code's own safety system once blocked my agent from installing an unreviewed third-party skill, which is exactly the paranoia you want near your credentials. How I failed before it worked The rules above sound obvious now, but each one exists because I burned myself without it. My first agent invented its own keywords because they sounded right, and the articles ranked for nothing, since nobody searched those phrases. That's where the data-only rule comes from, so no verified volume means no article. Then I let it chase big keywords and the articles landed on page 6 behind sites with 15 years of authority, which is the same as not existing. That failure built the winnability gate, the single rule I'd tattoo on every new site owner. Then came the robot voice, articles that were correct and read dead, with em dashes and lists everywhere and stat dumps. I turned everything I hated about them into a banned-patterns list that now runs on every draft automatically. And my early images were AI slop, glowing abstract nonsense, until I understood that image models reward obsessive detail, which is how the 500-word prompt rule was born. The formula, in one line: verified demand, plus a difficulty you can actually win, plus a written reason you'll beat the top 3, plus rules that keep it human, repeated six nights a week. The Sunday run, my favorite part Every Sunday at 2am the agent pulls Search Console data and finds the pages that underperform, meaning falling positions, weak clicks on high impressions, and quick wins sitting at position 5 to 20. It rewrites up to 5 of them, refreshes titles and metas, and rebuilds internal links between cluster pages so authority flows where it helps. The machine doesn't just produce, it adapts to how the site ranks, and keeps adapting as rankings grow. Set-and-forget systems rot, and this one re-reads its own results every week. Set this up yourself, A to Z Step 1 (10 minutes): install Claude Code from Anthropic's site, log in with your Claude account, and check it answers in your terminal. Step 2 (10 minutes): create the accounts, so DataForSEO, Search Console if not done, a Gemini API key, and a Telegram bot (search BotFather in Telegram, it takes 2 minutes). You'll need four secrets total: DATAFORSEO_AUTH, GEMINI_API_KEY, TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID. Step 3 (30 minutes): here's the part that makes this beginner-proof, because you get my actual rule files, not a summary. I packaged the exact engine my agent runs every night, cleaned of my site names, free at github.com/DigiHold/seo-agent-pack. Download it, open Claude Code in that folder, and paste the master prompt below. Your agent installs my real rules, writes its helper scripts, and asks you for each key at the right moment. You are setting up my autonomous SEO agent using the SEO Agent Pack in this folder. Do it step by step and verify each piece. 1. Install the engine by copying skills/seo-engine into your skills folder and read its four reference files (the five keyword gates, the competitor pass, the writing rules with the anti-slop, humanizer and AEO citability passes, the image method, the run protocol). 2. Create my site config from the template by interviewing me for the domain, audience, voice, 3 to 5 topic clusters, image palette, publish policy, currency, and where my blog lives. 3. Create the .env from the template and ask me to paste my four keys into it myself, and never print, copy or commit anything from it. 4. Write and test a script that queries the DataForSEO API with DATAFORSEO_AUTH, and show me one real result. 5. Walk me through connecting the Search Console API in plain words and test it with one real query, it only takes a few extra minutes, and quick wins plus the Sunday run depend on it. 6. Write and test an image script with GEMINI_API_KEY. 7. Send me a Telegram test message and find my chat id yourself. 8. Write and test an auto-indexing script that reads my sitemap daily, submits new or updated published URLs to Google through the Search Console API and to Bing through IndexNow (generate the IndexNow key and place it at my site root), and once a week submits the sitemap and reports what is still not indexed. 9. Install the nightly run prompt and the full schedule from the templates, disabled, and show me everything first. 10. Finish with one manual test run and show me the draft. Never publish anything live. Read what it builds and paste your keys only into the .env file it creates. The only slightly annoying step is Search Console access on Google's side, and the agent walks you through it in about 15 minutes, so the whole build stays a same-day job. Step 4 (5 minutes): when the test run works, tell the agent to enable the schedule. Six content nights, the Sunday optimization run, and the daily indexing job, all automatic from tonight. Step 5: read every draft of the first week and fix your rule files where the output disappoints you. Week one drafts are usually mediocre, and that's normal. Every correction you write into the engine file is permanent, so the agent gets sharper every week while your effort drops toward one review per day. The whole setup takes about an hour, and the machine works for you every night after that. Some final advice before you go. Begin with one site, keep articles on human approval forever, trust the quick wins before hunting new keywords, and never remove the gates when the agent proposes a seductive big keyword, because the gates are the system. What's next for me is pushing this machine even deeper into AI search, because most sites are invisible to ChatGPT without knowing it. I built a free AI visibility checker at amabrik.com/ai-visibility-checker if you want to see where your site stands today.