SEO Plan V2

Strategic SEO Planning

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/seo-plan from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Strategic SEO Planning

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Industry Templates, Output, DataForSEO Integration (Optional), Error Handling, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when building an SEO strategy or roadmap for a new or existing site.
• Use when planning content, architecture, and implementation phases together.
• Use when the user asks for an SEO plan rather than a point-in-time audit.
• Use when the request clearly matches the imported source intent: >.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Business type, target audience, competitors, goals
2. Current site assessment (if exists)
3. Budget and timeline constraints
4. Key performance indicators (KPIs)
5. Identify top 5 competitors
6. Analyze their content strategy, schema usage, technical setup
7. Identify keyword gaps and content opportunities

Imported Workflow Notes

Imported: Process

1. Discovery

• Business type, target audience, competitors, goals
• Current site assessment (if exists)
• Budget and timeline constraints
• Key performance indicators (KPIs)

2. Competitive Analysis

• Identify top 5 competitors
• Analyze their content strategy, schema usage, technical setup
• Identify keyword gaps and content opportunities
• Assess their E-E-A-T signals
• Estimate their domain authority

3. Architecture Design

• Load industry template from assets/ directory
• Design URL hierarchy and content pillars
• Plan internal linking strategy
• Sitemap structure with quality gates applied
• Information architecture for user journeys

4. Content Strategy

• Content gaps vs competitors
• Page types and estimated counts
• Blog/resource topics and publishing cadence
• E-E-A-T building plan (author bios, credentials, experience signals)
• Content calendar with priorities

5. Technical Foundation

• Hosting and performance requirements
• Schema markup plan per page type
• Core Web Vitals baseline targets
• AI search readiness requirements
• Mobile-first considerations

6. Implementation Roadmap (4 phases)

Phase 1: Foundation (weeks 1-4)

• Technical setup and infrastructure
• Core pages (home, about, contact, main services)
• Essential schema implementation
• Analytics and tracking setup

Phase 2: Expansion (weeks 5-12)

• Content creation for primary pages
• Blog launch with initial posts
• Internal linking structure
• Local SEO setup (if applicable)

Phase 3: Scale (weeks 13-24)

• Advanced content development
• Link building and outreach
• GEO optimization
• Performance optimization

Phase 4: Authority (months 7-12)

• Thought leadership content
• PR and media mentions
• Advanced schema implementation
• Continuous optimization

Imported: Industry Templates

Load from assets/ directory:

• saas.md: SaaS/software companies
• local-service.md: Local service businesses
• ecommerce.md: E-commerce stores
• publisher.md: Content publishers/media
• agency.md: Agencies and consultancies
• generic.md: General business template

Examples

Example 1: Ask for the upstream workflow directly

Use @seo-plan-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @seo-plan-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @seo-plan-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @seo-plan-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/seo-plan, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

• agency.md
• ecommerce.md
• generic.md
• local-service.md
• agency.md
• ecommerce.md

Imported Reference Notes

Imported: Output

Deliverables

• SEO-STRATEGY.md: Complete strategic plan
• COMPETITOR-ANALYSIS.md: Competitive insights
• CONTENT-CALENDAR.md: Content roadmap
• IMPLEMENTATION-ROADMAP.md: Phased action plan
• SITE-STRUCTURE.md: URL hierarchy and architecture

KPI Targets

Success Criteria

• Clear, measurable goals per phase
• Resource requirements defined
• Dependencies identified
• Risk mitigation strategies

Imported: DataForSEO Integration (Optional)

If DataForSEO MCP tools are available, use dataforseo_labs_google_competitors_domain and dataforseo_labs_google_domain_intersection for real competitive intelligence, dataforseo_labs_bulk_traffic_estimation for traffic estimates, kw_data_google_ads_search_volume and dataforseo_labs_bulk_keyword_difficulty for keyword research, and business_data_business_listings_search for local business data.

Imported: Error Handling

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.