agentleFS
tmolavitmolavi/n8n-agent-skills/skills/n8n-ai-seo-geo-automation/SKILL.md

n8n-ai-seo-geo-automation

Skill1 starsChanged 3 months agoMITView on GitHub

Use when building n8n workflows for SEO, AEO, GEO, AI visibility monitoring, content pipelines, schema/JSON-LD checks, rank/citation tracking, or integrating Molavi GEO tools (geo-scope, mcp-geo-server) with n8n.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No mass-generated thin content pushed live without human review.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

n8n for SEO / AEO / GEO Automation

Author: Taghi Molavi — Senior SEO & GEO Systems Architect

Why this skill exists

AI coding agents often build brittle "SEO bots". This skill encodes safe, measurable automation patterns that pair n8n with modern AI-visibility work.

Core workflow families

FamilyExample triggerOutputs
AI visibility pulseSchedule dailyBrand mention/citation checks → sheet + alert
Content opsCMS webhookBrief → draft QA → schema suggest → Slack approve
Technical watchCrawl finishBroken schema, indexation anomalies
Entity / source monitoringRSS + SearchCompetitor citations, Reddit/UGC spikes
Lead + twinForm submitEnrich → CRM → first response (human gate)

Pair with Molavi open source

Pattern: n8n orchestrates; GEO MCP/CLI measures; humans approve irreversible publishes.

Non-negotiables for SEO automations

  1. No mass-generated thin content pushed live without human review.
  2. Log every prompt/model/version used for GEO experiments (reproducibility).
  3. Separate measurement workflows from mutation workflows.
  4. Respect robots/ToS/rate limits of sources.
  5. Store evidence links for any "we are cited" claim.

Suggested n8n building blocks

  • Schedule / Webhook triggers
  • HTTP Request + credentials toward Search Console, CMS, analytics
  • Data Tables for prompt sets & run history
  • AI Agent only behind approval gates for publish actions
  • Error workflow → Telegram/Slack

References

  • references/GEO_PIPELINE.md
  • references/CONTENT_GUARDRAILS.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.