You rename a post slug because the title changed, a typo shipped, or marketing finally picked a cleaner URL. WordPress happily serves the new permalink. Every old inbound link, internal link you missed, and indexed Google result still points at the previous path. Without a redirect, that equity and traffic fall into a 404. Rankify Pro’s auto-redirect on slug change writes the redirect for you, chain-free, so fixing a typo in a URL does not break every link to it.
Rankify is the DaftPlug SEO and answer-engine plugin. This post’s hero is Pro auto-redirect on slug change. Around it sits the broader redirect manager (301, 302, 307, 308, 410, 451, with wildcards, regex, and loop detection) and the 404 monitor. For manual wildcard and regex patterns that stay 404-safe, keep WordPress wildcard and regex redirects nearby. This post does not invent crawl tools, bulk CSV redirect importers, or server nginx snippets Rankify does not claim.
What Rankify actually ships here
Stay inside the real feature set:
- Auto-redirect on slug change (Pro): rename a slug and Rankify writes the redirect for you, chain-free
- Redirect manager with 301, 302, 307, 308, 410, and 451, plus wildcards and regex
- Loop detection at save time, before a rule can strand a page
- 404 monitor that records broken URLs people still reach, with one-click paths into redirects
- Rules that only run on requests that would otherwise 404, so a redirect cannot shadow a page that exists
This post does not invent undocumented “redirect consolidation wizards,” automatic external backlink outreach, or promises that every CDN cache purges itself when a slug changes. The product promise for the hero feature is Pro auto-redirect on slug change, chain-free. Stay there.
Why slug changes need redirects on WordPress
Slugs change more often than style guides admit. Editors fix spelling. SEOs shorten URLs. Product teams rename evergreen guides. Each change is a potential 404 storm.
Manual redirect entry does not scale with editorial velocity. Asking every author to open a redirect screen after every permalink edit fails the first busy week. Auto-redirect on slug change removes that ritual for the common case.
Chains are how sites get slow and confusing. A old URL redirects to a middle slug that redirects again to today’s slug. Rankify’s Pro framing is chain-free writes when the slug changes, which is the behavior you want for clean hops.
404 monitors catch what auto-redirect cannot. External sites may link to URLs you never had as formal slugs, or to deleted posts. The 404 monitor plus manual redirect manager covers that residue. Auto-redirect covers the rename you just made in the editor.
Status codes still matter. A permanent content move usually wants 301. Temporary campaigns may want 302 or 307. Gone content may want 410. Rankify’s manager includes 301 through 451 so you are not stuck with a single hammer when you create rules by hand. The hero feature’s job is still the automatic write on slug change.
How to rely on auto-redirect when slugs change
Assume Rankify is installed and you are on a plan that includes Pro auto-redirect on slug change (Rankify’s own free vs Pro notes list auto-redirects on slug change under Pro). Free still includes the redirect manager and 404 monitor for manual work.
1. Confirm Rankify is the SEO plugin emitting redirects
Do not run two SEO plugins both trying to own redirects and meta. Rankify detects competing Open Graph output and warns; the same operational hygiene applies to redirects. Pick Rankify, deactivate the duplicate SEO stack when you are ready, and keep one source of truth.
2. Know what auto-redirect will do on a rename
Mental model:
- A published URL exists at
/old-slug/. - You change the slug to
/new-slug/and update. - Rankify Pro writes a redirect from the old path to the new one, chain-free.
- Visitors and crawlers that still request the old path get the redirect instead of a 404.
You still use the redirect manager for patterns, regex, and one-off fixes. You still use the 404 monitor for URLs nobody renamed inside WordPress.
3. Practice once on a safe post
- Pick a low-traffic post or a staging copy of production.
- Note the current permalink.
- Change the slug slightly (a clear test string you will recognize).
- Update the post.
- In a logged-out window, request the old URL.
- Confirm you land on the new URL via redirect (check status with your usual redirect checker or browser network panel).
- Open Rankify’s redirect manager and confirm the rule exists as Rankify wrote it.
- Change the slug a second time and confirm you still get a clean hop rather than a messy chain (this is the chain-free promise you are validating).
If nothing redirects, confirm Pro features are active on the site, confirm Rankify is not disabled for that post type by a role or conflict, and confirm a host-level rule is not intercepting first.
4. Use the redirect manager for everything that is not a simple rename
Wildcards, regex, and special status codes (410, 451, temporary redirects) stay in the manager. Loop detection at save time is your friend: if Rankify refuses a rule, fix the loop instead of forcing it in .htaccess. The related wildcard/regex post covers 404-safe pattern design in more depth.
5. Keep the 404 monitor on a weekly glance
Even with auto-redirect on slug change, old campaigns, mistyped marketing URLs, and deleted content create 404s. Glance the 404 monitor, turn real traffic misses into redirects, and ignore bot noise when it is clearly junk. Auto-redirect does not replace that hygiene.
6. Document the editorial rule
Runbook: “Authors may fix slugs on published posts. Rankify Pro auto-redirect on slug change is on. Do not also paste manual redirects for the same rename unless you are handling a special case. Check 404 monitor weekly. Patterns and regex go through the redirect manager with loop detection.”
Who this is for
Editorial WordPress sites that refresh titles and slugs as content improves.
SEO teams that shorten URLs without wanting a ticket queue for every redirect.
Sites migrating naming conventions (for example dating year prefixes, or removing stopwords from slugs) where many renames will happen in a controlled window.
Anyone who has shipped a typo in a permalink and watched social posts keep sending people to a 404.
Teams already using Rankify redirects who want the Pro auto write so humans stop forgetting the manual step.
This is less urgent for sites that never change slugs after publish by policy. Even then, one emergency rename per quarter is enough to justify having Pro auto-redirect ready.
What good looks like
- Changing a published slug results in an automatic redirect from the old URL to the new one.
- The hop stays chain-free when slugs change again.
- Redirect manager still handles 301, 302, 307, 308, 410, 451, wildcards, and regex with loop detection.
- 404 monitor still surfaces broken URLs that were never a simple in-editor rename.
- Rules only fire when the request would otherwise 404, so live pages are not shadowed.
- You did not invent server config exports or claim free includes auto-redirect on slug change if your plan is free-only.
- Authors can rename without opening a separate redirect ritual for the common case.
If old URLs still 404 after a rename, verify Pro, verify the post was published (not a draft-only slug experiment), verify no reverse proxy is stripping paths, and inspect the redirect manager for the rule Rankify should have written.
Pitfalls (the ones that bite)
Assuming free includes auto-redirect on slug change. Rankify documents that feature under Pro. Manual redirects and 404 monitoring still help on free.
Stacking a manual redirect on top of the automatic one carelessly. Special cases exist. Blind duplicates create loops. Trust loop detection when it complains.
Renaming on production during a campaign blast without checking social URLs. Auto-redirect saves you, but you should still prefer correct slugs before a big send when you can.
Using regex for a problem auto-redirect already solved. Keep patterns for true patterns. Use slug auto-redirect for single renames.
Ignoring 410 for truly gone content. Not every old URL should 301 to the homepage. Homepage dumps dilute relevance and confuse users.
Running Yoast/Rank Math redirects alongside Rankify. Two managers will fight. One plugin owns redirects.
Forgetting CDN cache of 404 responses. Rare, but some edges cache 404s aggressively. Purge if an old URL still looks dead after a correct rule exists.
Practical checklist before you call it done
- Confirm Rankify is the active SEO plugin for redirects.
- Confirm Pro is active if you need auto-redirect on slug change.
- Practice one safe slug rename and request the old URL logged-out.
- Confirm the redirect exists in the redirect manager and the hop is clean.
- Rename once more on the test post and confirm chain-free behavior.
- Glance loop detection by attempting a silly loop on staging if you train teammates (optional, careful).
- Keep 404 monitor on a weekly checklist.
- Use wildcard/regex only for pattern problems (see related post).
- Avoid duplicate SEO redirect managers.
- Document the author-facing slug policy.
- Purge stubborn edge caches if an old URL still 404s after a correct rule.
- Leave schema, llms.txt, and AI crawler controls for their own posts unless already stable.
Takeaway
Slug changes are normal. Broken old URLs are optional. Rankify Pro auto-redirect on slug change writes the redirect for you, chain-free, so a typo fix or cleanup does not orphan every inbound link. The redirect manager (301 through 451, wildcards, regex, loop detection) and 404 monitor remain the manual and discovery layers around that hero feature.
Rankify handles the automatic rename redirect beside the rest of SEO and AI-visibility tooling. Enable Pro auto-redirect, test one rename, and keep pattern rules in the manager as described in wildcard and regex redirects.
One Pro membership unlocks Rankify plus Progressify, Lightify, Generatify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when renaming a slug should never mean losing the old URL.
Fix the slug. Let Rankify write the redirect. When the old link still lands on the new page, editorial cleanup stops costing SEO.