Spectare reads where each visitor came from (referrer, UTM parameters, page context) and silently assembles a personalised version of your page from a library of content blocks called atoms. No surveys, no cookies, no asking visitors who they are.

You write your content once as atoms: a pricing block, a feature explanation, a case study, a FAQ. Spectare picks the right 3 to 5 atoms for each visitor and slots them into your page in milliseconds.

How it works

A visitor arrives on your site. Spectare reads their referrer URL, UTM parameters, and page content.
An AI classifies their likely audience (developer, executive, manager) and buyer stage (awareness, consideration, decision).
Spectare selects the most relevant atoms from your library and assembles them into named slots on the page.
The assembled content is cached so repeat visitors are served instantly.

Two ways to personalise

The plugin supports two integration paths. You can use either, or both on different pages.

Option A: client-side slots. The Spectare widget script fills named placeholders in the browser after the page loads. Simplest to set up, and safe with any page cache because the personalisation happens client-side.
Option B: server-side zones. PHP calls Spectare with your API key and renders personalised components into the HTML before the page is sent, so there is no flash of default content. Pages using a zone automatically send a Cache-Control: no-store header so caching plugins cannot serve stale personalised HTML.

What this plugin does

Injects the Spectare widget script onto every page for client-side slots (optional, can be disabled)
Provides a Gutenberg block (Spectare Slot) and a [spectare_slot] shortcode for client-side slots
Provides a Gutenberg block (Spectare Zone) and a [spectare_zone] shortcode for server-side zones
Optionally serves an agent entry point at your-domain.com/llms.txt (off by default), generated from your Spectare content: a curated map of what you offer, so an AI agent reading your site extracts your facts accurately from a few fetches instead of scraping every page
Adds a settings page under Settings Spectare for your organisation slug, base URL, and API key

Client-side slots (Option A)

Slots are named placeholders the widget script fills in the browser. Slot names map to positions in your assembled layout:

primary: the main content area, highest priority atom
supporting: secondary content, one or more blocks
secondary: lowest priority, often a FAQ or comparison

Use the Spectare Slot block in Gutenberg or the shortcode in the classic editor:

[spectare_slot name="primary"]
[spectare_slot name="supporting"]
[spectare_slot name="secondary"]

You can reserve vertical space to prevent layout shift while content loads:

[spectare_slot name="primary" height="200"]

Server-side zones (Option B)

Zones are rendered by PHP before the page is sent, using your API key. Each zone renders a different kind of personalised component: hero banners at the top, body content in the middle, social proof and calls to action further down. There are four zones:

[spectare_zone zone="hero"]
[spectare_zone zone="body"]
[spectare_zone zone="proof"]
[spectare_zone zone="cta"]

Server-side zones need your API key in Settings Spectare (find it in your Spectare admin under Settings). Any page using a zone sends Cache-Control: no-store automatically.

Requirements

A Spectare account is required. Sign up at spectare.ai. Spectare is free to start with a 14-day trial; paid plans start at $19/month. See spectare.ai/pricing for current plans and limits.

External services

This plugin connects to the Spectare service (spectare.ai, or your own base URL if you self-host) to personalise your pages. It sends and receives data in the following ways:

Widget script. When auto-inject is on and your organisation slug is set, the plugin loads spectare.js from the Spectare service on your public pages. The script sends the visitor’s referrer, UTM parameters, current page URL, and (in the visitor’s own browser storage) their recent page history on your site to the Spectare API to classify intent and fetch personalised content. No account data, names, or email addresses are collected, and Spectare sets no cookies by default.

Server-side zones. Pages using [spectare_zone] call the Spectare assembly API from your server, sending the visitor’s referrer, UTM parameters, and page URL, authenticated with your API key. If you enable the returning-visitors option, the visitor’s last three page paths on your own site are included from a first-party cookie.

Conversion reporting. When WooCommerce or a supported form plugin completes an order or submission, the plugin reports the goal name, type, and (for orders) the total and currency to the Spectare API. No customer personal data is sent.

Agent entry point. If you enable llms.txt serving, the plugin fetches your generated llms.txt from the Spectare API and serves it on your domain.

These calls go to the Spectare service: privacy policy. No data is sent to Spectare until you enter your organisation slug in settings.

Spectare Personalisation

External services