You shipped it. Nothing finds it.
You hold every job at your company. Groundcrew guides your coding agent to audit your site, fix one verified defect and check it again after deploy. You keep the final say.
curl -fsSL https://raw.githubusercontent.com/techwright-lab/groundcrew-seo/main/install.sh | bash
Who holds each job at your company?
Your name is on 10 boxes. Your agent holds 0.
Hand over what an agent can hold. The rest stays yours.
Example data Plan of organization, northwind.example. One employee.
- Chief executive You Everything else
- SEO You After hours
- Site audit You
- Fixes You
- Re-check You
- Coding agent Open Can take three boxes
- Engineer You Ships it
- Support You Answers everyone
- Marketing You Tells people
- Outreach You Refused
- Link verdicts You Refused
- Calendar Soon
Site audit
- Your agent does
- Audits your site from your public pages, your repository and evidence you import.
- Stays with you
- You approve anything that can deindex the site.
Fixes
- Your agent does
- Fixes one verified defect in your repository and prepares a pull request.
- Stays with you
- You review the pull request. It reaches your default branch only if your workflow allows it.
Re-check
- Your agent does
- Checks the fix again after deploy. With no account, your agent looks at the live page again. Connected, from Starter, a TrustGrowth re-audit closes the finding.
- Stays with you
- You count a fix as finished only when a fresh measurement closes the finding.
Outreach
- Refused
- Groundcrew refuses automated outreach. This box stays yours.
Link verdicts
- Refused
- Groundcrew refuses disavow and toxicity verdicts. This box stays yours.
Calendar
- Coming soon
- Calendar, briefs and drafts are coming soon. Nobody can hold this box yet.
Why does nothing find it?
Getting found is a job. Someone checks the site, fixes what is broken and checks again. At your company that someone also ships, answers support and runs the place.



Who does the audit report to?
You, either way. There are two audits, and they reach you differently.
- Your agent's audit
- No account. It works from your public site, your repository and evidence you import.
- The TrustGrowth audit
- 80+ checks, free in your account, and you read it there. The audit needs Search Console connected. Your agent reads it only when connected, from Starter.

| Issue | Found on | Reports to |
|---|---|---|
| Missing canonical tag | 14 pages | You |
| Same title tag | 12 pages | You |
| No llms.txt | 1 file | You |
| Slow largest contentful paint | 9 pages | You |
| Images without set sizes | 22 pages | You |
| Missing meta descriptions | 31 pages | You |
A TrustGrowth audit of northwind.example. It runs 80+ checks across technical, performance and content, and files issues with the affected pages attached.

Who writes the fix?
Your own coding agent, on your own repository. You pick a finding, it prepares a pull request and you read a normal diff. Every fix then climbs three levels and is finished only at the third.
Your agent has the finding and has not pushed yetYour agent pushed one commit Example data
src/layouts/base.html+1 line <head> <title>Stock counts for small warehouses | Northwind</title> <meta name="description" content="Count stock in minutes."> No canonical here. 14 pages inherit this file.+ <link rel="canonical" href="https://northwind.example{{ page.url }}"> <link rel="stylesheet" href="/app.css"> </head> <body> {{ content }} </body>
src/layouts/marketing.html+1 line, -1 line <head>- <title>Home</title> Same title on the 12 pages that inherit this file.+ <title>{{ page.title }} | Northwind</title> <meta name="description" content="{{ page.description }}"> <link rel="stylesheet" href="/app.css"> </head> <body> {{ content }} </body>
public/llms.txtNew file, +6 lines GET https://northwind.example/llms.txt: 404 Not Found+# Northwind+> Stock counts for small warehouses.++## Start here+- [Quick start](https://northwind.example/docs/start)+- [Pricing](https://northwind.example/pricing)
It prepares the pull request. It reaches your default branch only if your workflow allows it. The Fixes box is held by You.
- Your agentPrepares the pull request
- Locally verified Tests pass. Every page renders one canonical. No two pages share a title. The file is served as plain text. Passed
- Deployed The change is live. Passed
- Audit-verified A fresh measurement confirmed the finding is closed. Passed
- YouRead the result
All three passed. This fix is finished.
Who does my agent report to?
You. It does the work, asks before the risky part and refuses the rest.
- DoesPrepares a pull request.
- Asks youAnything that can deindex a site needs your approval.
- Your callIt pushes to your default branch only if your workflow allows it.
- RefusesDisavow, toxicity verdicts and automated outreach.
Do I need an account?
No. No account and no API key. Groundcrew is twenty open-source Markdown skills, MIT licensed.
- Works with Claude Code, Cursor, or any LLM agent that reads your repo.
- Works from your public site, your repository and evidence you import.
What does connecting add?
By MCP or API, from Starter.
- Live findings
- Prioritisation
- History
- Scheduled work
- Post-deploy re-audits
How do I show it worked?
A proof page: a live public scorecard for a company of one. It re-renders from the latest audit.

Proof page of northwind.example
Example data
TrustGrowth Score
58Up 6 since prior score. Our score, not Google's.
- AI visibility
- 12 of 48 answers Up 5
- E-E-A-T
- 61/100 Up 7
- Performance
- LCP 2,140 ms Good is 2,500 ms or less
- Standing
- #212 of 640 Down 3
- Your proof page is yours to control. Keep it live or hide it with one toggle in Settings.
- The page shows your name, a register number and your public rank. Competitor names and private data never reach it.
- If Search Console is lost, agents pause and the page stops being publicly eligible after a grace period.
What does it cost to staff this?
Groundcrew needs no account and no plan. A plan adds TrustGrowth audits, the proof page and research. Audits and proof pages never use credits.
Free
$0
1 site, audits with no credits, proof page, no card.
Starter
$9 a month
50 credits. Connect as many sites as you like. Keywords, 5 tracked competitors, weekly AI visibility, strategy, approve, MCP and API.
Pro, recommended
$49 a month
300 credits. Connect as many sites as you like. Adds authority and link gap, competitor deep dives, 25 tracked competitors, regenerate, style guide, unlimited score history, 5 seats on a site.
Research and strategy spend credits. Plan credits reset on the 1st. Bought credits never expire. Fair use applies.
See every plan on the pricing pageWho holds the Calendar box?
Nobody yet. Calendar, briefs and drafts are coming soon. Tell us which one you would use and we will write when it opens.
No spam, no date promises.
What else do founders ask?
Will my agent push to main?
Groundcrew prepares a pull request. It does not push to your default branch unless your workflow allows it.
What about changes that can deindex my site?
Anything that can deindex a site needs your approval.
When is a fix really finished?
At audit-verified, when a fresh measurement confirms the finding is closed. Tests passing or a live change are not enough.
Do audits spend credits?
No. Audits and proof pages never use credits. Research and strategy spend them.
How much of my site gets audited?
Per site, up to 5,000 pages every 30 days on Free, 10,000 pages every 14 days on Starter, 25,000 pages every 7 days on Pro.
Can it write my content?
Not yet. Calendar, briefs and drafts are coming soon.
Will it send outreach or disavow links?
No. Groundcrew refuses disavow, toxicity verdicts and automated outreach.
Does the TrustGrowth audit need Search Console?
Yes. The audit needs Search Console connected. If an agency runs yours, it needs access to your property. Groundcrew needs no account.
Who gets the next box?
Put your agent on the chart with one line, or start free with your site address.
curl -fsSL https://raw.githubusercontent.com/techwright-lab/groundcrew-seo/main/install.sh | bash
Your name is on 10 boxes.
- Site auditYou
- FixesYou
- Re-checkYou
- Sign-offYou
Pictures, public domain, via Wikimedia Commons: "Organizational diagram of the New York and Erie Railroad, 1855" by Daniel McCallum and George Holt Henshaw. "C.W.J. Johnson with his one man band invention" by C. W. J. Johnson. "Panhandle Pete, one-man band, at the Mountain Music Festival, Asheville, North Carolina" by Alan Lomax. "One Man Band", The Strand Magazine vol. 3 no. 13, 1892.