# 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. - Skill: `gabrielmoreira/seo-geo-optimize` (Agent Skill) - Install (CLI): `npx skillmds@latest add gabrielmoreira/seo-geo-optimize` - Raw SKILL.md: https://api.skillmd.com/api/skills/gabrielmoreira/seo-geo-optimize/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Marketing & Growth - License: MIT - Author: gabrielmoreira (https://skillmd.com/u/gabrielmoreira) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/gabrielmoreira/seo-geo-optimize --- # 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 ``, ``, or a `` 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 `

` wrapping for main content and absence of multiple `

` 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 (`