Data Storytelling in Action: Cleansing Bot Traffic for Hancock Hotel’s Local SEO

Posted by: Lhealene Bautista Lazaro Date Posted: July 18, 2025
Back to Case Studies

Issue

While reviewing Hancock Hotel’s Local SEO performance, we spotted a spike in website sessions from Ashburn, Virginia—a location unrelated to the hotel’s target market in Findlay, Ohio. This anomaly was inflating reported numbers and potentially misleading the client about their true audience.

Solution

Root Cause Analysis (The 5 Whys Approach)

  1. Why is Ashburn, VA a top traffic city? – Unexpected for a local hotel—prompted deeper investigation.
  2. Why so much Ashburn traffic? – No logical user reason; Ashburn is not a relevant market.
  3. Why would Ashburn generate non-genuine traffic? – Found it’s a major data center hub—home to cloud/bot traffic.
  4. Why does this matter? – Bot traffic skews metrics, leading to inaccurate reporting.
  5. Why filter it out? – To ensure data reflects real, local user engagement and supports smarter marketing strategy.

Data Deep Dive & Action

  • Cross-referenced GA4, GBP, and NinjaCat data to confirm the anomaly and its source.
  • Updated monthly reporting to exclude Ashburn sessions:
    • Before filtering: 1,909 sessions
    • After filtering: 2,008 sessions (clearer quality, more actionable)
  • Delivered a narrative, not just numbers—explained the “why” and business impact to both the team and client.

Recommendations

  • Continue monitoring for similar data anomalies.
  • Focus reporting and optimization on genuine local markets.
  • Maintain transparency with the client around data adjustments.

Achievement

  • Identified and diagnosed a major reporting anomaly: Discovered Ashburn is a global data center hub, likely generating bot or automated traffic.
  • Data clarity: Filtered out non-human sessions, resulting in more accurate, actionable insights.
  • Client trust: Communicated findings transparently, building credibility and enabling better decision-making.

Snippet/Screenshot/Link

Original Traffic Report (with Ashburn):
Sessions including Ashburn – 1,909

Filtered Traffic Report (Ashburn excluded):
Sessions excluding Ashburn – 2,008