sanity-io/agent-toolkit

seo-aeo-best-practices

SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces.

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

SEO & AEO Best Practices

Principles for optimizing content for both traditional search engines (SEO) and AI-powered answer engines (AEO). Includes Google's EEAT guidelines and structured data implementation.

When to Apply

Reference these guidelines when:

  • Implementing metadata and Open Graph tags
  • Creating sitemaps and robots.txt
  • Adding JSON-LD structured data
  • Optimizing content for featured snippets
  • Preparing content for AI assistants (ChatGPT, Perplexity, etc.)
  • Evaluating content quality using EEAT principles

Core Concepts

SEO (Search Engine Optimization)

Optimizing content to rank well in traditional search results (Google, Bing).

AEO (Answer Engine Optimization)

Optimizing content to be selected as authoritative answers by AI systems.

EEAT (Experience, Expertise, Authoritativeness, Trustworthiness)

Google's framework for evaluating content quality.

References

Start with the one reference that matches the task, such as technical SEO, structured data, EEAT, or AI-answer readiness. See references/ for detailed guidance:

  • references/eeat-principles.md — EEAT implementation and author schema
  • references/structured-data.md — JSON-LD patterns (Article, FAQ, Breadcrumb, Product)
  • references/technical-seo.md — Technical SEO checklist (metadata, sitemaps, hreflang, robots.txt)
  • references/aeo-considerations.md — AI/AEO considerations (AI Overviews, crawler management)
from this repository

More skills

All skills
sanity-io
Official

sanity-best-practices

Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, event-driven content automation, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.

installs
7
GitHub stars
182
Updated
Sep 4
sanity-io
Official

sanity-migration

Plans, implements, and reviews migrations from other CMSes and content systems into Sanity. Use when migrating or replatforming to Sanity from AEM, Adobe Experience Manager, Contentful, Strapi, Webflow, WordPress, Payload, Drupal, Markdown/MDX/frontmatter files, WXR/XML exports, CMS APIs, database dumps, static HTML, or when designing extraction, transformation, Portable Text conversion, asset migration, redirects, validation, and cutover workflows.

installs
6
GitHub stars
182
Updated
Sep 4
sanity-io
Official

content-experimentation-best-practices

Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.

installs
3
GitHub stars
182
Updated
Sep 4
sanity-io
Official

content-modeling-best-practices

Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.

installs
3
GitHub stars
182
Updated
Sep 4