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:
- Dynamic Meta Tags:
title, description, canonical URLs.
- Semantic HTML Elements: Ensure proper
<h1> wrapping for main content and absence of multiple <h1> tags on a single page.
- 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:imagetwitter: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.
- Implement
LocalBusiness / Organization schemas globally or on contact pages.
- Implement
BreadcrumbList on subpages.
- Ensure
hreflang header mapping in multi-lingual apps so geo-targeting works correctly for different regions.
Step 5: Web Crawlability Hooks
- Create or verify
robots.txt.
- 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
- Be constructive: Do not just output an audit report; actively add the
robots.txt, SEO components, and tags to the code.
- Use centralized components: Always prefer creating a single reusable
<Seo> component over hardcoding tags into 20 different routes.
- Escaping JSON: When injecting JSON-LD, ensure variables and content are cleanly stringified to avoid breaking HTML.
- 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.
1---2name: seo-geo-optimize3description: Audits and automatically implements SEO, local SEO (Geo/Schema.org), and Social Graph structured data across web projects according to modern best practices.4license: MIT5---6
7# Skill: SEO & Geo Optimize
8
9## What This Skill Does
10
11Analyzes 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.
12
13## When to Use
14
15- When launching a new frontend project (after the MVP is generally complete).
16- Before shipping a website to production.
17- When the user asks to "optimize for search engines", "add meta tags", or "implement local SEO".
18- For localized apps and landing pages that need schema.org injection.
19
20## Execution Model
21
22- **Always**: the primary agent or an `engineer` subagent runs this skill directly.
23- **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.
24
25## Workflow
26
27### Step 1: Analyze Current State & Routing
28Use `find` and `grep` to analyze the project's routing structure and identify existing SEO components:
29- Does the project have a global `<Head>`, `<svelte:head>`, or a `<Seo>` component?
30- Are there `robots.txt` and `sitemap.xml` (or generator endpoints) present?
31- Is there an existing configuration for `hreflang` (for multi-language apps)?
32
33### Step 2: On-Page SEO Implementation
34For each major route or the global layout, ensure the following are implemented:
351. **Dynamic Meta Tags:** `title`, `description`, `canonical` URLs.
362. **Semantic HTML Elements:** Ensure proper `<h1>` wrapping for main content and absence of multiple `<h1>` tags on a single page.
373. 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.
38
39### Step 3: Social & Open Graph Metadata
40Inject essential social sharing tags into the centralized SEO component or layout:
41- `og:title`, `og:description`, `og:type`, `og:url`, `og:image`
42- `twitter:card` (typically `summary_large_image`), `twitter:title`, `twitter:description`, `twitter:image`
43
44### Step 4: Local & Geo SEO (Structured Data via JSON-LD)
45Audit 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.
461. Implement `LocalBusiness` / `Organization` schemas globally or on contact pages.
472. Implement `BreadcrumbList` on subpages.
483. Ensure `hreflang` header mapping in multi-lingual apps so geo-targeting works correctly for different regions.
49
50### Step 5: Web Crawlability Hooks
511. Create or verify `robots.txt`.
522. Ensure there's a dynamic or static `sitemap.xml` available (e.g. `src/routes/sitemap.xml/+server.ts` in SvelteKit).
53
54### Step 6: Verify and Run Tests
55- Use `npm run build` or the project's equivalent type checker/linter to ensure injecting metadata hasn't broken page compilation.
56- Ensure all injected JSON-LD strings are properly escaped to prevent XSS issues in the template.
57
58## Rules
59
601. **Be constructive:** Do not just output an audit report; actively add the `robots.txt`, SEO components, and tags to the code.
612. **Use centralized components:** Always prefer creating a single reusable `<Seo>` component over hardcoding tags into 20 different routes.
623. **Escaping JSON:** When injecting JSON-LD, ensure variables and content are cleanly stringified to avoid breaking HTML.
634. **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.
gabrielmoreira