🔍 Overview
If your scheduled Local SEO Heatmap scans are running at a different time than you intended, this article explains what to check and what information to have ready when contacting support for investigation.
🕐 Why the Scan May Run at the Wrong Time
Incorrect scan timing is a known issue that our team investigates on a per-account basis. Possible contributing factors can include how the schedule was configured and how time values are interpreted by the platform, but the exact cause needs to be confirmed by our support team reviewing your specific setup.
🛠️ What to Do If Your Scans Are Running at the Wrong Time
- Note the heatmap name and the schedule you set. Record exactly what time and frequency you entered when creating or last editing the scan schedule.
- Record the actual run times. Check your heatmap history and note the timestamps at which the scans are actually executing.
- Check your account timezone setting. Navigate to your account or profile settings and confirm which timezone is currently configured. Note this value.
- Contact support. Share the heatmap name, your intended schedule, the actual run times observed, and your account timezone with our team so they can investigate the root cause and correct the behavior on the backend.
Because this issue requires backend investigation, do not delete and recreate your heatmap schedule until support has reviewed the problem — doing so may remove the data needed to diagnose the issue.
📋 What to Have Ready When You Escalate
- The name of the affected heatmap(s)
- The scheduled time you entered (including any timezone you selected during setup)
- The actual timestamps the scans ran, copied from the platform
- Your account timezone as shown in your profile or account settings
❓ Still Seeing Incorrect Scan Times?
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.