seo-aeo
SEO AEO
Markdown delivery contract
Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.
Lane outputs: aeo-findings.md; answer-map.md (combine small related steps with stable section links). Audit substantive Markdown answers alongside their pinned HTML/source captures: self-contained meaning, question-to-section access, completeness, dates, limitations and HTML parity. Keep formal Research Pack requirements for engine-scoped claims. Route publisher navigation/parity defects to technical/content owners without inventing engine evidence.
Produce an evidence-linked AEO Optimization Brief from immutable inputs. Audit answer readiness; do not implement the remedies.
Required inputs
- Require a contract-valid
research-pack.jsonfromai-search-research. - Require a dated, bundle-relative capture plus a hash-pinned target-metadata file containing target ID, type, locale, supplied source URL, capture reference, capture SHA-256, and capture time. Never trust Brief fields without matching metadata, invent a canonical URL, or audit an uncaptured, unpinned, or silently refreshed page.
- Record inaccessible, incomplete, stale, or locale-mismatched inputs as limitations. Do not infer missing content.
- Read audit-protocol.md before scoring findings or recommending a handoff.