---
name: check-each-homepage-section-includes-relevant-image
description: "Give each main home page section a useful visual. Check that it helps readers on a phone too."
category: Website QA Audit
stage: —
definitive_article: /website-qa-audit
status: complete
---

# Check each homepage section includes relevant image

People should see what your business does, not just read a wall of text. This guide helps you check the pictures in each main part of your home page. Start with the live page on a phone and a large screen.

**The path:** Main sections → Useful visuals → Two screen sizes → Exact fixes.

**Use this when:** A home page is being built, changed or audited for the owned visual standard.

## Inputs
- The exact canonical home page, current page source and a list of major sections.
- Real approved photos, screenshots, diagrams or embedded media that support each section’s point, with source and use rights.
- Browser views at 1440×860 and 390×844, and access to repair visuals or a named page owner.
- The current [Article Guidelines](https://localservicespotlight.com/article-guidelines/) and the page’s intended reader and result.

## First-run prompt

> Review the supplied home page at 1440×860 and 390×844. List major sections, their main point and the useful visual actually visible. Fix authorized layout issues with real approved assets. Record missing proof and exact section results; do not replace gaps with invented images or claims.

## Steps
1. Open the normal public home page at both viewports. Record the date, URL and visible first screen. Identify the hero, service, about, proof, offer and other major content sections actually present.
2. For each major section, state its main point in one line and identify the visual that helps explain or prove it. Utility links, a small legal footer or a simple spacer are not reasons to invent another picture; record a reason when the section rule does not apply.
3. Inspect the visual itself. A real job photo, useful diagram, source screenshot or relevant player can qualify. A blank colored box, decorative icon row or unrelated landscape does not establish the section’s meaning.
4. Check that the first desktop and phone viewports contain meaningful visible visual content. A border, offscreen image, broken asset or tiny unreadable diagram label is not enough. A longer diagram can continue below the fold if the visible part communicates a useful complete point.
5. Scroll through both layouts and check each major section. Confirm the image is not hidden on mobile, stretched, covered by an overlay or separated so far from the relevant text that the relationship is lost.
6. Check factual fit and rights. A photo of one event proves that scene; it does not by itself prove a client relationship, award or speaking role. For missing proof, specify a real asset to obtain rather than inventing an experience or using a stock stand-in.
7. Add or repair relevant visuals already in scope using the supported builder. Preserve existing useful media and its aspect ratio. Give informative images suitable alt text; decorative elements follow their own accessibility treatment.
8. Reopen the normal canonical page after saving. Keep per-section evidence and a short list of missing assets or fixes with the responsible owner. A source edit alone does not prove visitor visibility.

## Definition of done (QA checklist)

- [ ] Each major section has a relevant useful visual or a documented reason the section rule does not apply.
- [ ] Both first viewports show meaningful readable content, not only an image container.
- [ ] Mobile visibility, aspect ratio and surrounding layout are checked on the canonical page.
- [ ] Visuals have appropriate provenance, context and text alternatives.
- [ ] Any missing real asset remains a specific request, not fictional proof.

## Example(s)

**Fictional teaching example — no page was changed.** Maple Cycle’s home page has a hero, repair service section, about section, quote offer and a small legal footer.

The hero’s real workshop photo supports the business. The repair section has only a gray rectangle, so its visual check fails. The proposed fix is an approved close-up of an actual repair with a caption explaining the work. The quote section uses a real preview of the photo checklist. The legal footer needs usable links, not an invented stock picture.

If the workshop photo is hidden at phone width, desktop success does not pass the phone check.

## Handoff and Content Factory context

The page owner receives the section map and real asset requests. [Check long stretches of text](https://local-service-spotlight.github.io/task-library/?task=ensure-no-text-only-sections-spanning-full-viewport#task-ensure-no-text-only-sections-spanning-full-viewport) reviews the broader visual rhythm; [Check image text alternatives](https://local-service-spotlight.github.io/task-library/?task=verify-all-images-have-descriptive-alt-text#task-verify-all-images-have-descriptive-alt-text) covers accessibility.

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 for a new home page and after material section or layout changes. Recurring review uses only the site’s existing agreed schedule.

## 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 each homepage section includes relevant image](https://local-service-spotlight.github.io/task-library/?task=check-each-homepage-section-includes-relevant-image#task-check-each-homepage-section-includes-relevant-image)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Website QA Audit](https://blitzmetrics.com/website-qa-audit/)
- [W3C image text alternatives](https://www.w3.org/WAI/tutorials/images/decision-tree/)

## 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.
- Actual assets, use rights and rendered evidence are still required for the target site.