This article explains why your UX signals count can change week over week — sometimes significantly — and what steps you can take to investigate and confirm the numbers you are seeing are accurate and up to date.
🔍 Common Causes of UX Signal Fluctuations
UX signals are aggregated from real user behavior data collected across your tracked pages. Because this data is dynamic, counts can shift between reporting windows for several legitimate reasons:
- Rolling data windows: UX signals are typically calculated over a rolling time period. As older data ages out and newer data enters the window, totals naturally rise and fall — a spike one week may simply reflect a short burst of activity that is no longer within the active window the following week.
- Crawl and data refresh timing: Signal counts update when a data refresh occurs. If a refresh runs mid-cycle or is delayed, the count shown may reflect an incomplete picture until the next full refresh completes.
- Page indexation changes: If pages are added, removed, or temporarily de-indexed between periods, the number of pages contributing signals will change, directly affecting the total count.
- Traffic volatility: A promotional campaign, viral content, or a seasonal event can temporarily inflate signal counts. Once that traffic subsides, counts return to their baseline.
- Data source connectivity: If your connected data source (such as Google Search Console) experienced an interruption or a gap in data reporting during a given period, signals derived from that source may be incomplete for that window.
🛠️ Steps to Investigate a UX Signals Fluctuation
- Wait for the current data cycle to complete. If a refresh is in progress or was recently triggered, allow it to finish fully before comparing counts. Counts viewed mid-refresh may be incomplete and can appear lower or higher than the final settled value.
- Check the date range applied to your report. Confirm which time window is selected in the view where UX signals are displayed. A change in the selected window — even by one day — can shift which data points are included and excluded, producing an apparent drop or rise.
- Compare the two periods and look for coinciding events. Note the exact dates when the count was higher versus lower. Cross-reference those dates with your own analytics for any events such as campaigns, site changes, or technical outages that coincide with the change.
- Review your connected data source status. Confirm that any integrated data sources (such as Google Search Console) are still connected and actively reporting within your project settings. A disconnected or re-authenticated integration can create a gap in signal collection that reduces counts for the affected period.
- Check for page-level changes. If pages were added to or removed from your tracked project during either period, the eligible page count will differ, which directly affects the total UX signals count. Review your tracked pages list to identify any additions or removals that align with the timing of the fluctuation.
- Escalate if the cause remains unclear. If you have worked through the steps above and cannot identify a clear reason for the fluctuation, contact our support team. When you reach out, please have the following ready: your project name, the specific reporting periods you are comparing, any error messages you have seen, and a screenshot of the signal counts in question.
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.