Temso AI

Description

Make AI SEO your next growth channel. Temso captures every request your WordPress origin serves over HTTP and streams it to Temso in the background. That’s how Temso sees which AI crawlers (like GPTBot and ClaudeBot) and visitors reach your content, so you can track and grow how you get recommended across ChatGPT, Gemini, and other AI search engines.

No DNS changes, no extra infrastructure. Install, paste two values, and you’re done.
* Captures all server-side requests: front-end, wp-admin, REST, AJAX, login, and xmlrpc. Bot classification happens in Temso.
* Non-blocking, batched delivery that adds no perceptible latency to your pages.
* No cookies, no JavaScript, and no client-side tracking.
* Visitor IPs are sent over TLS and hashed in Temso before storage. Raw IPs are never retained.
* WordPress Multisite supported. Activate and connect per site.

Publishing (optional). Temso can also publish content back to this site. You enable it from Temso: open Settings → Integrations → WordPress, generate a one-time setup link, and paste it into Settings → Temso AI → Publishing here. The plugin and Temso exchange a publish shared secret automatically — you never copy a secret by hand. Once connected, the plugin accepts signed, server-to-server requests from Temso and creates or updates WordPress posts — writing Yoast and Rank Math SEO metadata too when those plugins are installed. Publishing is authenticated by an HMAC signature over each request, is completely independent of request tracking and the ingest API key, and stays disabled until you connect it. The publish shared secret is stored only on this site.

Learn more at temso.ai.

Requests served from full-page cache never reach PHP, so no origin plugin can capture them. This is expected and matches the documented CDN-cache limitation.

Privacy

This plugin sends the following per HTTP request that WordPress serves (front-end, wp-admin, REST, AJAX, login, xmlrpc) to the Temso API endpoint you configure: timestamp, request URL, HTTP method, response status, user agent, referer, and the visitor IP address. The IP address is transmitted over TLS and hashed by Temso before storage — it is never stored in raw form, and the plugin sets no cookies and adds no client-side tracking.

When publishing is configured, the plugin also receives data from Temso in the inbound direction: the article title, HTML body, slug, and SEO metadata (meta title, meta description, canonical URL) arrive in signed requests from Temso and are stored as WordPress post content and post meta on this site.