By default, Tallysight widget bundles load from the official Google Cloud Storage CDN atDocumentation Index
Fetch the complete documentation index at: https://docs.tally.site/llms.txt
Use this file to discover all available pages before exploring further.
https://storage.googleapis.com/tallysight-widgets/dist/. Self-hosting lets you serve those same bundles from your own domain — giving you control over script origins and helping mitigate potential Google Site Reputation Abuse (SRA) issues that can arise when third-party scripts are loaded from external domains.
Why self-host?
Serving widget bundles from your own domain has two practical benefits:- SRA mitigation — Google may flag pages that load content from third-party CDNs as part of Site Reputation Abuse patterns. Serving from your own domain helps avoid this.
- Reliability — your delivery depends on your own infrastructure rather than an external CDN.
Self-hosting only affects where the JavaScript bundle files are served from. Widget data (odds, picks, branding) still comes from the Tallysight API.
Option 1: Reverse proxy (recommended)
Set up a reverse proxy on your domain that forwards requests to the Tallysight CDN on demand. This is the recommended approach because you always serve the latest bundles automatically — no manual updates required. Configure your web server or CDN to proxy requests fromhttps://assets.yourdomain.com/widgets/* to https://storage.googleapis.com/tallysight-widgets/dist/*, then point the SDK at your proxy:
Option 2: Manual download and host
Download the widget bundles from the Tallysight CDN and serve them as static files from your own server.Download the bundles
Fetch the widget bundles from
https://storage.googleapis.com/tallysight-widgets/dist/ and copy them to your hosting environment (e.g. https://assets.yourdomain.com/widgets/).Verify your setup
After configuring a custombundleBaseUrl, open your browser’s network panel and confirm that widget bundle requests (e.g. tile.js, feed.js) are being served from your domain rather than storage.googleapis.com.
You can also check that the SDK initialized correctly: