---
name: post-to-linkedin
description: "Share one useful lesson on LinkedIn. Use the right profile or Page and save the live link."
category: Content Factory — Post
stage: Post
definitive_article: GAP — to be written
status: needs-work
---

# Post to LinkedIn

A short lesson can help your work reach the right people. This guide helps you share it on LinkedIn in a clear voice. Start with one true point and the account the plan calls for.

**The path:** Useful point → Correct identity → Post and check → Comment handoff.

**Use this when:** A checked article or finished clip is ready for the LinkedIn audience named in the distribution plan.

## Inputs
- The exact profile or company Page in scope and authorized access. A Page needs a role that can post, such as super or content admin.
- The real source article/clip, use rights, intended audience, and speaker’s approved voice or factual notes.
- The specific article URL, a real image/video if suitable, and verified identities for any relevant mentions.
- The tracker, recent post history, comment owner, and a named receiver for any scheduled-post check.

## First-run prompt

> Use my source, actual voice notes, and specified LinkedIn identity to write a short lesson. Carry out the publication state already authorized, check the final identity and link, and record the result. Keep any company repost and later comment work within the agreed scope.

## Steps
1. Confirm whether the job calls for the owner’s profile, the company Page, or both. Do not assume access to one authorizes posting to the other. Check the recent history for duplicate coverage.
2. Write a hook about the problem or lesson. Add one concrete insight so the post helps even if no one opens the link. Use one to three short paragraphs. First person must match the real speaker and source.
3. Open Start a post. Select the correct identity and audience settings. Check who can see and comment on it. Apply a brand-partnership label when the real relationship and current rules require it. The current standard post limit is 3,000 characters; keep this task’s short format rather than filling the limit.
4. Add the real image or video when it helps the lesson. Add accurate photo alt text or usable video captions where the composer supports them; otherwise record the accessibility limit. Add the article link in the post or in the planned first comment. Keep media previews silent. Tag only verified, relevant people or organizations; no tag is better than the wrong identity.
5. Use a few relevant hashtags if useful; the source’s maximum of three is a house style, not a LinkedIn requirement. Check formatting and that the post does not invent a client result or relationship.
6. Post now, save a draft where supported, or schedule according to the existing instruction. If a company Page repost is also authorized and useful, add a distinct short frame and verify that separate result. Do not expand the job automatically.
7. Open the posted item and save its direct link, identity, time, audience, and state. For a Page, use the member view where available. A scheduled item or private-view check is not evidence of a publicly live post. Give a named receiver its scheduled time and timezone so the first firing and public URL are checked 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). A scheduled or failed item stays with its firing-check receiver until its public state is known. The source proposes review within 24 hours; answer legitimate questions within the actual scope, route sensitive issues, and do not promise to reply to every spam comment.

## Definition of done (QA checklist)

- [ ] The selected identity, audience, and publication state match the assignment; scheduled is not called live and has a named first-firing receiver.
- [ ] The post teaches a real supported point and links to the intended article.
- [ ] Media, mentions, voice, accessibility support and any required brand-partnership label are accurate, with no fabricated personal experience.
- [ ] Any separately requested company repost has its own checked link/state.
- [ ] The tracker and correct next owner for the current state have the evidence needed for follow-through.

## Example(s)

**Fictional teaching example — no LinkedIn post was sent.** A sample owner post for Maple Cycle says:

“A repair quote is useful only if the rider knows what it covers. I use three parts: the work we can see, the things we still need to check, and the next choice for the customer.

Our short guide shows how we explain that before a visit: `https://maplecycle.example/repair-quote/`.”

In a real post, “I use” needs the owner’s actual method behind it. If only the company Page is authorized, the frame becomes “Our team’s quote process uses three parts” only if that is true. A Page repost is not claimed unless it was separately saved and checked.

## Handoff and Content Factory context

The firing-check receiver gets any scheduled item, time and timezone. After the first firing is publicly verified, the comment owner gets the checked post and source material. The article owner gets any useful questions for the topic queue. Paid distribution remains a separate task.

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

Run for an agreed article or clip. Use a chosen schedule only when requested; a named receiver must verify its first firing before the live post enters comment review. A real account setting or named person must own the proposed 24-hour comment review.

## 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:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `post-to-facebook-page`
- **Suggested next station:** `share-in-44k-facebook-group`
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 LinkedIn](https://local-service-spotlight.github.io/task-library/?task=post-to-linkedin#task-post-to-linkedin)
- Working writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [LinkedIn’s current post controls](https://www.linkedin.com/help/linkedin/answer/a528176/post-and-share-updates)
- [LinkedIn Page drafts](https://www.linkedin.com/help/linkedin/answer/a1348619)

## 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.
- Actual identity, access, posting state and comment permissions require the real account.