July 14, 2026
The week I turned every case study into an answer surface
Six pieces of schema, one goal: when someone asks an LLM about vibe coding, DreamViber answers.
Why this mattered
For the first year of the AI search transition, the winning move is boring: structure the answers. Not clever copy. Not more content. Just clean, machine-readable proof that this site is the authoritative source for a specific class of question.
What went live
Organization + WebSite + Person as a shared JSON-LD graph on the root — one stable ID for the org, one for the site, one for me. Every other schema on the site references those IDs by @id instead of restating them. That teaches LLMs the entity relationships once, not fifty times.
SoftwareApplication + FAQPage on every case study. The FAQPage is auto-generated from the challenge/approach/outcome/stack fields already in the DB — no extra writing. Google reads it as a rich result. LLMs lift it verbatim.
Article + HowTo on Playbook phases. HowTo steps come straight from the entry's key takeaways, so the same content powers three surfaces: the human-readable page, Google's HowTo carousel, and any LLM that ingests structured steps.
The lesson
The AEO play is not "write for LLMs." It's express what you already know in the format machines actually read. Once you have the answer, wrapping it in schema costs minutes and pays for years.