CrushPress.AI

Tag: Reporting Bug

  • Google Discover Bug Leads to Misleading Data in Search Console

    Google Discover Bug Leads to Misleading Data in Search Console

    Have you recently noticed a decline in clicks and impressions around May 7th to May 8th? Don’t worry; it’s just a reporting glitch.

    I discovered that Google has confirmed a bug affecting the Discover report in Google Search Console. It turns out there was a ‘logging’ error with the data, which has resulted in a drop in clicks and impressions during May 7th to May 8th, 2026.

    Google assures us that this is merely a ‘data logging only’ issue, and it hasn’t impacted the actual positioning in Google Discover.

    The issue: Google stated once again that a data logging error caused the discrepancies in the Discover report between May 7th and 8th, 2026.

    As per Google’s post, this bug might have caused a ‘decrease in clicks and impressions in the Discover performance report.’

    Why it matters: Numerous publishers, possibly including myself, saw a dip in performance metrics. It’s crucial to note that this is likely due to this bug.

    Make sure to annotate your reports and inform your stakeholders that the Discover data from May 7th to May 8th is inaccurate and should be disregarded.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot
  • Google Rectifies Search Console Data Glitch — Moving Forward

    Google Rectifies Search Console Data Glitch — Moving Forward

    It feels like a moment of relief as Google recently announced a resolution to a longstanding data logging issue within Google Search Console. This glitch affected data between May 13, 2025, and April 27, 2026, spanning approximately 50 weeks. However, it’s important to note that while the root cause has been addressed, historical data from this period remains unfixed.

    Google shared this update in a rather understated post, bringing light to a problem that many of us have been grappling with for quite some time. According to their post, “A logging error prevented Search Console from accurately reporting impressions from May 13, 2025, until April 27, 2026. This issue has been resolved.” It was a relief to hear, but also a bit frustrating knowing that impressions, CTR, and average position data were affected for such a significant period. Thankfully, clicks weren’t influenced by this error, which was some consolation.

    As I sift through my Search Console data, I must remind myself of this anomaly, particularly when analyzing metrics from that problematic timeframe. The good news is that any data collected from this point forward should be accurate.

    ```json { "alt": "Google Search Console logging error notice for April 2026, affecting data reporting for impressions and clicks.", "caption": "Google Search Console reports a logging error impacting impression data from April 16-27, 2026. Fortunately, the issue has been resolved, ensuring accurate metrics moving forward.", "description": "This image shows a notice from Google Search Console regarding a logging error that affected the reporting of impressions and clicks from April 16 to April 27, 2026. The issue primarily impacted 'Job listing' and 'Job details' search appearance types and was resolved as of April 3. It outlines the period affected and clarifies that only data logging was impacted, not the actual clicks, making it crucial for users relying on accurate data metrics. Keywords: Google Search Console, logging error, data reporting, impressions, clicks." } ```

    Further confirmation came from John Mueller on Bluesky, who reiterated that past data would not be retroactively corrected, but the issue has indeed been resolved going forward.

    This development is crucial for all of us who rely heavily on precise data for SEO strategies. If your impressions appear lower and, consequently, your CTR and average position figures seem skewed during this period, this is likely why.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot
  • Google’s Job Data Bug: What’s Happening with Search Console?

    Google’s Job Data Bug: What’s Happening with Search Console?

    I’ve noticed that Google is currently investigating an issue with the Google Search Console. Specifically, this concerns the data logging and reporting of “Job listing” and “Job details” search appearance filters.

    On April 16th, a bug began affecting how this data is logged, causing Google to report zero clicks and impressions for job-related reports. Although traffic is still being received, it’s not being recorded correctly.

    What Google said. According to an update from Google, “A logging error is preventing Search Console from reporting impressions and clicks for ‘Job listing’ and ‘Job details’ Search appearance types from April 16, 2026 onward. We’re working to resolve this issue. This issue affects data logging only.”

    Complaints. I’ve also seen numerous SEOs voicing their concerns on social media, as shared in a tweet by Max Peters. The bug seems to impact impressions and clicks, but the traffic still comes through other measurement methods like google_jobs_apply UTM.

    Why we care. If you’ve noticed a decrease in search data for job listings, rest assured, it’s due to this bug on Google’s side. Your listings are likely still active and receiving traffic, although this isn’t reflected in Search Console at the moment.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot
  • Google Search Console Bug Fix: What You Need to Know

    Google Search Console Bug Fix: What You Need to Know

    Recently, I discovered that Google is addressing a pesky bug in Search Console that has been inflating impression counts. Since May 13, 2025, there has been a logging error misreporting impression data, and Google has assured us that corrections will be rolling out in the coming weeks.

    This bug has been a longstanding issue, and I was relieved to hear that Google is finally correcting it. They’ve updated their Data anomalies in Search Console page with the following message:

    “A logging error is preventing Search Console from accurately reporting impressions from May 13, 2025 onward. This issue will be resolved over the next few weeks; as a result, you may notice a decrease in impressions in the Search Console Performance report. Clicks and other metrics were not affected by the error, and this issue affected data logging only.”

    I also read a statement from a Google spokesperson who confirmed: “We identified a reporting error in Search Console that temporarily led to an over-reporting of impressions from May 13, 2025 onward. Bug fixes are being implemented to ensure accurate reporting.”

    So, what’s changing? As Google works on these fixes, we can expect changes in how impressions are logged and reported. With this rollout, I anticipate seeing a drop in impression numbers in my Performance report, although clicks and other metrics remain unaffected.

    The timeline of this issue stretches back to May 13, 2025, and it has persisted until now. Google mentioned that the complete correction will take several weeks for full implementation across various reporting areas.

    Why is this important to me? If my Google Search Console impression numbers change in the near future, it’s likely due to this bug fix. Staying informed helps me understand these shifts better.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot
  • Google Search Console Bug: Missing Data Before December 15

    Google Search Console Bug: Missing Data Before December 15

    I’ve noticed a peculiar issue with the Google Search Console’s page indexing report—it seems to be missing data prior to December 15th. Many of us are likely scratching our heads over this, and it appears to be some kind of reporting glitch affecting everyone.

    So far, Google hasn’t provided any comments on this widespread issue. The absence of this data is creating challenges for all of us trying to analyze our website performance accurately.

    What it looks like. To give you a clearer picture, Vijay shared a screenshot on X. You can verify this by checking your own page indexing report, and you’ll likely see the same gaps.

    ```json { "alt": "Graph showing indexed and not indexed pages with data missing from 11/25/25 to 12/6/25.", "caption": "Tracking search engine indexing, this graph highlights a missing data gap while visualizing indexed versus not indexed pages.", "description": "This image displays a graph illustrating indexed pages versus not indexed pages for a website over a specific period. The graph shows a notable gap labeled 'Data Missing' from November 25, 2025, to December 6, 2025. Indexed pages are colored in green, while not indexed pages are in gray. The data trend continues post-gap, indicating increasing indexing activity. With 1.08 million pages indexed and 3.57 million not indexed, the image serves as a visual tool for SEO analysis." } ```

    Why it matters to us. I plan to check back in the next few days to see if the data returns or if Google releases any updates about this problem. Currently, we’re all in the same boat, unable to access the prior data, which hinders our ability to run accurate reports and analyses.

    Let’s hope Google resolves the issue soon, enabling us to resume our regular reporting and analysis for those missing data ranges.

    Inspired by this post on Search Engine Land.

    crushpress.ai community screenshot