Temso AI

Temso captures every request your WordPress origin serves over HTTP and sends it to Temso in the background. No DNS changes, no extra infrastructure — install, paste two values, done.
<ul>
<li>Captures all server-side requests — front-end, wp-admin, REST, AJAX, login, xmlrpc. Bot classification happens in Temso.</li>
<li>Non-blocking, batched delivery — adds no perceptible latency to your pages.</li>
<li>No cookies, no JavaScript, no client-side tracking.</li>
<li>Visitor IPs are sent over TLS and hashed in Temso before storage; raw IPs are never retained.</li>
<li>WordPress Multisite supported (activate and connect per site).</li>
</ul>
Learn more at <a href="https://temso.ai/" rel="nofollow ugc">temso.ai</a>.
Requests served from full-page cache never reach PHP and therefore can’t be captured by any origin plugin — this is expected and matches the documented CDN-cache limitation.
<h3>Privacy</h3>
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.

Stream front-end request logs from your WordPress origin to Temso so AI-crawler and bot traffic shows up in your dashboard.

Lukasz Jasinski

robots.txt is a file, which tell’s search engines, which parts of your site it can display publicly. 
This plugin add’s some entries to this file, to make your site safer from some attacks, keeping all your stength in seo intact ex. allowing search engine robots to harvest pictures for image search. When preparing a new site in WordPress, it’s one of the first plugins I install.

LJPL Armored robots.txt

Add some directives to your robots.txt file to keep your site safer

Temso AI vs LJPL Armored robots.txt