# SEO QA acceptance checklist

Use one copy per change. Check production after the release and save the observed result with the task.

**Task:** __________  **URL or template:** __________  **Risk:** __________

**Implementer:** __________  **SEO verifier:** __________  **Approver, if needed:** __________

## Request

- [ ] Current state and exact expected state are written in the task.
- [ ] Affected URL(s), template variants, and acceptance method are listed.
- [ ] Owner, approval, and release dependency are clear.

## Implementation

- [ ] Deployment or publication date, environment, and ticket or release link are recorded.
- [ ] Implementer marks the change ready for live SEO review.

## Production check

- [ ] Fetch the production URL and record status code, final URL, and relevant response headers.
- [ ] Compare the requested element with the observed HTML, rendered page, or HTTP response.
- [ ] Check representative sibling URLs when a template or site rule changed.
- [ ] Record actual value, timestamp, verifier, and a screenshot, response, crawl, or test link.

## Decision and follow-up

- [ ] **Pass:** observed live state matches the requested state. **Fail:** reopen with the mismatch attached.
- [ ] Record a later Search Console check when indexing or canonical selection matters.
- [ ] Assign a recheck after the next relevant release or monitoring interval.

**Observed live state:** __________  **Checked at:** __________  **Evidence link:** __________

**Verdict:** Pass / Fail  **Next owner and date:** __________

Live acceptance confirms what production serves at the check time. Google indexing and search performance may need a later review.