mcp-seo-aeo-agency-engine

name	mcp-seo-aeo-agency-engine
description	Run a multi-client SEO and AEO delivery engine from an agent using Zapier MCP: intake form to keyword research, WordPress drafts, gated human review, and monthly performance reports. Use when an agency wants to cut hours-per-client, scale SEO without hiring, automate answer-engine optimization deliverables, or productize an SEO practice.

MCP SEO/AEO Agency Engine

Turn a small SEO or AEO practice into a repeatable delivery engine: one intake form per client, orchestrated research and content production, human gates where judgment matters, and a monthly report the client can read without rebuilding it by hand.

Customer story: How a two-person SEO shop is building an engine to run twelve clients in thirty minutes a month.

What This Skill Does

This skill instructs an AI agent to:

1. Capture client context once via a structured intake form.
2. Generate keyword research, answer-engine structure, content queues, and technical SEO notes.
3. Draft and stage content in WordPress or another CMS with explicit review gates.
4. Produce monthly performance reporting across site, traffic, and local/profile signals.
5. Use Zapier MCP for app actions the agent cannot perform natively.

The operator works from an agent hub for planning, context, and review. Zapier MCP is the production bridge.

When You Need This Pattern

Use this when:

• Agency delivery time per client caps growth.
• Strategy work happens in an agent, but execution still requires tab-hopping into CMS, analytics, and reporting tools.
• The team serves multiple clients who need similar deliverables with different source inputs.
• The desired operating model is sub-hour monthly hands-on time per client.

Skip this if you only need a single internal weekly marketing report. Use mcp-weekly-growth-report instead.

Architecture

Agent hub
  - Client context
  - Research docs
  - Article queues
  - Approval notes

Zapier MCP
  - Intake: forms or tables
  - CMS: draft posts and technical SEO fields
  - Reporting: analytics and search data
  - Optional: image tools, email, docs, chat

Typical Zapier MCP Connections

• Forms or Zapier Tables for client seed data.
• WordPress, Webflow, or another CMS for draft and publish workflow.
• Google Analytics or Search Console for performance sections.
• OpenAI or image APIs for on-brand visuals.
• Gmail, Slack, or Google Docs for review alerts and client-facing summaries.

Core Workflow

1. Define The Client Seed Form

Minimum fields:

• Business name, location, and service list.
• Value proposition and target geography.
• Review policy: auto-publish, alert-before-publish, or always human review.
• Brand assets, logo, and image style prompts.

Store one row per client in Zapier Tables or a form-connected destination so downstream steps use the same client key.

2. Build Research And Content Plan

Prompt the agent to:

• Build a master research doc with priority keywords, article list, and internal linking notes.
• Map AEO/GEO considerations: FAQ blocks, entity clarity, citation-friendly structure.
• Output an article queue the operator can approve before production.

3. Run Production Pipeline

For each approved article:

• Draft in the CMS with title, meta, schema where supported, and internal linking notes.
• Route legal, compliance, and client-tone questions to the operator.
• Generate supporting images only when the brand brief is explicit enough.

4. Assemble Monthly Client Report

The report should include:

• Work completed in the period.
• Traffic and conversion trends.
• Local/profile and campaign signals the client expects.
• Clear next actions.

Write the report to the client's preferred surface via Zapier MCP.

Example Prompts

New client row is in my intake table. Read the intake fields, create the research doc and article queue, and list the first three CMS drafts I should approve this week.

For client [name], pull last month's site and profile performance, summarize work shipped from the CMS, and draft the client-facing report in Google Docs.

Guardrails

• Never auto-publish unless the client policy explicitly permits it.
• Ask before deleting or overwriting production CMS content.
• Keep one join key per client across intake, queue, CMS, and reporting.
• Use summaries and links in reports; do not expose raw private records.
• Keep claims, legal/compliance language, and client-facing sends under human approval.

Related Skills

• mcp-weekly-growth-report: single-team operating report.
• mcp-media-inbox-triage: editorial and comms triage.
• mcp-sheet-cache-bridge: when lightweight sheet read paths must sit beside a source-of-truth table.

Inspired By

Built in production by Adrian Martinez at Hire Adrian, a Toronto digital marketing agency serving about 12 clients. Read the story: How a two-person SEO shop is building an engine to run twelve clients in thirty minutes a month.