seo-strategy

seo-strategy is a skill for Claude Code, Codex from Davidhevesi/marketing-skills-repo. It costs 35 tokens per session (5,331 once invoked), scanned A, original, MIT.

A guide for improving how easily a website is found in Google, AI search tools, and local search results.

In plain words
What is it for?
Use it for keyword research, page improvements, technical website checks, local search, content planning, and optimisation for AI-generated search answers.
Why use it?
It turns search-visibility problems into a prioritised set of practical changes instead of an unranked list of possible improvements.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for keyword research, page improvements, technical website checks, local search, content planning, and optimisation for AI-generated search answers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davidhevesi/marketing-skills-repo/seo-strategy
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Davidhevesi/marketing-skills-repo --skill seo-strategy
Clone the repo
git clone --depth 1 https://github.com/Davidhevesi/marketing-skills-repo

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for seo-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/seo-strategy/github.svg)](https://agentmods.dev/skills/davidhevesi/marketing-skills-repo/seo-strategy)
Your own site
<a href="https://agentmods.dev/skills/davidhevesi/marketing-skills-repo/seo-strategy"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/seo-strategy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for seo-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/davidhevesi/marketing-skills-repo/seo-strategy"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/seo-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.05331
Opus 5 $0.00017 $0.02665
Sonnet 5 $0.00007 $0.01066
Haiku 4.5 $0.00003 $0.00533

Measured 12d ago against content hash 1769c19e8777, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

seo-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/seo-strategy/SKILL.md · 497 lines

How it starts

The opening of the file, as written. The whole thing — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SEO Strategy

You help users understand, audit, and improve their search visibility — across traditional Google search, AI-powered search (ChatGPT, Perplexity, Google AI Overviews), and local search. This skill covers keyword research, on-page optimization, technical SEO fundamentals, content strategy for search, and local SEO. The goal is always actionable: not a list of things that could theoretically be better, but a prioritized set of changes that move the needle for this specific business.

Works for any business with a website — service providers, local businesses, e-commerce, SaaS, content publishers, and agencies.


Before You Start

Check for Context

Look for a Business Context document in the project knowledge files.

If it exists: Read it before doing anything. The website URL, platform, active channels, business type, audience, geographic area, and competitive landscape are all there. Use them — especially the target audience, the problems they solve, and the customer language section (actual words customers use are keyword gold).

If it doesn't exist: Say — "To give you useful SEO recommendations, I need to understand your business, your audience, and your goals. Do you have a Business Context document in this project? If not, tell me: what does your business do, who are your customers, and what's your website URL?"

At minimum, you need: the website URL or description, the business type, the primary audience, and the geographic scope (local, national, international).


Workflow

Step 1: Identify the Task

SEO is a wide discipline. Get specific about what's needed.

What type of SEO work?

  • Full audit (where do we stand, what should we fix first?)
  • Keyword research (what should we be ranking for?)
  • On-page optimization (improve existing pages)
  • Content strategy (what new content to create for search)
  • Technical SEO review (site health, speed, crawlability)
  • Local SEO (Google Business Profile, local pack rankings)
  • AI search optimization (visibility in ChatGPT, Perplexity, AI Overviews)
  • Competitor SEO analysis (what are they ranking for that we aren't?)

Read the full file on GitHub · 497 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 497 lines · 35 tokens per session scan A 1769c19e8777

Subscribe to this mod's changes

seo-strategy is a skill published in the GitHub repository Davidhevesi/marketing-skills-repo (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 5,331 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens