Temso AI
| 开发者 | temsoai |
|---|---|
| 更新时间 | 2026年8月23日 16:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
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.
安装:
- Install and activate the plugin.
- Open Settings → Temso.
- Paste the Ingest URL and API key from your Temso project (Crawlers → Add source → WordPress).
- Save. Tracking is on by default, so that is all it takes — uncheck it any time to pause sending.
常见问题:
Do I need a Temso account?
Yes. The plugin is an interface to the Temso service — create a source under Crawlers → Add source → WordPress in your Temso project to get the Ingest URL and API key.
Why are my counts lower than my own analytics?
Requests served from a full-page cache (a caching plugin or a CDN) never reach PHP, so no origin plugin can see them. Temso measures cache misses; expect lower numbers than total traffic.
What data leaves my site?
Per request: timestamp, URL, HTTP method, response status, user agent, referer, and the visitor IP. The IP is sent over TLS and hashed by Temso before storage — never retained raw. No cookies, no JavaScript, no client-side tracking. See the Privacy section.
Does it slow down my site?
No. Delivery is batched and non-blocking — the visitor response is never delayed by the upload.
Does it work on WordPress Multisite?
Yes. Activate and connect it per site; each site uses its own Ingest URL and key.
更新日志:
1.1.1
- Fix: address default in UI
- Fix: address defaults in UI
- add temso content publisher v1
- add temso content publisher v1
- add temso content publisher v1
- Fix: fix wordpress deploy
- Fix: enforce release
- Continuous Integration: add manual WordPress.org SVN deploy pipeline
- Fix: add sanitize for the key input in the admin panel
- Fix: point Plugin URI at the GitHub repo to differ from Author URI
- Fix: add Test connection button to verify Ingest URL and API key
- Fix: add Test connection button to verify Ingest URL and API key
- Fix: bump Tested up to 7.0 to match current WP release
- Fix: end wp-org strip markers with
.for WPCS InlineComment rule - Fix: strip self-updater references from the wordpress.org build
- Fix: ready readme.txt for .org review and auto-sync it from release-please
- Packaging: WordPress.org submission readiness — plugin headers, build pipeline, and uninstall flow finalized.
- Captures every server-side request (front-end, wp-admin, REST, AJAX, login, xmlrpc).
- Security hardening: stricter request-header sanitization, HTTPS-only ingest endpoint, bounded delivery buffer.
- Initial public release: request capture with batched, non-blocking background delivery, settings screen, and multisite support.