On-site kits

The analytics tag, the IndexNow key file and deploy notification, for every common stack.

Embed
Preview of the card
<a href="https://seolyticize.com/docs/site-kits"><img src="https://seolyticize.com/docs/_api/public/orgs/71cb2b7a-a719-4003-b3ea-6321dc1db8ab/spaces/3bf2dbf7-3faa-473c-ba3b-30588f5f8de4/pages/ff0c7d3d-b92d-4988-b31f-78dbeab5f29d/social-card.svg?v=3e7ae33eec8b" alt="On-site kits" width="600" height="315"></a>

onboard_site returns everything a site needs: an analytics site key, an IndexNow key, and optionally a deploy hook. Each kit puts those in place the way its stack expects.

Stack

Install

Source

Next.js / React

npm i @seolyticize/next

next

WordPress

Upload the seolyticize folder as a plugin

wordpress

PHP (Laravel, Symfony)

composer config repositories.seolyticize vcs https://github.com/Seolyticize/site-php && composer require seolyticize/site:dev-main

site-php

Ruby (Rails, Rack)

gem "seolyticize-site", git: "https://github.com/Seolyticize/site-ruby"

site-ruby

Python (Django, Flask)

seolyticize.site in the Python SDK

sdk-python

Go

package site in the Go SDK

sdk-go

Anything else

<script defer data-site="KEY" src="https://seolyticize.com/a.js"></script>

—

Each kit does the same four things:

  1. The analytics tag, with data-exclude for paths that should never be reported (accounts, checkout, verification links).

  2. The IndexNow key file at /KEY.txt: the key and nothing else, as plain text.

  3. Deploy notification: one POST to the deploy hook after each deploy; Seolyticize reads the sitemaps and sends what changed to IndexNow.

  4. Server-side events through the collect API, for conversions that happen on the server.

The WordPress plugin also sends a post to IndexNow the moment it is published or updated, and shows Seolyticize's findings for a page beside it in the editor.

Updated