Install on WordPress

Create or select your website in Seean, then copy its snippet from Settings → Installation. Replace YOUR_SITE_TOKEN below with that website’s public token. Keep the external script and both data attributes; never put a server order API secret in this code.

Choose the installation method

On self-hosted WordPress, use an existing site-wide header integration that preserves script attributes. If you need one, WordPress documents WPCode: install and activate it, then open Code Snippets → Header & Footer. Paste the tag into Header and save. The simplified mode may show Settings → Header & Footer. WordPress header-code instructions.

This works independently of whether the editor uses classic or block themes. A Custom HTML block in one post does not install analytics across the site. On WordPress.com, JavaScript requires eligible hosting features and permissions; if scripts are stripped or the plugin option is unavailable, check your site’s plan before continuing. WordPress code restrictions.

Add the header code

<script defer src="https://app.seean.io/k.js"
  data-site="YOUR_SITE_TOKEN"
  data-api="https://app.seean.io"></script>

Preserve existing header entries. If your team maintains theme code instead, use its existing child-theme or plugin integration with the site header hook. Do not edit the parent theme as the default installation: updates can replace those changes. Child themes.

Publish and verify

Save the configuration and clear any relevant page/CDN cache. Check public pages while signed out, including a post and a page. Admin screens and custom templates that do not render the site header are outside this installation.

Open the published site in a browser and follow installation verification: confirm k.js loads, a collection request is sent, and the correct website and paths appear in Events. Check a direct page load, a link to a different pathname, and Back/Forward. Setup health shows the last received pageview time and offers a published-homepage check; it does not certify every page.

If events are missing, check the published HTML, consent settings, content blockers, CSP and exclusions. Install the tracker only once: a second tag, plugin or tag-manager installation can double count. Supported pathname navigation is automatic; do not add another pageview tag for every history change. Hash-only changes are not distinct pages.

For a store, continue with WooCommerce scope; a tracker tag does not import orders.

Changes and removal

To change the site token, update this installation and publish again. To stop future collection, remove the same tag and publish; existing reports remain. Recheck installation after platform, theme or routing changes.

See script options, custom events and technical privacy. Loading this script must follow your site’s analytics-consent policy; a platform cookie banner does not necessarily control custom code automatically.

Something unclear? Contact support.