◆ Zyan SEO

SEO That Ships. As Pull Requests.

Every SEO tool ends with a to-do list. Zyan’s Autopilot ends with a diff — audits become fixes, fixes become pull requests your team reviews, and every applied change lands in a rollback ledger.

Register your agencyMeet the agent runtime
◆ Reviewable PRs, never silent edits◆ Rollback ledger on every change◆ Schema & canonicals always PR-first
◆ Strategy Center

Deep Research In. A Locked Strategy Out.

Autopilot doesn’t guess what matters. Each project gets a versioned strategy document built from your Search Console data, SERP snapshots, and competitor research — then red-teamed by a second model before it can lock.

  • Versioned like a release — draft, red-team, lock; the hash pins what runs
  • Every claim cites its source: GSC queries, SERP snapshots, competitor crawls
  • A second model argues against the plan and annotates the weak spots
  • Autopilot and Autoblog execute only from a locked version
The runtime that writes it →
◆ SEO Autopilot

From Finding to Fix, With a Gate in the Middle.

The lifecycle is a pipeline, not a dashboard: detect, draft, gate, ship, and log — with the risk tier deciding whether a fix may apply itself or must earn a review.

Detect

A scheduled crawl joins your Search Console queries, SERP snapshots, and DataForSEO research, then files findings with a severity and an owner page. Not a score — a queue.

P1LocalBusiness schema missing — 12 service pages
P1Canonical loop — /blog pagination
P2Meta description empty — /pricing
crawl · gsc · serp — joined 07/21

Draft

For each finding, the agent writes the actual change — the meta tag, the canonical, the JSON-LD block — against the site’s real code. A ticket describes work; a diff is work.

@@ /pricing — meta description
- <meta name="description" content="" />
+ <meta name="description" content="Detailing packages & pricing — Avid Auto, Austin." />

Gate

Every draft carries a risk tier. Below the floor you arm — metas, alt text, internal links — Autopilot may apply directly, straight into the ledger. Schema, canonicals, and redirects never take that path: they are always PR-first, whatever the floor is set to.

drafted fix
below your floormetas · alt text · internal linksauto-apply → ledger
always PR-firstschema · canonicals · redirectspull request → review

PR & merge

Structural fixes open a branch and a pull request through the platform’s GitHub connection. Checks run, your team reviews, and the merge is the approval — the same discipline as any other code.

mergedseo: LocalBusiness schema + canonical fix#214 · checks 3/3 ✓
openseo: canonical loop on /blog pagination#217 · review — Riley

Rollback ledger

Every applied change — auto-applied or merged — is recorded with what changed, when, and a revert path. Undo is a first-class operation, not an apology.

#183alt text · 6 imagesauto-applied↩ revert
#184meta description · /pricingauto-applied↩ revert
#185schema + canonical · PR #214merged↩ revert
◆ Autoblog

A Topic Radar Feeding a Publishing Pipeline.

The Autoblog writes from the locked strategy, not from a prompt box — topics graduate from the radar into drafts, revisions, and published URLs that Search Console knows about.

Draft → revise → publish

Every post runs a revision pass before it ships — and drafts wait for review until the strategy’s publish gate is armed.

Wired to the money pages

Posts internal-link into the service pages the strategy names. The cluster exists to push authority where revenue lives.

cadence from the locked strategytone from your brand kitevery URL submitted to GSChuman edit anytime
◆ The data plane

Real Data Under Every Decision.

Strategies cite it, Autopilot ranks by it, reports are drawn from it — the market view from DataForSEO, the ground truth from your own Google connections.

DataForSEOkeywords for sitekeyword ideasdifficultysearch intentranked keywordsSERP organicmaps local packcompetitor domain intersectionbacklinks summaryon-page instantcontent analysis
GoogleGSC · search analyticsGSC · sitemapsGSC · URL inspectionGA4 · runReport

per-project DataForSEO budget caps · Search Console and GA4 are your own connections

◆ Command Center

One Workbench Per Client. One Portfolio Over All.

Every project gets the full workbench — strategy, autopilot queue, results, evidence. The portfolio rolls them up so one person can run SEO for thirty clients without thirty tabs.

enrollmentautopilotautoblogreports
Avid Auto Detailing✓✓✓
Copperline Studio✓✓✓
Northbeam Digital✓—✓
Tality✓✓—
ProTech——✓
enrolled per project — nothing runs by default
P0Bulk review — this week

12 P0 findings across 8 projects, in one queue. Approve the batch below your floor; the structural three open as pull requests.

Approve 9 below the floorOpen 3 as PRs
send to terminal — Claude Code takes the ticket →
◆ Client reports

The Report Is a Link, Not an Attachment.

Share a live, branded report page per client — rankings, clicks, and the work that moved them. Delivery is QA’d before it sends, and the same numbers live in their portal.

  • Public share links clients open without a login
  • Scheduled sends pass a delivery-QA canary before any client sees them
  • Drawn from Search Console and GA4 — numbers, not screenshots
  • Branded under your agency, on your domain
The white-label portal →
◆ FAQ

Straight Answers.

Does Zyan edit my client’s site without asking?
Only inside the floor you set. Low-risk fixes — meta descriptions, alt text, internal links — can auto-apply if you arm that floor for the project, and every one lands in the rollback ledger. Anything structural — schema, canonicals, redirects — always ships as a pull request your team reviews. Nothing is ever silent: every change is a commit you can read and revert.
Where does the keyword and ranking data come from?
Two places: DataForSEO for the market view — keyword ideas, difficulty, SERP results, local pack, backlinks, competitor overlap — and your own Google Search Console and GA4 connections for the ground truth on your pages. Each project carries its own DataForSEO budget cap, so research spend is bounded per client.
How do fixes physically reach the site?
Through the site’s git repository, via the platform’s GitHub connection — a branch, a pull request, and checks, the same way a teammate would ship. Sites built with Zyan Build are wired for this from day one.
What if a change makes things worse?
Every applied change — auto-applied or merged — is recorded in the rollback ledger with what changed, when, and a revert path. Merged fixes revert like any other commit; auto-applied ones revert straight from the ledger.
Is the Autoblog on by default?
No. Autopilot, Autoblog, and reports each enroll per project from the portfolio view. The Autoblog only writes from a locked strategy, and posts wait as drafts until that strategy’s publish gate is armed.