feat(aeo): carry production claims in the canonical identity and pricing snippets - #113
Merged
Merged
Conversation
…ing snippets Answer engines build vendor profiles from claims corroborated across retrieved snippets. Every Steel identity surface previously said only "open-source browser API", so LLM answers slot Steel as open-source-only and credit production readiness elsewhere. Align the four identity surfaces (JSON-LD site description, OG fallback, docs homepage, llms.txt preamble) on one sentence that keeps open-source and adds the production attributes: stealth, residential proxies, CAPTCHA solving, persistent profiles, session replays, agent observability. Rewrite the pricing page description as one quotable claim with current plan rates, replacing the table-soup snippet retrieval engines were extracting from it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A live ChatGPT answer to "best cloud browser for ai agent" (112 retrieved sources analyzed) showed how answer engines pick recommendations: they build a per-vendor attribute profile from claims corroborated across retrieved snippets, then assign each vendor one slot. Browserbase won "best overall" with 15 docs pages all repeating "proxies, CAPTCHA solving, observability." Steel won only "open source / self-hostable" — because every Steel snippet leads with "open-source browser API" and claims nothing else.
Steel has every feature on the answer's "best overall" checklist, but no retrieved snippet said them together.
What
Canonical identity sentence — one sentence, applied to all four identity surfaces, keeping the open-source moat and adding the production attributes (stealth, residential proxies, CAPTCHA solving, persistent profiles, session replays, agent observability):
lib/structured-data.ts—DOCS_SITE_DESCRIPTION(JSON-LDWebSite)app/og/[...slug]/route.tsx— OG description fallback (shorter variant; renders inside an image)app/(home)/_pages/page.en.tsx— homepage proselib/agent-instructions.ts— llms.txt / AGENTS.md preamble (regenerated output verified)Pricing snippet —
content/docs/overview/pricinglimits.mdxdescription becomes one quotable claim with current rates ("start free with $30 in usage credits (about 300 browser hours), browser hours from $0.08/hour…"). The previous snippet retrieval engines extracted was flattened table cells: "Browser hours $0.10/hour $0.08/hour Custom $10/".Also updates the e2e assertion in
tests/e2e/llm-endpoints.test.tsthat pins the homepage sentence.Verification
bun run lint,bun run typecheck,bun run spell— cleanbun test tests/— 316 pass, 0 failbun run build— clean; regeneratedllms.txtpreamble carries the new sentence🤖 Generated with Claude Code