# Redirect map QA pass

> Use when a redirect map has been drafted and you need it checked before it goes live.

## Preencher antes de executar

- `{{REDIRECT_MAP}}`
- `{{VALUABLE_URLS}}`
- `{{NEW_SITE_URLS}}`
- `{{RULE_SET}}`

## Prompt

```
You are QA-ing a proposed redirect map before it ships. You are not building the map.

Redirect map (old URL, destination, status code): {{REDIRECT_MAP}}
Old URLs ranked by traffic, links or revenue: {{VALUABLE_URLS}}
Live URLs on the new site: {{NEW_SITE_URLS}}
Pattern rules being applied: {{RULE_SET}}

Output one table covering every row in {{REDIRECT_MAP}}: Old URL | Destination | Verdict (Correct / Loose match / Wrong intent / Chain / Loop / Destination not on new site / Wrong status code) | Evidence | Fix.

Then four sections:
- "Unmapped and valuable" - anything in {{VALUABLE_URLS}} with no row in the map, ordered by value.
- "Rules that overreach" - patterns in {{RULE_SET}} that catch URLs they were never meant to, with one example each.
- "Redirects to the homepage" - the count, and which of them deserve a real destination.
- "Cannot verify" - the checks that need the live server rather than this data.

Constraints:
- A redirect that resolves but lands on a page answering a different question is Wrong intent, not Correct.
- Treat any destination absent from {{NEW_SITE_URLS}} as unverified. Do not assume it exists.
- Flag every 302, meta refresh and JavaScript redirect on a permanent move.
- Do not add a closing summary. The table and the four sections are the whole output.
```

## Como obter um resultado melhor

- Feed it the map in batches by directory so the wrong intent verdicts stay reviewable.
- Sort the valuable URL list by referring domains as well as traffic, since links are what you lose permanently.
- Re-run the pass on the live server after launch, because the deployed rules rarely match the spreadsheet.

---

Da biblioteca de prompts da QuQi - https://www.quqi.io/pt/prompts/redirect-map-qa-pass