seo-geo-optimize
Audits and automatically implements SEO, local SEO (Geo/Schema.org), and Social Graph structured data across web projects according to modern best practices.
Best use case
seo-geo-optimize is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audits and automatically implements SEO, local SEO (Geo/Schema.org), and Social Graph structured data across web projects according to modern best practices.
Teams using seo-geo-optimize should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/seo-geo-optimize/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How seo-geo-optimize Compares
| Feature / Agent | seo-geo-optimize | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audits and automatically implements SEO, local SEO (Geo/Schema.org), and Social Graph structured data across web projects according to modern best practices.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill: SEO & Geo Optimize ## What This Skill Does Analyzes the project (especially frontend like SvelteKit, Next.js, or static static web apps) and ensures complete compliance with modern Search Engine Optimization (SEO) and Geotargeting (Local SEO) standards. Instead of just producing an audit report, this skill proactively implements missing meta tags, schema.org structured data, open graph entries, and semantic structures directly into the project's source code. ## When to Use - When launching a new frontend project (after the MVP is generally complete). - Before shipping a website to production. - When the user asks to "optimize for search engines", "add meta tags", or "implement local SEO". - For localized apps and landing pages that need schema.org injection. ## Execution Model - **Always**: the primary agent or an `engineer` subagent runs this skill directly. - **Rationale**: Implementing SEO often requires altering global layouts (e.g. `+layout.svelte`, `_app.tsx`), manipulating metadata routing handlers, and injecting JSON-LD scripts—all core engineering tasks. ## Workflow ### Step 1: Analyze Current State & Routing Use `find` and `grep` to analyze the project's routing structure and identify existing SEO components: - Does the project have a global `<Head>`, `<svelte:head>`, or a `<Seo>` component? - Are there `robots.txt` and `sitemap.xml` (or generator endpoints) present? - Is there an existing configuration for `hreflang` (for multi-language apps)? ### Step 2: On-Page SEO Implementation For each major route or the global layout, ensure the following are implemented: 1. **Dynamic Meta Tags:** `title`, `description`, `canonical` URLs. 2. **Semantic HTML Elements:** Ensure proper `<h1>` wrapping for main content and absence of multiple `<h1>` tags on a single page. 3. If no centralized SEO component exists, **scaffold one** (e.g., `src/components/Seo.svelte` or `src/components/Seo.tsx`) and integrate it into the layouts. ### Step 3: Social & Open Graph Metadata Inject essential social sharing tags into the centralized SEO component or layout: - `og:title`, `og:description`, `og:type`, `og:url`, `og:image` - `twitter:card` (typically `summary_large_image`), `twitter:title`, `twitter:description`, `twitter:image` ### Step 4: Local & Geo SEO (Structured Data via JSON-LD) Audit for local business context and create JSON-LD schema objects (`<script type="application/ld+json">`). Ask the user for specific business data if not evident. 1. Implement `LocalBusiness` / `Organization` schemas globally or on contact pages. 2. Implement `BreadcrumbList` on subpages. 3. Ensure `hreflang` header mapping in multi-lingual apps so geo-targeting works correctly for different regions. ### Step 5: Web Crawlability Hooks 1. Create or verify `robots.txt`. 2. Ensure there's a dynamic or static `sitemap.xml` available (e.g. `src/routes/sitemap.xml/+server.ts` in SvelteKit). ### Step 6: Verify and Run Tests - Use `npm run build` or the project's equivalent type checker/linter to ensure injecting metadata hasn't broken page compilation. - Ensure all injected JSON-LD strings are properly escaped to prevent XSS issues in the template. ## Rules 1. **Be constructive:** Do not just output an audit report; actively add the `robots.txt`, SEO components, and tags to the code. 2. **Use centralized components:** Always prefer creating a single reusable `<Seo>` component over hardcoding tags into 20 different routes. 3. **Escaping JSON:** When injecting JSON-LD, ensure variables and content are cleanly stringified to avoid breaking HTML. 4. **No built-in explore agent:** do NOT use the built-in `explore` subagent type. Wait for user input if business details (address, social links) are needed for the JSON-LD schema.
Related Skills
dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
llm-application-dev-prompt-optimize
You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati
reasoning-trace-optimizer
Debug and optimize AI agents by analyzing reasoning traces. Activates on 'debug agent', 'optimize prompt', 'analyze reasoning', 'why did the agent fail', 'improve agent performance', or when diagnosing agent failures and context degradation.
agent-orchestration-multi-agent-optimize
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
seo-fundamentals
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.
seo-forensic-incident-response
Investigate sudden drops in organic traffic or rankings and run a structured forensic SEO incident response with triage, root-cause analysis and recovery plan.
seo-content-writer
Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.
seo-content-refresher
Identifies outdated elements in provided content and suggests updates to maintain freshness. Finds statistics, dates, and examples that need updating. Use PROACTIVELY for older content.
seo-content-planner
Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.
seo-content-auditor
Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines.
seo-cannibalization-detector
Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.
seo-audit
Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.