🗺️ Fix a Local SEO Heatmap Stuck Fetching

🔍 Why Does This Happen?

A Local SEO heatmap can get stuck on fetching data for several reasons:

• The ranking data request timed out in the background before results were returned.
• Your Google Business Profile (GBP) account hit its API quota limit, temporarily blocking new data pulls.
• A one-time sync error caused the scan to stall without displaying an error message.
• A slow polling cycle meant the system could not confirm whether data had arrived or not.

In most cases your historical baseline data is safe — the issue is with the active scan, not stored results.

✅ Step-by-Step Resolution

1. Wait 10–15 minutes. Background ranking fetches can take longer than expected. If the spinner is still showing after 15 minutes, continue to the next step.
2. Refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to do a hard refresh. This clears cached states that can falsely show a fetch in progress.
3. Navigate back to Local SEO Heatmaps. Go to Left sidebar → Local → Local SEO Heatmaps. Check whether the heatmap now shows data or a clear error message.
4. Check your GBP Project connection. Go to Left sidebar → Local → GBP Projects and confirm your GBP account is connected and the project status is active. A disconnected account will cause all heatmap scans to stall.
5. Re-import or refresh the heatmap. On the Local SEO Heatmaps page, use the Import from Google Business Profile button to re-sync your location data, or click Save to trigger a new scan cycle. This will not overwrite existing historical data.
6. Verify historical data is intact. After the page reloads, scroll through your heatmap results to confirm previous scans are still visible. Baseline data is stored separately from active scan results and is not affected by a stalled fetch.

⚠️ API Quota Limit

If your heatmap gets stuck repeatedly, your GBP account may have reached its daily API quota. When quota is exhausted, new ranking fetches are queued but cannot complete until the quota resets — typically within 24 hours.

• Avoid triggering multiple manual refreshes in quick succession, as each attempt consumes quota.
• Wait until the following day and allow the heatmap to run its scheduled scan automatically.
• If you manage multiple GBP locations, consider spacing out heatmap scans to reduce quota consumption.

🛠️ If the Heatmap Is Still Stuck

If you have completed all the steps above and the heatmap remains on fetching data after more than an hour, collect the following details before contacting support:

• The name of the affected heatmap or GBP project (e.g., Starstone Fellowship).
• How long the heatmap has been stuck.
• Whether the issue affects one location or multiple locations.
• Any error messages you see on screen.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.