---
title: "Discussion on \"meta-externalagent and meta-webindexer: crawlers were a third of my visitors\" | Hashnode"
description: "Discussion on \"meta-externalagent and meta-webindexer: crawlers were a third of my visitors\". Meta's crawlers run JavaScript, so they fire analytics like a 1920x1080 Chrome. Crawlers were 31% of my week's visitors. How I filtered them."
url: "https://hashnode.com/posts/meta-externalagent-webindexer-analytics/6b02700936535fe8c8d4b748"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [meta-externalagent and meta-webindexer: crawlers were a third of my visitors](https://mohamedgado.hashnode.dev/meta-externalagent-webindexer-analytics?utm_source=hashnode&utm_medium=feed)

Meta's crawlers run JavaScript, so they fire analytics like a 1920x1080 Chrome. Crawlers were 31% of my week's visitors. How I filtered them.

4h ago · 5 min read · mohamedgado.hashnode.dev  
Read the article

-   [#analytics](https://hashnode.com/tag/analytics)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#seo](https://hashnode.com/tag/seo)

## Written by

[Mohamed Gado](https://hashnode.com/@mohamedgado)

@mohamedgado · Tanta, Egypt

  
[View profile](https://hashnode.com/@mohamedgado)

Staff Software Engineer · React, Next.js, React Native · Building Masareef, Rafiq & Nafis

Staff Software Engineer, 6+ years. I build React, Next.js, React Native and TypeScript apps for fintech and Arabic users, including Masareef, Rafiq and Nafis. Originals live at mohamedgado.com/writing.

## Responses 1

Markdown supported · ⌘↵ to post

[Hafiz Waleed Ahmed](https://hashnode.com/@hafizwaleedahmed5)

[23m ago](https://hashnode.com/posts/meta-externalagent-webindexer-analytics/6b02700936535fe8c8d4b748/comment/6b02a598bf10f5aed4c1234e)

The useful part is treating the user agent as the source of truth, not screen size or navigator.webdriver. Meta's crawlers render like a normal desktop Chrome, so a filter that only drops HeadlessChrome or webdriver=true will keep counting them as people. Matching the crawler token before the analytics beacon, and reusing that same pattern on older queries, keeps live traffic and dashboards aligned. It is also worth testing the regex against real device names so a loose "bot" match does not drop phones such as Cubot.
