---
name: boost-top-3-5-facebook-posts
description: "Pick the best posts for a small paid test. Keep the cost and the next check clear."
category: Content Factory — Promote
stage: Promote
definitive_article: /social-amplification
status: complete
---

# Boost top 3–5 Facebook posts

Some of your posts helped people more than others. This guide helps you choose a few to test with a small ad budget. Start with the real posts and their recent results.

**The path:** Recent results → qualified short list → small tests → checked verdicts.

**Use this when:** The Post stage has produced usable organic work and the owner wants a bounded Facebook amplification batch.

## Inputs
- The actual Page’s recent organic post log, ideally the last 30 days, with URLs, format and metrics.
- Ad account roles, original-post eligibility, media/claim rights, and a goal with its target.
- Eligible relevant audiences, currency, minimums, total budget, dates and scope for any launches or stops.

## First-run prompt

> Rank these Facebook posts against the Page’s comparable baseline. Pick up to three to five that fit the goal and have usable rights. Price each actual supported test and carry out only authorized actions. Return post/ad IDs, dates, cost and due review; do not fill the list with weak posts.

## Steps
1. Read the available 30-day organic log and disclose any shorter or missing history. Separate paid amplification from organic response. Compare like formats instead of ranking every post by raw reach.
2. Read shares, real questions, substantive comments and meaningful video metrics. Keep the goal in view: a funny post can be popular without helping the intended buyer.
3. Shortlist up to three to five posts with evidence and rights. Use fewer if fewer qualify. Preserve proof and relationship limits; a famous face or co-appearance alone does not support a client endorsement.
4. Choose relevant warm audiences first when they are eligible and fit the goal, as the source method recommends. A warm label does not prove enough people exist or make a mismatched audience right for the post.
5. Verify the original post in the supported preview, including captions, crops and destination. Use current platform options and record any limitation rather than guaranteeing every post can be boosted.
6. Plan the nominal $1/day for seven days where supported. Price all rows and check true budget limits. A staged one-per-day sequence and a parallel batch have different overlapping commitments and due dates.
7. Launch only within the supplied scope, read back settings and monitor early delivery/ceiling errors. Preserve a stable full-window comparison while allowing protective actions already authorized.
8. At each due date, stop rows that fail the agreed rule and identify qualified winners. About 90% retirement is a portfolio expectation, not a forced quota. A winner can be considered for $30 total over 30 days or a separately bounded increase; neither happens automatically.

## Definition of done (QA checklist)

- [ ] The selected posts have comparable organic evidence and fit the goal.
- [ ] Up to three to five qualify without forced filler or invented proof.
- [ ] Original-post eligibility, media and audience conditions are checked.
- [ ] Combined budgets and individual end/review dates fit actual scope.
- [ ] Saved state, delivery and final verdicts are recorded separately.

## Example(s)

**Fictional teaching example:** A shop has four recent helpful repair posts, but only two beat their comparable baseline and have clear music rights. The operator chooses those two, not a weak third to meet a quota. Their nominal seven-day plan is $14 total in an eligible setup, with actual platform limits checked. One test misses its goal and is paused under the agreed rule; the other is a candidate for a new dated continuation. The report does not call the second a proven sales winner from views alone.

## Handoff and Content Factory context

Give the batch report to [run dollar a day campaign on winning content](https://local-service-spotlight.github.io/task-library/?task=run-dollar-a-day-campaign-on-winning-content#task-run-dollar-a-day-campaign-on-winning-content) for any next campaign plan, and to [analyze cost per result and engagement](https://local-service-spotlight.github.io/task-library/?task=analyze-cost-per-result-and-engagement#task-analyze-cost-per-result-and-engagement) for matched scoring. Do not launch the same post twice because both task names apply.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run after a useful body of organic posts exists. A repeated boost batch needs an agreed budget and review cadence; downloading this task creates no ongoing spend.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** `run-dollar-a-day-campaign-on-winning-content`
- **Suggested next station:** `boost-one-minute-videos-for-personal-branding`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Organic metrics CSV (or Ads Manager export), pixel ID, creative filenames, kill/scale log. Next week's ranking starts from this file.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/social-amplification
- Exact task: [Boost top 3–5 Facebook posts](https://local-service-spotlight.github.io/task-library/?task=boost-top-3-5-facebook-posts#task-boost-top-3-5-facebook-posts)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)
- [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/)
- [Social Amplification Engine](https://blitzmetrics.com/social-amplification/)
- [Meta budget help](https://www.facebook.com/business/help/190490051321426)
- [Meta Advantage+ audience help](https://www.facebook.com/business/ads/meta-advantage-plus/audience)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- No current account controls or actual post rights were inspected in this source-writing batch.
- The linked SAE access prerequisites remain a source conflict, not a reason to demand unrelated admin accounts for selecting posts.