---
name: post-roundup-listicle-content
description: "Make one helpful page from strong past posts. Link readers to the full guides they need."
category: Content Factory — Promote
stage: Promote
definitive_article: GAP — to be written
status: needs-work
---

# Post roundup/listicle content

Your readers may need one place to find your best answers. This guide helps you turn strong past posts into a useful list. Start with one reader question and the pages that truly help answer it.

**The path:** Reader question → proven source pages → useful roundup → checked publication.

**Use this when:** A campaign or period has enough relevant published source material for a reader-focused roundup.

## Inputs
- Exact published source URLs and dated evidence of their usefulness; rights to images, clips and excerpts.
- The reader question, existing topic hub and [SEO Tree](https://blitzmetrics.com/seo-tree/) placement so the roundup has a distinct job.
- Current [Article Guidelines](https://localservicespotlight.com/article-guidelines/), the actual CMS/save rail, author/category requirements, publication scope and any named distribution channels.

## First-run prompt

> Build a helpful roundup for this reader question from the supplied verified pages. Keep the topic hub authoritative, use meaningful owned links and check media rights. Publish only through the supported existing CMS rail when authorized, then verify the canonical page at desktop and phone sizes. Distribution and paid promotion must match their own existing scope.

## Steps
1. Choose the exact question the roundup answers and check existing pages first. Update an appropriate existing roundup when it serves the same job; do not create a competing definitive page or rename a source hub to make room.
2. Select the strongest relevant source pieces using the period’s actual evidence. The source suggests five to ten, but use only as many as the question warrants. Different metrics serve different goals; traffic alone does not prove qualified business impact.
3. For each item, read the full source and write a brief takeaway that helps the reader decide whether to open it. Link with descriptive text to the maintained owned leaf or guide. Preserve primary external proof when needed instead of replacing evidence with a vague internal link.
4. Place a clear grade-5 opening and a meaningful photo or diagram in the first desktop and phone screen. Each item needs useful visual context when it aids understanding, with accurate captions, alt text and rights. Keep video embeds silent during checks and captions available.
5. Tie the roundup to its parent branch and relevant included leaves through the [SEO Tree](https://blitzmetrics.com/seo-tree/). Explain methods on their maintained owned pages at first mention. Do not add every sibling or turn the roundup into a wall of unrelated links.
6. Review factual and relationship claims against their sources. A name, image or mention does not establish endorsement. Do not turn a selected example into a task recipe or certify an article merely because it appears in this roundup.
7. Use the actual supported CMS pipeline for the existing type and builder. Preserve canonical URL, Page/Post identity and durable save source. Apply the maintained editorial checks; plugin scores and automatic link suggestions do not replace semantic and visual review.
8. When authorized, publish and read back the saved source, then the ordinary canonical URL. Check links, readable first-screen content, media and phone/desktop overflow. Share only to named channels in scope, then measure the roundup’s own response before treating it as a paid winner.

## Definition of done (QA checklist)

- [ ] The reader question and distinct SEO Tree role are clear.
- [ ] Each selected source was read and linked with relevant descriptive text.
- [ ] Opening, meaningful lead visual, captions and claims meet current standards.
- [ ] Publication preserves the supported CMS type, source and canonical URL.
- [ ] Actual public read-back and channel receipts are separate from saved drafts and future boost eligibility.

## Example(s)

**Fictional teaching example:** A shop has three strong articles on loose seats, brake checks and tire wear. It makes “Three checks before a school bike ride” as a short entry page, linking each takeaway to the full guide and linking up to the bike-care hub. A simple three-part inspection diagram leads the page. The site has an existing Page built with its supported builder, so the operator updates that source rather than converting it to a Post. The roundup’s own response is still unknown after publication; the success of its linked pieces does not automatically qualify it for a paid boost.

## Handoff and Content Factory context

Use [verify all items on blog posting checklist](https://local-service-spotlight.github.io/task-library/?task=verify-all-items-on-blog-posting-checklist#task-verify-all-items-on-blog-posting-checklist) for the relevant final editorial check if that exact task is part of the publishing plan. Give the public URL and initial evidence to [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) only after an actual distributed post earns its own signal.

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

A roundup is event-, campaign- or period-driven. Quarterly repetition is optional when the format helps readers and fresh evidence exists; no automatic cross-channel or paid schedule is implied.

## 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 4, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** —
- **Suggested next station:** —
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

- Dedicated canonical article: not mapped in this source record. Use the maintained owned training below until that article gap is reviewed.
- Exact task: [Post roundup/listicle content](https://local-service-spotlight.github.io/task-library/?task=post-roundup-listicle-content#task-post-roundup-listicle-content)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [SEO Tree](https://blitzmetrics.com/seo-tree/)
- [Content Factory](https://blitzmetrics.com/content-factory/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)

## 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.
- The source record still lacks a dedicated roundup definitive article; maintained Article Guidelines and SEO Tree provide the method context.
- Actual publication and distribution receipts must come from the real run.