Loading tutorials…
Loading tutorials…
The Yoast Premium redirect manager catches slug changes automatically, lets you map old URLs to new ones with one click, and prevents the 404-and-lost-rankings cycle every WordPress site eventually hits. This is the full setup — and the limits to know before relying on it.
Who this is forWordPress site owners on Yoast SEO Premium ($99/yr) who change URLs occasionally (URL restructures, deleted posts, slug rewrites, e-commerce category reorganizations). This is a Premium-only feature — Yoast free does not have a redirect manager.
What you'll need
Step 1
Yoast SEO → Redirects. If this menu item is missing, Yoast Premium is not active. Confirm Premium license is valid.
WordPress Admin → Yoast SEO → Redirects. If you do not see this item, Premium is either not installed or the license is not activated.
Verify: WordPress Admin → Plugins → Installed Plugins → confirm both "Yoast SEO" and "Yoast SEO Premium" are active.
Verify: Yoast SEO → General → Premium → license status shows "Active." If "Inactive," reactivate via the field on the same page.
The redirect manager has three tabs: Redirects (manual entries), Regex Redirects (pattern-based), Settings.
Open Settings first. Confirm "Auto-redirect" toggle is ON — this is the autopilot that catches slug changes automatically.
Step 2
Yoast SEO → Redirects → Add new. Pick redirect type (301 permanent), enter old URL and new URL, save.
Click "Add Redirect" at the top right.
Type: choose 301 (permanent move) for almost every case. 302 (temporary) only if the change is genuinely temporary. 307 (temporary, method preserved) for API/POST redirects. 410 (gone) if the URL should be deindexed and not redirected.
Old URL: enter the path part only — /old-post-slug/ not https://yoursite.com/old-post-slug/. Yoast prepends your domain automatically.
New URL: enter the destination path — /new-post-slug/ or a full URL if redirecting to an external domain.
Click "Add Redirect." The row appears in the redirects list.
Test immediately: open the OLD URL in a private window. You should see the new page load, and the URL bar should show the new URL. View Source on a request inspector (curl -I) to confirm the response is "301 Moved Permanently."
Step 3
Yoast SEO → Redirects → Settings → Auto-redirect: ON. Now any post slug change triggers a 301 automatically.
Yoast SEO → Redirects → Settings tab. Confirm "Automatically redirect URLs after slug change" is ON.
Edit any published post → change the URL slug → click Update. Yoast pops a notification: "We noticed the slug changed. We made a redirect from the old URL to the new one."
Open Yoast SEO → Redirects. The new redirect should appear in the list with type 301 and an "Auto" tag.
This catches the single most common cause of broken links: someone changes a slug to "improve SEO" without redirecting the old URL.
Also fires when you delete a post AND opt to "Trash" rather than "Permanent Delete" — Yoast prompts for a redirect destination during trash action.
Step 4
Yoast SEO → Redirects → Regex Redirects → Add Redirect. Use regex for bulk pattern matches like /blog/.* → /articles/$1.
Yoast SEO → Redirects → Regex Redirects → Add Redirect.
Type: 301 permanent.
Regex Old URL: a pattern using regex syntax. Example: ^/blog/(.+)$ matches anything under /blog/.
New URL: the replacement with backreferences. Example: /articles/$1 captures the matched group and inserts it.
Real example: restructuring /products/category/item → /shop/item. Regex Old: ^/products/[^/]+/(.+)$. New URL: /shop/$1.
Test the regex against multiple URLs in regex101.com BEFORE adding it to Yoast. A wrong regex can redirect your entire site to one URL.
Save. Open 3-5 example old URLs in a private window. All should 301 to the correct new URL.
Step 5
Yoast SEO → Redirects → Import. CSV with columns: type, old_url, new_url. Bulk imports save hours during site migrations.
Prepare CSV: three columns — type (301/302/410/451), old_url, new_url. No headers required by Yoast (it auto-detects).
Example row: 301,/old-page,/new-page. Save as redirects.csv.
Yoast SEO → Redirects → Import. Click "Choose File" → select your CSV → Upload.
Yoast imports row-by-row and reports success/failure counts. Failed rows usually have format issues (extra commas, missing slashes).
For sites migrating FROM .htaccess: write a script to extract Redirect 301 lines and convert to CSV. Or paste .htaccess rules into Claude/ChatGPT to convert format.
Validate: spot-check 10 imported redirects in private window. All should 301 correctly.
Step 6
Yoast SEO → Redirects. Sort by Old URL. Look for: A → B already exists AND B → C is being added (chain). Or A → B + B → A (loop).
Redirect chains (A → B → C → D) lose ~15% of link equity per hop. Three-hop chains lose >40%. Google may stop following after 3-5 hops.
When adding a new redirect, search the existing redirects list for the destination URL. If it appears as an Old URL, you are about to create a chain.
Fix: update the original redirect to point directly to the final destination. A → B → C becomes A → C, B → C separately.
Loops (A → B → A) cause infinite redirect errors in browsers. Yoast usually catches and rejects these on save, but check after bulk imports.
Audit quarterly: export redirects to CSV → sort by Old URL → manually scan for chains and overlaps.
Step 7
Yoast SEO → Redirects → Settings → "404 Monitor" or check GSC Indexing → Not indexed → 404s. Convert recurring 404s to redirects.
Yoast Premium does not include a built-in 404 monitor. Use GSC instead: Google Search Console → Indexing → Pages → "Not indexed" → "Not found (404)."
You see every URL Google tried to crawl that returned 404. Sort by Last crawled to find recently broken URLs first.
For each significant 404 (URL with prior backlinks or organic traffic): decide whether to redirect (Yoast → Redirects → Add) or leave as 410 Gone.
Redirect if: the URL had backlinks (check via Ahrefs/Moz), is a top-50 URL by historical traffic, or has a clear replacement page.
410 Gone if: URL is genuinely deprecated, no replacement exists, you want Google to drop it from the index faster than 404 (404 = try again later; 410 = never coming back).
Common mistakes
Using 302 (temporary) for permanent URL changes
What goes wrong: 302 tells Google 'this is temporary, keep crawling the original.' Link equity does not transfer. Google keeps the old URL indexed. You see no SEO benefit from the redirect. Common with WordPress because the default redirect via wp_redirect() is 302.
How to avoid: Always 301 for permanent moves. Yoast defaults to 301 in the manual form — verify it stayed 301 if you copied from elsewhere.
Creating redirect chains
What goes wrong: A → B → C → D loses ~15% link equity per hop. Google may give up at 5 hops. Rankings drop on the destination page despite the URL technically resolving.
How to avoid: Audit redirects table for chains. Update intermediate redirects to point to final destination. Yoast does not flag chains automatically — manual audit required.
Redirecting bulk URLs to the homepage
What goes wrong: Common 'fix' for deleted content: redirect 100+ old URLs to the homepage. Google interprets this as a 'soft 404' for non-equivalent content. Link equity does not transfer. The redirect is ignored.
How to avoid: Redirect each URL to its closest topical match. /old-post-about-yoast → /best-yoast-tutorials, not homepage. For URLs with no equivalent, use 410 Gone instead of 301 to homepage.
Not redirecting case-sensitive variants
What goes wrong: /Old-Post and /old-post are different URLs to most servers. You redirect /old-post → /new-post but /Old-Post still 404s. Lost backlinks from sites that linked with mixed case.
How to avoid: Use a regex redirect to handle case: regex old URL ^/(?i)old-post$ → /new-post. Or add explicit redirects for known case variants.
Storing thousands of redirects in Yoast on a high-traffic site
What goes wrong: Each request checks the redirects table. At 10K+ redirects with thousands of requests/minute, the database query becomes a bottleneck. Page load times tick up 100-300ms.
How to avoid: Move bulk historical redirects to .htaccess (Apache) or nginx config. Keep Yoast for ongoing one-off redirects (under 1,000 total). Best-of-both-worlds.
Forgetting to test redirects after adding them
What goes wrong: Typo in the new URL — Yoast happily saves and 'redirects' to a 404 page. Visitors hit the broken redirect. SEO juice flows to a dead end.
How to avoid: After every batch of redirects, open 5+ old URLs in private window. Verify they 301 to the right new URL. Use curl -I or httpstatus.io for header-level verification.
Recap
Done — what's next
How to install the Yoast SEO plugin on WordPress
Read the next tutorial
Hand it off
Redirects are deceptively risky. A wrong type (302 vs 301), an unintentional chain, or a regex that catches more URLs than intended can wipe weeks of SEO progress. A vetted technical SEO specialist runs a one-time audit + migration of existing redirects, sets up monitoring, and trains your team on the right patterns — typically $80-200 total at $14-16/hr.
See specialist rates
No. The redirect manager has been Premium-only since 2016. Yoast Premium costs $99/year for one site. If you cannot afford Premium, the free Redirection plugin (by John Godley, 2M+ installs) is a solid alternative with similar features.
Yoast for ongoing one-offs (1-1,000 redirects), .htaccess for bulk historical redirects (1,000+). Server-level redirects are ~10x faster per request because they fire before WordPress loads. Yoast is more convenient (no FTP needed) but slower per request.
301 says "this URL has permanently moved to URL X." Use when there is an equivalent replacement page. 410 says "this URL is gone permanently, do not try again." Use when no replacement exists. 410 deindexes faster than 404 (which Google retries periodically). Both pass no link equity.
Yes if the post had backlinks or organic traffic. Pick a topical equivalent as the destination. No (use 410 instead) if the post was junk content with no backlinks. Yoast prompts but does not enforce — the choice is yours.
Yes via CSV import (Yoast SEO → Redirects → Import). Format: type, old_url, new_url, one per line. Most SEO plugins (RankMath, AIOSEO, Redirection) can export to CSV. For very large imports (>10K), split into batches of 5K to avoid PHP timeouts.
Yoast SEO
Yoast SEO powers SEO on 13M+ WordPress sites. The install itself takes five minutes — but doing it on a live site with a competing plugin, a caching layer, and a paid license is where most owners corrupt their meta data. This is the clean-install path.
Yoast SEO
Yoast generates a multi-file sitemap_index.xml automatically — but the default output usually includes content you do not want indexed and excludes content you do. This is the audit + submit workflow that produces a sitemap Google actually trusts.
Yoast SEO
Yoast fails in predictable patterns: plugin conflicts, REST API blocks, cache layers, theme schema duplication, license activation issues, and indexable corruption. This is the diagnostic playbook to find which one you have — without trial-and-error.
Google Search Console
GSC's Indexing report shows you what's broken — in language that often hides what to actually do about it. This is the field-tested decoder: every error type, what causes it, and the specific fix that works.
Yoast SEO
Most WordPress site owners can install and configure Yoast themselves. But some scenarios — migrations, schema deep-debugging, 5+ year old sites with technical debt — burn more DIY time than the specialist would cost. This is the honest signals list.