WebmasterID on Netlify
Netlify-hosted static sites use WebmasterID with the same consent-gated script tag. helperg.com page delivery is moving to Vercel; Netlify temporarily continues to serve the API, Forms and durable data. The pattern below still applies to any Netlify-hosted static site.
Add the tracker
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>Headers
If you ship a CSP via netlify.toml or _headers, include the script source and ingest endpoint in script-src / connect-src.
Clean URLs
Netlify serves .html files at extension-less paths; keep canonical URLs consistent with whichever form you choose and reflect it in your sitemap.
- One shared include = single injection.
- Gate on analytics consent.
- Keep canonical + sitemap consistent.
FAQ
Does this need a backend?
No. The tracker posts to its own ingest endpoint; Netlify only serves static files.
Is helperg.com on Netlify?
Partly. helperg.com pages are served by Vercel; Netlify still handles the API and Forms during an in-progress migration. This guide documents the Netlify deployment pattern generally.
Redirects/headers?
Configure CSP in netlify.toml/_headers to allow the script + endpoint.
Related
Related tools
Owned, lightweight,
privacy-conscious
WebmasterID is designed for website visibility you control. Explore the product, docs, and integrations.