---
name: check-lead-magnet-section-has-visual-mockup
description: "Show people what they will get from your free offer. Check that the preview matches the real file."
category: Website QA Audit
stage: —
definitive_article: /website-qa-audit
status: complete
---

# Check lead magnet section has visual mockup

People should know what your free offer gives them. This guide helps you check the picture beside the offer. Start with the real file so the preview does not promise something else.

**The path:** Actual offer → Honest preview → Page and phone check → Delivery handoff.

**Use this when:** A page offers a downloadable guide, checklist or similar opt-in resource. A lead magnet is the useful resource offered in return for contact details.

## Inputs
- The canonical offer pages, current downloadable file or approved resource, and its version/title.
- The approved cover, real preview or accurate visual mockup, with source rights and any private details removed.
- The offer text, form/CTA and expected delivery path; submission scope and test receiver if delivery testing is included.
- Supported page/media edit access and the owner of the actual offer file.

## First-run prompt

> Compare the supplied offer file with every scoped page preview and promise. Fix authorized visual mismatches using real approved assets. Check desktop and phone visibility, then report visual accuracy separately from form and delivery tests.

## Steps
1. List the offer’s live placements in scope, including a landing page, home-page section or active popup if present. If the site has no such offer, record not applicable with the reason; do not invent a resource just to pass the check.
2. Open the actual supplied resource and read its title and main contents. Confirm the version and whether it is a PDF, checklist, video or something else. A cover image alone does not verify the promised contents.
3. Compare the preview with that resource. Use a real cover or page view, or a clearly honest mockup of the digital file. Do not imply a physical book, extra chapters or proven results the offer does not provide.
4. Check that the preview sits with the relevant promise and CTA on desktop and phone. Its useful text or shape should be recognizable, not a tiny unreadable stamp. Confirm it loads, preserves aspect ratio and does not obscure form controls.
5. Read the visible title, description, file format and CTA together. They should describe the same offer. Remove exposed client/contact details from a preview before it becomes public; do not upload private source pages to a design service without the job’s authority.
6. Repair the preview or placement already in scope using the actual source asset and supported editor. Keep a useful existing image if it already fits. If the real resource is unavailable, specify the missing file/version rather than drawing an invented cover as proof.
7. Recheck the normal canonical placements after saving. Keep visual/offer accuracy separate from form submission, email arrival and download access; perform those tests only under their actual scope and receipts.
8. Record the asset version, checked placements, screenshot evidence and any delivery handoff. Do not claim better conversion from this image audit without an actual measured comparison.

## Definition of done (QA checklist)

- [ ] The preview matches a real available resource and its current promise.
- [ ] Every in-scope offer placement has a useful visible preview on desktop and phone.
- [ ] No private data, fake physical format or unsupported result is implied.
- [ ] Canonical visual changes are checked; delivery remains separately measured or explicitly untested.
- [ ] Missing resource or rights evidence has an exact owner.

## Example(s)

**Fictional teaching example — no offer was created.** Maple Cycle’s sample free resource is a two-page “Photos for a repair quote” PDF. Its old picture says “Complete bike care handbook.” That preview fails because it promises a different resource.

The teaching fix uses a real preview of the two-page checklist and the words “Two-page photo checklist.” The image check can pass once the correct preview is visible. It does not prove that a submitted email receives the file; the opt-in test needs its own receiver evidence.

## Handoff and Content Factory context

The page owner receives the verified visual and file version. [Verify the opt-in form and delivery](https://local-service-spotlight.github.io/task-library/?task=verify-email-opt-in-form-exists-and-works#task-verify-email-opt-in-form-exists-and-works) owns the next functional check when included in the project.

This is a supporting quality check for 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. This check does not automatically execute all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run when an offer or its placement changes. There is no need to create a new offer, email sequence or recurring campaign for this check.

## 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:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 2, gating 3 (supporting)
- **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:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## 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://blitzmetrics.com/website-qa-audit
- Exact task: [Check lead magnet section has visual mockup](https://local-service-spotlight.github.io/task-library/?task=check-lead-magnet-section-has-visual-mockup#task-check-lead-magnet-section-has-visual-mockup)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Website QA Audit](https://blitzmetrics.com/website-qa-audit/)

## 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 real resource, rights, page placements and delivery evidence require the actual project.