Skip to main content
Home/Tools/SEO Autopilot
Back

SEO Autopilot

An agent that keeps a site's SEO cycle turning β€” find, plan, write, publish, measure

A small SEO team juggles six to ten tools and still misses the obvious wins β€” the queries sitting at position 8 to 20, the pages quietly losing clicks β€” because nobody reads Search Console every day. This runs that loop instead: it pulls the opportunities out of Search Console, scores them, drafts a content plan that respects your posting rhythm, writes the articles, puts them into WordPress as drafts, and tracks what happened at 3, 7, 14, 30, 60 and 90 days. Nothing leaves the system without going through a policy engine and a change set, so every outward change is logged and can be undone. Full automation is a setting you turn on, not the default.

Web app In build Β· runs end to end on dev

Key Features

Add a site through a wizard; onboarding runs in the background with progress on the audit screen
A 7, 14 or 30-day cycle: five detectors read Google Search Console and score what is worth doing
A content plan that never exceeds your posting rhythm, approved whole or item by item, as a table or a calendar
Draft β†’ quality gate β†’ WordPress draft β†’ your approval β†’ publish or schedule
Post-publish tracking at 3, 7, 14, 30, 60 and 90 days
Every outward change goes through a policy engine and a change set, and can be undone
An automation level you set yourself, from approve-everything to self-approving at level 3 and above
Multi-tenant: organisations, role-based access, row-level isolation in the database

Built with

NestJSNext.jsTemporalPostgresPythonAnthropic

How it works

Long-running work is Temporal workflows, not cron jobs: onboarding, the site cycle and each article are separate workflows, so a run that takes days can be paused on a human approval, resumed, replayed and tested with time-skipping. A NestJS API serves a versioned REST contract generated from OpenAPI, with row-level security scoping every query to one organisation. Two workers do the work β€” TypeScript for research, strategy, content and quality; Python for crawling, embeddings and Vietnamese word segmentation. The planner calls a real LLM to cluster and outline, but the publishing schedule is plain code, and if the model fails or the budget runs out it falls back to a deterministic planner. Connectors to Search Console, GA4, DataForSEO and WordPress sit behind a port with a contract kit, and all outbound fetches go through an SSRF-safe client.

How to use it

SEO Autopilot

Every step, in the order you will meet them.

  1. 01

    Connect the site β€” about ten minutes

    A four-step wizard. Enter the domain and it checks DNS, robots.txt and the sitemap. Sign in to Search Console and GA4, and the matching property is found for you. Pick your CMS and install the companion plugin β€” it writes one test draft so you can see which permissions actually work. Last, the brand profile: your industry, your voice, the words you never want used, your competitors. Leave halfway through and the wizard remembers where you stopped.

  2. 02

    Read the first audit

    The agent crawls the site and pulls sixteen months of Search Console history. That finishes within a day, and the overview screen then shows what is wrong with the site and the first strategy it proposes. Nothing has been changed yet β€” this step is only the agent telling you what it found.

  3. 03

    Decide how much it may do on its own

    Four levels. Advisor: it analyses and plans, you do the work. Co-pilot: it writes the drafts, you publish. Limited autopilot: it publishes inside the guardrails, you approve the plan. Full autopilot: it runs on its own, except on health, finance and legal topics, which always come back to you. Start at Advisor. Moving up to full autopilot has its own confirmation screen, because it is the one setting that is hard to walk back.

  4. 04

    Approve the content plan

    Every 7, 14 or 30 days β€” you choose β€” the agent scores what it found and turns it into a plan. See it as a table or a calendar, drag an item to a different day, change the keyword or the format, then approve the whole set or go item by item. Each line carries the reason it is there and the data behind it, so you are deciding rather than guessing.

  5. 05

    Approve the articles

    Everything waiting on you collects in one screen. Each article shows its quality-gate score, why the agent wrote it, and a draft already sitting in your CMS. There is no editor here on purpose: you click through to WordPress, edit where you normally edit, and the change syncs back and is re-scored. Approvals work at phone width, and a one-time link sent over Telegram or Zalo lets you clear the queue without signing in again.

  6. 06

    Watch what happened, and step in when needed

    Each article has a performance tab covering the first 90 days. If a page starts slipping, a separate screen walks the diagnosis in order β€” technical errors, recent changes, pages competing with each other, competitor moves, a shift in what searchers want, stale content, industry change β€” and proposes a fix, with merges and 301s always requiring your approval. A weekly digest arrives Sunday morning. And a stop button sits in the top bar of every screen: one site or all of them, within thirty seconds.

Why choose this tool?

The four things that decide whether this is worth your time.

Nothing leaves without passing the gate

Every outward change goes through a policy engine. Health, finance and legal topics always wait for a person, even at the highest automation level.

Every decision, with its reason

Each action is logged with why the agent took it, and the undo button sits next to the change itself rather than buried in settings.

A quality gate before you see it

Banned words, brand voice, search-intent coverage and duplication are checked first. An article that fails is held back with the reason for each criterion it missed.

Measured for 90 days, not 9

Each article is followed for three months after publishing. If the whole site loses more than 30% of its traffic in a week, automation steps itself down and waits for you.

How it works

How It Works

Collect

crawl the site, then pull Google Search Console and GA4

Analyse

find queries stuck at position 8–20, pages losing clicks, pages competing with each other

Strategy

score what is worth doing and group related opportunities into clusters

Plan

lay the articles onto a calendar that respects your posting rhythm

Execute

write, pass the quality gate, land in the CMS as a draft for you to approve

Measure

track indexing and position at 3, 7, 14, 30, 60 and 90 days β€” then start again

Frequently Asked Questions