Skip to content

AEO content remainder: the 'GloriaFood alternatives (Switzerland)' listicle + per-market guides (SOFRA-AEO-PLAN §2) #242

Description

@mahmutkaya

What

The agent-writable remainder of SOFRA-AEO-PLAN §2 (content engine). §1 quick wins, the RUMI case study (/case/rumi), the Sofra-vs-GloriaFood compare page (/compare/gloriafood, #42, closed #6) and /changelog are shipped. Still to write:

  1. «GloriaFood alternatives (Switzerland)» — the listicle/comparison page. Table-driven like the shipped compare page: facts a machine can lift, Q&A subheadings, a visible "Last checked ", and a sources list. The pattern to copy is components/compare-gloriafood-data.ts + app/[locale]/compare/gloriafood/page.tsx — GloriaFood's pricing there was verified from gloriafood.com/pricing on the day, with source URLs and a re-verify note shipped alongside.
  2. Per-market guides — one genuinely useful guide per market, not keyword mush: «QR-Menü für Restaurants in der Schweiz» (de), «menu QR pour restaurants à Genève» (fr). The plan's own bar: "genuinely useful content, not keyword mush; the craft brand voice is a differentiator". fr copy quality matters most (Geneva is the first market).

The working model these pages serve (from the plan)

  • Retrieval: be indexed everywhere (Bing's index feeds ChatGPT search; sitemap + llms.txt exist).
  • Extraction: engines prefer machine-liftable facts — structured data, Q&A blocks, tables, transparent pricing.
  • Trust: dated, sourced claims beat self-description. Any competitor claim needs a verified source + a checked date, exactly as feat(aeo): content engine — changelog, RUMI case study, GloriaFood comparison #42 did.

Constraints

  • All six locales (en/fr/de/nl/tr/ar), JSON-LD generated from the same message keys as the visible copy (the FAQ/compare pattern).
  • ⚠ Anything marked in the plan before publishing: re-verify competitor pricing at write time; never carry an unverified number.
  • This is the AGENT-writable half only. The owner-owed halves of §2/§3 (case-study numbers, Bing/GSC/G2/Wikidata checklist) are separate backlog rows — do not fold them in here.

Acceptance criteria

  • The listicle is live under /compare/ (or the plan's chosen path) in all six locales with JSON-LD and a claims table with sources + checked dates.
  • At least the fr and de market guides exist, in the craft voice, with verifiable local facts.
  • Every new page is in the sitemap and linked from the site's internal links (footer/nav or existing pages).
  • SOFRA-AEO-PLAN §2 rows updated in the same change.

Ref: workspace docs/plans/BACKLOG.md, Track S queue row "AEO content remainder"; docs/plans/SOFRA-AEO-PLAN.md §2.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions