404 Hunter

Lives on SEO Tools → Content tab. Paste up to 30 URLs (typically from Google Search Console's "Pages with issues" or analytics 404 reports). We:

1. HEAD-check each URL
2. For every 404 or 410, derive the slug text + embed it
3. Search product + article embeddings for the closest live page (≥0.45 similarity floor)
4. Suggest as a redirect target

One-click 301

Each suggested redirect has an Apply 301 button. Click it; we call Shopify's urlRedirectCreate mutation to create the redirect. Idempotent — re-applying on an existing redirect surfaces "Already exists" instead of failing.

The redirect appears in Online Store → Navigation → URL Redirects immediately.

Why semantic beats slug overlap

Other 404 tools (Yoast, SEMrush) suggest matches by URL slug overlap. They miss obvious cases like /products/old-creatine-monohydrate → /products/creatine-2024-formula (different slugs, same product). Embeddings catch the semantic relationship.

Stats row

After running, the stats row shows:

• Checked — total URLs scanned
• OK (200s) — URLs that returned 200 (no action needed)
• Broken (404/410) — URLs that need redirects
• With redirect target — broken URLs we found a ≥45% similarity match for
• Errors — URLs that failed to fetch (timeout, network error, invalid)

Cost

~$0.00005 per 404 URL (one embedding call). Free-tier accessible.

Tips

• The 30-URL cap is per request. To process more, batch.
• HEAD checks have a 6s timeout — slow servers may time out and surface as errors.
• Private/loopback IP addresses are blocked (SSRF guard).
• A 0.45 similarity floor prevents misleading suggestions on pages with no semantic neighbor.