Private beta — free credits to start
The autonomous SEO agent on your team.
VectoSEO finds what's costing you traffic, files the ticket, opens the PR — or ships the fix itself. You set the autonomy; it does the work; the results are measured.
Private beta · No credit card · You control what it may change
Clicks fell 18%, concentrated on two pages. /reviews lost its FAQ rich result after the June 10 deploy dropped the schema. Here's the fix:
Restore FAQ schema on /reviews
Proposedapp/reviews/page.tsx
@@ app/reviews/page.tsx @@return (<>+ <script type="application/ld+json">+ {faqSchema(faqs)}+ </script><ReviewsList reviews={reviews} /></>);
→ Pull request #131 opened by vectoseo[bot] — review & merge on GitHub
How it works
From question to merged fix
Connect
Link Google Search Console and your GitHub repo. The agent reads your real clicks, impressions and source code — framework auto-detected.
Set the autonomy
Choose how far the agent may go — SEO Consultant (plans and drafts), SEO Engineer (opens PRs you merge), or Full AI SEO Agent (ships on its own). Per project, changeable anytime.
It does the work
The agent diagnoses, prioritizes, and ships — as a ticket, a pull request, or a direct commit — then measures the impact. You stay in control.
You're in control
Dial the autonomy up as you build trust
Set how far the agent may act — per project, changeable anytime. Every level adds to the ones before it, and everything it ships is a revertable commit.
SEO Consultant
Consultant & project manager
Analysis, audits, recommendations and planning. Drafts the fix and files it as a task — but never touches your code.
SEO Engineer
Engineer on your team
Everything in L1, plus opens pull requests with the change ready to review. Your merge is the gate.
Full AI SEO Agent
Autonomous teammate
Everything in L1 and L2, plus commits whitelisted low-risk fixes with minimal supervision. Every change is revertable.
The difference
Commits you own — not an overlay you rent.
Some "autonomous" SEO tools inject changes through a JavaScript layer or CDN edge — optimizations that vanish the day you stop paying. VectoSEO works in your repository like an engineer would: real tickets, real commits, real pull requests.
- Everything lands in your Git history — yours to keep, yours to revert
- Whitelisted, SEO-only edits — never your application logic, configs or CI
- Deterministic validators gate every change before it ships
task lifecycle
Found
Issue detected from your data, evidence attached
Ticketed / PR / committed
Delivered to your autonomy level — a ticket, a PR, or a direct commit
Shipped
You merge it, or the agent does at L3
Verified
Impact measured against your data — “+180 clicks/mo”
Capabilities
An SEO consultant's brain, a developer's workflow
Traffic-drop diagnosis
Page-level and query-level deltas from your GSC data, correlated with your deploys — root cause, not guesswork.
Striking-distance keywords
Keywords sitting in positions 5–20, scored by real opportunity: expected clicks gained per fix.
Technical audits
Metadata, schema, canonicals, broken links, sitemaps — prioritized by impact, flagged auto-fixable.
Ships the work, its way
Files a ticket, opens a PR from vectoseo[bot], or commits directly — to the autonomy level you set. Metadata, schema, alt text, llms.txt and more.
AI-search ready
llms.txt generation and structured data so ChatGPT, Claude and Perplexity cite you cleanly.
Impact tracking
After a fix merges, VectoSEO watches your data and reports the result: “+240 clicks/mo from 6 meta descriptions.”
Pricing
A fraction of one consultant hour
Starter
$29/month
- 100 credits/mo
- 1 connected site
- Autonomy L1–L2 (Consultant, Engineer)
- Credit rollover
Pro
$49/month
- 250 credits/mo
- 3 connected sites
- Autonomy L3 — autopilot
- Scheduled autonomous runs
- Priority support
Launch pricing — 1 credit per message, fixes and PRs included. Credits roll over one month.
Built for people who ship
Placeholder quote — swap with a real beta user. “It found the schema my deploy broke and had a PR open before I finished my coffee.”
Placeholder quote — “I merged 9 SEO fixes in a week without opening a single SEO tool. The diffs made it trivially easy to trust.”
Placeholder quote — “Finally an SEO tool that speaks PR. Analysis was solid, but shipping the fix is the whole point.”
Questions, answered
What can the agent change without asking me?+
That's entirely up to you — the autonomy dial. At L2 SEO Engineer (the default) it opens pull requests and waits for your merge. Only at L3 Full AI SEO Agent, and only for whitelisted low-risk fix types you enable (metadata, alt text, llms.txt, sitemap), will it commit on its own. You can start at L1 SEO Consultant — where it plans and drafts but never touches your code — and raise it as you build trust.
How do I undo something the agent did?+
Everything the agent ships is a normal git commit or PR — so you revert it the way you revert anything. There's no proprietary overlay or hidden layer; your repo is the source of truth, and it stays that way if you cancel.
Which frameworks are supported?+
Next.js, Astro and Hugo first, with framework auto-detection. Other Git-based sites still get full analysis plus exact, copy-pasteable change instructions when a file can't be mapped automatically.
Do I have to connect Search Console?+
No — research mode works on any domain using SERP and keyword data. Connecting GSC grounds every recommendation in your real clicks, impressions and positions, which is where the agent is strongest.
Is my code safe?+
The GitHub App gets access only to the repos you select, using short-lived tokens. The agent edits a whitelist of SEO-relevant surfaces (metadata, schema, alt text, llms.txt, robots/sitemap), runs deterministic validators before any change, and never touches application logic, configs or CI.
Connect your Search Console.
Merge your first fix today.
Get started for freeFree credits included · No credit card required