Netlify-hosted static sites use WebmasterID with the same consent-gated script tag. This is exactly how helperg.com itself is deployed.
For GDPR/ePrivacy, load the tracker only after analytics consent. The pattern below is the same consent-gated approach documented in Privacy & GDPR — inject it from your consent manager when the analytics category is granted, not unconditionally.
<script
id="webmasterid-tracker"
defer
src="https://webmasterid.com/tracker.iife.min.js"
data-wmid="wm_xxxxxxxxxxxxxxxx"
data-endpoint="https://webmasterid-ingest-api.vercel.app/api/events">
</script>
If you ship a CSP via netlify.toml or _headers, include the script source and ingest endpoint in script-src / connect-src.
Netlify serves .html files at extension-less paths; keep canonical URLs consistent with whichever form you choose and reflect it in your sitemap.
No. The tracker posts to its own ingest endpoint; Netlify only serves static files.
Yes — this is the same deployment pattern documented here.
Configure CSP in netlify.toml/_headers to allow the script + endpoint.
WebmasterID is designed for website visibility you control. Explore the product, docs, and integrations.