seo-report
Skill0 starsChanged 3 months agoMITView on GitHub
Deep SEO analysis for aljazeera360.com: reads the snapshot history, runs the MCP SEO tools for fresh data, and — via the onvesper-expert agent — turns every finding into concrete Vesper Back Office fix instructions. Produces a prioritized markdown report in reports/seo/. Use when the user asks for an SEO report, SEO analysis, "شوف الـ SEO", or wants to know what to fix this week.
- Reads credentials
11 other projects use a version of this.
Adopted by
Most recently taken up by
- teemukarjaluoto/seo-sauna-mcptheir own version, first seen Nov 16, 2026
- sitetiller/ai-visibility-skillstheir own version, first seen Nov 15, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- foverse/seoversetheir own version, first seen Nov 8, 2026
- lcrvl2/seo-skillstheir own version, first seen Oct 15, 2026
- every-app/open-seotheir own version, first seen Oct 8, 2026
Used with
Projects with it also use ai-prompt-research, seo-project-setup and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
every-appSkillai-prompt-research
Find the questions people ask about a market, how ChatGPT answers them, and which sites get cited in the answers. Use when the user asks what people ask AI about their niche, wants prompt ideas, or wants to know where their brand is missing before choosing prompts to track. Research only; it never saves tracking or starts answer collection.
Also in 3 projects that use this
JwuthriSkillseo-project-setup
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
Also in 4 projects that use this
JwuthriSkilllink-prospecting
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Also in 4 projects that use this
akii-technologies-ltdSkillkeyword-clustering
Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.
Also in 4 projects that use this
huiferSkilllocal-seo
本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。
Also in 5 projects that use this
MicrosoftSkillcompetitive-landscape
Use when a branch manager asks something like \"Who are we up against in each metro\"
Also in 4 projects that use this
- +1 more from Jwuthri
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- every-app/open-seo★ 28ksame name
- risukisu/marketing-skills★ 6same name
- 01clauding/claude-seo-skill★ 4same name
- foverse/seoverse★ 4same name
- kid7st/agenticseo★ 2same name
- nisarth/claude-skills-store★ 1same name
- emeraldwalk/skills★ 0same name
- lcrvl2/seo-skills★ 0same name
- sitetiller/ai-visibility-skills★ 0same name
- teemukarjaluoto/seo-sauna-mcp★ 0same name
1 more not listed
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 repository25 other files it gives its agents.
- seo-auditSkill
- seo-backlinksSkill
- seo-clusterSkill
- seo-competitor-pagesSkill
- seo-content-briefSkill
- seo-contentSkill
- seo-dataforseoSkill
- seo-driftSkill
- seo-ecommerceSkill
- seo-flowSkill
- seo-geoSkill
- seo-googleSkill
- seo-hreflangSkill
- seo-image-genSkill
- seo-imagesSkill
- seo-localSkill
- seo-mapsSkill
- seo-pageSkill
- seo-planSkill
- seo-programmaticSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-sxoSkill
- seo-technicalSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If empty, this is a first run — generate a fresh baseline and say so instead of inventing trends.
- Distinctive: line 36
Read the last snapshots from history.
- Distinctive: line 38
Run or refresh live data if the latest snapshot is older than 3 days.
- Very specific: line 51
Write the report to reports/seo/deep-dive-YYYY-MM-DD.md (this directory is gitignored — reports are on-demand deliverables for the …
- Very specific: line 64
If the claude-seo plugin is installed (its /seo … commands are available), combine forces: use its technical/page-level audit commands (e.g.
- Distinctive: line 75
Never invent Back Office UI labels — if onvesper-expert can't confirm a step from the docs, say so and link the closest doc page.
- Distinctive: line 77
Keep the report scannable: tables + checkboxes, no walls of text.
“Common” is measured: kept by at least 6 in 10 of the 9 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
/seo-report — Deep SEO analysis with actionable Vesper fixes
You produce a prioritized, actionable SEO report for aljazeera360.com. The difference between this and the raw snapshot script: you analyze trends, prioritize, and translate every finding into exact Back Office steps.
Inputs you have
- Snapshot history —
reports/seo/history/metrics.jsonl(gitignored, local-only; one JSON row per run) and rendered reports inreports/seo/*.md. If empty, this is a first run — generate a fresh baseline and say so instead of inventing trends. - Live data — run
python scripts/seo_snapshot.pyfrom the repo root for a fresh row (requiresAJ360_API_KEYin env;server.pyis imported directly from the repo, no install step), or import tools straight from theservermodule for targeted queries (e.g.get_ai_discoverability_scoreon one section,get_series_seo_mapfor one series,audit_metadata_quality). - Platform expertise — the
onvesper-expertagent (.claude/agents/) knows the Vesper/Deltatre platform that powers the site, with the full docs mirror inonvesper-kb/. Always consult it to convert findings into exact Back Office/DVE steps.
Procedure
- Read the last snapshots from history; compute per-section trends (discoverability avg, health score) across the available weeks.
- Run or refresh live data if the latest snapshot is older than 3 days.
- Identify the top issues, e.g.:
- Sections with declining or low (<55) discoverability
- Videos in
needs_improvementlists (recurring ones are top priority) - Metadata gaps: missing descriptions, categories, thumbnails
- Stale sections (>30 days without new content)
- Rising audience search tags with little matching content (content gaps)
- For each issue class, ask the onvesper-expert agent HOW to fix it in the
platform. Examples of the mapping you're after:
- Missing/short video metadata → DVE → Video → Metadata (fields, limits)
- Section SEO title/description → Back Office → Content → Sections (SEO metadata)
- Typed tags coverage → DVE typed tags best practices + batch enum upload
- Series schema/interstitials → collections & series curation pages
- Write the report to
reports/seo/deep-dive-YYYY-MM-DD.md(this directory is gitignored — reports are on-demand deliverables for the requester, never committed to the public repo):- Executive summary (5 lines max, Arabic)
- Trends table (per section, across weeks)
- Priority actions — each with: what, why (metric evidence), and exact Back Office steps (cite the onvesper-kb page used)
- Content gaps — search tags/topics the audience wants but the catalog under-serves
- Reply to the user with the executive summary and the report path.
Works with the claude-seo plugin (optional)
If the claude-seo plugin is installed (its /seo … commands are available),
combine forces: use its technical/page-level audit commands (e.g. /seo audit,
/seo schema) for generic web checks, feed them the platform data from this
repo's MCP tools (catalog metadata, tag maps, discoverability scores), and keep
this skill as the layer that turns all findings into Vesper Back Office fix
steps via the onvesper-expert agent.
Rules
- Match the user's language (Egyptian Arabic → Arabic report body is fine; keep metric names in English).
- Never invent Back Office UI labels — if onvesper-expert can't confirm a step from the docs, say so and link the closest doc page.
- Keep the report scannable: tables + checkboxes, no walls of text.
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.

