Copy the published post text
Receipts
copy ready · render pending
Output-policy spec format · dimensions (asset_specs.output_policy)
formatnative cut · 9:16 · 1:1 · 16:9
dims1080×1920 · 1080×1080 · 1920×1080
cadence5/day floor × 9 channels
Channels 9 destinations
TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube
This post a distinct social asset — its own angle, storyboard, and cuts
thread-receipts-W24-Fri
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel
Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)
| Channel | Native caption |
|---|---|
| Tiktok | Receipts: 19 days from a brand-new domain to ranking page one for a real keyword. We used to guess at keywords. Now we map real search intent first, mark up the page with schema, then write. That is the order that moved it. (AI-assisted) |
| Receipts. 0 to ranked. 19 days. Brand-new domain. Page one. Real keyword. How: Map real search intent first. Mark up the page with schema. Then write. We used to guess at keywords. This is the order that worked. #seo #contentmarketing #buildinpublic #schema #ranking | |
| Receipts: nineteen days from a brand-new domain to ranking page one for a real keyword. We used to guess at keywords and write first. That is backwards. The order that actually moved it: map real search intent first, mark up the page with schema, then write to the intent you found. Future-you does not write blind. The sequence is the whole trick, not the word count. | |
| X | Receipts: 19 days from a brand-new domain to page one for a real keyword. We used to guess at keywords. The fix: map intent first, add schema, then write. Order matters. temerarii.com |
| Receipts: nineteen days from a brand-new domain to ranking page one for a real keyword. We used to guess at keywords and write first. The order that actually worked: map real search intent first, mark up the page with schema, then write. Try mapping intent before your next post. | |
| Threads | Receipts: 19 days from a brand-new domain to page one for a real keyword. That is the number. We used to guess at keywords. Future-you does not write blind. Map real search intent first, mark up the page with schema, then write. The order is the trick. |
| How a brand-new domain ranked page one in 19 days. SEO receipts: stop guessing at keywords. Map real search intent first, mark up the page with schema, then write to that intent. The sequence is what moves a new site, not word count. A practical SEO method you can copy. | |
| Bluesky | Receipts: 19 days from a brand-new domain to page one for a real keyword. We used to guess at keywords. The fix: map intent first, add schema, then write. Order matters. |
| Youtube | Title: 0 to Ranked in 19 Days: The SEO Order That Actually Worked Nineteen days from a brand-new domain to ranking page one for a real keyword. That is the receipt. We used to guess at keywords and write first, which is backwards. The order that moved it: map real search intent first, mark up the page with schema, then write to the intent you found. The sequence is the trick, not the word count. |
Composition layer × scene 5 scenes · this post's OWN storyboard (distinct per asset)
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | matches intent StatScoreboard template | stat | 0–5.8s | receipts-count | icon·wireframe | ♪ node_lock | Nineteen days from a brand-new domain to ranking page one for a real keyword. That's the number. on-screen: 0 to ranked. 19 days. |
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape torusground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→0 to ranked. 19 days.curate pillar, stats, statsLabels | |||||||
| 2 |  first render · fix pending ComparisonTable templatedead_air | proof | 5.8–10.8s | receipts-count | icon·wireframe | ♪ node_lock | We used to guess at keywords and write first. Now we map what people actually search, then add schema markup so the page tells search engines what it answers. on-screen: Schema + intent map. |
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape torusground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Schema + intent map.curate colA, colB, rows, statsLabels | |||||||
| 3 |  matches intent LogStream template | diff | 10.8–16.8s | crossfade-8f | icon·wireframe | ♪ node_lock | Future-you doesn't write blind. Map real search intent first, mark up the page, then write. on-screen: Map intent. Then write. |
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Nuntius leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual codeshape torusground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Map intent. Then write.curate codeLines, rows | |||||||
| 4 |  matches intent ProcessFlow template | step | 16.8–23.1s | kinetic-build | icon·wireframe | ♪ node_lock | The order matters. Search data first, schema second, writing last. Flip it and you wait months. on-screen: Data, schema, then words |
expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Nuntius leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual pipelineshape torusground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Data, schema, then wordscurate stages, steps | |||||||
| 5 |  matches intent shared field signature-3d | resolve | 23.1–28.6s | coalescence | icon·wireframe | ♪ bed_out | Nineteen days, one keyword, zero guesswork. Receipts over rhetoric. The Big T-M, signing off. on-screen: Receipts over rhetoric |
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Receipts over rhetoric | |||||||