My first build with 5.6 sol
What happened when I used 5.6 sol to audit AppHeat, coordinate parallel fixes, dogfood the result, and build a deterministic audit framework.
Answer engine optimization
Use this path for notes on making technical pages easier to read, summarize, crawl, quote, and cite: visible answers, topic hubs, schema, search, AI crawler access, and checks against the built site.
What this path is for
-
Put the real answer on the page instead of hiding it in markup.
-
Build topic hubs that give recurring ideas a clear home.
-
Make important answers visible to readers before mirroring them in schema.
-
Check generated pages, feeds, crawler files, and search text after the build.
Writing in this topic
-
-
Steps to Make Accept: text/markdown Work Everywhere
I thought I had built Accept-header Markdown for AppHeat. Production had other plans, because Cloudflare was skipping the Worker entirely.
-
I Built an AEO Agent Workflow. Google Made Me a Skeptic.
A field note from setting up a local Pi workflow with OpenRouter agents to research AEO topical authority. The real surprise was not any agent tactic — it was what Google's own guidance actually says.
-
AEO from the jump: build pages people can quote
A practical note on making pages easy to read, cite, and hard to misquote.