Guides

Get the most out of Spectare

Three areas: WordPress, content, and integration. Pick the one that matches your role.

WordPress

Setup, day-to-day content work, and bringing an existing site in.

For developers

Spectare for WordPress

Plugin installation, slots (client-side), zones (server-rendered), Gutenberg blocks, shortcodes, and caching configuration.

  • →Slots vs zones: which to use
  • →Gutenberg blocks for slots and zones
  • →Zone caching: how DONOTCACHEPAGE works
  • →Troubleshooting slots and zones

For: WordPress developers and site owners

For marketers

Content on your WordPress site

What running Spectare on WordPress means day to day: writing and reviewing atoms, and getting a head start from your existing pages.

  • →What stays the same as any Spectare site
  • →Getting a head start from existing pages
  • →Reviewing imported drafts
  • →Keeping the library current as your site changes

For: Marketers and content editors on WordPress

For marketers and developers

Importing your existing content

How Spectare turns an existing WordPress site into a starting content library, and the review workflow after.

  • →Two ways content gets in
  • →How a scan reads a page
  • →Limits per run
  • →Troubleshooting an import

For: Anyone bringing an existing site into Spectare

Content

Write, review, and constrain what Claude assembles. No code required.

For content teams

Writing and publishing atoms

How to write atoms that convert, use the review workflow, manage images, and keep your content library in good shape.

  • →Atom types and when to use them
  • →Review workflow: draft to published
  • →Images, grouping, and the optimisation algorithm
  • →Publishing and what goes live

For: Marketers and content editors

For marketers

Component rules

How Spectare decides which components a visitor sees, what you can constrain, and what is better left to Claude.

  • →The four steps, in the order they apply
  • →Rules versus advice, and why it matters
  • →Writing guidance that is about content, not audience
  • →How rules interact with the learning loop

For: Marketers and content editors

Integration

Get Spectare running on your stack and prove it is working.

For developers

Adding Spectare to your site

Step-by-step setup for every integration path: script tag, WordPress plugin, Next.js SSR, and the direct REST API.

  • →Script tag: slots and existing element targeting
  • →WordPress plugin and Gutenberg blocks
  • →Next.js SSR with zero DOM swap
  • →Conversion tracking and the REST API

For: Developers and engineers

For developers

Next.js SSR, step by step

A deeper walkthrough of the recommended path: render personalised content into the HTML on the server for zero shimmer.

  • →Get your API key and install the package
  • →The fail-safe server fetch
  • →Three ways to render, including zero-flicker
  • →Caching rules and troubleshooting

For: Next.js and React developers

For marketers and developers

Tracking conversions

Set up conversion tracking with URL patterns or a single manual call. See what the data feeds into.

  • →URL pattern setup in Settings (no code)
  • →Manual call for multi-step forms and in-app flows
  • →What each conversion event feeds into
  • →Common questions and edge cases

For: Marketers, content editors, and developers