Technical SEO, Schema.org JSON-LD & AI Answer Engine (AEO) Skill

Audit and implement programmatic SEO & AI Answer Engine Optimization (AEO): canonical tags, XML sitemaps, `llms.txt` / `llms-full.txt`, `SoftwareApplicatio

---
name: technical-seo-aeo-audit
description: Audit and implement programmatic SEO & AI Answer Engine Optimization (AEO): canonical tags, XML sitemaps, `llms.txt` / `llms-full.txt`, `SoftwareApplication` & `FAQPage` JSON-LD. Use when working with Technical SEO, AEO / llms.txt, JSON-LD Schema, Sitemap XML.
triggers:
  - technical seo aeo audit
  - technical seo
  - aeo / llms.txt
---

# Technical SEO, Schema.org JSON-LD & AI Answer Engine (AEO) Skill

## 1. When to Use This Skill
Load `skill-technical-seo-aeo-audit` whenever an engineering or operations task involves **Technical SEO, AEO / llms.txt, JSON-LD Schema, Sitemap XML**. Specifically:
- Audit and implement programmatic SEO & AI Answer Engine Optimization (AEO): canonical tags, XML sitemaps, `llms.txt` / `llms-full.txt`, `SoftwareApplication` & `FAQPage` JSON-LD.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Technical SEO, AEO / llms.txt, JSON-LD Schema, Sitemap XML
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://schema.org/docs/schemas.html`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Technical SEO**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
curl -sI https://example.com/llms.txt
curl -sI https://example.com/sitemap.xml
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide