WebmasterID on WordPress

WordPress sites add WebmasterID with a small header/footer snippet. The key requirement is the same everywhere: load it only after analytics consent.

Where to add it

Use a reputable header/footer scripts plugin, a child-theme wp_head/wp_footer hook, or your consent plugin's post-consent custom-code slot.

<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>

Consent plugins

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.

Most consent plugins provide a slot or category for analytics scripts that only fire after consent — use that rather than placing the tag directly in the theme head.

Common mistakes

• Adding the snippet in two places (theme + plugin) → duplicate injection.
• Placing it before the consent plugin initializes.
• Hardcoding it in the head with no consent gate in EU/EEA.

FAQ

Related

Integrations hubAll platforms Install docsMethods overview WebmasterIDProduct overview Privacy & GDPRConsent-gating

Related tools

Meta Tag CheckerTitle, description, canonical, OG, Twitter Sitemap ValidatorInspect sitemap XML structure JSON-LD ValidatorCheck structured data syntax Robots.txt ValidatorTest Allow/Disallow rules