Changeset 3754930

Timestamp:

10/19/2026 02:15:01 PM (33 hours ago)

Author:

zainkhandev001

Message:

Update to version 1.2.4 from GitHub

Location:

rankraft-ai-analytics

Files:

• tags/1.2.4 (copied) (copied from rankraft-ai-analytics/trunk )
• tags/1.2.4/includes/class-cache-bypass.php (modified) (1 diff)
• tags/1.2.4/includes/class-capture.php (modified) (1 diff)
• tags/1.2.4/rankraft-ai-analytics.php (modified) (2 diffs)
• tags/1.2.4/readme.txt (modified) (3 diffs)
• trunk/includes/class-cache-bypass.php (modified) (1 diff)
• trunk/includes/class-capture.php (modified) (1 diff)
• trunk/rankraft-ai-analytics.php (modified) (2 diffs)
• trunk/readme.txt (modified) (3 diffs)

rankraft-ai-analytics/tags/1.2.4/includes/class-cache-bypass.php

@@ -37 +37 @@
 
     /** Self-test user-agent (also in the bot registry, so the test hit shows up in the dashboard as RankRaft-Test). */
-    public const TEST_UA = 'RankRaft-Test/1.0 (cache-check; +https://rankraft.ai/docs/integrations/wordpress)';
+    public const TEST_UA = 'RankRaft-Test/1.0 (cache-check; +https://docs.rankraft.ai/agent-analytics/wordpress/introduction)';
 
     /**

rankraft-ai-analytics/tags/1.2.4/includes/class-capture.php

@@ -431 +431 @@
             'status' => 200,
             'ip' => self::client_ip() ?? '127.0.0.1',
-            'user_agent' => 'RankRaft-Test/1.0 (+https://rankraft.ai/docs/integrations/wordpress)',
+            'user_agent' => 'RankRaft-Test/1.0 (+https://docs.rankraft.ai/agent-analytics/wordpress/introduction)',
         ];
     }

rankraft-ai-analytics/tags/1.2.4/rankraft-ai-analytics.php

@@ -2 +2 @@
 /**
  * Plugin Name: RankRaft AI Analytics
- * Plugin URI: https://rankraft.ai/docs/integrations/wordpress
+ * Plugin URI: https://docs.rankraft.ai/agent-analytics/wordpress/introduction
  * Description: Sends lightweight server-side request logs to RankRaft so you can see how AI crawlers and AI answer engines interact with your site.
- * Version: 1.2.3
+ * Version: 1.2.4
  * Author: RankRaft
  * Author URI: https://rankraft.ai
@@ -18 +18 @@
 }
 
-define('RANKRAFT_AA_VERSION', '1.2.3');
+define('RANKRAFT_AA_VERSION', '1.2.4');
 define('RANKRAFT_AA_DB_VERSION', '2');
 define('RANKRAFT_AA_PLUGIN_DIR', plugin_dir_path(__FILE__));

rankraft-ai-analytics/tags/1.2.4/readme.txt

@@ -1 +1 @@
 === RankRaft AI Analytics ===
 Contributors: zainkhandev001
-Tags: ai, analytics, crawlers, ai-seo, seo
+Tags: ai seo, chatgpt, ai crawlers, analytics, geo
 Requires at least: 6.0
 Tested up to: 7.1
-Stable tag: 1.2.3
+Stable tag: 1.2.4
 Requires PHP: 8.0
 License: GPLv2 or later
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
-See how AI crawlers (GPTBot, ClaudeBot, PerplexityBot…) and AI answer engines interact with your WordPress site.
+See which AI bots read your site and how many visitors ChatGPT, Perplexity, Gemini and other AI assistants send you.
 
 == Description ==
 
-RankRaft AI Analytics records every public front-end request server-side and sends it to your RankRaft dashboard, where it is classified into AI crawlers, search bots and visitors referred by AI assistants. Ordinary visitors are only counted, never stored individually.
+People now ask ChatGPT, Gemini, Perplexity and Google's AI Overviews what to buy, which service to use and who to trust. Those answers are built from websites, and the AI companies send bots to read them.
 
-= How it works =
+**RankRaft AI Analytics shows you that hidden side of your traffic**: which AI bots visit your site, which pages they read, whether they are who they claim to be, and how many real people click through to you from an AI answer. Normal analytics tools miss almost all of this, because AI bots don't run JavaScript.
 
-1. At the end of each public request the plugin writes one small row (path, status, IP, user agent, referrer) to a local queue table. This happens after the page is sent, so visitors never wait.
-2. Once a minute a background job sends the queue to RankRaft in batches.
-3. If RankRaft cannot be reached, rows are kept and retried with exponential backoff. After repeated failures sending pauses for 30 minutes and resumes automatically.
-4. Old unsent rows are cleaned up daily.
+= What you'll see in your RankRaft dashboard =
 
-= Privacy =
+* **Which AI bots visit:** GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot, Bingbot and more, grouped by company and by purpose (training, search, live answers).
+* **What they read:** your most-read pages and page types — products, blog posts, docs, pricing — so you can see what AI actually learns about you.
+* **Real or fake:** every bot is checked against the IP ranges its company publishes, so a scraper pretending to be GPTBot is flagged rather than counted.
+* **Visitors from AI answers:** people who arrive from ChatGPT, Perplexity, Gemini, Claude or Copilot, and the pages they land on.
+* **Your AI share of traffic:** AI activity next to your ordinary traffic, day by day.
+* **Problems to fix:** pages AI bots can't reach, and sites that block AI crawlers by accident in robots.txt or a firewall.
 
-* Admin pages, login, REST API, AJAX, cron and XML-RPC requests are never logged. This is not a setting.
-* Query parameters whose names contain `password`, `token`, `key`, `secret`, `card`, `email`… are replaced with `[REDACTED]` before leaving your server. The list is fixed and cannot be switched off.
-* No cookies, no JavaScript, nothing is injected into your pages.
-* Your site key is stored encrypted (libsodium + WordPress salts) or can be defined in `wp-config.php` and never stored in the database.
-* Visitor IPs are used by RankRaft to verify crawlers against published IP ranges and are stored only as salted hashes.
+RankRaft also tracks how AI assistants talk about your brand — whether ChatGPT, Gemini and Google's AI answers mention you, how you compare with competitors, and which sites they cite — with recommendations on what to do next. This plugin is the piece that connects your WordPress site to it.
+
+= Why a plugin and not a tracking script? =
+
+AI bots don't run JavaScript, so tracking scripts never see them. This plugin notes each visit on your server instead — the only place bot visits can be seen — and it works even when your pages are served from a cache.
+
+= Simple to set up =
+
+1. Install and activate the plugin.
+2. Paste the site key from your RankRaft dashboard.
+3. Click **Test connection**. That's it — data appears in your dashboard within a minute.
+
+= Private by design =
+
+* Nothing is sent until you add a site key and switch it on, and you can switch it off at any time.
+* Admin pages, logins, checkouts, carts and account pages are never recorded — this cannot be turned off.
+* Passwords, tokens, email addresses and similar values in links are blanked out before anything leaves your site.
+* No cookies, no JavaScript and nothing added to your pages. Your visitors see no difference.
+* Visitor IP addresses are used only to check that bots are genuine and are stored as one-way hashes.
+
+= Fast =
+
+Visits are noted after the page has been sent, so visitors never wait. The data goes to RankRaft in small batches in the background about once a minute. If RankRaft can't be reached, nothing is lost: the plugin keeps the data and sends it later.
+
+= You'll need a RankRaft account =
+
+The plugin sends data to RankRaft, where your reports live. [Start a free 7-day trial](https://app.rankraft.ai/signup) — no credit card needed.
+
+= Documentation =
+
+Setup, caching, privacy and troubleshooting guides: [RankRaft WordPress plugin docs](https://docs.rankraft.ai/agent-analytics/wordpress/introduction).
 
 == External services ==
 
-This plugin sends data to **RankRaft** (https://rankraft.ai), the analytics service it is built for. Nothing is sent until you enter a site key in *Settings → RankRaft AI* and test the connection — a successful test confirms the key and switches request logging on, and the **Enable request logging** tick box on the same screen turns it off again at any time. Freshly activated and unconfigured the plugin is inert: it makes no network request and changes nothing on your server.
+This plugin sends data to **RankRaft** (https://rankraft.ai), the analytics service it is built for. Nothing is sent until you enter a site key in *Settings → RankRaft AI* and test the connection. A successful test confirms the key and switches request logging on; the **Enable request logging** tick box on the same screen turns it off again at any time. Freshly activated and not yet set up, the plugin does nothing: it makes no network requests and changes nothing on your server.
 
-* **What is sent:** for each public front-end request — timestamp, hostname, path, HTTP method, response status, response size, the visitor's IP address, User-Agent and the referring page's address (without its query string), and the query string with sensitive parameters redacted. No cookies, form data, page content or logged-in user data.
-* **When:** batched and sent about once a minute from your server to `https://ingest.rankraft.ai`. The address is fixed and cannot be changed. The *Test connection* and *Send test event* buttons and the *Check cache bypass* self-test also contact the service.
-* **Why:** RankRaft classifies the requests into AI crawlers, search engines and visitors referred by AI assistants, verifies crawler identities against the providers' published IP ranges, and shows the results in your dashboard. IP addresses are used for that verification and stored only as salted hashes.
+* **What is sent:** for each public page request — the time, hostname, path, HTTP method, response status and size, the visitor's IP address and browser identification (User-Agent), the address of the referring page without its query string, and the page's query string with sensitive values blanked out. No cookies, form data, page content or information about logged-in users.
+* **When:** in batches, about once a minute, from your server to `https://ingest.rankraft.ai`. The *Test connection*, *Send test event* and *Check cache bypass* buttons also contact the service.
+* **Why:** RankRaft sorts the requests into AI bots, search engines and visitors referred by AI assistants, checks bots against the IP ranges their companies publish, and shows the results in your dashboard. IP addresses are used for that check and stored only as salted hashes.
 * **Terms of service:** https://rankraft.ai/terms
 * **Privacy policy:** https://rankraft.ai/privacy
@@ -42 +70 @@
 == Installation ==
 
-1. Upload the `rankraft-ai-analytics` folder to `/wp-content/plugins/` and activate it, or install the zip from the RankRaft dashboard.
-2. Go to **Settings → RankRaft AI** and paste the site key from your RankRaft dashboard (Site → Setup).
-3. Click **Test connection**. You should see "Connected to <your site>"; the key is saved and request logging switches on by itself. Untick **Enable request logging** whenever you want it to stop.
-4. Optionally click **Send test event**; it appears in the Logs tab of your dashboard within a minute.
+1. In WordPress, go to **Plugins → Add New**, search for **RankRaft AI**, then click **Install Now** and **Activate**.
+2. Go to **Settings → RankRaft AI** and paste the site key from your RankRaft dashboard (your site → Integrations).
+3. Click **Test connection**. You should see "Connected to" your site's name; the key is saved and logging switches on.
+4. Optional: click **Send test event**. It appears in your dashboard within a minute.
 
-For production sites we recommend keeping the key out of the database:
+Developers can keep the key out of the database by adding it to `wp-config.php` instead:
 
 `define('RANKRAFT_SITE_KEY', 'rr_live_…');`
 
+Step-by-step guide with screenshots: [docs.rankraft.ai](https://docs.rankraft.ai/agent-analytics/wordpress/introduction).
+
 == Frequently Asked Questions ==
 
-= Will this slow down my site? =
+= Do I need a RankRaft account? =
 
-No. Logging runs after the response is sent and costs a single database insert. Sending happens in the background via WP-cron.
+Yes. The plugin collects the data; your reports are in the RankRaft dashboard. You can [try RankRaft free for 7 days](https://app.rankraft.ai/signup), no credit card needed.
 
-= My site uses a CDN or a full-page cache. Will crawlers be logged? =
+= Why can't Google Analytics show me AI bots? =
 
-Yes for WordPress page caches. The plugin writes a small rule to .htaccess so AI and search crawlers skip FlyingPress, WP Rocket, LiteSpeed Cache, WP Super Cache and LiteSpeed's server cache and reach PHP; visitors still get cached pages. Use "Check cache bypass" on the Status tab to confirm. Caches that sit in front of your server (Cloudflare, a CDN, some managed hosts on Nginx) cannot be bypassed from WordPress — for those, add the RankRaft Cloudflare integration, which sees every request.
+Google Analytics and similar tools count visits by running JavaScript in a browser. AI bots read your pages without running JavaScript, so those tools never see them. This plugin notes visits on your server, where every request arrives.
 
-= WP-cron is disabled on my host. =
+= Will it slow down my site? =
 
-Point a system cron at `wp-cron.php` every minute. The Status tab shows the exact command.
+No. Each visit is noted after the page has already been sent to the visitor, and data is sent in the background about once a minute.
+
+= Does it work with caching plugins? =
+
+Yes. With WP Rocket, FlyingPress, LiteSpeed Cache or WP Super Cache, the plugin makes sure AI bots still reach WordPress so their visits are counted, while your visitors keep getting fast cached pages. Use **Check cache bypass** on the Status tab to confirm it's working. If a service in front of your site (such as Cloudflare or your host's own cache) answers before WordPress does, connect the RankRaft Cloudflare integration instead — it sees every visit.
+
+= What data is collected? Is it GDPR-friendly? =
+
+Only technical details of each public page request: the page address, time, response status, browser identification, the referring page and the visitor's IP address. Logged-in areas, checkouts and account pages are never recorded, sensitive values in links are blanked out, and IP addresses are stored only as one-way hashes. No cookies are set. The plugin also adds suggested wording to WordPress's privacy policy guide (*Settings → Privacy*). See the External services section for the full list.
+
+= Can I stop some pages being recorded? =
+
+Yes. On the Privacy tab, list any extra paths you never want recorded, for example a members area. Admin, login, checkout, cart and account pages are always excluded.
 
 = What happens if RankRaft is down? =
 
-Logs queue locally (up to 100,000 rows) and are sent when the service is back. Nothing is lost for up to 7 days.
+Nothing is lost. The plugin keeps the data on your site and sends it when RankRaft is back, for up to seven days.
 
-= What happens if my RankRaft subscription lapses? =
+= What happens if my RankRaft subscription ends? =
 
-RankRaft tells the plugin, which pauses logging (nothing is queued or sent) and shows a notice in wp-admin with a link to update billing. Once billing is fixed, RankRaft notifies the plugin through a signed request to `/wp-json/rankraft-aa/v1/resume` and logging resumes by itself; anything still queued is sent. "Test connection" on the Status tab re-checks immediately.
+The plugin pauses — nothing is recorded or sent — and shows a notice in your WordPress admin. When billing is sorted out it resumes by itself.
+
+= WP-Cron is disabled on my host. =
+
+Point a server cron job at `wp-cron.php` every minute. The Status tab shows the exact command.
 
 = Does it work on multisite? =
 
-Each site in the network is configured separately with its own site key.
+Yes. Each site in the network is set up separately with its own site key.
 
 == Screenshots ==
@@ -81 +127 @@
 1. Settings → RankRaft AI: the whole General tab — site key, logging toggle and the crawler cache-bypass option.
 2. Privacy tab: exactly what is sent, the redaction list that cannot be switched off, and optional extra paths to exclude.
+3. Status tab: delivery health, queue depth, last send and the next scheduled run.
 
 == Changelog ==
 
+= 1.2.4 =
+* The plugin's links now point to its documentation at docs.rankraft.ai.
+* A clearer description in the plugin directory.
+
 = 1.2.3 =
-* Security: the visitor's address is now taken from a proxy header only when the request came from a proxy the plugin can name — Cloudflare's published ranges, a proxy on the host or local network, or one added through the new `rankraft_aa_trusted_proxies` filter (an array of IPs or CIDR blocks). Before, any visitor could set `CF-Connecting-IP` or `X-Forwarded-For` themselves and be recorded, and verified, as a crawler from that address. Sites behind another CDN or load balancer should add its addresses through the filter.
-* Privacy: the referring page is sent without its query string or fragment, so a link clicked from a page carrying a token (a password-reset link, an order confirmation) no longer ships that token.
-* Fixed: a resume push from RankRaft can no longer be replayed inside its five-minute window.
-* Fixed: a `429 Too Many Requests` from the ingest API keeps the batch for retry instead of deleting it.
-* Fixed: the cache-bypass rule now leaves real directories alone, and on an https site it waits for the site's own http→https redirect rather than catching the request first.
-* Fixed: unticking "manage .htaccess" or disabling logging removes the cache-bypass block instead of leaving it in place.
-* Fixed: the queue cap is checked against a fresh count when the cached size has lapsed; cron is no longer spawned from a visitor's request under `ALTERNATE_WP_CRON`.
-* Changed: with no `AUTH_KEY`/`SECURE_AUTH_KEY` in wp-config.php the site key is stored as typed rather than under a key derived from the install time, which was no protection.
+* Security: bot visits can no longer be faked by a visitor sending a made-up proxy header. The visitor's address is read from a proxy header only when the request came through a proxy the plugin trusts — Cloudflare, your host or local network, or addresses you add with the `rankraft_aa_trusted_proxies` filter. Sites behind another CDN or load balancer should add its addresses there.
+* Privacy: the referring page is now sent without its query string, so private links (such as password-reset or order-confirmation pages) are never passed on.
+* Fixed: data is kept and retried, not dropped, when RankRaft asks the plugin to slow down.
+* Fixed: the cache-bypass rule no longer affects real folders on your server, and works with the site's own http→https redirect.
+* Fixed: turning off logging now removes the cache-bypass rule from .htaccess.
+* Other small reliability and security fixes.
 
 = 1.2.2 =
-* Fixed: a backslash in the query string or request path was being removed from requests that came through the cache-bypass rule. 1.2.1 added `wp_unslash()` to those two `$_SERVER` reads, but they run on `plugins_loaded`, before WordPress slashes `$_SERVER` in `wp_magic_quotes()` — so there was nothing to unslash and real backslashes were stripped instead.
+* Fixed: backslashes in page addresses were being removed from some recorded requests.
 
 = 1.2.1 =

rankraft-ai-analytics/trunk/includes/class-cache-bypass.php

@@ -37 +37 @@
 
     /** Self-test user-agent (also in the bot registry, so the test hit shows up in the dashboard as RankRaft-Test). */
-    public const TEST_UA = 'RankRaft-Test/1.0 (cache-check; +https://rankraft.ai/docs/integrations/wordpress)';
+    public const TEST_UA = 'RankRaft-Test/1.0 (cache-check; +https://docs.rankraft.ai/agent-analytics/wordpress/introduction)';
 
     /**

rankraft-ai-analytics/trunk/includes/class-capture.php

@@ -431 +431 @@
             'status' => 200,
             'ip' => self::client_ip() ?? '127.0.0.1',
-            'user_agent' => 'RankRaft-Test/1.0 (+https://rankraft.ai/docs/integrations/wordpress)',
+            'user_agent' => 'RankRaft-Test/1.0 (+https://docs.rankraft.ai/agent-analytics/wordpress/introduction)',
         ];
     }

rankraft-ai-analytics/trunk/rankraft-ai-analytics.php

@@ -2 +2 @@
 /**
  * Plugin Name: RankRaft AI Analytics
- * Plugin URI: https://rankraft.ai/docs/integrations/wordpress
+ * Plugin URI: https://docs.rankraft.ai/agent-analytics/wordpress/introduction
  * Description: Sends lightweight server-side request logs to RankRaft so you can see how AI crawlers and AI answer engines interact with your site.
- * Version: 1.2.3
+ * Version: 1.2.4
  * Author: RankRaft
  * Author URI: https://rankraft.ai
@@ -18 +18 @@
 }
 
-define('RANKRAFT_AA_VERSION', '1.2.3');
+define('RANKRAFT_AA_VERSION', '1.2.4');
 define('RANKRAFT_AA_DB_VERSION', '2');
 define('RANKRAFT_AA_PLUGIN_DIR', plugin_dir_path(__FILE__));

rankraft-ai-analytics/trunk/readme.txt

@@ -1 +1 @@
 === RankRaft AI Analytics ===
 Contributors: zainkhandev001
-Tags: ai, analytics, crawlers, ai-seo, seo
+Tags: ai seo, chatgpt, ai crawlers, analytics, geo
 Requires at least: 6.0
 Tested up to: 7.1
-Stable tag: 1.2.3
+Stable tag: 1.2.4
 Requires PHP: 8.0
 License: GPLv2 or later
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
-See how AI crawlers (GPTBot, ClaudeBot, PerplexityBot…) and AI answer engines interact with your WordPress site.
+See which AI bots read your site and how many visitors ChatGPT, Perplexity, Gemini and other AI assistants send you.
 
 == Description ==
 
-RankRaft AI Analytics records every public front-end request server-side and sends it to your RankRaft dashboard, where it is classified into AI crawlers, search bots and visitors referred by AI assistants. Ordinary visitors are only counted, never stored individually.
+People now ask ChatGPT, Gemini, Perplexity and Google's AI Overviews what to buy, which service to use and who to trust. Those answers are built from websites, and the AI companies send bots to read them.
 
-= How it works =
+**RankRaft AI Analytics shows you that hidden side of your traffic**: which AI bots visit your site, which pages they read, whether they are who they claim to be, and how many real people click through to you from an AI answer. Normal analytics tools miss almost all of this, because AI bots don't run JavaScript.
 
-1. At the end of each public request the plugin writes one small row (path, status, IP, user agent, referrer) to a local queue table. This happens after the page is sent, so visitors never wait.
-2. Once a minute a background job sends the queue to RankRaft in batches.
-3. If RankRaft cannot be reached, rows are kept and retried with exponential backoff. After repeated failures sending pauses for 30 minutes and resumes automatically.
-4. Old unsent rows are cleaned up daily.
+= What you'll see in your RankRaft dashboard =
 
-= Privacy =
+* **Which AI bots visit:** GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot, Bingbot and more, grouped by company and by purpose (training, search, live answers).
+* **What they read:** your most-read pages and page types — products, blog posts, docs, pricing — so you can see what AI actually learns about you.
+* **Real or fake:** every bot is checked against the IP ranges its company publishes, so a scraper pretending to be GPTBot is flagged rather than counted.
+* **Visitors from AI answers:** people who arrive from ChatGPT, Perplexity, Gemini, Claude or Copilot, and the pages they land on.
+* **Your AI share of traffic:** AI activity next to your ordinary traffic, day by day.
+* **Problems to fix:** pages AI bots can't reach, and sites that block AI crawlers by accident in robots.txt or a firewall.
 
-* Admin pages, login, REST API, AJAX, cron and XML-RPC requests are never logged. This is not a setting.
-* Query parameters whose names contain `password`, `token`, `key`, `secret`, `card`, `email`… are replaced with `[REDACTED]` before leaving your server. The list is fixed and cannot be switched off.
-* No cookies, no JavaScript, nothing is injected into your pages.
-* Your site key is stored encrypted (libsodium + WordPress salts) or can be defined in `wp-config.php` and never stored in the database.
-* Visitor IPs are used by RankRaft to verify crawlers against published IP ranges and are stored only as salted hashes.
+RankRaft also tracks how AI assistants talk about your brand — whether ChatGPT, Gemini and Google's AI answers mention you, how you compare with competitors, and which sites they cite — with recommendations on what to do next. This plugin is the piece that connects your WordPress site to it.
+
+= Why a plugin and not a tracking script? =
+
+AI bots don't run JavaScript, so tracking scripts never see them. This plugin notes each visit on your server instead — the only place bot visits can be seen — and it works even when your pages are served from a cache.
+
+= Simple to set up =
+
+1. Install and activate the plugin.
+2. Paste the site key from your RankRaft dashboard.
+3. Click **Test connection**. That's it — data appears in your dashboard within a minute.
+
+= Private by design =
+
+* Nothing is sent until you add a site key and switch it on, and you can switch it off at any time.
+* Admin pages, logins, checkouts, carts and account pages are never recorded — this cannot be turned off.
+* Passwords, tokens, email addresses and similar values in links are blanked out before anything leaves your site.
+* No cookies, no JavaScript and nothing added to your pages. Your visitors see no difference.
+* Visitor IP addresses are used only to check that bots are genuine and are stored as one-way hashes.
+
+= Fast =
+
+Visits are noted after the page has been sent, so visitors never wait. The data goes to RankRaft in small batches in the background about once a minute. If RankRaft can't be reached, nothing is lost: the plugin keeps the data and sends it later.
+
+= You'll need a RankRaft account =
+
+The plugin sends data to RankRaft, where your reports live. [Start a free 7-day trial](https://app.rankraft.ai/signup) — no credit card needed.
+
+= Documentation =
+
+Setup, caching, privacy and troubleshooting guides: [RankRaft WordPress plugin docs](https://docs.rankraft.ai/agent-analytics/wordpress/introduction).
 
 == External services ==
 
-This plugin sends data to **RankRaft** (https://rankraft.ai), the analytics service it is built for. Nothing is sent until you enter a site key in *Settings → RankRaft AI* and test the connection — a successful test confirms the key and switches request logging on, and the **Enable request logging** tick box on the same screen turns it off again at any time. Freshly activated and unconfigured the plugin is inert: it makes no network request and changes nothing on your server.
+This plugin sends data to **RankRaft** (https://rankraft.ai), the analytics service it is built for. Nothing is sent until you enter a site key in *Settings → RankRaft AI* and test the connection. A successful test confirms the key and switches request logging on; the **Enable request logging** tick box on the same screen turns it off again at any time. Freshly activated and not yet set up, the plugin does nothing: it makes no network requests and changes nothing on your server.
 
-* **What is sent:** for each public front-end request — timestamp, hostname, path, HTTP method, response status, response size, the visitor's IP address, User-Agent and the referring page's address (without its query string), and the query string with sensitive parameters redacted. No cookies, form data, page content or logged-in user data.
-* **When:** batched and sent about once a minute from your server to `https://ingest.rankraft.ai`. The address is fixed and cannot be changed. The *Test connection* and *Send test event* buttons and the *Check cache bypass* self-test also contact the service.
-* **Why:** RankRaft classifies the requests into AI crawlers, search engines and visitors referred by AI assistants, verifies crawler identities against the providers' published IP ranges, and shows the results in your dashboard. IP addresses are used for that verification and stored only as salted hashes.
+* **What is sent:** for each public page request — the time, hostname, path, HTTP method, response status and size, the visitor's IP address and browser identification (User-Agent), the address of the referring page without its query string, and the page's query string with sensitive values blanked out. No cookies, form data, page content or information about logged-in users.
+* **When:** in batches, about once a minute, from your server to `https://ingest.rankraft.ai`. The *Test connection*, *Send test event* and *Check cache bypass* buttons also contact the service.
+* **Why:** RankRaft sorts the requests into AI bots, search engines and visitors referred by AI assistants, checks bots against the IP ranges their companies publish, and shows the results in your dashboard. IP addresses are used for that check and stored only as salted hashes.
 * **Terms of service:** https://rankraft.ai/terms
 * **Privacy policy:** https://rankraft.ai/privacy
@@ -42 +70 @@
 == Installation ==
 
-1. Upload the `rankraft-ai-analytics` folder to `/wp-content/plugins/` and activate it, or install the zip from the RankRaft dashboard.
-2. Go to **Settings → RankRaft AI** and paste the site key from your RankRaft dashboard (Site → Setup).
-3. Click **Test connection**. You should see "Connected to <your site>"; the key is saved and request logging switches on by itself. Untick **Enable request logging** whenever you want it to stop.
-4. Optionally click **Send test event**; it appears in the Logs tab of your dashboard within a minute.
+1. In WordPress, go to **Plugins → Add New**, search for **RankRaft AI**, then click **Install Now** and **Activate**.
+2. Go to **Settings → RankRaft AI** and paste the site key from your RankRaft dashboard (your site → Integrations).
+3. Click **Test connection**. You should see "Connected to" your site's name; the key is saved and logging switches on.
+4. Optional: click **Send test event**. It appears in your dashboard within a minute.
 
-For production sites we recommend keeping the key out of the database:
+Developers can keep the key out of the database by adding it to `wp-config.php` instead:
 
 `define('RANKRAFT_SITE_KEY', 'rr_live_…');`
 
+Step-by-step guide with screenshots: [docs.rankraft.ai](https://docs.rankraft.ai/agent-analytics/wordpress/introduction).
+
 == Frequently Asked Questions ==
 
-= Will this slow down my site? =
+= Do I need a RankRaft account? =
 
-No. Logging runs after the response is sent and costs a single database insert. Sending happens in the background via WP-cron.
+Yes. The plugin collects the data; your reports are in the RankRaft dashboard. You can [try RankRaft free for 7 days](https://app.rankraft.ai/signup), no credit card needed.
 
-= My site uses a CDN or a full-page cache. Will crawlers be logged? =
+= Why can't Google Analytics show me AI bots? =
 
-Yes for WordPress page caches. The plugin writes a small rule to .htaccess so AI and search crawlers skip FlyingPress, WP Rocket, LiteSpeed Cache, WP Super Cache and LiteSpeed's server cache and reach PHP; visitors still get cached pages. Use "Check cache bypass" on the Status tab to confirm. Caches that sit in front of your server (Cloudflare, a CDN, some managed hosts on Nginx) cannot be bypassed from WordPress — for those, add the RankRaft Cloudflare integration, which sees every request.
+Google Analytics and similar tools count visits by running JavaScript in a browser. AI bots read your pages without running JavaScript, so those tools never see them. This plugin notes visits on your server, where every request arrives.
 
-= WP-cron is disabled on my host. =
+= Will it slow down my site? =
 
-Point a system cron at `wp-cron.php` every minute. The Status tab shows the exact command.
+No. Each visit is noted after the page has already been sent to the visitor, and data is sent in the background about once a minute.
+
+= Does it work with caching plugins? =
+
+Yes. With WP Rocket, FlyingPress, LiteSpeed Cache or WP Super Cache, the plugin makes sure AI bots still reach WordPress so their visits are counted, while your visitors keep getting fast cached pages. Use **Check cache bypass** on the Status tab to confirm it's working. If a service in front of your site (such as Cloudflare or your host's own cache) answers before WordPress does, connect the RankRaft Cloudflare integration instead — it sees every visit.
+
+= What data is collected? Is it GDPR-friendly? =
+
+Only technical details of each public page request: the page address, time, response status, browser identification, the referring page and the visitor's IP address. Logged-in areas, checkouts and account pages are never recorded, sensitive values in links are blanked out, and IP addresses are stored only as one-way hashes. No cookies are set. The plugin also adds suggested wording to WordPress's privacy policy guide (*Settings → Privacy*). See the External services section for the full list.
+
+= Can I stop some pages being recorded? =
+
+Yes. On the Privacy tab, list any extra paths you never want recorded, for example a members area. Admin, login, checkout, cart and account pages are always excluded.
 
 = What happens if RankRaft is down? =
 
-Logs queue locally (up to 100,000 rows) and are sent when the service is back. Nothing is lost for up to 7 days.
+Nothing is lost. The plugin keeps the data on your site and sends it when RankRaft is back, for up to seven days.
 
-= What happens if my RankRaft subscription lapses? =
+= What happens if my RankRaft subscription ends? =
 
-RankRaft tells the plugin, which pauses logging (nothing is queued or sent) and shows a notice in wp-admin with a link to update billing. Once billing is fixed, RankRaft notifies the plugin through a signed request to `/wp-json/rankraft-aa/v1/resume` and logging resumes by itself; anything still queued is sent. "Test connection" on the Status tab re-checks immediately.
+The plugin pauses — nothing is recorded or sent — and shows a notice in your WordPress admin. When billing is sorted out it resumes by itself.
+
+= WP-Cron is disabled on my host. =
+
+Point a server cron job at `wp-cron.php` every minute. The Status tab shows the exact command.
 
 = Does it work on multisite? =
 
-Each site in the network is configured separately with its own site key.
+Yes. Each site in the network is set up separately with its own site key.
 
 == Screenshots ==
@@ -81 +127 @@
 1. Settings → RankRaft AI: the whole General tab — site key, logging toggle and the crawler cache-bypass option.
 2. Privacy tab: exactly what is sent, the redaction list that cannot be switched off, and optional extra paths to exclude.
+3. Status tab: delivery health, queue depth, last send and the next scheduled run.
 
 == Changelog ==
 
+= 1.2.4 =
+* The plugin's links now point to its documentation at docs.rankraft.ai.
+* A clearer description in the plugin directory.
+
 = 1.2.3 =
-* Security: the visitor's address is now taken from a proxy header only when the request came from a proxy the plugin can name — Cloudflare's published ranges, a proxy on the host or local network, or one added through the new `rankraft_aa_trusted_proxies` filter (an array of IPs or CIDR blocks). Before, any visitor could set `CF-Connecting-IP` or `X-Forwarded-For` themselves and be recorded, and verified, as a crawler from that address. Sites behind another CDN or load balancer should add its addresses through the filter.
-* Privacy: the referring page is sent without its query string or fragment, so a link clicked from a page carrying a token (a password-reset link, an order confirmation) no longer ships that token.
-* Fixed: a resume push from RankRaft can no longer be replayed inside its five-minute window.
-* Fixed: a `429 Too Many Requests` from the ingest API keeps the batch for retry instead of deleting it.
-* Fixed: the cache-bypass rule now leaves real directories alone, and on an https site it waits for the site's own http→https redirect rather than catching the request first.
-* Fixed: unticking "manage .htaccess" or disabling logging removes the cache-bypass block instead of leaving it in place.
-* Fixed: the queue cap is checked against a fresh count when the cached size has lapsed; cron is no longer spawned from a visitor's request under `ALTERNATE_WP_CRON`.
-* Changed: with no `AUTH_KEY`/`SECURE_AUTH_KEY` in wp-config.php the site key is stored as typed rather than under a key derived from the install time, which was no protection.
+* Security: bot visits can no longer be faked by a visitor sending a made-up proxy header. The visitor's address is read from a proxy header only when the request came through a proxy the plugin trusts — Cloudflare, your host or local network, or addresses you add with the `rankraft_aa_trusted_proxies` filter. Sites behind another CDN or load balancer should add its addresses there.
+* Privacy: the referring page is now sent without its query string, so private links (such as password-reset or order-confirmation pages) are never passed on.
+* Fixed: data is kept and retried, not dropped, when RankRaft asks the plugin to slow down.
+* Fixed: the cache-bypass rule no longer affects real folders on your server, and works with the site's own http→https redirect.
+* Fixed: turning off logging now removes the cache-bypass rule from .htaccess.
+* Other small reliability and security fixes.
 
 = 1.2.2 =
-* Fixed: a backslash in the query string or request path was being removed from requests that came through the cache-bypass rule. 1.2.1 added `wp_unslash()` to those two `$_SERVER` reads, but they run on `plugins_loaded`, before WordPress slashes `$_SERVER` in `wp_magic_quotes()` — so there was nothing to unslash and real backslashes were stripped instead.
+* Fixed: backslashes in page addresses were being removed from some recorded requests.
 
 = 1.2.1 =