SEO Fundamentals V3

SEO Fundamentals

Overview

This public intake copy packages plugins/antigravity-bundle-seo-specialist/skills/seo-fundamentals 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.

SEO Fundamentals > Foundational principles for sustainable search visibility. > This skill explains how search engines evaluate quality, not tactical shortcuts. ---

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 1. E-E-A-T (Quality Evaluation Framework), 2. Core Web Vitals (Page Experience Signals), 5. Structured Data (Schema), 7. Relative Importance of SEO Factors, 8. Measurement & Evaluation, 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.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.
• 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.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

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. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: 1. E-E-A-T (Quality Evaluation Framework)

E-E-A-T is not a direct ranking factor. It is a framework used by search engines to evaluate content quality, especially for sensitive or high-impact topics.

Pages competing in the same space are often differentiated by trust and experience, not keywords.

Examples

Example 1: Ask for the upstream workflow directly

Use @seo-fundamentals-v3 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-fundamentals-v3 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-fundamentals-v3 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-fundamentals-v3 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.

• Element - Purpose
• XML sitemaps - Help discovery
• robots.txt - Control crawl access
• Canonical tags - Consolidate duplicates
• HTTP status codes - Communicate page state
• HTTPS - Security and trust
• Factor - Why It Matters

Imported Operating Notes

Imported: 3. Technical SEO Principles

Technical SEO ensures pages are accessible, understandable, and stable.

Crawl & Index Control

Performance & Accessibility

Imported: 4. Content SEO Principles

Page-Level Elements

Content Quality Signals

Imported: 6. AI-Assisted Content Principles

Search engines evaluate output quality, not authorship method.

Effective Use

• AI as a drafting or research assistant
• Human review for accuracy and clarity
• Original insights and synthesis
• Clear accountability

Risky Use

• Publishing unedited AI output
• Factual errors or hallucinations
• Thin or duplicated content
• Keyword-driven text with no value

Troubleshooting

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

Symptoms: The result ignores the upstream workflow in plugins/antigravity-bundle-seo-specialist/skills/seo-fundamentals, 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

• @competitive-landscape-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @competitor-alternatives-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @copywriting-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @cpp-pro-v3 - 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.

• seo_checker.py
• seo_checker.py

Imported Reference Notes

Imported: 2. Core Web Vitals (Page Experience Signals)

Core Web Vitals measure how users experience a page, not whether it deserves to rank.

Important context:

• CWV rarely override poor content
• They matter most when content quality is comparable
• Failing CWV can hold back otherwise good pages

Imported: 5. Structured Data (Schema)

Structured data helps search engines understand meaning, not boost rankings directly.

Schema enables eligibility for rich results but does not guarantee them.

Imported: 7. Relative Importance of SEO Factors

There is no fixed ranking factor order. However, when competing pages are similar, importance tends to follow this pattern:

Technical SEO enables ranking; content quality earns it.

Imported: 8. Measurement & Evaluation

SEO fundamentals should be validated using multiple signals, not single metrics.

Key Principle: Sustainable SEO is built on useful content, technical clarity, and trust over time. There are no permanent shortcuts.

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.