This Site Cannot Be Reached After URL Rename: Root Cause and Fix

When you rename a SharePoint site URL in the admin center, the new URL should redirect visitors automatically. But sometimes users see a browser error saying “This site cannot be reached” instead of the expected site. This problem occurs because SharePoint’s automatic redirect rule is missing or broken after the rename operation. This article explains why the redirect fails and provides a step-by-step fix to restore access to the renamed site.

Why the Redirect Fails After a SharePoint URL Rename

When you rename a SharePoint site URL using the admin center, SharePoint should create a 301 redirect from the old URL to the new URL. This redirect tells browsers and search engines to send traffic to the new address automatically. The redirect is stored as a property on the site collection object in SharePoint Online.

The redirect fails for several reasons:

Incomplete rename operation. The rename process in the admin center can time out or fail silently, especially for large sites with many subsites or complex permissions. When the operation does not complete fully, the redirect rule is never written to the site collection.

Missing redirect property. Even when the rename appears to succeed in the admin center, the RedirectUrl property on the site collection may remain empty. This leaves the old URL with no forwarding instruction, causing the “cannot be reached” error.

Browser or network cache. Sometimes the redirect exists but the browser cache or a local proxy server serves a stale DNS record or a cached error page. This is less common but can mimic the same symptom.

Tenant-level restrictions. In rare cases, a tenant policy or a custom URL namespace prevents the redirect from being applied. This typically only affects tenants with custom vanity domains or strict URL policies.

Steps to Fix a Broken Redirect After a URL Rename

Use the following method to check the redirect status and repair it. You need the SharePoint Online Management Shell and global admin or SharePoint admin permissions.

Method 1: Verify and Repair the Redirect Using PowerShell

1. Connect to SharePoint Online Management Shell
   Open Windows PowerShell as an administrator. Run Connect-SPOService -Url https://yourtenant-admin.sharepoint.com and sign in with your admin credentials.
2. Check the current redirect property
   Run Set-SPOSite -Identity https://yourtenant.sharepoint.com/sites/oldsiteurl -RedirectUrl https://yourtenant.sharepoint.com/sites/newsiteurl. Replace the old and new URLs with your actual site paths. This command sets the redirect even if one already exists and overwrites any empty or broken value.
3. Verify the redirect was applied
   Run Get-SPOSite -Identity https://yourtenant.sharepoint.com/sites/oldsiteurl | Select RedirectUrl. The output should show the new site URL. If it shows blank or an incorrect URL, repeat step 2.
4. Test the redirect in a private browser window
   Open an InPrivate window in Edge or a private window in Chrome. Navigate to the old site URL. You should be automatically forwarded to the new URL. If the redirect works, close the private window and clear your regular browser cache.

Method 2: Use the Admin Center to Re-Run the Rename Operation

1. Go to the SharePoint admin center
   Sign in to https://admin.microsoft.com. In the left navigation, select Admin centers and then SharePoint.
2. Locate the site that was renamed
   Under Sites, select Active sites. Find the site with the new URL. Click the site name to open the details panel.
3. Check the current site address
   In the details panel, look under General for Site address. It should show the new URL. If it still shows the old URL, the rename did not complete. Click Edit next to the address, enter the new URL, and save. This re-runs the rename process and should create the redirect.
4. Wait and test
   Wait 5 minutes for the operation to finish. Then test the old URL in a private browser window. If the redirect still does not work, use Method 1.

Method 3: Tenant-Level Fallback Redirect

If the site-level redirect continues to fail, you can create a tenant-level redirect that forwards all traffic from the old site URL to the new one. This method is a last resort because it applies to the entire tenant and may interfere with other redirects.

1. Connect to SharePoint Online Management Shell
   Run Connect-SPOService -Url https://yourtenant-admin.sharepoint.com with admin credentials.
2. Set the tenant-level redirect
   Run Set-SPOTenant -SiteRedirectUrl https://yourtenant.sharepoint.com/sites/newsiteurl. This redirects all traffic from the old URL to the new URL at the tenant level.
3. Test the redirect
   In a private browser window, navigate to the old site URL. You should be forwarded to the new URL. If this works, the site-level redirect was missing or corrupt. You can later remove the tenant-level redirect by running Set-SPOTenant -SiteRedirectUrl $null after confirming the site-level redirect works.

If SharePoint Still Has Issues After the Main Fix

Old URL shows a 404 error after rename

A 404 error means the old URL is not found and no redirect exists. Run the PowerShell command from Method 1 again to set the redirect. If the error persists, check if the site was deleted instead of renamed. In the admin center, go to Deleted sites to see if the old site appears there. If it was deleted, restore it and then re-run the rename.

Redirect works for some users but not others

This symptom points to a browser cache issue. Instruct users to clear their browser cache and cookies. Alternatively, have them use a private or incognito window to test the redirect. If the problem persists for all users, the redirect may be missing the RedirectUrl property for a specific region or content delivery network node. Wait 30 minutes and test again.

New site works but old URL shows a SharePoint error page

An error page on the old URL indicates the redirect exists but the destination site has a permission or configuration issue. Check the new site’s permissions and sharing settings. Ensure the site is not in read-only mode and that the user has at least read access. If the site is a communication site, verify the site is not set to “No access” for external users.

Site-Level Redirect vs Tenant-Level Redirect: Key Differences

Item	Site-Level Redirect	Tenant-Level Redirect
Scope	Affects only the specific old URL	Affects all URLs in the tenant
Created by	Admin center rename or Set-SPOSite -RedirectUrl	Set-SPOTenant -SiteRedirectUrl
Persistence	Stored on the site collection object	Stored on the tenant configuration
Use case	Standard fix for a single broken redirect	Last resort when site-level redirect fails
Removal	Set RedirectUrl to $null	Set SiteRedirectUrl to $null

The “This site cannot be reached” error after a SharePoint URL rename is almost always caused by a missing or broken redirect rule. You can fix it by using the PowerShell Set-SPOSite command with the RedirectUrl parameter. If the issue persists, check the admin center to confirm the rename completed and use a tenant-level redirect as a fallback. Always test in a private browser window to rule out cache problems.