Checklist the per-video bar — engine/sim
75.7/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-field-notes-W31-Sat good|bad)⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 5 scenes · 25.0s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | hook | 0–5.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Field note. You rank where your competitor ranks, but they get the clicks. on-screen: Same rank, half the clicks |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Same rank, half the clicks | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·white-knockout | ♪ node_lock | Legacy SEO stopped at the title tag. Now you hand Google FAQ schema so it reads the page in full. on-screen: Feed Google the schema |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Feed Google the schemacurate items, nodes | |||||||
| 3 |  matches intent BuildLog template | diff | 10.0–15.0s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Drop FAQ schema on one page and run it through the Rich Results test. on-screen: Add FAQ schema, test it |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape knotground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Add FAQ schema, test itcurate codeLines, lines | |||||||
| 4 |  first render · fix pending WireframeMock templatedead_airgeneric_scene | proof | 15.0–20.0s | receipts-count | icon·white-knockout | ♪ node_lock | Field Notes |
expected on screen: red ground · a WireframeMock panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id WireframeMockvisual receiptsshape knotground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Field Notescurate statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.0–25.0s | coalescence | icon·white-knockout | ♪ bed_out | Field Notes |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||
Format stack 3 aspects · same scenes[], re-cropped
9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video
Channels 9 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky
Social captions supplemental published copy · per channel (comp_id level)
tiktokField note: you rank where your competitor ranks, but they get the clicks. Legacy SEO stopped at the title tag. Now you hand Google FAQ schema so it reads the page in full. Drop FAQ schema on one page and run the Rich Results test. (AI-assisted)
instagramField Notes
Same rank. Half the clicks.
Legacy SEO stopped at the title tag.
Now:
Add FAQ schema to a page.
Run the Rich Results test.
#seo #schema #structureddata #searchmarketing #fieldnotes
linkedinField note: you rank in the same spot as your competitor, but they get the clicks. Legacy SEO often stopped at the title tag. Now you hand Google FAQ schema so it can read the page in full and show richer results. The move is small and testable: drop FAQ schema on one page, then run it through Google's Rich Results test before you ship it everywhere. Same rank, more reasons to click.
xField note: same rank as your competitor, half the clicks. Legacy SEO stopped at the title tag. Add FAQ schema to one page, then run the Rich Results test. temerarii.xyz
facebookField note: you rank in the same spot as your competitor, but they get the clicks. Legacy SEO stopped at the title tag. Now you hand Google FAQ schema so it reads the page in full. Try it on one page: add FAQ schema, then run Google's Rich Results test to confirm it works.
threadsField note: you rank where your competitor ranks, but they get the clicks. Legacy SEO stopped at the title tag. Now you hand Google FAQ schema so it reads the page in full. Drop FAQ schema on one page and run it through the Rich Results test.
pinterestGet more clicks from the same search ranking using FAQ schema. Legacy SEO stopped at the title tag, but structured data lets Google read your page in full and show richer results. The simple move: add FAQ schema to one page, then validate it with Google's Rich Results test. A practical technical SEO tip.
blueskyField note: same rank as your competitor, half the clicks. Legacy SEO stopped at the title tag. Add FAQ schema to one page, then run the Rich Results test.
youtubeTitle: Same Rank, Half the Clicks? Add FAQ Schema and Test It
You can rank where your competitor ranks and still lose the clicks. Legacy SEO stopped at the title tag. We show how to hand Google FAQ schema so it reads the page in full, then validate it with the Rich Results test. A small, testable move you can ship on one page first.