Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Services blocked (ignored) by Prerender.io

This article contains a comprehensive list of services that will be ignored during rendering. This is done to avoid wasting resources and to speed up the rendering process.

Prerender renders your pages for bots only and returns a clean HTML snapshot that’s fast to generate and safe to cache. To keep renders predictable and to avoid triggering third‑party trackers or heavy media requests, Prerender blocks the services and file types below by default (they are not fetched or executed during rendering). This does not affect what human visitors load in their browsers.

Why Prerender blocks these

  • Bots don’t need ads, analytics, or chat widgets. Prerender focuses on your main content, not auxiliary resources like images or code, which aligns with how our service decides what to render for crawlers. This keeps the snapshot lean and relevant. 

  • Speed & stability. Avoiding asset-heavy requests (fonts, videos, large images) reduces render time and timeouts, improving cache quality and throughput. 

  • Accurate metrics & compliance. Blocking analytics/ad calls prevents inflating pageviews, ad impressions, session recordings, or firing consent tooling for bot traffic. 

Blocked by default:

Analytics & Tracking Services

  • Google Analytics (google-analytics.com)

  • Google Tag Manager (www.googletagmanager.com)

  • Google Ads related services

    • googleads.g.doubleclick.net

    • pagead2.googlesyndication.com

    • tpc.googlesyndication.com

    • partner.googleadservices.com

  • Mixpanel (api.mixpanel.com)

  • Segment.io (api.segment.io)

  • DoubleClick Stats (stats.g.doubleclick.net)

  • Yandex Metrica (mc.yandex.ru)

  • Woopra (woopra.com)

  • Heap Analytics (cdn.heapanalytics.com)

  • Inspectlet (hn.inspectlet.com)

Chat & Support Widgets

  • Olark (static.olark.com)

  • GetClicky (static.getclicky.com)

Fonts & Asset Networks

  • Typekit / Adobe Fonts (use.typekit.net)

  • Fast Fonts (fast.fonts.com)

Other Services

  • New Relic Browser agent (js-agent.newrelic.com)

  • Tapfiliate (beacon.tapfiliate.com)

  • Cookie Law / consent manager (cdn.cookielaw.org)

  • Browser Update banner (browser-update.org)

  • Brightcove players (players.brightcove.net)

URL Fragments (specific paths/patterns)

  • FullStory recordings (fullstory.com/rec)

  • Navilytics (navilytics.com/nls_ajax.php)

  • Optimizely events (log.optimizely.com/event)

  • YouTube embeds (youtube.com/embed)

File Extensions (Media & Assets)

  • Fonts: .ttf, .eot, .otf, .woff
  • Images & Docs: .png, .gif, .tiff, .pdf, .jpg, .jpeg, .ico, .svg, .webp
  • Audio: .m4a, .flac, .mp3, .wav, .wma, .aac
  • Video: .mp4, .webm, .avi, .flv, .mkv, .mov, .wmv

FAQ

Can I make an exception (allowlist) for something on this list?
In most cases, it’s better to include SEO‑critical content directly in your HTML and keep third‑party trackers disabled for bot renders. However, if you're sure you want to whitelist one of these services contact Prerender Support and we’ll make it happen for you.

Do these blocks affect human visitors?
No. These rules apply only to the headless render that produces HTML for bots. Your production site for users continues to load analytics, ads, media, and chat widgets as usual.

Will previews (e.g., social shares) still work?
Yes—make sure your preview metadata (Open Graph/Twitter cards) is in the HTML. Social crawlers read the tags from the rendered snapshot; they don’t need the analytics or embed scripts to run.

Related reading

 

Was this article helpful?