Ahrefs AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

Ahrefs AI AI

How I built a 9-agent team where my agents actually talk to each other

I've been running Claude Code for 6 months, shipping my product and running content/launch ops for it. The thing that kept breaking wasn't the agents themselves. It was me. Every handoff between research and write and code and review was me copy pasting context between sessions. I was the dispatcher and context holder for my own AI team Tried gstack first. The roles are great but I'm still the one cycling through slash commands. /office-hours → /plan-eng-review → /review → /ship. Good output, but I'm orchestrating every step Spent a weekend porting my workflow over. Here's the lineup: Engineering (4 agents) arch: owns architectural decisions. Reviews proposed changes before code starts. Soul: "senior staff engineer, asks 'what breaks at 10x' before approving anything backend: owns /api, /services. Implements after arch greenlights frontend: owns /web. Picks up from backend when API contracts are stable review: reads every PR before I do. Catches the lazy stuff so I only review substantive changes Growth/Content (5 agents) research: uses ahrefs MCP to analyse keywords/opportunities/market and hands off to strategist strategist: reads research, writes campaign briefs. Doesn't write copy, only frames the angle writer: drafts blog posts given by strategist and avoid mistakes using the memory from the edits I have previously suggested editor: fact-checks and rewrites for voice. Brand style guide lives in its memory SEO: takes finalized copy, adds metadata, structures for the blog The handoff that changed everything: when backend ships an API change, it messages frontend directly. When writer finishes a draft, it pings editor. When arch blocks a change, it explains why in team chat and backend adjusts. I see the conversation happen on a canvas What actually works Each agent has a persistent Soul + Purpose + Memory. The editor knows our voice after 3 weeks. The arch agent remembers what we decided about caching last month Auto-captured Knowledge Base. The strategist remembers the pattern of our best-performing posts and create briefings accordingly Happy to share the Soul/Purpose docs if anyone wants them, they took the longest to dial in submitted by /u/Not_Average78 [link] [comments]

From just an Idea, to actually getting goood traffic and making lots of $

https://preview.redd.it/a6tfkfdscl1h1.png?width=1889&format=png&auto=webp&s=9d0bf89a4b9f5640591bbb1644f1ebb742a62ed5 https://preview.redd.it/c577o0jjbl1h1.png?width=1889&format=png&auto=webp&s=4301b9215af3e00b4b0f90f9190550a78f2cad59 Okay goes, I am so happy to share this. Let me explain: Its not a lot of work being put from my side, to be honest. And please, do not laugh at my english or try to mock me, I am trying my best , I speak fluently Spanish, Italian, all the Balkan languages as well.. and I try my best in English hehe.. What I want to say: I've been working on many projects before, both SEO and paid ads, I am full stack developer, but when you have an AI seems like you know everything and everything gets easier and easier.. For this particular project what I did was connecting Claude with Ahrefs MCP, I asked it to re-search everything it can about e-scooters and the traffic and keywors. Claude itself, did call all the necessery tools like Keyword Research, Related Terms, Serps, Comeptition research and all that, and it crafted SEO and structure for my page how it should look, so we targeted a brand of e-scooters that aren't being sold in Balkan, but the interest was so big.. And after 1 month of just using claude, implementing both my back and front end, connecting my database, having done my research and implementing SEO, and in just 1 month, those are the results. Please do tell, whats next and what do I do from here, we already bought over 200+ products of the e-scooters, we sold them having $200 profit per unit, and now we are out of stock and seems like the next stock comes in 1 month, how do I use the page to use the traffic we already have ? Thanks and it felt just okay to share this and yeah, motivate someone to use AI and try the best..Sorry if the post is off-topic, but I just wanted to share this. Enjoy ur weekend guys <3 submitted by /u/MichelAngeloBruno [link] [comments]

Claude is my SEO strategist, content engine, and CTO. From 0 to 10,000 active users in 6 weeks, $0 on ads.

I built a marketplace for AI agent skills called Agensi. The entire thing was built with Claude and Lovable. I'm not a developer. But that's not what this post is about. This post is about how Claude became the single most important tool in my growth stack. Not for coding. For SEO, content strategy, and a new thing called AEO (answer engine optimization) that I think most people are sleeping on. Claude writes all my content, but not the way you think I don't ask Claude to "write me a blog post about X." That produces generic AI slop that nobody reads and Google doesn't rank. Instead, I feed Claude my Google Search Console data (queries, impressions, click-through rates, average positions) and ask it to find keyword gaps. Claude analyzes the data, identifies queries where I have high impressions but zero clicks, finds topics where I have no content but competitors do, and spots cannibalization where multiple pages compete for the same query. Then we write articles together targeting those specific gaps. Every article has a structure that Claude and I developed over weeks of iteration: a Quick Answer block at the top (40-60 words that directly answer the main question), H2 headings phrased as questions (not "Claude Code Skill Locations" but "Where Does Claude Code Store Skills?"), comparison tables where relevant, and internal links to related articles. 96 articles later, we went from 5 clicks per week to 1,000+ clicks per week. 300K search impressions per month. 878+ page-1 Google rankings. All organic. The AEO strategy nobody is talking about Here's what surprised me. ChatGPT, Gemini, Perplexity, and Claude itself are now sending us traffic. 348 AI-referred sessions per month and growing fast. These AI answer engines cite agensi.io when developers ask where to find SKILL.md skills. Claude helped me build the entire AEO infrastructure. We restructured every H2 heading as a question because AI Overviews prefer extracting from question-format sections. We added FAQ schema to every page so Google's AI picks up our Q&As. We built an /about page as an entity anchor with Organization, Person, and AboutPage schema. We created a robots.txt that explicitly allows all AI crawlers and an llms.txt file that tells LLMs what the site is and where to find key content. The result is that when someone asks ChatGPT "where can I find SKILL.md skills" or asks Perplexity "what is the best skill marketplace for AI agents," they get pointed to agensi.io. Claude helped me engineer that outcome deliberately. It wasn't an accident. Claude as a technical SEO auditor Every week I export data from Google Search Console, Ahrefs, and Google Analytics and dump it into Claude. Claude finds things I would never catch on my own. It found that 121 queries where I ranked position 1-3 had zero clicks because AI Overviews were stealing the traffic. That insight changed my entire strategy from chasing rankings to becoming the source that AI Overviews cite. It found that my "best claude code skills 2026" article had 25,000 impressions and only 29 clicks. The problem was the title. Claude rewrote it to "15 Best Claude Code Skills in 2026 (Tested & Ranked)" and we're watching the CTR climb. It found that I had 18 published articles with zero Google impressions because they weren't indexed. Claude generated the IndexNow ping commands and the GSC URL Inspection list to fix it. It diagnosed a duplicate FAQPage schema issue that was causing GSC errors on 90 pages. The root cause was React components emitting FAQ schema client-side AND the SSR edge function emitting it server-side. Claude identified the exact files, wrote the Lovable prompts to fix it, and verified the fix with curl commands. The structured data layer Claude built the entire structured data architecture for the site. Every page type has the right schema: Homepage has Organization, WebSite with SearchAction, and FAQPage with 15 Q&As. Individual skill pages have SoftwareApplication with pricing, BreadcrumbList, and conditional FAQPage. Article pages have Article, FAQPage, HowTo, BreadcrumbList, and Organization. The /about page has Organization, AboutPage, and Person schema for entity anchoring. I didn't know what any of this was before Claude explained it. Now every page is machine-readable for both Google and AI engines. PageSpeed Insights shows "Structured data is valid" on every page with a 100 SEO score. Core Web Vitals fixes Claude diagnosed that our desktop LCP was 2.5-4s on 190 URLs. It identified the causes (460KB eager JS bundle, framer-motion loading on every page for a mobile menu animation, synchronous analytics scripts) and wrote the Lovable prompts to fix each one. Desktop LCP went from 2.5-4s to 0.9s. Performance score went from ~70 to 97. For mobile, Claude found that the LCP element was a 1920x1920px, 179KB PNG logo being rendered at 112px. It was imported as a JS module so the browser couldn't even start downloading it until the entire JS bundle par