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.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- n8n-agentsSkill
- n8n-binary-dataSkill
- n8n-code-nodesSkill
- n8n-credentials-securitySkill
- n8n-data-tablesSkill
- n8n-debuggingSkill
- n8n-error-handlingSkill
- n8n-expressionsSkill
- n8n-loopsSkill
- n8n-mcp-toolingSkill
- n8n-node-configurationSkill
- n8n-production-opsSkill
- n8n-subworkflowsSkill
- n8n-workflow-lifecycleSkill
- using-n8n-skillsSkill
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
- Distinctive: line 39
No mass-generated thin content pushed live without human review.
≈ “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.
Files
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
| Family | Example trigger | Outputs |
| AI visibility pulse | Schedule daily | Brand mention/citation checks → sheet + alert |
| Content ops | CMS webhook | Brief → draft QA → schema suggest → Slack approve |
| Technical watch | Crawl finish | Broken schema, indexation anomalies |
| Entity / source monitoring | RSS + Search | Competitor citations, Reddit/UGC spikes |
| Lead + twin | Form submit | Enrich → CRM → first response (human gate) |
Pair with Molavi open source
- geo-scope — benchmark prompts & SoM-style experiments
- mcp-geo-server — GEO/RAG readiness audits via MCP
- Site: molavi.pro
Pattern: n8n orchestrates; GEO MCP/CLI measures; humans approve irreversible publishes.
Non-negotiables for SEO automations
- No mass-generated thin content pushed live without human review.
- Log every prompt/model/version used for GEO experiments (reproducibility).
- Separate measurement workflows from mutation workflows.
- Respect robots/ToS/rate limits of sources.
- 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.mdreferences/CONTENT_GUARDRAILS.md
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
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.

