Promptwatch Logo

HubSpot Page Fetcher

When posting to LinkedIn from Hubspot, images need to be pulled through to LinkedIn when published. The crawler performs this function.
HubSpotHubSpot Page Fetcher
Preview

What is HubSpot Page Fetcher?

HubSpot Page Fetcher supports a specific social-publishing handoff. When someone publishes to LinkedIn from HubSpot, the fetcher pulls the images needed to carry that post through to LinkedIn.

A request from this identity is therefore consistent with a HubSpot social post referencing the page or one of its images. It is automated publishing traffic rather than a reader clicking the resulting LinkedIn post. A failed fetch can interfere with the image handoff, although the record does not define LinkedIn's fallback.

The recorded user agent is HubSpot Page Fetcher/1.0 http://www.hubspot.com/ [email protected]. This identity should not be confused with HubSpot Crawler, which HubSpot documents for SEO scans and content imports. The Page Fetcher record includes no verified IP status or signature-agent URL.

Nothing here assigns HubSpot Page Fetcher an AI indexing or training function. Its documented outcome is an image used in a LinkedIn publishing workflow. Robots.txt support is unknown in the bot metadata, and Cloudflare's bot directory marks the fetcher as not following robots.txt.

Indirectly relevant

Is HubSpot Page Fetcher relevant for AI search?

Indirectly. HubSpot Page Fetcher has no AI product of its own, but its output can end up in the systems that AI answers draw on.

HubSpot Page Fetcher fetches pages to build link-preview cards. It does not feed an AI index, but it reads the same Open Graph and structured metadata that AI systems parse to understand your pages, so clean preview metadata doubles as AI-friendly metadata.

How to handle HubSpot Page Fetcher

If your team publishes LinkedIn posts through HubSpot, allow the fetcher to reach the public images used in those posts. Do not grant it access to private media libraries or draft routes merely because the user agent contains a HubSpot address.

The recorded stable value can be used to state a robots.txt preference:

User-agent: HubSpot Page Fetcher
Disallow: /

Compliance is not established, and Cloudflare's bot directory records it as false. Check later requests or enforce the block at the origin. When troubleshooting an approved workflow, separate this exact identity from HubSpot's other crawlers before changing a broad rule.

Examples

  • A marketing team schedules a LinkedIn post in HubSpot, and the image host logs HubSpot Page Fetcher retrieving the selected public asset.
  • A firewall rule blocks the fetcher from a campaign image, so the team investigates that request without allowlisting HubSpot across its private media routes.

Frequently asked questions about HubSpot Page Fetcher

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

The recorded workflow is publishing to LinkedIn from HubSpot. The fetcher pulls images needed for that social post.

Related bots

Buffer Link Preview Bot

Helps Buffer users create better social media posts by generating rich previews when they share links

Preview

Chrome Privacy Preserving Prefetch Proxy

Chrome's Privacy Preserving Prefetch Proxy service that fetches /.well-known/traffic-advice to enable privacy-preserving prefetch hints.

Preview

Discord Bot

Discord's link preview bot that crawls URLs shared in Discord chats to generate rich previews.

Preview

FacebookExternalHit

Fetches content for shared links on Meta platforms to generate rich previews.

Preview

GitHub Camo

GitHub Camo sits between a GitHub reader and an externally hosted image.

Preview

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