Judge one owned Page post after one hour before repeating, replying broadly, or changing the angle.
POST WINDOW1 hour
One post, one URL, one first-hour read. If there is no useful signal, rewrite or pause instead of spraying the same link again.
Each post should carry one exact Ledger route so link clicks and reader questions have a clean source.
Reply only to specific source, date, route, or caveat questions under the owned post.
No boost or paid rescue until the paid-launch proof gates are cleared and the post shows organic signal.
CHECKPOINTS
Before publish through next dayWhat to capture after a manual post
| Time | Where to look | Evidence | Decision |
|---|---|---|---|
| Before publish | Composer preview | Page identity, correct link card, disclosure line, no boost selected | Publish only if the route and preview are correct. |
| 15 minutes | Post visible | Live URL saved, reach visible or not available, first comments noted | Reply only to real source questions. |
| 30 minutes | Comment scan | Questions to answer, corrections needed, hostile or low-signal replies separated | Use one answer link or pause. |
| 60 minutes | First-hour log | Reach, link clicks, saves/shares if visible, replies, route used | Repeat only if clicks or useful replies exist. |
| Next day | Traffic check | Page views, referrer, returning visits, route performance | Keep winners; rewrite or retire flat copy. |
REPLY PROMPTS
Three maxAnswer only useful questions under the owned post
DECISION RULES
Repeat only with proofDo not rescue a flat post with noise
- A live Page post is the minimum evidence. A copied draft, preview, or planned post is not reach.
- Reply to source questions under the owned post; do not use this desk to join groups, message people, or target political audiences.
- Do not boost a post just because it is flat. Boosting remains blocked until account, billing, authorization, preview, and attribution receipts are captured.
- Repeat an angle only when it earns measured clicks, useful replies, saves/shares, accepted referrals, or returning visits.
- If a post draws corrections, fix the route or wording before posting again.
LOG LINE
Keep the signal attached to the exact post.
Paste this after the post exists. Leave any unavailable insight blank instead of estimating. Use the next-day Traffic Pulse check, then move the result into Signal Review before making bigger changes.
Copy first-hour log
Facebook Page post | live URL | Ledger route | published time | 15-min notes | 30-min replies | 60-min reach | link clicks | saves/shares | next-day visits | repeat/rewrite/pause
Where are the files?
Use under the owned Page post when a reader asks for official release routes.
Proof after replying: Comment URL or visible reply count, then later check whether the answer page received visits.
What should I look at first?
Use when a reader asks for the main takeaways before opening the source map.
Proof after replying: Comment URL or visible reply count, then check clicks before repeating the angle.
Does a name prove anything?
Use when a reply treats a name mention or screenshot as proof by itself.
Proof after replying: Visible correction reply or reduced repeat confusion; do not count it as traffic unless clicks appear.
How can people follow?
Use only after the thread has been useful and a reader asks for updates or future checks.
Proof after replying: Visible reply plus later returning visits or feed/referral evidence if available.