AUREVA · BACKEND PIPELINE PROTOTYPE

Seven agents that take a client from onboarding to AI citations — and never stop.

A working prototype of the full agentic SEO/GEO pipeline: research, briefing, writing, quality gating, publishing, citation monitoring and continuous optimization, with human oversight at the points that matter and a full audit trail per client.

Open the interactive demo → How it works

The pipeline

1 · Researchopportunities ⏸ specialist approves plan 2 · Briefper-article specs 3 · WriterGEO-ready drafts 4 · Qualityscore & gate ⏸ optional client review 5 · Publishlive + llms.txt 6 · Monitorcitations weekly ⏸ specialist approves report 7 · Optimizefix & refresh

Optimize feeds newly discovered content gaps back to Research — the loop runs monthly, indefinitely. Below-threshold drafts bounce between Quality and Writer up to a configurable number of attempts, then escalate to a human. Every action lands in the per-client audit log.

What each agent does

AGENT 1

Research

Keyword expansion, conversational long-tail discovery, competitor gap analysis, AI-intent mapping and a hub-and-spoke topical map. Long-tail first is enforced: high-competition terms are excluded from month one. Output: a prioritized monthly content plan (8–12 articles).

AGENT 2

Brief

One brief per planned article: target keywords with fan-out queries, word count, heading structure, internal link targets (spokes → pillar, pillar → spokes), schema type, competing URLs and a unique-angle directive.

AGENT 3

Writer

Long-form, people-first drafts built for citation: a direct answer in the first 150 words, named entities, sourced facts, structured Q&A, a mandatory FAQ, JSON-LD schema and 2,000+ words. Rewrites target the exact criteria Quality failed.

AGENT 4

Quality

Scores every draft 0–100 against the GEO rubric below. Below threshold → returned to the Writer with the failed criteria. Still failing after max attempts → escalated to a human with one-click resolution.

AGENT 5

Publish

Verifies robots.txt allows GPTBot, ClaudeBot, PerplexityBot and Googlebot (blocked = escalate, publish nothing), pushes the post with metadata, canonical, Open Graph and schema, regenerates llms.txt, pings IndexNow and Search Console.

AGENT 6

Monitor

Weekly per-keyword rankings, GA4 traffic, AI-bot crawl activity and per-engine citation status (ChatGPT, Gemini, Perplexity, Google AI Overview). Citations are probabilistic, so every run re-checks; drops are flagged the moment they happen.

AGENT 7

Optimize

Rewrites intros, extends FAQs, reinforces internal links and refreshes facts on flagged pages, republishes them, and feeds new content gaps back to Research — closing the loop.

CROSS-CUTTING

Orchestration

Structured JSON handoffs with PASS / FAIL / NEEDS_REVIEW / ESCALATE_TO_HUMAN statuses, independently triggerable stages, configurable thresholds per client, multi-client state and a central audit log.

The GEO scoring rubric

What makes content citable by AI engines — every article is scored before it can go live.

CriterionPointsCheck
Direct answer format15Clear answer to the query within the first 150 words
Entity density15≥ 8 named and defined entities
Fact density15≥ 5 verifiable statistics with named sources
FAQ section15Mandatory — ≥ 3 likely follow-up questions with direct answers
Structured answers10Q&A blocks, numbered lists, definition blocks
Schema readiness10Article/BlogPosting + FAQPage + Author JSON-LD
Unique perspective10An angle competitors are not using
Word count10≥ 2,000 words of expert-level content

Human oversight, by design

Three gates keep specialists in control without slowing the machine down: the content plan requires specialist approval before production starts; drafts can require client review before publishing (configurable per client); the performance report requires specialist sign-off before optimization runs. Anything the agents can't resolve raises an ESCALATE_TO_HUMAN into the escalation queue.

The WordPress plugin interface

The client-facing dashboard connects over a small authenticated REST API (per-client x-api-key):

GET  /api/plugin/published         → published content metadata (URL, title, keywords, date, schema)
GET  /api/plugin/performance       → latest rankings, per-engine citations, traffic, dropped pages
POST /api/plugin/settings          → client settings push (keywords, niche, competitors, brand voice)
POST /api/plugin/content-decision  → client approvals (approved / rejected / revision requested)

About this prototype

The engine, orchestration, gates, scoring and APIs are fully implemented and covered by an automated end-to-end test suite. Every external service (Google Ads, DataForSEO, Search Console, GA4, Ahrefs, WordPress REST, IndexNow, the writing LLM, and per-engine citation checks) sits behind an adapter interface with deterministic mocks, so the whole system runs — and can be demoed — without credentials. Swapping a mock for a live integration is a one-file change per service.

The interactive demo runs the real agents entirely in your browser: onboard a client, run each stage, approve plans, watch the quality retry loop, publish, see a citation drop get flagged and optimized. Nothing leaves the page.