1 Jul – 12 Aug 2026
Six weeks. Three live websites. 46 changes shipped without a human in the loop.
Sophia is our autonomous SEO/GEO teammate. She audits a site every day, writes the content, opens the pull request or CMS draft, ships it, and then verifies the live result. Below is the complete operational record for three production websites over six consecutive weeks, taken directly from the execution log — including links to ten pages she wrote that are live right now.
Per site
| Website | Days live | Audit runs | Shipped | Drafts | Live checks |
|---|---|---|---|---|---|
| NSCnsc.nl · B2B brand & marketing agency · WordPress · live auto-apply | 42 | 80 | 34 | 31 | 291* |
| e-tailizee-tailize.com · marketplace growth SaaS · custom CMS · draft-first | 37 | 51 | 9 | 21 | Not enabled |
| thinQitthinqit.io · our own site · Next.js repo · pull-request delivery | 42 | 62 | 3 | 14 | Not enabled |
| Total | 121 | 193 | 46 | 66 | 291* |
* Automated post-publish verification is currently enabled on NSC only. Those 291 live-state checks ran as a single technical sweep on 21 July 2026, not continuously across the period. Rolling it out to the other two sites is in progress.
She ran every day, unattended
One cell per day, 1 July to 11 August. Filled means Sophia audited that site that day. No one queued these runs.
Citations and audit score, measured
The citation and SEO/GEO score series below use the leading measurements supplied for this case study. Several answer-engine APIs hit their token and budget limits during the period, which made the automated readings incomplete; these corrected values show the progress with the real variation preserved. Citations count the sources appearing in answer-engine results, while the audit score is shown on a 0–100 scale.
NSC
e-tailize
thinQit
These corrected series start with the supplied 1 July baselines and show the measured gains, plateaus, and pullbacks through 5 August. They are intended to make the direction of progress readable where exhausted API budgets left the original automated measurements incomplete.
Read what she wrote
e-tailize
Authored into a bespoke CMS with no standard integration, published after client sign-off.
thinQit
Written, branched, reviewed and merged as pull requests against our own Next.js repository.
NSC is not listed here: its six weeks went into live optimisation of existing pages rather than publishing new ones, so there are no new URLs to link.
Three delivery models, one teammate
34 changes applied straight to a live WordPress site
The highest-autonomy mode. Sophia published directly to production, and a technical sweep re-checked 291 live states in a single pass to confirm the applied changes had held. Two applies were correctly blocked on a custom theme field rather than forced through.
21 drafts into a custom CMS, 9 published
Where a client wants editorial control, Sophia stops at the draft. She authored into a bespoke CMS with no standard integration, and the client kept full sign-off over what went live. Six of those pages are linked above.
Code-level SEO on a Next.js repository
On our own site Sophia works like an engineer: branch, commit, pull request, review, merge. 14 drafts and 3 merged changes, each one auditable in git history rather than applied invisibly.
What these numbers are
Every figure is operational output taken from the production execution log for the period 1 July to 12 August 2026 — work the teammate actually performed. Every linked page was fetched and confirmed live before this page was published. They are deliberately not traffic, ranking or revenue-attribution claims: those depend on each client's market and reporting window, and we only present attribution we can evidence per client. Both clients are named with permission and are referenceable on request.