Last fall, I was standing behind a booth at a startup event, helping a friend man his table. A prospective attendee stopped by, interested in the product. My friend pulled out his phone: “Just scan this QR code.” They scanned. Nothing loaded. They scanned again. Still nothing.
The QR code pointed to:
app.theirstartup.com/onboarding/step-one?ref=event-sf&utm_source=qr&utm_medium=expo
I pulled out my own phone and typed a short link I had set up for them thirty seconds the night before:
theirstartup.com/start
The page loaded in three seconds. The visitor registered. Walked away.
My friend texted me later: “We’ve been using that long link for two months. No one ever said it didn’t work.”
I said: “That’s because no one actually tried to type it. They glanced at it and gave up.”
Not Every Short Link Is a Vanity URL
A lot of people confuse vanity URLs with WordPress custom permalinks. I did, too, five years ago.
Custom permalinks change your site-wide URL structure. You switch from /?p=123 to /%postname%/, and every new post from that point forward gets a URL based on its title. It’s a one-time, global change.
Vanity URLs are one-off shortcuts. They don’t have to point to a page on your own site—they can go to an Amazon affiliate link, a Calendly booking page, or a Dropbox file. Their only reason to exist: to make people willing to type, remember, and share.
yoursite.com/spring-sale is a vanity URL.
yoursite.com/2026/03/21/spring-sale-announcement-final-version is not.
One is an invitation. The other is a file cabinet label.
Three Things That Will Save You Two Hours
When I set up my first vanity URL with a plugin, I picked the highest-rated one at the time: “301 Redirects.” Installed it. Activated it. Added /book → target URL. Tested it.
Infinite redirect loop.
Forty minutes later, I noticed the plugin hadn’t been updated in two years. The compatibility notice said “untested up to WordPress 6.0.” I was on 6.2.
Now, no matter how urgent the request, I do three things first:
1. Check that WordPress and the plugin have been updated within the last three months. Not necessarily the latest version, but recently maintained. Redirect plugins depend heavily on WordPress’s rewrite API; version mismatches cause weird, silent failures.
2. Back up the site. Not just as insurance—to sleep at night. I use UpdraftPlus, set to daily auto-backups to Dropbox. Creating a vanity URL doesn’t touch the database, but modifying .htaccess or functions.php with one typo can take the whole site down. A five-minute backup investment pays off in avoided midnight debugging.
3. Name the shortlink deliberately. This step is the easiest to skip, and the one you’ll regret most. In 2023, I set up /black-friday for a client. The next year, they asked: “Can we reuse this year’s campaign link?” I said yes, but that original URL was already printed on five thousand flyers. If you’re certain the campaign is one-time, use /bfcm-2023. If you’re not sure, use /holiday-sale. Never embed a year in a vanity URL unless you’re prepared to register a new domain every twelve months.
Four Paths, Four Real-World Scenarios
1. Edit the Slug: Fastest, but Not Free
In the WordPress editor, right sidebar, Permalink section. Delete the auto-generated webinar-registration-2026-spring-marketing-masterclass-v2 and type three words: /webinar.
Hit Update. Done.
The trade-off: the old URL dies. If that post was already indexed by Google, or if someone bookmarked it, they’ll see a 404. Quick fix: go to Settings → Permalinks, change nothing, and click “Save Changes.” This flushes WordPress’s rewrite rules and—sometimes—creates an automatic 301 from the old slug to the new one.
But this automatic redirect doesn’t work on every host. I’ve tested it on SiteGround—fine. On Kinsta—no luck.
Safer approach: after changing the slug, use one of the redirect plugins below to manually point the old path to the new one.
2. Redirection Plugin: What I Use for Almost All Clients
Not because it’s flashy. Because it has a module called 404 Logs.
One day you notice 87 requests for /discount in the past week, all returning 404. Someone’s looking for that link—but you never created it. With Redirection, you can turn that 404 entry into a redirect directly from the log screen, without typing the source path manually.
Setup:
Plugins → Add New → search “Redirection” (author: John Godley). Activate. Then Tools → Redirection → Add New.
Source URL: /start (domain not included)
Target URL: full destination address
HTTP Code: 301
The dropdown also offers 302 and 307, but 99% of cases call for 301. 302 is for temporary moves—search engines won’t transfer ranking signals. Unless your shortlink points to a different page every week, don’t touch 302.
One detail: Redirection checks “preserve query parameters” by default. If a user visits /start?utm_source=twitter, the target URL will still carry ?utm_source=twitter. Leave this on unless you have a specific reason to strip parameters.
3. Pretty Links: When You Need to Know Who Clicked
This is the affiliate marketer’s choice. Redirection tells you “this link was clicked X times.” Pretty Links tells you “who, when, from which site, on what device.”
Last year, I set up /instructor for an online course platform, placed in the social media bios of five different instructors. Two weeks of data showed one instructor converting three times better than the others—not because they had more followers, but because they put the link prominently on their personal website, while the others only had it in their Instagram bios (where external link clicks are naturally low).
That insight came from Pretty Links. Redirection doesn’t give you that granularity.
Downside: the free version caps the number of active links, and the interface is heavier. If you only need a dozen vanity URLs and don’t require detailed reports, Redirection is sufficient.
4. Code-Level Intervention: When Rules Need to Be Dynamic
This March, I had a client request: logged-in members visiting /vip should go to an exclusive resource page; non-members should go to a signup page with an affiliate referral code appended.
No plugin does this for free.
In functions.php:
add_action('template_redirect', function() { if ($_SERVER['REQUEST_URI'] === '/vip') { if (is_user_logged_in()) { wp_redirect('https://yoursite.com/vip-content', 301); } else { $ref_code = 'partner2026'; wp_redirect('https://yoursite.com/register?ref=' . $ref_code, 302); } exit; } });
exit is mandatory. Without it, WordPress continues loading the page template after the redirect instruction—wasting server resources and, in edge cases, triggering “headers already sent” errors.
The obvious risk: next time you update your theme, functions.php gets overwritten. Solutions: use a child theme, or move the snippet into a custom functionality plugin. I prefer Code Snippets—it keeps these tweaks independent of the theme and survives updates.
Three Mistakes I Actually Made
1. Conflict with existing content
I set up /contact as a vanity URL pointing to an external customer support form. But /contact still landed on the WordPress “Contact” page.
Because I already had a page with that slug. WordPress’s content routing runs before most redirect plugins.
My fix: use a namespace. All marketing shortlinks now get a /go/ prefix: /go/contact, /go/ebook, /go/vip. This never collides with existing pages. I manage over 60 redirects under /go/ on a Flywheel-hosted site—two years, zero conflicts.
2. Case sensitivity
A client set their vanity link to /BlackFriday on a banner stand. I asked why the capital B. “Looks better.”
Linux servers are case-sensitive in filesystem paths. /BlackFriday and /blackfriday are two different resources. Even though we’re using redirects (not real files), Apache and Nginx match URLs case-sensitively by default.
I spent an hour bulk-converting every historical shortlink to lowercase and adding fallback redirects from the uppercase versions. Now: all vanity URLs, forced lowercase.
3. Forgetting to turn off expired campaigns
The most embarrassing kind. Three months after a promotion ends, the client’s /summer-sale still points to a long-dead landing page. Users click and see “Page not found.”
Redirect rules are living assets, not one-time configurations. Every quarter, I crawl the site with Ahrefs or the free version of Screaming Frog, export all active redirects, and flag any with zero clicks in the last 90 days—or any pointing to a 4xx destination. Delete or update accordingly.
You Don’t Need Four Hundred Shortlinks
A client once asked me to audit his redirect strategy. Four years of site history. 480 vanity URL rules in the database. I spot-checked twenty. Fifteen pointed to products that had been discontinued. Two pointed to external domains that had expired. Three were /a, /b, /c—codes no one on the team could explain.
Vanity URL count is not a measure of brand sophistication. It’s a direct measure of future maintenance cost.
I advised him to start from zero: keep the twenty rules that actually receive traffic, delete the rest. Three months later, he told me Redirection’s admin panel loaded twice as fast, and the team finally knew which shortlinks were still in use.
Late Sunday, One Text
Last weekend, an old friend texted me: “That shortlink thing you showed me—how do I set one up? I’m going on a podcast and don’t want to paste that monstrosity Spotify gives me.”
I screenshotted the Redirection setup screen. Three minutes later, he said it was done and sent me a test link.
I tapped it: hisdomain.com/listen. Clean, sharp, like he’d been running the brand for a decade.
He didn’t thank me. Didn’t need to. That’s the point of a vanity URL—not to make you look technical, but to make sure your users never have to think about the technical part at all. They just remember the word, open their phone, type it in, and arrive where they need to be.
Everything else is plumbing that should never be seen.
