AI Search / GEO Optimization (February 2026)

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/seo-geo

https://github.com/sickn33/antigravity-awesome-skills

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

metadata.json

ORIGIN.md

AI Search / GEO Optimization (February 2026)

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Key Statistics, Critical Insight: Brand Mentions > Backlinks, GEO Analysis Criteria (Updated), AI Crawler Detection, llms.txt Standard, Main sections.

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 improving visibility in AI Overviews, ChatGPT, Perplexity, or similar AI search systems.
• Use when evaluating llms.txt readiness, AI crawler access, or citation-oriented content structure.
• Use when the user asks about GEO, AI SEO, LLM visibility, or AI citations.
• Use when the request clearly matches the imported source intent: Optimize content for AI Overviews, ChatGPT, Perplexity, and other AI search systems. Use when improving GEO, AI citations, llms.txt readiness, crawler accessibility, and passage-level citability.
• 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

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

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: Key Statistics

Examples

Example 1: Ask for the upstream workflow directly

Use @seo-geo 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-geo 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-geo 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-geo 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-claude/skills/seo-geo

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

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-v2

  - 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.

• @20-andruia-niche-intelligence-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @2d-games

  - 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.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Critical Insight: Brand Mentions > Backlinks

Brand mentions correlate 3x more strongly with AI visibility than backlinks. (Ahrefs December 2025 study of 75,000 brands)

Only 11% of domains are cited by both ChatGPT and Google AI Overviews for the same query, so platform-specific optimization is essential.

Imported: GEO Analysis Criteria (Updated)

1. Citability Score (25%)

Optimal passage length: 134-167 words for AI citation.

Strong signals:

• Clear, quotable sentences with specific facts/statistics
• Self-contained answer blocks (can be extracted without context)
• Direct answer in first 40-60 words of section
• Claims attributed with specific sources
• Definitions following "X is..." or "X refers to..." patterns
• Unique data points not found elsewhere

Weak signals:

• Vague, general statements
• Opinion without evidence
• Buried conclusions
• No specific data points

2. Structural Readability (20%)

92% of AI Overview citations come from top-10 ranking pages, but 47% come from pages ranking below position 5, demonstrating different selection logic.

Strong signals:

• Clean H1->H2->H3 heading hierarchy
• Question-based headings (matches query patterns)
• Short paragraphs (2-4 sentences)
• Tables for comparative data
• Ordered/unordered lists for step-by-step or multi-item content
• FAQ sections with clear Q&A format

Weak signals:

• Wall of text with no structure
• Inconsistent heading hierarchy
• No lists or tables
• Information buried in paragraphs

3. Multi-Modal Content (15%)

Content with multi-modal elements sees 156% higher selection rates.

Check for:

• Text + relevant images
• Video content (embedded or linked)
• Infographics and charts
• Interactive elements (calculators, tools)
• Structured data supporting media

4. Authority & Brand Signals (20%)

Strong signals:

• Author byline with credentials
• Publication date and last-updated date
• Citations to primary sources (studies, official docs, data)
• Organization credentials and affiliations
• Expert quotes with attribution
• Entity presence in Wikipedia, Wikidata
• Mentions on Reddit, YouTube, LinkedIn

Weak signals:

• Anonymous authorship
• No dates
• No sources cited
• No brand presence across platforms

5. Technical Accessibility (20%)

AI crawlers do NOT execute JavaScript. Server-side rendering is critical.

Check for:

• Server-side rendering (SSR) vs client-only content
• AI crawler access in robots.txt
• llms.txt file presence and configuration
• RSL 1.0 licensing terms

Imported: AI Crawler Detection

Check

robots.txt

Recommendation: Allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot for AI search visibility. Block CCBot and training crawlers if desired.

Imported: llms.txt Standard

The emerging llms.txt standard provides AI crawlers with structured content guidance.

Location:

/llms.txt

Format:

# Title of site
> Brief description

#### Imported: Main sections

- `Page title -> https://example.com/page`: Description
- `Another page -> https://example.com/another-page`: Description

#### Imported: Optional: Key facts

- Fact 1
- Fact 2

Check for:

• Presence of

  /llms.txt

• Structured content guidance
• Key page highlights
• Contact/authority information

Imported: RSL 1.0 (Really Simple Licensing)

New standard (December 2025) for machine-readable AI licensing terms.

Backed by: Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons

Check for: RSL implementation and appropriate licensing terms.

Imported: Platform-Specific Optimization

Imported: Output

Generate

GEO-ANALYSIS.md

1. GEO Readiness Score: XX/100
2. Platform breakdown (Google AIO, ChatGPT, Perplexity scores)
3. AI Crawler Access Status (which crawlers allowed/blocked)
4. llms.txt Status (present, missing, recommendations)
5. Brand Mention Analysis (presence on Wikipedia, Reddit, YouTube, LinkedIn)
6. Passage-Level Citability (optimal 134-167 word blocks identified)
7. Server-Side Rendering Check (JavaScript dependency analysis)
8. Top 5 Highest-Impact Changes
9. Schema Recommendations (for AI discoverability)
10. Content Reformatting Suggestions (specific passages to rewrite)

Imported: Quick Wins

1. Add "What is [topic]?" definition in first 60 words
2. Create 134-167 word self-contained answer blocks
3. Add question-based H2/H3 headings
4. Include specific statistics with sources
5. Add publication/update dates
6. Implement Person schema for authors
7. Allow key AI crawlers in robots.txt

Imported: Medium Effort

1. Create

   /llms.txt

   file
2. Add author bio with credentials + Wikipedia/LinkedIn links
3. Ensure server-side rendering for key content
4. Build entity presence on Reddit, YouTube
5. Add comparison tables with data
6. Implement FAQ sections (structured, not schema for commercial sites)

Imported: High Impact

1. Create original research/surveys (unique citability)
2. Build Wikipedia presence for brand/key people
3. Establish YouTube channel with content mentions
4. Implement comprehensive entity linking (sameAs across platforms)
5. Develop unique tools or calculators

Imported: DataForSEO Integration (Optional)

If DataForSEO MCP tools are available, use

ai_optimization_chat_gpt_scraper

ai_opt_llm_ment_search

ai_opt_llm_ment_top_domains

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.