oegeyilmaz9/seo-aeo-geo-ultimate / skills/seo-technical
seo-technical
VerifiedUse when investigating crawlability, indexability, canonicalization, rendering, performance, redirects, directives, sitemaps, crawler controls, site migrations, sudden traffic/index incidents, manual actions, hacked-site recovery, or when evaluating, generating, validating, publishing, and maintaining an evidence-scoped llms.txt publisher guide; return safe, testable implementation recommendations rather than a generic technical score.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.5 KB |
| agents/openai.yaml | config | 454 B |
| assets/llms.txt.template | other | 623 B |
| references/contracts/contracts-lock.json | config | 1.5 KB |
| references/contracts/evidence-record.schema.json | config | 1.7 KB |
| references/contracts/platform-controls.schema.json | config | 6.6 KB |
| references/contracts/seo-findings.schema.json | config | 5.2 KB |
| references/external-claim-adjudication.md | markdown | 1.3 KB |
| references/favicon-search-protocol.md | markdown | 1.8 KB |
| references/live-verification-matrix.md | markdown | 1.8 KB |
| references/llms-txt-protocol.md | markdown | 4.2 KB |
| references/markdown-delivery-contract.md | markdown | 4.3 KB |
| references/migration-and-recovery-protocol.md | markdown | 6.2 KB |
| references/platform-control-protocol.md | markdown | 2.8 KB |
| references/technical-evidence-protocol.md | markdown | 1.2 KB |
references/markdown-delivery-contract.md
View on GitHub# Markdown delivery: seo-technical
Every material work step has a substantive Markdown document and a direct link in private `index.md`. Include outcome/status, scope, evidence dates/links, facts vs inferences, decisions, limitations, owner and next destination. Drafts remain draft/provisional until their owning semantic validator passes. Use the suite artifact renderer for validated formal bundles; do not replace immutable JSON, CSV, raw captures or schema.
Lane documents: `technical-findings.md; markdown-delivery.md; live-verification.md`.
Own robots.txt and llms.txt delivery, MIME/UTF-8, explicit Markdown routing, access, redirects, cache invalidation and a documented HTTP canonical/indexing policy. Verify the full declared resource set after authorized release; no SPA HTML fallback may pass.
## Public knowledge profile
For authorized public-site implementation, require lowercase `/llms.txt`, `/sitemap.md`, topic maps and substantive `.md` equivalents for every eligible canonical page in the declared scope. These are owner-defined delivery requirements, not universal SEO/AEO/GEO platform requirements. robots.txt, XML sitemaps, feeds, schema and protocol files keep their native formats. One-page or answer-only work stays bounded and records its work note without changing the whole site.
Use reviewed content from the same revision as HTML. Preserve facts, citations, dates, units, locale, media meaning and public access policy. Private reports, analytics, credentials, admin URLs, personalized content and paywalled material never become public mirrors. Every excluded/unknown inventory URL has a private disposition; unknown eligibility or a partial inventory prevents a whole-site-complete claim.
Direct destinations must actually resolve; planned URLs are labelled planned. Verify links, map coverage, source hashes, public output hashes, editorial parity, UTF-8 MIME delivery, cache/deletion refresh, maintenance owner and the chosen canonical/indexing policy. Public Markdown is a content representation, not a crawler permission, schema replacement or evidence that an engine retrieves/cites it.
Native entry points also carry concise navigation hints: robots `#` comments, XML sitemap/index comments, and two reader-facing sentences in llms.txt direct an interested LLM to the actual Markdown map and answer. Preserve all existing crawl rules and native sitemap elements; comments are discovery hints with no guaranteed consumer. The technical/sitemap owners verify protocol invariance, real destinations and delivered comment retention. Read the full contract's “Native entry-point navigation hints” section before editing those sources.
## Shared tools and full contract
Resolve `<suite-root>` from `.seo-suite-runtime.json` beside SKILL.md in Codex, `${CLAUDE_PLUGIN_ROOT}` in Claude Code, or the absolute suite checkout. Read `<suite-root>/docs/MARKDOWN-DISCOVERY.md` before corpus generation/publication. It owns the detailed inventory, routing, native-format exceptions, privacy, acceptance and source-review rules; do not improvise a conflicting contract.
- Public export: `python "<suite-root>/scripts/manage_markdown_site.py" build --inventory <private/inventory.json> --output <new-public-candidate>`.
- Local projection: `python "<suite-root>/scripts/manage_markdown_site.py" validate --manifest <private-manifest.json> --root <public-candidate>`.
- Full live delivery after authorized publication: same tool, `live --manifest ... --root ... --report <private/live-verification.md>`. A failed/rate-limited run is incomplete, never retried in a loop.
- Work index: `python "<suite-root>/scripts/manage_markdown_work.py" --root <private-work> init --title "Work title"`; use `add --id <step-id> --path <step.md> --title "Step title" --status <draft|provisional|completed|blocked|not-applicable> --owner "Owner" --outcome "Actual result"`, then `check --final` before complete closeout. Equivalent maintained tooling is acceptable when these invariants are verified.
The deterministic export verifies parity with supplied reviewed Markdown, not editorial truth or live HTML. Formal AEO/GEO claims still require the pinned Research Pack. Owner-required source navigation/parity work can proceed locally without inventing engine observations. Preserve separate local acceptance, live delivery and provider outcome states.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |