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.
