---
name: verify-all-items-on-blog-posting-checklist
description: "Check the article with the current rules. Save what you found and name the work still left to do."
category: Content Factory — Post
stage: Post
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Verify all items on Blog Posting checklist

Small missed details can make a good article hard to trust or use. This guide helps you check the work before it ships. Start with the current rules, then save what you found for each check.

**The path:** Current rules → Real evidence → Fix and recheck → Honest decision.

**Use this when:** An article is ready for its prepublication check or a postpublication review needs a recorded checklist.

## Inputs
- The exact draft or live URL, accepted source revision and original material behind its facts, quotes and media.
- The current [Article Guidelines](https://localservicespotlight.com/article-guidelines/) and [definitive article standard](https://blitzmetrics.com/definitive-article-guide/) when the page is a task recipe.
- The page’s role, [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief, link/identity map, intended channels and actual publication authority.
- The supported editor/checking tools, access to fix scoped issues, and a named owner for problems outside this scope.

## First-run prompt

> Review the exact article against the current maintained rules and its declared role. Save evidence for PASS, FAIL, UNKNOWN and justified NOT APPLICABLE items. Fix issues within the authority already given, then recheck what changed. Distinguish draft readiness from public delivery and do not fabricate a score, quote source or visual pass.

## Steps
1. Read the current maintained rules rather than a cached checklist from an old run. State the page’s role: a recipe, topic hub, story, reference or run record. Select applicable checks and keep the source/rule link beside each.
2. Check the reader’s start. Does the title match the answer? Does the short opening explain who, why, the work and the useful result in plain words? Apply the maintained grade-5-or-lower opening rule to every document. A reading score flags difficulty; also check that a person new to the subject can explain the value and first action.
3. Check facts, voice and proof against the source. Use first person on a personal-brand site when the evidence supports that person’s authorship. Keep named scenes, exact quotes, proper attribution and evidence-limited relationship language. Require no trophy-name paragraph and no repeated defensive caveats. Remove unsupported claims and public internal scoring labels unrelated to the article’s subject.
4. Check identity, permission and testimonials. Verify the speaker’s identity, primary source and needed permission for each quote. Missing proof and domain/company-only attribution fail publication; keep the claim on HOLD. Do not repair it with invented reassurance. Preserve any materially necessary legal, regulatory, or compliance disclosure, scoped to the claim it qualifies.
5. Check the meaningful lead visual at 1280×800 and 390×844 before scrolling. It must have real visible content and readable labels, not just a border. Review other media, captions, alt text and source players. Keep agent playback muted at zero volume; record untested sound or player behavior.
6. Check body links and the [SEO Tree](https://blitzmetrics.com/seo-tree/): the correct parent, useful related pages, accurate first-mention term explanations and verified identity destinations. Read each new target and named anchor. Keep exact official proof/download links when needed; do not replace them solely to reach an internal-link count. Check the useful course/service or do-it-yourself action link when the maintained role requires one.
7. Check the saved site fields and visible page: intended author, category/tags where supported, stable URL, metadata and supported Page/Post/builder source. Treat a Rank Math score as the agreed internal target, not proof of article quality or Google ranking.
8. For a task recipe, check trigger, inputs/access, source-backed prerequisites, ordered method, measurable result, acceptance and handoff. Check the lower Content Factory context, bidirectional exact-task link, and relevant verified execution examples or an explicit example gap. Preserve the contributor task status separately: it does not certify the current article or candidate revision. A better opening alone does not certify a task guide.
9. Record PASS, FAIL, UNKNOWN or NOT APPLICABLE with a reason and evidence for each check. UNKNOWN on a required item is unfinished; NOT APPLICABLE needs a real role/scope reason. Fix failures within the existing authority and recheck the affected item and anything the fix could break.
10. Make the decision for this actual stage. A passed draft checklist means ready for the already-authorized publishing step, not proof of public delivery. Save the final checklist, revision, date, operator and unresolved owner/actions; write the run’s meta record even if the result is partial or blocked.

## Required first-screen visual gate

Every visitor-facing page, including home, money, relationship, archive and
utility pages, must show a relevant authentic photograph, source-video poster
or useful diagram above the fold. At 390x844 and 1280x800, test the anonymous
unscrolled first visit with JavaScript on and off. A logo, social icon, decorative
background, thin strip, broken image or empty player rectangle fails.

Use the [canonical numeric standard](https://github.com/dennisyu/local-service-spotlight-skills/blob/main/standards/visuals-above-the-fold.md) and its
[shared browser checker](https://github.com/dennisyu/local-service-spotlight-skills/blob/main/scripts/rendered_visual_check.mjs) in the real builder/publisher:
`rendered_visual_check.mjs --url URL --selector CSS --output DIRECTORY`.
Measure the complete preview with site chrome before release and the ordinary
public URL after the authorized release. Save both screenshot/JSON receipts.
The checker can measure a loaded photographic CSS background as well as images,
diagrams and video posters. Its geometry pass remains `REVIEW_REQUIRED` until
an independent reviewer opens the actual screenshots and source evidence and
accepts the relevance, authentic moment, useful crop, labels and permission.
A source-order regex or an `<img>` count cannot mark this gate complete.

YouTube uses youtube-nocookie.com with rel=0, cc_load_policy=1 and cc_lang_pref.
No media autoplays on first paint. Before any separate playback verification,
mute and set volume zero; if that cannot be verified, use metadata, captions,
frames or a loaded poster and record playback NOT_TESTED. Never play through
the user's speakers without their explicit current request.

## Definition of done (QA checklist)

- [ ] The live first 2–3 sentences pass `step-7-write-hook-and-establish-context`: actual reader/situation, reason to care, useful outcome and supporting mechanism; exact text and quoted reviewer evidence retained, and the body delivers its promise
- [ ] Preview and ordinary-live first-screen geometry plus source-backed screenshot review pass on both viewports; actual evidence stored

- [ ] The rule version, page role and exact source revision are recorded.
- [ ] Each required item has evidence and a truthful state; no required UNKNOWN or FAIL is hidden.
- [ ] Task recipes have their exact task link, handoff and relevant verified examples, or a visible example gap; contributor status is not used as document-readiness proof.
- [ ] Any NOT APPLICABLE result has a specific reason, rather than avoiding a difficult check.
- [ ] Accepted fixes have relevant rechecks, including both exact first-screen sizes for visual changes.
- [ ] The final decision describes draft readiness or live acceptance accurately and names outstanding owners.

## Example(s)

**Fictional teaching example — not an accepted article.** Maple Cycle’s quote guide gets this sample review:

| Check | First result | After scoped repair |
| --- | --- | --- |
| Plain opening | PASS: reader and next step clear | Unchanged |
| Lead photo on phone | FAIL: image hidden below a large blank box | PASS after the box is removed and 390×844 is checked |
| Named quote | UNKNOWN: source message missing | Remains on HOLD; quote omitted from publishable version |
| Video player | NOT APPLICABLE: this article is based on written source, not video | Reason retained |

This sample shows why a checklist needs judgment and evidence. Four checked boxes without these states would hide the missing quote proof. The example is invented and supplies no actual screenshot or acceptance receipt.

## Handoff and Content Factory context

The publisher gets the reviewed revision and decision. If it is a draft, [the supported WordPress publication task](https://local-service-spotlight.github.io/task-library/?task=step-12-post-article-on-wordpress#task-step-12-post-article-on-wordpress) completes the authorized publish. [Final formatting and QA checks](https://local-service-spotlight.github.io/task-library/?task=step-17-final-formatting-and-qa-checks#task-step-17-final-formatting-and-qa-checks) checks the final served page and agreed distribution.

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 before publication and after meaningful edits; use it again in final QA. Rerun checks affected by new work rather than claiming a past pass covers a new revision. No unconfigured perpetual loop exists.

## 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:** `step-17-final-formatting-and-qa-checks`
- **Suggested next station:** `upload-processed-video-to-youtube`
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

- Canonical article: https://localservicespotlight.com/article-guidelines/
- Exact Task Library record: [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)
- Working writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Task recipe and publishing standard](https://blitzmetrics.com/definitive-article-guide/)
- [Our YouTube caption-default method](https://blitzmetrics.com/youtube-captions-on-by-default/)

## 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.
- Independent editorial acceptance and real source/view checks are still required; a generated checklist is not a passed execution.