---
name: post-to-facebook-page
description: "Share a useful article or clip from the right business Page. Check the post and save its link."
category: Content Factory — Post
stage: Post
definitive_article: GAP — to be written
status: needs-work
---

# Post to Facebook page

Your page can help customers find a useful answer. This guide shows you how to share a clear post from the right business. Start with the real article or clip and one point worth sharing.

**The path:** Approved source → Correct Page → Clear post → Live link and comments.

**Use this when:** The distribution plan calls for a post on a specific Facebook Page and the source is ready.

## Inputs
- The exact Facebook Page, approved posting scope and access to create its content. Facebook access and task access are different; task access may use Meta Business Suite.
- The checked article URL and/or finished media, rights, source facts, caption notes, and intended audience.
- The real voice and attribution of the speaker or business. First person must refer to a real supported speaker, not a fabricated personal experience.
- The content tracker, current posting history, named comment owner, and a named receiver for any scheduled-post check.

## First-run prompt

> Use the exact Page and source I provide to prepare a short factual post. Check the current posting history and media rights. Publish, schedule, or save only as already requested, verify the resulting state, and log the direct link. Do not start ads or claim reach from a post existing.

## Steps
1. Open the specified Page or its Meta Business Suite workspace. Verify the selected business and account identity before creating anything. Use the existing approved route; possession of a token alone is not a posting instruction.
2. Check the recent content list for the same article or clip so retries do not create duplicate posts. Confirm the article is publicly readable if the caption says it is live.
3. Write two to four short sentences: the real question or point, one supported takeaway, and a helpful next step. Keep the wording true to the actual speaker. Use the owner’s first person only where the source and assignment support it.
4. Open the create-post composer for that Page. Add the caption and the selected real photo or video. Choose the available media/post format shown by the Page. Native media is an editorial choice, not a promise of higher reach.
5. Include the specific article link where readers can find it. If the plan uses a first comment, that comment is part of the handoff and must actually be added and checked. Tag only confirmed featured people or Pages when the mention is relevant and available.
6. Preview the source, crop, text, link, and selected destinations. Add accurate photo alt text or usable video captions where the composer supports them; otherwise record the accessibility limit. Keep any media preview muted at volume zero. Publish when already authorized, or save the in-scope draft/scheduled post. Do not add a boost, spend, or another platform just because the composer offers it.
7. Open the resulting post as the intended viewer where possible. Check the Page name, caption, media, link, and mentions. Copy its direct URL and record the observed status and time. For a scheduled item, give a named receiver the scheduled time and timezone; that receiver checks the first firing and public URL after the due time.
8. Hand a verified live post to [Engage with social comments](https://local-service-spotlight.github.io/task-library/?task=engage-with-social-comments#task-engage-with-social-comments) under the agreed response scope. A scheduled or failed item stays with its firing-check receiver until its public state is known. Later measurement can inform [the Facebook boost shortlist](https://local-service-spotlight.github.io/task-library/?task=boost-top-3-5-facebook-posts#task-boost-top-3-5-facebook-posts); a Page post is not automatically eligible or approved for an ad.

## Definition of done (QA checklist)

- [ ] The post belongs to the specified Page and has the intended draft/scheduled/live state; scheduled is not called live and has a named first-firing receiver.
- [ ] The caption and media match the actual source and rights; accessibility support or its exact limitation is recorded, with no unsupported reach claim or personal story.
- [ ] The article link and intended mentions work, or a specific limitation is recorded.
- [ ] The direct URL, time, channel, and correct next owner for the current state are saved once.
- [ ] No ad spend or extra distribution is implied by the organic post.

## Example(s)

**Fictional teaching example — no Facebook post exists.** Maple Cycle’s sample caption reads:

“Not sure what to send us for a repair quote? A clear photo and a short note about the problem help us plan the next step. Our guide explains what a photo can tell us and what needs a shop visit: `https://maplecycle.example/repair-quote/`.”

The planned image is the shop owner beside an actual workbench. In a real run it must be the real authorized photo. If the post is scheduled for tomorrow, the tracker must say “scheduled,” not “live.” This invented post supplies no engagement or boost evidence.

## Handoff and Content Factory context

The firing-check receiver gets any scheduled item, time and timezone. After the first firing is publicly verified, the named comment owner receives the direct post link and source facts. The promotion owner receives actual later measurements, not an assumed winning post.

This task serves **Post** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce supplies the source, Process prepares it, Post places and checks it on the agreed channels, and Promote distributes proven work under its own scope. The task’s actual handoff above defines the next step; list order alone does not create a prerequisite.

## When this runs

One post per agreed distribution item. Scheduling is optional and needs the chosen time, timezone and named receiver who checks the first firing. Early comment review follows the actual response plan; this guide installs no timer.

## First-run setup and continuity

Use the exact account, source, destination and authority recorded for the job. Carry out publication, messages or repairs already authorized once their required checks pass; do not ask for the same approval again. If an action is outside that scope, finish the authorized work and state the specific remaining need. A login, plugin, or task file does not itself grant new authority.

Keep the latest state, record IDs, revisions and next owner in the project tracker or files. Before a retry, check the current saved/sent/published item to avoid duplicates or overwriting another edit. A model has no guaranteed memory, scheduler or account access just because it is called persistent. A future check needs a configured timer or a named person.

Keep all agent media previews muted with volume zero before playback. If this cannot be verified, use captions, metadata or still frames and state what was not tested. No first-load autoplay is part of these page instructions.

## Write up the real run

For each actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this exact task, source revision, trigger, work, decisions, evidence, result and next owner. Failed, partial and blocked attempts still get a written record. A private draft is a valid writing outcome; public publication follows the existing scope.

Keep one stable execution ID for the actual task run. Retries, checks and changed artifacts do not add runs. A separately scoped child task may have its own ID linked to its parent; writing the parent’s meta record is part of that same run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the distinction. Teaching examples below or above are not execution evidence and must not enter the run count.


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

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

- **Phase:** Post
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** `upload-processed-video-to-youtube`
- **Suggested next station:** `post-to-linkedin`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Draft URL or WP post ID, slug, author user ID, featured-image media ID. Promote reads the live URL, not the draft.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **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

- Dedicated canonical article: not mapped in this source record. The owned training references below remain the method until that gap is reviewed.
- Exact Task Library record: [Post to Facebook page](https://local-service-spotlight.github.io/task-library/?task=post-to-facebook-page#task-post-to-facebook-page)
- Working writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Meta’s Page access roles](https://www.facebook.com/help/289207354498410/)

## Review and evidence still needed

The original contributor status in the header is preserved. It does not certify this proposed rewrite or prove that this account, publication, message, player or check has run. Every worked teaching example is explicitly invented; replace it with actual evidence when documenting a real execution.
- The exact Page composer, permissions, media options and live state must be checked in the real account; no login was used for this draft.