Promptwatch Logo

LogRocketBot

LogRocketBot is the asset-fetching client associated with LogRocket session replay.
UnverifiableLogRocketBot
MonitoringAnalytics

What is LogRocketBot?

LogRocketBot is the asset-fetching client associated with LogRocket session replay. LogRocket records changes to a page, while its backend downloads and caches the CSS, JavaScript, and images needed to play that session back. The same cached asset can be used in more than one recording instead of being uploaded with every session.

This is a supporting part of an analytics product, not a crawler building a page index. Its requests should point to resources used by recorded pages. LogRocket advises customers to keep old, versioned assets available because a replay may still need them after the live application has moved to a newer build.

Private applications need a little extra setup. LogRocket documents a baseHref option that can direct playback requests to a public host with the same assets and folder structure. Without accessible styles and images, the recorded DOM may still exist but the replay can look incomplete or wrong.

None of this has a documented role in AI search or model training. Blocking the asset cacher affects LogRocket playback, not whether a page can appear in an AI answer. The record supplies the token LogRocketBot, but LogRocket does not publish a DNS check or scanner address list for that identity, so the header alone cannot authenticate a request.

Not relevant for AI search

Is LogRocketBot relevant for AI search?

No. LogRocketBot is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

LogRocketBot runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle LogRocketBot

Allow these requests when your team uses LogRocket and needs reliable session playback. If LogRocket is not installed, inspect the requested asset paths and the surrounding session activity before deciding that a matching header is legitimate.

The directory records a stable token and marks the bot as respecting robots.txt:

User-agent: LogRocketBot
Disallow: /

That support is recorded, but LogRocket's public asset-caching documentation does not explain how the bot parses or refreshes robots rules. Treat the exact compliance behavior as undocumented and confirm the result in server logs. After any restriction, open a recent replay and check its layout and images. Use a server or WAF rule when access must be enforced.

Examples

  • A support engineer sees `LogRocketBot` request an older hashed stylesheet used by yesterday's recording. Restoring that file fixes the unstyled replay.
  • A team keeps its application private but mirrors playback assets on a public host and points LogRocket to that host with `baseHref`.

Frequently asked questions about LogRocketBot

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

It fetches and caches web assets for LogRocket session replay. Those assets help LogRocket reconstruct how a recorded page looked.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard