Review image markup before publishing or migrating.

1. Export rendered image markup

1. Capture final rendered image HTML for launch-relevant templates.
2. Include product, category, article, landing page, and hero image examples.
3. Review both ordinary `img` tags and images inside `picture` elements.
4. Keep staging, preview, test, draft, and localhost URLs out of production launch sets.

2. Review alt text quality

1. Flag image tags with no alt attribute.
2. Flag empty alt text unless the image is intentionally decorative.
3. Replace generic values like image, photo, product image, banner, hero, or logo when descriptive alt is needed.
4. Make sure product and content images describe the visible subject, not just the page keyword.

3. Check filenames and dimensions

1. Replace generic filenames such as IMG_1234.jpg, screenshot.png, product.png, hero.jpg, or untitled.webp.
2. Use descriptive filenames that match the image and page context.
3. Confirm every launch image includes width and height attributes where templates can provide them.
4. Review missing dimensions as a layout stability risk before release.

4. Validate responsive and hero image behavior

1. Confirm important images have `srcset` or `picture` source candidates when multiple sizes exist.
2. Add `sizes` when using `srcset` so browsers can select the right asset for the viewport.
3. Do not lazy-load the primary hero or above-the-fold image without a clear performance reason.
4. Retest after CDN, image optimizer, CMS, or frontend template changes.

5. Copyable image SEO QA handoff

Image SEO QA handoff

Page context:
Hero expectation:

Counts
- Image tags:
- Markup image URLs:
- Inventory image URLs:

Risks to fix
- Missing or generic alt text:
- Generic filenames:
- Missing width/height:
- Responsive image gaps:
- Lazy-loaded hero images:
- Inventory drift:

Decision
- Fix before launch / Manual review / Ready for final image SEO check