[5/5] seo: add FAQ structured data to the simulator camera doc - #1108
Merged
Conversation
ralph-cmyk
changed the title
AvdLee
marked this pull request as ready for review
July 27, 2026 12:34
Rebased onto master (now includes the AvdLee#1109 retitle) and onto the hardened test harness from AvdLee#1110. The FAQ block and its test are unchanged in substance from the original branch.
AvdLee
force-pushed
the
seo/camera-doc-faq-schema
branch
from
July 27, 2026 12:37
c8ccb56 to
9e863e6
Compare
Owner
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
2 participants
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.
Merge order 5 of 5 — shows #1105's commits until that merges — the diff on top is the camera doc FAQ block plus its test. I will rebase after each merge.
Problem. The docs system already emits FAQ structured data, but exactly 1
of 55 pages uses it. The highest-traffic non-brand page has none.
Why it matters. FAQ structured data is what makes a page eligible for
expanded search results and gives AI assistants a clean question-and-answer
block to cite. The report's core finding was that RocketSim loses the category
conversation in AI answers; this is the cheapest way to feed those answers.
What changed. A
faq:block added to the camera doc's frontmatter. No codechanges — the rendering path already exists and is verified working.
KPI — starting point. Camera doc: 637 clicks, 18,427 impressions, 3.46%
CTR, position 5.20 — the top non-brand page. Zero FAQ structured data on it
today. Site-wide: 1 of 55 docs has FAQ data. (Search Console 90 days to
24 Jul 2026; verified in production HTML 25 Jul 2026.)
KPI — expectation. FAQ rich result eligibility within 2–4 weeks of
reindexing; CTR from 3.46% toward 5%. Secondary: the page becomes citable for
"can the iOS Simulator use my camera" style questions.
How to measure it. Google Rich Results Test on the live URL to confirm
eligibility, then Search Console → Pages → camera doc, 28 days before vs after,
comparing CTR. Search Console's Enhancements report will also list FAQ items
once detected.
Risk / rollback. Answers must match what the page body actually says, or
the structured data is misleading. Verified by the JSON validity check in the
task. Revert the single commit to remove.