How to Set Up Pretty Links for Small Teams

If your team manages anywhere from one to five websites, you can have Pretty Links installed, configured, and creating clean redirect links within a single working session. This tutorial walks you through every decision point so you finish with a working link management system — not just a plugin sitting idle in your WordPress dashboard.

What You Will Have Working by the End

By the time you finish this setup, Pretty Links will be active on your WordPress site, your team members will have the right access levels assigned, and you will have at least one working redirect link ready to share or embed. The plugin will be connected to your workflow, not just installed.

Requirements Before You Start

Getting this right the first time means checking a few things before you touch any settings. Missing one of these is the most common reason small teams stall mid-setup.

A couple of notes worth calling out. First, Pretty Links only runs on self-hosted WordPress — if your site is on WordPress.com's free or basic plans, this setup will not apply. Second, you do not need the Pro version to follow this tutorial, but some team features discussed later are Pro-only.

Expected Outcome When Setup Is Complete

When you finish, your system will be in this exact state:

• Pretty Links is installed and activated on each WordPress site your team manages
• At least one team member beyond the admin has a WordPress user account with an appropriate role assigned
• Your first redirect link is live, tested, and returning the correct destination URL
• Link categories are created so your team can sort links by site, campaign, or purpose from day one
• You have confirmed the plugin's tracking is recording clicks correctly

That is a genuinely usable foundation. Nothing half-done, nothing that requires a follow-up session just to make it functional.

Get Pretty Links for Your Team

Steps 1–3: Getting Pretty Links Running on Your Sites

Before anything else — if you're managing one to five WordPress sites and want cleaner, trackable links without a steep learning curve, this is where you start. The setup is genuinely straightforward, but there are a few decisions in these first three steps that affect how well the tool serves your team long-term. Worth doing carefully once rather than undoing later.

Step 1: Install and Activate the Plugin

Go to your WordPress dashboard. Navigate to Plugins → Add New , then search for "Pretty Links." The free version appears immediately. If you're on the Pro plan, you'll install it differently — upload the ZIP file you received after purchase via Plugins → Add New → Upload Plugin .

Click Install Now , then Activate .

Once activated, a new Pretty Links menu item appears in your left sidebar. That's your confirmation it worked.

Why this matters for small teams: You're likely managing multiple sites under limited admin bandwidth. Getting activation right on each site — rather than half-installing and wondering why the menu isn't showing — saves you a round of troubleshooting later. If you're rolling this out across two or three WordPress installs, do the activation check on each one before moving forward.

What to verify:

• Pretty Links appears in the WordPress sidebar
• Clicking it opens the main dashboard without a plugin conflict error
• If you see a white screen or fatal error, check for theme/plugin conflicts first (disable other plugins temporarily to isolate the issue)

One more thing here: if your team uses a staging environment before pushing to production, install on staging first. It takes five extra minutes and has saved more than a few teams from a messy rollout.

Step 2: Configure Your General Settings

This step gets skipped more than it should. Head to Pretty Links → Options (or Settings , depending on your version). You'll see several tabs — start with General .

The most important setting here for small teams is the default redirect type . You have three main choices:

• 301 (Permanent Redirect) — tells search engines this link is permanent; use this for affiliate links and evergreen content
• 302 (Temporary Redirect) — use when the destination might change; doesn't pass link equity
• 307 (Temporary Redirect, preserves method) — rarely needed for most small-team use cases

For most affiliate and content links, 301 is what you want. If you're testing a campaign and the destination URL might change, go with 302 — you can always update individual links later regardless.

Also on this page: the link prefix . This is the base slug your links will use. By default it might be /go/ or /recommends/ or just blank. You're setting something like yourdomain.com/go/tool-name, so choose a prefix that's clean and consistent across your sites. Changing it later means updating every existing Pretty Link, which is a hassle.

Why it matters: Your default settings cascade down to every link you create going forward. Spending two minutes here means you won't need to manually correct redirect types across 40 links three months from now.

What to verify:

• Your preferred redirect type is selected as the default
• Your link prefix is set and makes sense for your brand (e.g., /go/, /visit/, /out/)
• Save settings and confirm the page reloads without error

There's also a Replacement or Auto-link tab in some versions. Hold off on that for now — it's powerful but worth configuring after you understand how your links are structured. Rushing into auto-replacement settings before your link architecture is solid can create unintended substitutions across old posts.

Step 3: Create Your First Pretty Link

Now you're building something real. Go to Pretty Links → Add New Link .

You'll see a few fields:

Target URL — paste the full destination URL here. This is where the visitor actually lands.

Pretty Link — this is the slug after your domain and prefix. So if your prefix is /go/, and you type ahrefs here, your final link becomes yourdomain.com/go/ahrefs. Keep slugs lowercase, short, and descriptive.

Title — internal label only. Nobody sees this but your team. Name it something you'll recognize in three months, not just "Ahrefs link." Something like "Ahrefs – Blog Sidebar CTA" is far more useful when you're managing 30 links across multiple sites.

Redirect Type — this will default to whatever you set in Step 2. Override it here if this specific link needs a different behavior.

Tracking — make sure the tracking checkbox is enabled. This is how Pretty Links logs clicks, referrers, and geographic data. For small teams watching affiliate performance, this is the whole point.

Why this matters: Your first link is also your template for everything that follows. Getting the naming convention right now — clear titles, consistent slugs, tracking enabled — means your dashboard stays readable as the list grows. Two sites with 50 links each starts to feel chaotic fast if your naming is sloppy from day one.

What to verify:

• Paste your Pretty Link URL into a browser tab and confirm it redirects to the correct destination
• Visit Pretty Links → All Links , find your new link, and confirm the click counter registers (you may need to click through once yourself to see it populate — some caching setups delay this)
• Check that the title makes sense to someone else on your team, not just you

A small note on slugs: avoid numbers and dates in your slugs unless they're meaningful. /go/tool-2024 will look odd in 2026. Timeless slugs age better and don't require updates.

Before You Move to Steps 4–6

These three steps get your foundation right — activation, settings, and your first working link. The decisions here are quiet but load-bearing. The redirect type you default to, the prefix you choose, the naming system you start with — these small calls shape how much maintenance your team faces six months out.

If you're still deciding whether Pretty Links is the right fit before committing to setup, the Pretty Links review covers the honest tradeoffs without the marketing spin. And if you're weighing it against other tools, Pretty Links vs. alternatives breaks down the comparison for small-team use cases specifically.

Ready to keep going with the full setup?

Continue Setup with Pretty Links Pro

Step 4: Create Your First Pretty Link

Once the plugin is active and your license is connected, head to Pretty Links → Add New Link in your WordPress dashboard. This is where the actual setup starts to feel real.

You'll see a form with a few fields. Here's what each one does and what to fill in:

• Target URL — paste the destination URL here, whether that's an affiliate link, a partner page, or a product you promote
• Pretty Link — this is the slug that appears after your domain (e.g., yourdomain.com/go/toolname)
• Link Type — for most small teams, 301 Redirect works fine; use 302 only if you plan to rotate or retire the link soon
• Title — give it a name your whole team will recognize at a glance, not just you

The slug is worth slowing down on. Keep it short, readable, and consistent with whatever naming convention your team agrees on from day one. "go/pretty-links" is easier to manage across three sites than "track/aff-link-052924." Inconsistency at the start creates confusion later, especially when someone other than you needs to update a link.

Why this step matters: Pretty Links replaces long, ugly affiliate or tracking URLs with clean branded ones you actually control. If the original URL ever changes, you update it in one place and every page using that Pretty Link stays correct automatically. For small teams managing multiple sites, that single-point-of-edit capability saves real time.

How to verify: After saving, click the Test button next to your new link. It should redirect you to the correct destination page. You can also paste the Pretty Link into a browser tab and confirm the redirect fires correctly. If it doesn't, check the Target URL field for typos and make sure your permalink settings in WordPress are set to anything other than Plain.

Step 5: Organize Links With Categories and Groups

Creating one link is easy. Managing 40 links across three websites six months from now is a different situation entirely. That's why you set up organization now, not later.

Pretty Links lets you assign categories to each link. Use them. Go to Pretty Links → Categories and create a simple structure before your link library grows. A few examples that work well for small teams:

• Affiliate — links to products you earn a commission on
• Tools — links to software or services you recommend without affiliate terms
• Partners — co-marketing links or partner pages
• Internal — links used inside your own content to track click behavior on specific CTAs

You don't need a complicated taxonomy. Four to six categories covers most small-team use cases across multiple sites. The goal is being able to filter links quickly when you're troubleshooting, auditing, or handing work off to someone else.

Why this step matters: Without categories, Pretty Links becomes a flat list. At 20 links it's manageable. At 80 it's chaos. Organizing early is the kind of setup decision that feels optional until the moment it isn't. Teams that skip this step tend to either rebuild their structure later under pressure or just stop using the tool effectively.

If your team uses Pretty Links across more than one website, consider adding the site name or a short prefix to your slugs as a secondary organizational layer — for example, go/site1-toolname vs go/site2-toolname. It's low-tech but practical.

How to verify: After creating your categories, open the All Pretty Links screen. You should see a filter dropdown at the top that lets you sort by category. Test it. Make sure your first link from Step 4 appears under the right category. If categories aren't showing up in the filter, check that you actually saved the category assignment when you created the link — it's easy to skip that dropdown on the first pass.

Step 6: Enable and Review Click Tracking

This is the step most small teams either rush past or forget entirely. Don't.

Go to the link you created in Step 4 and open it for editing. Look for the Tracking settings — depending on your version of Pretty Links, this may appear as a toggle labeled "Track Clicks" or inside a settings panel within the link editor. Enable it if it isn't already on by default.

Once tracking is active, Pretty Links will log every click on that link, including:

• Total clicks
• Unique clicks
• Click date and time
• Referring URL (where the click came from)

For small teams, the referring URL data alone is worth the setup effort. It tells you which blog post, landing page, or email is actually driving traffic through your links — not what you assumed was working, but what the data shows.

A quick note on privacy: If your sites operate under GDPR or similar regulations, check whether you need to disclose link click tracking in your privacy policy. Pretty Links tracks behavior at the link level, not cookies across sessions, but it's worth reviewing with whoever handles your legal or compliance questions.

Why this step matters: You can't improve what you're not measuring. Knowing that a link got 400 clicks tells you something. Knowing 380 of those came from one specific article, and the other 20 came from your email footer, tells you something actionable. Small teams with limited content bandwidth need that kind of signal to make better decisions about where to focus.

How to verify: After enabling tracking, click the Pretty Link yourself two or three times from different pages on your site. Then go to Pretty Links → Reports (or click the stats icon next to your link in the All Pretty Links view). You should see your test clicks recorded. If the click count stays at zero, double-check that tracking is toggled on for that specific link — global settings and per-link settings can sometimes differ.

What You've Done So Far

At this point in the setup, your team has:

• Created a working Pretty Link with a clean, branded slug
• Built a category structure that scales as your link library grows
• Turned on click tracking so you're collecting real data from the start

These three steps form the operational foundation of how Pretty Links runs for a small team. Everything from here — automation rules, link health audits, reporting — builds on this structure. If any of these steps feel shaky, go back and tighten them before moving forward.

For a broader look at how this tool fits into a wider strategy, the Pretty Links automation strategy guide covers how teams use features like auto-linking and rules-based redirects once the basics are solid.

If you're still deciding whether Pretty Links is the right fit for your specific setup, the Pretty Links review breaks down who it works best for without the marketing spin.

And if you're weighing this against other tools, the Pretty Links vs alternatives comparison puts the options side by side in practical terms.

Try Pretty Links for Your Team

Troubleshooting Pretty Links: Common Failures, Fixes, and Validation Checks

Even a clean setup hits snags. Most issues fall into a small set of patterns, and once you know what to look for, they're fixable in minutes. Here's what actually goes wrong for small teams and how to sort it.

Redirects That Don't Work After Creation

You created a link, saved it, tested it — and nothing happens. The slug just returns a 404 or lands on the homepage.

The most common cause is a permalink structure conflict. Pretty Links depends on WordPress's permalink settings being set to anything other than Plain. If your site is still using the default plain structure (?p=123), Pretty Links slugs won't resolve correctly.

Fix:

• Go to Settings → Permalinks in your WordPress dashboard
• Select any option except Plain — Post Name is the most common choice for small sites
• Click Save Changes, even if nothing appears to have changed (this flushes the rewrite rules)
• Test your Pretty Link again

If that doesn't resolve it, check whether another plugin is interfering with rewrite rules. Caching plugins are frequent culprits.

Caching Plugins Serving Stale Redirects

This one trips up a lot of small teams because the fix isn't obvious. You update a redirect — maybe changing the destination URL — and the old destination keeps appearing. The link looks correct inside Pretty Links, but the redirect is still going to the wrong place.

That's usually your cache. Page-level and server-level caches can hold onto old redirect responses longer than you'd expect.

Fix:

• Clear your caching plugin's cache completely (not just for one page)
• If you're using a host with server-side caching (like WP Engine or Kinsta), purge that separately
• Disable the cache temporarily and retest the redirect
• Once confirmed working, re-enable caching

For teams managing more than one site, make cache-clearing a standard step whenever you update a redirect. It saves a lot of confused troubleshooting later.

Slug Conflicts With Existing Pages or Posts

Pretty Links slugs share the same namespace as your WordPress pages and posts. If you create a Pretty Link with a slug that matches an existing page — say /about or /contact — WordPress will prioritize the page and your redirect won't fire.

Fix:

• In Pretty Links, go to Pretty Links → All Pretty Links and review your slugs
• Cross-check against your existing pages and posts under Pages and Posts
• Rename conflicting Pretty Links slugs to something distinct — adding a prefix like /go/ or /ref/ keeps them clearly separated from site content

Building a consistent slug convention from the start (like always using /go/ for affiliate links) prevents this problem entirely. It's easier to establish that habit early than to audit everything later.

Click Counts Not Recording

You're seeing redirects work correctly, but the click count stays at zero. Or it increments inconsistently.

A few things cause this. The most common is that your own IP address is being excluded from tracking — which is usually intentional, but easy to forget when you're testing. Pretty Links has an option to ignore certain user roles and IP addresses.

Check this first:

• Go to Pretty Links → Options → General
• Look for the tracking exclusion settings
• Confirm your IP or user role isn't excluded from tracking

If tracking exclusions aren't the issue, check whether a bot-blocking or privacy plugin is stripping the request data that Pretty Links uses to log clicks. Some aggressive cookie-consent or privacy tools interfere with this.

For teams that care about accurate link data — especially for affiliate links — it's worth testing with a fresh incognito window using a mobile data connection, which sidesteps both your IP exclusion and any cached browser state.

The Pretty Link Slug Shows as "Already Taken" But You Can't Find It

Occasionally, Pretty Links will refuse to save a slug and report it's already in use, but searching your existing links turns up nothing. This can happen when a link was deleted but the record wasn't fully cleared, or when a WordPress rewrite rule is holding onto the slug.

Fix:

• Go to Tools → Permalink Settings and save again to flush rewrites
• Check the Trash inside Pretty Links (if you've previously deleted links, they may still be reserving slugs)
• If neither works, try a slightly different slug — sometimes the cleanest path is just picking a variation

Links Working in One Browser But Not Another

Cross-browser redirect failures are almost always a caching or cookie issue on the client side, not a Pretty Links problem. If a redirect works in Chrome but not Firefox, check:

• Whether your browser has a cached version of the old destination
• Whether a browser extension (ad blocker, redirect tracker, VPN) is intercepting the link
• Whether the target URL uses HTTPS and your Pretty Link is set to HTTP — mismatched protocols can cause silently dropped redirects in some browsers

For affiliate links especially, always test in a clean private window with extensions disabled before assuming something is broken.

SSL / HTTPS Redirect Loops

If your site recently moved to HTTPS and Pretty Links redirects are now looping or showing security warnings, the issue is usually a mismatch between how Pretty Links has stored the redirect destination and your current site protocol.

Fix:

• Open the Pretty Link record and check the destination URL
• Make sure it starts with https:// — not http://
• Also confirm your WordPress Address and Site Address under Settings → General both use https://

If you migrated to HTTPS using a plugin, run a search-replace to update any http:// stored destination URLs inside Pretty Links. WP-CLI or a plugin like Better Search Replace can handle this at scale without manually editing every link.

Validation Checks Before You Call It Done

After fixing any issue — or after initial setup — run through these checks before closing the tab.

For each link:

• Open the Pretty Link in a fresh incognito/private window
• Confirm the redirect lands on the correct destination
• Check that the protocol matches (HTTP vs HTTPS)
• If you're using tracking, click the link and then check the Pretty Links dashboard to confirm the count incremented

For your overall setup:

• Confirm at least one test link for each redirect type you're using (301, 302, or cloaked)
• Check that your slug naming convention is consistent — random slugs create maintenance headaches fast
• If you're managing links across multiple sites, document which slugs are active on each site somewhere your whole team can see it

Small teams don't need elaborate systems, but they do need one shared place where link decisions are visible. A simple shared doc or spreadsheet beats relying on memory.

When to Look Beyond the Plugin Itself

Most Pretty Links failures are environmental — hosting configuration, plugin conflicts, caching layers, or permalink settings. The plugin itself is rarely broken. Before spending time on support tickets, eliminate the environment as the source.

If you've worked through all of the above and something still isn't resolving, check your hosting error logs for 500 or redirect-related entries. Those logs often point directly at the conflict in a way that's faster than trial and error.

For teams still deciding whether Pretty Links is the right fit before committing to setup, the Pretty Links review covers what the tool actually delivers versus what the marketing suggests. And if you're weighing it against other options, Pretty Links vs alternatives breaks down where it wins and where it doesn't.

If you've worked through setup and troubleshooting and you're ready to move on to building automated workflows around your links, Pretty Links automation strategy is the logical next step.

Get Pretty Links

Did It Work? Go Live With Pretty Links

Quick Binary Checks Before You Publish

Before you tell anyone a link exists, run through these. Each one has a clear yes or no answer — no interpretation needed.

Redirect check

• Open your Pretty Link URL in a browser tab you're not logged into
• You should land on the destination URL within one or two seconds
• If you land on your own homepage instead, the slug is conflicting with a page — rename it
• If you get a 404, the destination URL was saved incorrectly — edit the link and re-check

Redirect type check

• In your Pretty Links dashboard, confirm the redirect type shows 301, 302, or whatever you intentionally chose
• A 301 tells search engines the destination is permanent — use it for affiliate links and evergreen content
• A 302 is temporary — use it for seasonal promos or links you expect to swap out
• If you're unsure what you selected, edit the link and look at the "Redirect Type" dropdown before assuming it's fine

Tracking pixel / click count check

• Click your own Pretty Link once from a browser where you're logged out, or from your phone
• Wait 30 seconds, then check the link's click count in the dashboard
• The number should read 1
• If it still reads 0 after a minute, your caching plugin might be intercepting the redirect — temporarily disable it and test again

Nofollow / sponsored attribute check (affiliate links only)

• If this link goes to an affiliate offer, open it in a browser and inspect the HTTP headers, or use a free redirect tracer tool
• Confirm the link does not pass direct link equity to the merchant without the correct rel attribute
• Pretty Links Pro handles this automatically if you've toggled the nofollow option on — verify that toggle is actually on

Four checks. Less than five minutes. If all four pass, you're clear.

Ready to Go Live? The Subjective Layer

The binary checks tell you the link works. This part tells you whether you're ready to actually use it.

Does the slug make sense to a human?

Your slug is the part after your domain — /go/tool-name, /ref/product, whatever you chose. If someone reads the URL aloud, they should know roughly where it's going. Slugs like /a1b2c3 or /lnk99 don't help your team, your audience, or you six months from now when you're looking at a spreadsheet of 40 links.

Is it in your link management system?

Small teams skip this constantly and regret it. Before you go live, record the link somewhere your team can find it — a shared Notion doc, a Google Sheet, a Trello card, wherever you already track things. The Pretty Links dashboard is great, but it's not a substitute for your own documentation. Teams managing even two websites can lose track of which link goes where if it only lives in one place.

Have you tested it from the actual placement?

Testing in a browser tab is different from testing inside a newsletter, a social media bio, or a blog post. Paste the link into its real context and click it there. Some email clients and social platforms modify URLs — you want to catch that before your audience does.

Do you know who owns this link?

On a team of two to five people, "someone will update it" is how links break and stay broken for months. Before you publish, decide who is responsible for this link. That means who updates the destination if it changes, who checks the click stats, and who notices if it stops working.

If you can answer yes to all four of those, you're ready.

Toolvoro Pro Tips

Pro Tip 1: Use link categories from the start, not after you have 50 links

Pretty Links lets you assign categories to every link you create. Most small teams ignore this until their dashboard becomes a scroll of confusion. Set up two or three categories before you build your first link — something like "Affiliate," "Internal," and "Campaign." It takes 90 seconds. Retroactively categorizing 40 links takes much longer and usually doesn't happen.

Pro Tip 2: Set a link expiration date for time-sensitive campaigns

If you're running a promotion with a deadline, use Pretty Links' expiration feature to automatically redirect to a fallback URL when the offer ends. This prevents the embarrassing scenario where someone clicks an affiliate link three months after a deal closed and lands on a broken merchant page. Your fallback can be your own review post, a general landing page, or a different offer. Just make sure it goes somewhere useful.

Pro Tip 3: Standardize your slug naming convention across all your websites

If you manage multiple sites, decide on one slug format and stick to it everywhere. For example: /go/[brand-name] for affiliate links, /ref/[campaign-name] for campaign tracking, /tools/[product] for tools pages. When you're troubleshooting a link six months from now, a consistent naming format means you'll recognize immediately what a link is for — no digging through notes required. It also makes sharing links across your team faster, because everyone uses the same pattern.

FAQ

Can I change a Pretty Link's destination URL after it's already live?

Yes. Edit the link in your dashboard and update the destination. The slug stays the same, so any existing placements — blog posts, emails, social bios — continue to work. The only thing that changes is where the link sends people. This is one of the main reasons to use Pretty Links: you can update the destination without hunting down every place you posted the link.

Will Pretty Links slow down my website?

For small sites running one to five domains, the performance impact is minimal. Pretty Links processes the redirect server-side, which is fast. If you notice speed issues, check whether your caching plugin is configured correctly — some cache settings interfere with redirect tracking. Excluding Pretty Links URLs from your cache usually resolves it.

Do I need Pretty Links Pro, or does the free version work for a small team?

The free version handles basic redirects and click tracking, which is enough for some setups. Pro adds features like automatic keyword linking, advanced redirect types, link expiration, and deeper analytics. Whether you need Pro depends on how heavily you use affiliate links, whether you're running campaigns, and whether auto-linking to keywords inside your content would save your team real time. Read the full breakdown in our Pretty Links review before making the call.

How do I share link management access with my team?

Pretty Links runs inside WordPress, so access is controlled by WordPress user roles. Editors and Administrators can create and manage links by default. If you want a team member to have access without giving them full admin rights, review the WordPress role capabilities and assign accordingly. There's no separate team seat system to configure — it's handled through the same user management you already use.

What happens if I delete a Pretty Link by accident?

The link goes dead immediately. Anyone who clicks it will hit a 404 or your site's default error page. There's no recycle bin inside Pretty Links itself. If you're managing links that appear in content you don't control — guest posts, email campaigns, partner pages — be especially careful before deleting. When in doubt, redirect to a fallback URL rather than deleting.

Can Pretty Links track clicks from different traffic sources separately?

With the Pro version, you get more granular tracking options. The free version shows total clicks per link. If you need source-level data, you'll want to combine Pretty Links with UTM parameters and review the data in Google Analytics or a similar tool. Pretty Links creates the clean URL — your analytics stack handles the segmentation.

What to Do Next

You've set up your first link, confirmed it works, and established the habits that keep link management from becoming a mess. That's the foundation.

Where you go from here depends on what you're actually trying to accomplish. If your goal is saving time on repetitive linking tasks, the automation side of Pretty Links is worth exploring.

Pretty Links automation strategies for small teams walks through how to use auto-linking and campaign workflows without overcomplicating a setup built for a small team.

If you're still deciding whether Pretty Links is the right tool for your situation, don't guess.

Our Pretty Links review covers what it actually does well, where it falls short, and what kind of team gets the most out of it — without the sales framing.

And if you're managing multiple sites and wondering whether a different tool might suit one of them better, it's worth knowing your options before you commit.

Pretty Links vs. alternatives compares the main contenders side by side so you can make a clean decision.

There's also a dedicated list of the best Pretty Links alternatives if you want to browse what else exists in this category.

If you've done the checks, your team knows who owns which links, and you've got a naming convention in place — you're in better shape than most small teams running link management. The only thing left is to actually go live.

Start Using Pretty Links

If you're still working through the initial configuration and want to revisit any earlier steps, the full walkthrough is on the Pretty Links tutorial page.

Read the Full Pretty Links Tutorial

Not sure Pretty Links is right for your team's setup? Compare your options before committing.

See Pretty Links Alternatives