Manage Redirects When Changing Page URLs

Why URL Changes Are Risky

Every URL on your site accumulates value over time:

Search engines have indexed it and ranked it for certain queries
External sites have linked to it, passing authority
Bookmarks, email signatures, and social profiles may reference it
Analytics tools have tracked its traffic

When you change a URL without a redirect, all of that value disappears. The new URL starts from zero. Old links become 404s. Search engines eventually deindex the old URL. External traffic drops.

The fix is simple: when you change a URL, set up a 301 redirect from the old URL to the new one. This tells search engines and browsers that the content has moved permanently, transferring most of the value to the new URL.

Before You Change Anything: Assess the Impact

Not every URL is worth preserving. Before changing, ask:

Does the current URL have inbound traffic? Check Google Analytics or Pixelesq's built-in analytics. If it has 0 visits per month, the impact of a change is minimal.
Does it rank for search queries? Check Google Search Console for impressions and clicks on the old URL. High-performing URLs need more care.
Are there backlinks? Use Ahrefs, Semrush, or Google Search Console to see which external sites link to the URL. Links are valuable; preserving them is worth the effort.
Is the URL referenced internally? Search your own site for links to the URL. You will need to update these too.

For high-value URLs (ranked, linked, trafficked), follow every step in this guide. For low-value URLs (internal drafts, test pages), you can skip the redirect step without major consequence.

Step 1: Change the Page Slug

Open the page in Pixelesq and update its slug to the new URL. The page slug is in the page settings or detail view. For example, change /old-page to /new-page.

Save the change. The page is now accessible at the new URL. However, the old URL now returns 404. This is the critical window where redirects matter.

Step 2: Create a 301 Redirect from Old to New

Go to Settings > Redirects in your sidebar. Click + create. In the dialog:

Source Path: the old URL (e.g., /old-page)
Destination Path: the new URL (e.g., /new-page)
Status Code: 301 (permanent redirect). Critical for SEO.
Match Type: exact (unless you are redirecting a whole section, in which case use prefix)
Notes: "Redirect after slug change on YYYY-MM-DD" so future you remembers why this exists

Click save. The redirect is active immediately. Visitors to the old URL are now automatically redirected to the new URL.

[Screenshot: Create redirect dialog with source and destination filled in]

Step 3: Update Internal Links

Redirects are a safety net, not a replacement for clean internal linking. Every internal link in your site that still points to the old URL should be updated to the new URL directly. Reasons:

Direct links pass full SEO value. Redirected links lose a small amount (though 301 redirects preserve most of it).
Redirects add a fraction of a second of latency. Direct links are faster.
Redirects accumulate over time and become hard to audit. Clean links are maintainable.

Use Pixelesq's link health checker to find internal references. Open any page and click the link health icon. Broken or redirected links show up. Update them to point directly to the new URL.

Step 4: Verify the Redirect Works

Test the redirect in an incognito browser window to avoid cached results:

Visit the old URL (yourbrand.com/old-page).
Confirm the browser automatically redirects to the new URL (yourbrand.com/new-page).
Confirm the final URL in the browser is the new one, not the old one.
Check that the page loads correctly (no 404 or 500 errors).

Also test with httpstatus.io or redirect-checker.org to verify the HTTP status is 301, not 302. 301 is permanent (SEO-friendly). 302 is temporary (does not transfer SEO value).

Step 5: Submit the New URL to Google for Re-indexing

Google will eventually discover the new URL and the redirect from the old URL, but you can speed it up. In Google Search Console:

Open the URL Inspection tool.
Enter the new URL.
Click Request Indexing.

This tells Google to prioritize the new URL for crawling. Within a few days, Google re-crawls and updates its index. The old URL stays in the index for a while (pointing to the redirect) before being deindexed; the new URL takes its place.

Pixelesq auto-submits your sitemap to Google whenever pages are published, so the new URL should appear in your next sitemap submission. URL Inspection just accelerates the process for specific URLs.

Handling URL Structure Migrations

Sometimes you are not changing one URL but an entire section (e.g., moving all blog posts from /blog to /articles). The principles are the same, but you use prefix matching instead of exact matches:

Change all page slugs (or the section root) to the new structure.
Create a single prefix redirect: source /blog, destination /articles, match type prefix, status 301. This one rule handles every URL under /blog/* automatically.
Verify with a few test URLs.

Prefix matching is a huge time saver. One rule replaces dozens of individual rules.

Pro Tips

Never change a URL without a redirect. Even for low-traffic pages. The cost of creating a redirect is 30 seconds. The cost of a broken link is potentially ongoing.
Do not chain redirects. If /a redirects to /b, and /b redirects to /c, fix this by making /a redirect directly to /c. Chains waste SEO value at every hop.
Keep old redirects even after content is updated. A redirect you set up two years ago might still be needed if someone out there still has a link to the old URL. Only delete redirects for URLs that clearly have no remaining traffic.
Document URL migrations. For big URL changes, keep a spreadsheet of every old URL, its new URL, and the date you migrated. Makes troubleshooting and auditing easier.
Use descriptive slugs that are unlikely to change. The best way to avoid the cost of URL changes is to pick good slugs up front. Avoid slugs tied to dates ("/2024-sale") or marketing campaigns ("/summer-launch") that go stale.

Troubleshooting

Old URL is returning 404 instead of redirecting: The redirect is not active or is misconfigured. Check that you saved the redirect in Settings > Redirects, that the source path is an exact match for the old URL (with or without trailing slash depending on your setup), and that the redirect is enabled (not disabled).

Redirect works but Google still shows the old URL in results: This is normal for a few weeks. Google takes time to re-crawl, follow the redirect, and update its index. Request indexing in GSC to speed it up. Expect full replacement within 2-4 weeks for most sites.

Redirect is working but I lost rankings: Some ranking loss is normal during a URL migration. 301 redirects preserve most but not all SEO value. If rankings drop significantly and do not recover within a month, investigate deeper causes: did the new page content change significantly, is the new URL structure worse, did you break internal linking?

Browser is caching the old URL: 301 redirects are aggressively cached by browsers. If you are testing changes and getting confused by cached redirects, use an incognito window. After launching, real visitors may also see stale cached redirects for a day or two after changes; this is normal.

I need to undo a URL change: Change the slug back to the old URL and either delete the redirect or swap its source and destination. The content is unchanged; only the URL mapping moves back. Update internal links to point to the original URL.

FAQ

How long should I keep a redirect active after changing a URL?

Keep 301 redirects indefinitely. They cost nothing to maintain, and external sites or old bookmarks may still reference the old URL years later. The only reason to remove a redirect is if you confirm (through analytics or server logs) that the old URL receives zero traffic for a long time, and even then, keeping it is rarely harmful.

Do I need to update external sites that link to the old URL?

Not required because the 301 redirect handles it, but ideally yes. Contact sites with significant inbound links and ask them to update. Direct links pass slightly more SEO value than redirected ones. For most external links, the redirect is enough.

Can I change the URL of a page that is currently ranking in Google?

Yes, but be prepared for temporary ranking fluctuations during the migration. With a proper 301 redirect, most rankings recover within 2-4 weeks. High-authority URLs with strong backlinks recover faster. Brand-new sites or pages may see longer recovery times.

What happens if I delete the redirect after a URL change?

The old URL returns a 404. Visitors with old links see an error. Search engines eventually deindex the old URL. Any remaining SEO value from external backlinks is lost. Keep redirects active indefinitely to preserve this value.

Can I redirect from a URL I never used to a URL I use now?

Yes. Redirects do not require the source URL to have ever been a real page. This lets you redirect typos, short URLs, or vanity URLs to real pages. Example: redirect /demo to your full Calendly URL, even though /demo was never a page on your site.

Are there any URLs Pixelesq does not let me redirect?

You cannot redirect the root URL (/) in most cases because it maps to your homepage, and redirecting your homepage somewhere else breaks most navigation. For other URLs, redirects work broadly. If a specific URL cannot be redirected, it may conflict with an existing Pixelesq internal route; contact support for guidance.

How to Manage Redirects When Changing Page URLs