How We Built visibility.so - From a Chaotic Tool Stack to One Operating System for SEO
I started my career as a web developer at Acodez back in 2012. Around 2018, I moved into managing Acowebs — a portfolio of WordPress and Shopify plugins used by 70,000+ stores.
At Acowebs, we work closely with Acodez's digital marketing and SEO team. Watching their daily workflow was eye-opening — and honestly, exhausting.
They were juggling:
Ahrefs for backlinks and research
Screaming Frog for audits
SERP tracking tools for rankings
Google Sheets for planning
Content writing tools
Slack for coordination
Asana or similar for task tracking
Every week, the same chaos. Data lived in 7 different places. Context was lost at every handoff. Insights were there, but execution was scattered. Unplanned workflows meant tasks fell through the cracks constantly.
So my co-founders (Rithesh, Farhan, Ilyasy) and I decided to build what was missing — a single operating system that connects everything.
We built visibility.so. Set a domain on a project, and two AI agents are automatically provisioned — one for on-page audits, one for technical SEO. They run weekly, skip duplicate issues, and create tasks automatically. Human teams approve, guide, and strategize. Agents execute the repetitive work.
It worked for us first. Then we opened it up for others.
Current state:
30+ beta users
$99-199/mo, all AI API costs and DataForSEO data included
Integrates with GSC, GA, WordPress, GitHub, DataForSEO
Full architecture breakdown here: How to Automate Technical SEO Audits with AI Agents
Happy to answer questions!
What stood out to me is that the problem doesn't sound like "too many SEO tools."
It sounds like execution gets fragmented because every tool owns a different part of the workflow. If visibility.so becomes the system that turns SEO findings into coordinated action, that's a much stronger position than simply being another AI-powered SEO platform.
Exactly. It’s less about "tool fatigue" and more about "execution fatigue." When insights live in one place and action lives in another, things get lost. We want "visibility .so" to bridge that gap entirely so teams can focus on strategy rather than handoffs.
I think that's the more interesting direction.
Reading your reply made me notice an implication of becoming the layer that coordinates execution rather than just producing insights. It seems subtle, but it changes more than positioning.
I don't think I can explain the reasoning properly in a thread without skipping over the important parts.
If you're open to it, what's the best email to reach you on?