seo-research
Skill0 starsChanged 53 days agoMITView on GitHub
SEO topic selection and research: SERP analysis, competitor deep-dives, LSI/related keywords, People-Also-Ask mining, and finding a differentiated angle. Use when picking what a blog article should cover, researching a keyword before writing, or when the user asks "what should I write about" / "research blog topics" for their niche.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- oegeyilmaz9/seo-aeo-geo-ultimatetheir own version, first seen Oct 13, 2026
- empowerment-ai/agent-site-kittheir own version, first seen Sep 30, 2026
- hyperfx-ai/marketing-skillstheir own version, first seen Jun 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- hyperfx-ai/marketing-skills★ 112same name
- oegeyilmaz9/seo-aeo-geo-ultimate★ 6same name
- empowerment-ai/agent-site-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- blog-imagesSkill
- blog-publishSkill
- humanizeSkill
- seoblog-humanizeSkill
- seoblog-publishSkill
- seoblog-setupSkill
- seo-blogSkill
- seoblog-statusSkill
- seo-writingSkill
- social-articleSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
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 11
Read runtime instructions before running scripts.
- Distinctive: line 61
If research shows the topic is too thin to support a substantive article, or it's already well covered on the site, skip it and choose …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read runtime instructions before running scripts.
SEO research
Research with WebSearch and WebFetch only. Never use a logged-in browser (the
Social Cue browser tools) for research: no reddit .json or other API
endpoints, no scripted fetch loops. That traffic carries the user's session,
looks like a bot and gets their accounts banned.
Topic selection
Keyword mode — the user supplied keywords:
- First keyword = primary (title, first paragraph, at least one H2).
- Remaining keywords = secondary/LSI — woven naturally into ONE article, not one article each.
- Research all of them together to find a cohesive angle.
Auto-discover mode — no keywords given:
- Review existing content (state history + live article list, all statuses) for coverage and gaps. Archived articles are drafts the site owner rejected: treat the topic and close variants of it as covered, not as a gap.
- WebSearch for: trending topics in the niche; "People Also Ask" questions; competitor content the site hasn't covered; seasonal/timely opportunities.
- Select a topic that is NOT already covered, complements existing content (extends a topical cluster or starts a new one), shows real search interest, and genuinely helps readers in this niche.
Research steps (per topic)
- SERP analysis — WebSearch the primary keyword. From the top results: what subtopics do they cover, what depth is typical, what questions are answered?
- Competitor deep-dive — WebFetch 2–3 top-ranking articles: content structure (headings, flow), unique angles and data points, what's missing or could be done better.
- Related/LSI keywords — WebSearch variations:
- "[keyword] tips"
- "[keyword] best practices"
- "[keyword] vs [alternative]"
- "how to [keyword]"
- Find your angle — what will this article do differently? More actionable advice, more current information, a unique perspective from the site's niche, or better organization/comprehensiveness.
- Product research (only if the site config has a
product) — WebFetch the product URL and understand features, audience, and value proposition; note where the product genuinely relates to the topic. If the keyword has no natural connection to the product, plan a great article without forcing it.
Quality bar
If research shows the topic is too thin to support a substantive article, or it's already well covered on the site, skip it and choose another. Never write filler to satisfy a keyword.
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.