Disable auto-inject in Settings \u2192 Spectare \u2192 Auto-inject widget. Then add the script tag yourself:<\/p>\n\n
<script src=\"https:\/\/spectare.ai\/spectare.js\" data-org=\"your-slug\" async><\/script>\n<\/code><\/pre><\/dd>\nWhat is the agent entry point (llms.txt) feature?<\/h3><\/dt>\nSpectare generates an llms.txt file from your published content and the plugin can serve it at your-domain.com\/llms.txt. It is a curated entry point that maps your content, so an AI agent reading your site extracts accurate facts from a few fetches instead of guessing from a scraped page, and it keeps agent crawl cost down as pay-per-crawl arrives. It also documents your qualify endpoint, so an assistant helping someone can send them on to a page built for their intent. It is off by default: turn it on with the \"Serve llms.txt\" setting. Once on, it updates automatically as you edit content, and \"Refresh llms.txt\" pulls the latest immediately. Only published atoms are included, never drafts. Requires pretty permalinks (Settings \u2192 Permalinks, any option other than Plain).<\/p><\/dd>\n
Does this slow down my site?<\/h3><\/dt>\nThe Spectare script loads asynchronously and does not block page rendering. Personalised content fills slots after the page is visible. Cached assemblies (repeat visitors with the same intent profile) are served in under 100ms.<\/p><\/dd>\n
What WordPress versions are supported?<\/h3><\/dt>\nWordPress 5.8 and above. The Gutenberg block requires the block editor introduced in WordPress 5.0, but the shortcode works in any editor version.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.11.3<\/h4>\n\n\n- All script and style output now travels through the WordPress enqueue system: the zone\nstylesheet is an inline style enqueued in the head, the conversion-attribution snippet an\ninline script enqueued in the footer, and the import page script an admin enqueue scoped\nto its own page. No raw script or style tags remain.<\/li>\n
- Shortcode fallback content is passed through wp_kses_post on return.<\/li>\n<\/ul>\n\n
1.11.2<\/h4>\n\n\n- The Plugin URI now points to the plugin guide at spectare.ai\/guide\/wordpress, distinct from\nthe Author URI, as the directory requires.<\/li>\n<\/ul>\n\n
1.11.1<\/h4>\n\n\n- Plugin Check pass: settings fields now escape at the point of output, the UTM reads and the\nDONOTCACHEPAGE convention constant carry documented sniff exemptions, and the renderer\nfallback notice only logs under WP_DEBUG.<\/li>\n<\/ul>\n\n
1.11.0<\/h4>\n\n\n- WordPress.org directory release. The build distributed through the directory updates via\nWordPress.org only; the self-hosted update channel is not present in it.<\/li>\n
- New \"External services\" section in this readme documenting every call the plugin makes to\nthe Spectare service and what data travels with it.<\/li>\n
- Tested against WordPress 7.1.<\/li>\n<\/ul>\n\n
1.10.0<\/h4>\n\n\n- Zone pages now tell Spectare which zones they placed, detected from the page's own\nshortcodes and blocks. The assembled content is then composed only from components those\nzones can render, so a page with just a body zone gets a fuller body instead of a hero\nand call to action it never shows. Pages the plugin cannot read (page builders, widgets)\nbehave exactly as before.<\/li>\n
- Conversions on zone pages now credit the hero image that was shown, so image selection\ncan learn which images convert on WordPress sites.<\/li>\n<\/ul>\n\n
1.9.0<\/h4>\n\n\n- Zones now respect per-component zone placements set in your Spectare settings. Previously a\nzone override saved in Spectare was silently ignored on WordPress, which rendered every\ncomponent in its default zone. If you set zone overrides, components may move to the zone\nyou actually chose after this update.<\/li>\n
- The llms.txt feature is now described as what it is: an agent entry point. A curated map of\nyour content so an AI agent reading your site extracts accurate facts from a few fetches,\nrather than a visibility promise.<\/li>\n<\/ul>\n\n
1.8.2<\/h4>\n\n\n- The Spectare logo now appears on the settings page, on update rows and in the plugin\ndetails window, so the plugin is recognisable at a glance in a busy admin.<\/li>\n<\/ul>\n\n
1.8.1<\/h4>\n\n\n- Supporting content now renders as a compact card: the title, a one-sentence summary, and the\nfull text one tap away. Pages read as pages rather than columns of full prose, and nothing\nbecomes unreachable.<\/li>\n<\/ul>\n\n
1.8.0<\/h4>\n\n\n- Form conversions. Submissions through Gravity Forms, WPForms and Contact Form 7 now report a\nlead conversion to Spectare automatically, with no thank-you page or URL goal needed. Rename\nthe goal with the spectare_form_goal_name filter, or disable with spectare_track_forms.<\/li>\n
- Click goals. Clicks on phone numbers, email links and booking platforms (OpenTable, Tock,\nDesign My Night, SevenRooms, Resy, Eventbrite and others) count as conversions, since those\njourneys never end on a page a URL goal could match. On by default; switch off in settings.<\/li>\n<\/ul>\n\n
1.7.0<\/h4>\n\n\n- Automatic updates. The plugin now checks spectare.ai for new versions and updates through the\nnormal WordPress update screen. This is the last version you install by uploading a zip.<\/li>\n
- WooCommerce order tracking. When WooCommerce is active and your API key is set, every paid\norder reports a conversion to Spectare with the real order total and currency, so the\nanalytics and the learning loop see what actually sells. No configuration needed; disable\nwith the spectare_track_woocommerce filter.<\/li>\n
- The comparison table now carries proper header scope attributes for screen readers.<\/li>\n<\/ul>\n\n
1.6.1<\/h4>\n\n\n- The announcement zone added in 1.6.0 was missing from the block editor's zone list and from the\nsetup instructions, so the only way to use it was to type the shortcode by hand. It is now\noffered like every other zone.<\/li>\n<\/ul>\n\n
1.6.0<\/h4>\n\n\n- New announcement bar. A single line above the rest of a personalised section, for one\ntime-limited fact worth knowing first: a member priority window, the last days of a run,\nunder-12s free this month. Place it with [spectare_zone zone=\"announce\"].<\/li>\n
- It only appears when your content actually states such a fact and carries the dates it is true\nbetween, so it disappears on its own when the offer ends rather than sitting there out of date.<\/li>\n<\/ul>\n\n
1.5.4<\/h4>\n\n\n- Longer content in a personalised section was cut off after four lines, mid-sentence, with no\nway for the reader to see the rest. The shortening was meant for a narrow column beside another\nblock, and sections are laid out full width, so it was hiding content for no reason.<\/li>\n<\/ul>\n\n
1.5.3<\/h4>\n\n\n- Personalised sections can now hold your own content as a fallback. Write it between the tags,\nfor example [spectare_zone zone=\"hero\"]Your normal hero copy[\/spectare_zone], and it is shown\nwhenever there is nothing personalised to show: if the connection fails, if you have not\npublished content for that visitor yet, or before the page finishes loading. Previously those\nsituations left a gap and there was no way to say what belonged there.<\/li>\n<\/ul>\n\n
1.5.2<\/h4>\n\n\n- A personalised section containing a content block this version of the plugin does not know\nhow to draw used to leave a gap, with nothing in the logs to say why. It now draws the block\nas a content card and records a note, so an out-of-date plugin degrades visibly rather than\nquietly dropping content.<\/li>\n<\/ul>\n\n
1.5.1<\/h4>\n\n\n- The primary button in a call to action block was white on a white background, so on most\nthemes it was invisible. It now uses your brand colour, which you can set in Settings.<\/li>\n
- New \"Brand colour\" setting. Personalised sections already inherit your theme's background and\ntext colour; this is the one colour Spectare picks, used for links, labels and the primary\nbutton. Previously it could only be changed by overriding a CSS variable, which worked or did\nnot depending on the order your stylesheets loaded in.<\/li>\n
- Improved the contrast of the faintest text colour, which fell below the accessibility minimum\non light themes.<\/li>\n<\/ul>\n\n
1.5.0<\/h4>\n\n\n- Atom content written with paragraphs, lists, bold or headings rendered as one unbroken block\nof text in server-rendered zones. It is now converted to HTML, matching every other way\nSpectare content is displayed.<\/li>\n
- Added the styles that markdown content needs, including the three code styles that were\nmissing, so an atom containing code no longer renders unstyled.<\/li>\n<\/ul>\n\n
1.4.1<\/h4>\n\n\n- Security fix. The page URL is sent to Spectare and shapes the personalisation, but was not\npart of the key used to cache a zone's assembly. Because that URL includes the query string,\ntwo visitors on the same page with different query strings shared one cached entry, so one\nvisitor could be served content assembled for another. Found by a security review. Zone\nassemblies now cache per page URL as well as per referrer, campaign and visit history.<\/li>\n<\/ul>\n\n
1.4.0<\/h4>\n\n\n- Server-rendered zones can now personalise for returning visitors. Zones are rendered on your\nserver, which cannot see the page history Spectare keeps in the visitor's browser, so a\nreturning visitor previously looked new to them and got your default content. Enable\n\"Returning visitors in zones\" in Settings to store the visitor's last three page paths in a\nfirst-party cookie on your own domain, which your server passes to Spectare. Off by default,\nbecause it adds a cookie: check your cookie policy before enabling. Slots have always\npersonalised for returning visitors and are unaffected either way.<\/li>\n
- Zone assemblies are cached per visit history as well as per referrer and campaign, so two\nvisitors with different histories no longer share a cached zone.<\/li>\n<\/ul>\n\n
1.3.1<\/h4>\n\n\n- Atom body text in server-rendered zones is now clamped to four lines instead of printing\nthe full atom. Long atoms were rendering as a wall of prose beside structured components.\nSet full on an atom in the assembly to print the whole body.<\/li>\n
- Zone assemblies are now cached for an hour instead of a minute. At one minute the cache\nexpired between visitors on lower traffic sites, so most visitors paid a cold blocking\nrender and billed a personalisation. Filter: spectare_assembly_cache_ttl.<\/li>\n
- The zone request timeout is now 15 seconds instead of 20. This call blocks the page render,\nso it stays bounded, but it has to sit above a cold assembly rather than below it: a cold\nmiss is a full model call and can take 9 to 13 seconds. With the hour-long cache above, at\nmost one visitor per hour per traffic source waits that long. Filter:\nspectare_assembly_timeout.<\/li>\n
- A failed zone request is remembered for 30 seconds, so a slow or unavailable backend costs\none visitor the timeout rather than every visitor until it recovers. Filter:\nspectare_assembly_fail_ttl.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Added content import (Settings \u2192 Spectare Import): scan your published pages, pick which to import, and Spectare rewrites them into focused content atoms saved as drafts for review. Nothing is published automatically. Reads raw Gutenberg blocks where available and falls back to a heading split for classic\/page-builder content. Requires your Spectare API key.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Added an agent entry point: the plugin serves an llms.txt at your domain root, generated from your published Spectare content, so an AI agent reading your site extracts accurate facts from a few fetches.<\/li>\n
- Added \"Serve llms.txt\" toggle (off by default) and a \"Refresh llms.txt\" button in Settings \u2192 Spectare.<\/li>\n
- llms.txt is cached locally and refreshes automatically as your content changes. Requires pretty permalinks.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Added server-side Zone blocks: the [spectare_zone] shortcode and Spectare Zone Gutenberg block render personalised components in named zones (hero, body, proof, cta) via server-side assembly.<\/li>\n
- Added an API key setting (Settings \u2192 Spectare) required for the server-side zone path.<\/li>\n
- Pages using [spectare_zone] now send a Cache-Control: no-store header automatically to prevent caching plugins from serving stale personalised content.<\/li>\n
- Reorganised the settings Quick start into Option A (client-side slots) and Option B (server-side zones).<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n
- Auto-inject of Spectare widget script via wp_enqueue_scripts.<\/li>\n
- Gutenberg block (Spectare Slot) with slot selector, custom name, and reserved height options.<\/li>\n
- Shortcode [spectare_slot] with name and height attributes.<\/li>\n
- Settings page with organisation slug, base URL, and auto-inject toggle.<\/li>\n<\/ul>","raw_excerpt":"AI-driven personalisation for WordPress. Spectare assembles a different page experience for every visitor based on referrer and UTM signals.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/331879","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=331879"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/nigemchugh"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=331879"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=331879"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=331879"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=331879"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=331879"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=331879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}