Hub Navigation Does Not Update on Associated Sites: Fix

When you update the navigation on a SharePoint hub site, the changes may not appear on associated sites even after several hours. This problem occurs because SharePoint caches hub navigation data at the site collection level and refreshes it on a scheduled interval rather than instantly. This article explains why the navigation cache delays updates and provides a step-by-step method to force a refresh so associated sites display the latest hub navigation links.

Why Hub Navigation Fails to Update on Associated Sites

SharePoint hub sites store navigation settings in a dedicated property bag on the hub site itself. When you modify the hub navigation — adding, removing, or reordering links — SharePoint writes the changes to the hub site’s navigation storage. Associated sites do not read this data in real time. Instead, each associated site caches a copy of the hub navigation when a user first visits it after a change. The cached version persists for up to 24 hours or until the site’s application pool recycles.

The delay is by design. SharePoint uses caching to reduce server load and improve page load performance. However, this design means that edits to hub navigation can take a full day to propagate to all associated sites. The cache is stored per site collection, so one associated site may show the updated navigation while another still shows the old version.

Another common cause is that the associated site has lost its connection to the hub. If the hub site association is broken — for example, after a site move or a permissions change — the navigation cannot update because the link between the sites no longer exists.

How Hub Navigation Inheritance Works

When a site is associated with a hub, it can either inherit the hub’s navigation or use its own custom navigation. The setting is controlled by a toggle in the site’s navigation settings. If inheritance is turned off, the site ignores all hub navigation updates. This is a frequent source of confusion because administrators assume inheritance is enabled when it is not.

Steps to Force Hub Navigation Updates on Associated Sites

Follow these steps to clear the cached hub navigation and force the associated site to fetch the latest data. Perform the actions on the hub site first, then on each affected associated site.

1. Verify the hub site association in SharePoint admin center
   Go to the SharePoint admin center and select Active sites. Locate the hub site and check that its Hub site column shows the correct hub site ID. Then find each associated site and confirm its Hub site column matches the same ID. If an associated site shows no hub, you must re-associate it.
2. Check hub navigation inheritance on the associated site
   Navigate to the associated site. Click Settings (gear icon) and select Site information. Then click View all site settings. Under Look and Feel, select Navigation. In the Navigation Settings page, ensure the option Inherit hub navigation is set to On. If it is off, switch it on and click OK.
3. Clear the browser cache on the associated site
   On the associated site, press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac) to perform a hard refresh. This bypasses the browser’s local cache and requests a fresh copy of the page from the server.
4. Re-register the associated site with the hub
   If the navigation still does not update, you can force the site to re-register with the hub. In the SharePoint admin center, go to Active sites. Select the associated site. In the command bar, click Hub and then Unregister from hub. Wait one minute. Then select the site again, click Hub, and choose Register as hub site. Select the correct hub site from the list and click Save.
5. Verify the navigation update
   Browse to the associated site again and press Ctrl+F5. The hub navigation should now display the latest links. If it does not, wait 15 minutes and repeat step 4.

If Hub Navigation Still Does Not Update After the Main Fix

The steps above resolve most cases. If the navigation still fails to update, one of the following issues is likely present.

Hub Navigation Cache on the Server Level

SharePoint Online also maintains a server-side cache for hub navigation. This cache refreshes every 15 to 30 minutes under normal load. If you have recently made many changes to the hub navigation, the server may still be processing the updates. Wait 30 minutes and then repeat the browser hard refresh on the associated site.

Associated Site Is Not Properly Connected to the Hub

A site can appear in the hub’s associated sites list but still have a broken connection. This happens when the hub site was deleted and recreated with the same URL, or when the associated site was moved to a different tenant. To fix this, unregister the site from the hub and re-register it as described in step 4 above.

Custom Script or Theme Blocks Navigation Inheritance

If the associated site uses a custom master page or a custom theme that overrides navigation rendering, the hub navigation may not display at all. Check the site’s Master Page settings under Site settings. If a custom master page is applied, switch back to the default Seattle master page and test the navigation again.

Symptom	Cause	Fix
Hub navigation shows old links	Browser or server cache not refreshed	Hard refresh with Ctrl+F5 and wait 30 minutes
Hub navigation is missing entirely	Hub navigation inheritance is disabled	Enable inherit hub navigation in site settings
Navigation updates on some sites but not others	Some associated sites have broken hub association	Unregister and re-register those sites with the hub

The table above summarizes the most common failure patterns for hub navigation updates. Use it to quickly diagnose which fix applies to your situation.

You can now force hub navigation updates on any associated site by clearing the browser cache and re-registering the site if needed. To prevent future delays, schedule hub navigation changes during low-usage periods so the 30-minute server cache window causes minimal disruption. If you manage many associated sites, consider using PowerShell with the Set-SPOHubSiteAssociation cmdlet to bulk refresh associations after a navigation change.