內容簡介
Vireo Analytics 是一款自我託管的 WordPress 分析工具，提供無需使用 Cookie 的 Google Analytics 替代方案。它能夠保留使用者的歷史數據，顯示每篇文章的 Google 搜尋來源，並分析 AI 助手對網站的影響，確保所有訪客數據安全存儲於自己的資料庫中。
【主要功能】
• 保留 Google Analytics 歷史數據
• 顯示每篇文章的 Google 搜尋統計
• 分析 AI 助手帶來的流量
• 排除已知爬蟲和自動化工具的數據
• 支援多個前端網站的訪問計數
• 提供每週電子郵件摘要和 CSV 匯出功能
外掛標籤
開發者團隊
② 後台搜尋「Vireo Analytics – Cookieless WordPress Stats & Google Analytics Alternative」→ 直接安裝（推薦）
📦 歷史版本下載
原文外掛簡介
Vireo Analytics is self-hosted analytics for WordPress. It brings your history with you when you leave Google Analytics, shows the Google searches behind each post, and tells you what AI assistants take from your site against the readers they send back. Visitor data stays in your own database, with no cookies and no consent banner.
Bring your history with you
Switching analytics tools usually means your charts start again on the day you switch. Vireo imports your daily traffic, pages, referrers, countries and devices from Google Analytics 4, so the years you already have stay in front of you.
It also imports from Koko Analytics, Jetpack Stats, Statify, WP Statistics, Burst Statistics, Independent Analytics, SlimStat and Plausible (from Plausible’s CSV export), bringing whatever each one kept: referrers per post, browsers and devices, missing pages, outbound clicks, downloads and custom events where the source recorded them. Imports run in batches you can watch, stop the day before Vireo’s own data begins so no day is counted twice, and ask before importing a range you’ve already brought in. The switching guides show what comes across from each one.
The searches behind each post
Google stopped passing search terms to websites years ago, so most analytics plugins see a visit from Google and nothing more. Connect Search Console once and every post’s stats screen lists the searches it appeared for, with clicks, impressions and average position. The Overview shows the landing page beside each search.
What AI takes, and what it sends back
ChatGPT, Claude, Gemini, Perplexity and Copilot are reported as their own traffic source. Next to the readers they send, Vireo counts the pages their crawlers fetched, so you can see the ratio for your own site. It works on the history you’ve already collected.
Numbers you can check
Over 800 known crawlers, AI trainers, SEO tools, uptime monitors and headless browsers are kept out of your numbers. Vireo reports how many it excluded and why, so a figure lower than your server logs makes sense. Automated browsers that claim to be Chrome are caught by the flags automation tools set on themselves, and prefetched pages nobody looked at aren’t counted. The bot directory lists every one Vireo knows.
Headless WordPress: Astro, Next.js and others
If your posts live in WordPress but visitors read them on an Astro, Next.js or other front end, Vireo can count that front end too. Enter its address in Settings, paste one script tag into the front end, and each pageview is matched to the WordPress post it shows, so per-post stats and Search Console searches keep working. It’s free for one front end.
Your other sites, in the same dashboard
Run a static site, a docs site or a landing page next to your WordPress site? Add it under Settings and paste one tag into it. Its visits are counted on their own, without cookies, and a site selector on the Overview switches between your sites. One connected site is free.
Everything else
An Overview that opens with what changed since the previous period, and the pages and sources behind it.
A Popular posts block, shortcode and widget built on your real, bot-filtered view counts, plus a view counter for single posts.
A Year in review for any year with data, including the history you imported from another tool, and weekly highlights on the Overview and in the weekly email.
Top pages, referrers grouped by how people arrived, countries and devices, with filters for each.
Average time on page and bounce rate, with each page’s time in Top pages. Time counts only while the tab is in front of the reader.
Core Web Vitals from your real visitors, graded at the 75th percentile the way Google grades them, with Google’s PageSpeed lab test of any page one click away.
Notes pinned to a date, so a spike still has its explanation weeks later.
A weekly email digest, CSV export of any view, and a views column on the Posts screen.
Custom events for clicks and form submissions, and 404 tracking to find broken links.
Read-only dashboard access for editors or clients, without making them administrators.
An MCP server, so Claude, Cursor or any other AI assistant can answer questions about your traffic from the real numbers. A REST API and WordPress Abilities for everything else.
Multisite support, with one view across the network.
Headless WordPress support: count visits to the Astro, Next.js or other front end that shows your WordPress content.
Connected sites: count visits to your other sites, WordPress or not, from the same dashboard.
A warning in Site Health if recording stops, so a broken setup doesn’t look like a quiet week.
Reports for WP RSS Aggregator and Spotlight sites: clicks through to aggregated articles per feed source, and what visitors do with Instagram feeds.
Translated into German, Spanish, French, Italian, Japanese, Dutch, Portuguese (Portugal and Brazil) and Russian.
Vireo Pro: see which pages and visitors make you money
The free plugin is complete on its own. Vireo Pro is for sites that sell something or report to clients:
Revenue from WooCommerce, Easy Digital Downloads, FluentCart and Freemius, traced to the page and source that brought each buyer.
Goals and funnels, with each step’s conversion on screen.
Shareable read-only dashboards for clients, with an expiry date and a password.
More connected sites, a live view, entry and exit pages, and a weekly email that explains what changed.
Pro starts at $60 for the first year on one site, with a 30-day money-back guarantee. See Vireo Pro and pricing.
Privacy
Vireo sets no cookies and stores nothing on visitors’ devices. Visitors are counted with a salted hash that changes every day, so nobody can be followed from one day to the next. Do Not Track and Global Privacy Control are honoured without a setting. Visitor data is never sent to RebelCode or anyone else; the only outside services are the ones you choose to connect, listed under External services below.
External services
This plugin includes an optional importer for historical Jetpack Stats data. When (and only when) a site owner runs that importer from Vireo Analytics → Settings → Import data, the plugin calls the WordPress.com Stats API at https://stats.wordpress.com/csv.php to retrieve the site’s existing pageview, referrer, and top-post history.
What is sent:
The WordPress.com API key the site owner pastes into the import screen.
The site address whose stats are being imported.
A requested date range and table name (e.g. views, referrers, topposts).
What is not sent: no visitor data, no user data, no site content, no credentials beyond the API key the site owner entered.
When it is sent: only while the import is actively running, in response to a site owner clicking “Run Import”. No background or recurring calls are made.
The Stats API is provided by Automattic Inc. (WordPress.com).
Terms of Service: https://wordpress.com/tos/
Privacy Policy: https://automattic.com/privacy/
The importer is entirely optional.
Google Analytics (optional, importer)
When a site owner runs the Google Analytics importer, the plugin signs a request with the service-account key they pasted and calls https://oauth2.googleapis.com/token for an access token, then https://analyticsdata.googleapis.com to read that property’s history.
What is sent: the service account’s own credentials and a date range. No visitor data, no site content, nothing about anyone reading the site.
When it is sent: only while an import is running, in response to a site owner starting one. The key can be removed from the same screen afterwards.
Google Search Console (optional)
When a site owner connects Search Console, the plugin authenticates the same way and calls https://searchconsole.googleapis.com to read the searches that led people to the site.
What is sent: the service account’s own credentials, the property address the owner entered, and a date range.
When it is sent: once a day on a schedule, and whenever the owner presses the refresh control. A refresh fetches the last week straight away and then the rest of the requested history in the background, a fortnight at a time over a few minutes, so that one press can produce several calls in a row. This is the one recurring outbound call the plugin makes, and it only happens on sites that have connected Search Console. Disconnecting stops it and removes the schedule.
Both Google APIs are provided by Google LLC.
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
Google PageSpeed Insights (optional)
The Page speed tab and each post’s stats screen have a button for Google’s PageSpeed Insights lab test. It works one of two ways.
Without an API key (the default), the button is a link. It opens https://pagespeed.web.dev/ in the admin’s own browser, with the address of the page being tested in the link, and Google runs the test there. The plugin’s server sends nothing and stores nothing.
With an API key the site owner adds under Settings, the plugin calls https://www.googleapis.com/pagespeedonline/v5/runPagespeed from the server and shows the result on the dashboard.
What is sent: the address of the page being tested, which is always a page on this site or on a connected site, the device to test as (mobile or desktop), the admin’s language, and, on the API path, the site owner’s API key. No visitor data and nothing about anyone reading the site.
When it is sent: only when someone with access to the Vireo dashboard presses the button. Nothing runs on a schedule or on the front end. API results are kept for a day so the page can show them again without another test.
PageSpeed Insights is provided by Google LLC.
Terms of Service: https://developers.google.com/terms
Privacy Policy: https://policies.google.com/privacy
DB-IP (optional, geolocation)
Country-level geolocation needs a local database, and Pro’s city-level detail needs a second one. When a site owner presses the download button, the plugin fetches the current monthly file from https://download.db-ip.com.
What is sent: nothing but the request for the file. No site data, no visitor data, no identifiers. Lookups afterwards happen entirely on your own server against the downloaded file; no address is ever sent anywhere.
When it is sent: only when the owner presses the button.
DB-IP Lite data is provided by DB-IP under CC BY 4.0.
Website: https://db-ip.com/
Privacy Policy: https://db-ip.com/legal/privacy
A site that imports nothing, connects nothing, adds no PageSpeed API key and downloads no geolocation database contacts none of these services from its own server.
It does make one recurring request to itself: once an hour the plugin posts to its own tracking endpoint to check the fast path is still reachable, because a host rule or a CDN change can break it silently. That request never leaves your server and carries no data about anyone.
None of these paths send visitor data anywhere. Every one of them pulls data in.
