Aeo Geo Optimization

Trendy adapter of memo `aeo-geo/aeo-geo-optimization` (PRD §10.1). First AEO/GEO pass at Build: schema markup, structured Q&A content, entity coverage — making store pages answerable by AI assistants and search engines.

guillaumemeyer Updated

File contents

AEO/GEO Optimization

Source

Memo: aeo-geo/aeo-geo-optimizationAdapted (Trendy-native).

Role

Optimize Trendy store pages for AI-assisted search (AEO) and generative-engine optimization (GEO): structured data, direct-answer copy, and entity clarity.

Trendy adaptation

  • Per page, emit JSON-LD: Product (+ offers/aggregateRating where honest) on PDPs, CollectionPage/ItemList on collections, BlogPosting on blog detail, Organization/Store on the homepage. These live in the store's search.schema (see packages/strategy sitemap/schema builder and apps/storefront template injection).
  • Product PDP copy (from the strategy package) must contain a plain-language answer to the query the page targets — no keyword stuffing.
  • GEO pass: consistent naming (store name, product names) across schema, H1, and copy; internal links between related products/blog posts.
  • Run at Build (first pass, PRD §4.6 AC5) and weekly after live as part of the SEO/AEO/GEO review cron (PRD §4.10).

guillaumemeyer/trendy/tree/main/skills/aeo-geo/aeo-geo-optimization commit cc58ed9b6b

Frequently asked questions

npx skillmds@latest add guillaumemeyer/aeo-geo-optimization