Vireo Analytics – Cookieless WordPress Stats & Google Analytics Alternative

By RebelCode

★ 5.0/5 (6 ratings)20+ active installationsVersion 0.31.0

Cookieless WordPress analytics. Import your Google Analytics history, see the searches behind each post and what AI crawlers take. Data stays yours.

Description

Vireo Analytics is self-hosted, cookieless analytics for WordPress. Visitor data stays in your own database. It brings your history with you when you switch, shows the Google searches behind each post, and weighs what AI crawlers take from your site against the readers AI assistants send back.

Bring your history with you

Vireo imports your daily traffic, pages, referrers, countries and devices from Google Analytics 4. It also imports from Koko Analytics, Jetpack Stats, Statify, WP Statistics, Burst Statistics, Independent Analytics, SlimStat, Post Views Counter, Matomo, Plausible, Fathom Analytics, Simple Analytics, Cloudflare Web Analytics and Clicky. On a site connected to Jetpack, that import needs no API key. Imports stop the day before Vireo’s own data begins, so no day is counted twice. The switching guides show what comes across from each tool.

The searches behind each post

Connect Search Console once and every post’s stats screen lists the searches it appeared for, with clicks, impressions and average position.

What AI takes, and what it sends back

Vireo reports ChatGPT, Claude, Gemini, Perplexity and Copilot 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. Assistants that fetch a page because a reader asked get their own list, apart from crawlers.

The AI visibility scan fetches a page the way an AI crawler does and lists what could be keeping crawlers out: robots.txt rules, a firewall answering GPTBot or ClaudeBot with an error, text that only appears with JavaScript, a missing sitemap. Each failed check says how to fix it.

Numbers you can check

Vireo keeps known crawlers, AI trainers, SEO tools, uptime monitors and headless browsers out of your numbers and reports how many it excluded and why. The bot directory lists them all.

When a visit you expected isn’t in the report, “Why wasn’t my visit counted?” under Settings, Troubleshooting checks your browser against every exclusion, Do Not Track, the bot filter and consent, and tests that the tracker loads and the collector answers. Each reason comes with the setting to change. A Privacy check tab marks each privacy setting Good or Worth a look and writes a “what this site collects” statement for your privacy policy.

Headless WordPress and your other sites

If visitors read your posts on an Astro, Next.js or other front end, or you run a static or docs site next to WordPress, paste one script tag into it and switch between sites on the Overview. Pageviews are matched to the WordPress post they show. One connected site is free.

Everything else

  • An Overview that opens with what changed and why, then top pages, referrers by channel (email included), countries and devices, each filterable.
  • Average time on page and bounce rate, and Core Web Vitals from your real visitors with Google’s PageSpeed test one click away.
  • Chart notes that pin the likely cause of a spike or dip (a post update, a plugin or WordPress update), your own notes, and a Year in review for any year with data.
  • Form submissions and signups from Contact Form 7, Gravity Forms, Ninja Forms, Formidable, Forminator, Fluent Forms, Jetpack Forms and other form plugins, recorded as events with nothing the visitor typed, plus custom events, a most-clicked links report and 404 tracking.
  • A Popular posts block, widget and shortcode builder, an email digest, and CSV export in plain, Excel-friendly or tab-separated form.
  • An MCP server, so Claude, Cursor or any other AI assistant can answer questions about your traffic from the real numbers, plus a REST API and WordPress Abilities.
  • Read-only dashboard access for editors or clients, and multisite support.
  • Translated into German, Spanish, French, Italian, Japanese, Dutch, Portuguese (Portugal and Brazil) and Russian.

Vireo Pro: see what earns money and report it

For sites that sell, run campaigns or report to clients:

  • Revenue from WooCommerce, Easy Digital Downloads, FluentCart and Freemius, traced to the page and source that brought each buyer, with goals and funnels.
  • Orders and revenue for each UTM campaign, QR codes and short links, and affiliate clicks by the page they came from.
  • Heatmaps of where visitors click and scroll.
  • A report builder for scheduled email reports, and client dashboards with an expiry date, a password and your logo.
  • A live view, entry and exit pages, on-site search analytics, and CSV data feeds for spreadsheets.
  • The pages AI assistants send readers to, alerts when AI crawlers drop off, and weekly scans of what ChatGPT, Claude and Gemini say about your site.

Pro starts at $69 a year for 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. Vireo counts visitors with a salted hash that changes every day and honours Do Not Track and Global Privacy Control. It never sends visitor data 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 to retrieve the site’s existing pageview, referrer, and top-post history. On a site connected to Jetpack it reads https://public-api.wordpress.com/rest/v1.1/sites/{site ID}/stats/ through Jetpack’s own connection; with an API key it reads https://stats.wordpress.com/csv.php.

What is sent:

  • Over the Jetpack connection: the site’s WordPress.com site ID and the request signed with the connection Jetpack already holds.
  • With an API key: the WordPress.com API key the site owner pastes into the import screen, and the site address whose stats are being imported.
  • A requested date range and report name (e.g. views, referrers, top-posts).

What is not sent: no visitor data, no user data, no site content, no credentials beyond Jetpack’s existing connection or 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: while an import is running, in response to a site owner starting one. The key can be removed from the same screen afterwards.

Cloudflare Web Analytics (optional, importer)

When a site owner runs the Cloudflare Web Analytics importer, the plugin calls https://api.cloudflare.com/client/v4/graphql with the API token they entered to read that site’s history.

What is sent: the API token, the account ID, the website and a date range. No visitor data, no site content, nothing about anyone reading the site.

When it is sent: while an import is running, in response to a site owner starting one. The token can be removed from the same screen afterwards.

The API is provided by Cloudflare.

  • Terms of Service: https://www.cloudflare.com/website-terms/
  • Privacy Policy: https://www.cloudflare.com/privacypolicy/

Matomo (optional, importer)

When a site owner runs the Matomo importer, the plugin calls the Reporting API at the Matomo address they entered to read that site’s history. For a self-hosted Matomo, the data goes to the site owner’s own Matomo server and to no third party.

What is sent: the auth token (in the request body), the site ID and a date range. No visitor data, no site content, nothing about anyone reading the site.

When it is sent: while an import is running, in response to a site owner starting one. The token can be removed from the same screen afterwards.

For a Matomo Cloud address, the Matomo Cloud privacy policy applies.

  • Privacy Policy: https://matomo.org/privacy-policy/

Fathom Analytics (optional, importer)

When a site owner runs the Fathom Analytics importer, the plugin calls https://api.usefathom.com/v1/aggregations with the API token they entered to read that site’s history.

What is sent: the API token, the Fathom site ID and a date range. No visitor data, no site content, nothing about anyone reading the site.

When it is sent: while an import is running, in response to a site owner starting one. The token can be removed from the same screen afterwards.

The API is provided by Fathom Analytics.

  • Terms of Service: https://usefathom.com/legal/terms
  • Privacy Policy: https://usefathom.com/legal/privacy

Simple Analytics (optional, importer)

When a site owner runs the Simple Analytics importer, the plugin calls the Stats API at https://simpleanalytics.com/ for the website they entered, with their API key, to read its history.

What is sent: the API key, the website’s hostname and a date range. No visitor data, no site content, nothing about anyone reading the site.

When it is sent: while an import is running, in response to a site owner starting one. The key can be removed from the same screen afterwards.

The Stats API is provided by Simple Analytics.

  • Terms of Service: https://www.simpleanalytics.com/general-terms-and-conditions
  • Privacy Policy: https://www.simpleanalytics.com/privacy-policy

Clicky (optional, importer)

When a site owner runs the Clicky importer, the plugin calls https://api.clicky.com/api/stats/4 with the site ID and sitekey they entered to read that site’s history.

What is sent: the site ID, the sitekey and a date range. No visitor data, no site content, nothing about anyone reading the site.

When it is sent: while an import is running, in response to a site owner starting one. The sitekey can be removed from the same screen afterwards.

The API is provided by Clicky.

  • Terms of Service: https://clicky.com/terms
  • Privacy Policy: https://clicky.com/terms/privacy

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

MaxMind GeoLite2 (optional, geolocation)

A site owner can connect their own free MaxMind account so the plugin downloads and updates the GeoLite2 Country database for them. Nothing is contacted until the owner saves an account ID and license key under Settings, Geo-location.

What is sent: the owner’s MaxMind account ID and license key, as HTTP Basic authentication on the request for the database file to https://download.maxmind.com, plus the usual details of any web request (this server’s IP address). No visitor data, no site content and no identifiers of anyone reading the site. Lookups afterwards happen entirely on your own server against the downloaded file; no visitor address is ever sent anywhere.

When it is sent: when the owner saves the account details or presses Update now, and then once a day to check whether MaxMind has published a newer file. A day with nothing new is a single small request for the file’s checksum.

GeoLite2 data is created by MaxMind and used under the GeoLite End User License Agreement. This product includes GeoLite2 Data created by MaxMind, available from https://www.maxmind.com.

  • Website: https://www.maxmind.com/
  • GeoLite End User License Agreement: https://www.maxmind.com/en/geolite2/eula
  • Privacy Policy: https://www.maxmind.com/en/privacy-policy

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.

Installation

  1. Upload the plugin files to /wp-content/plugins/vireo-analytics/, or install via Plugins → Add New and search for “Vireo Analytics”.
  2. Activate the plugin through the Plugins menu.
  3. Visit Vireo Analytics → Overview to see your dashboard. First pageviews will appear within a minute.

To bring your history across from Google Analytics or another plugin, go to Vireo Analytics → Settings → Import data. If another supported analytics plugin is installed, the Overview offers to import from it.

FAQ

Is there a paid version?

Yes, Vireo Pro. Everything described above stays free. Pro adds revenue and conversion reports for stores, goals and funnels, client dashboards and more connected sites. If you stop paying, the free plugin keeps working with all your data. Pricing is on vireowp.com.

Is this GDPR-compliant?

Yes. Vireo Analytics doesn’t set cookies, doesn’t use localStorage for tracking, and hashes visitor identifiers with a salt that rotates every 24 hours. With Shorten IP addresses on, it also meets the IP condition in CNIL’s guidance on audience measurement without consent. Whether your site needs a banner is for you and your adviser to decide. Country-level geolocation is derived from the IP on the server; the raw IP is never written to the analytics tables, and the short-lived buffer file holding it is deleted as soon as the aggregator processes it, usually within a minute. You should still mention the plugin in your privacy policy.

What exactly does the “Visitors” number mean?

Within a single day it’s a true unique count: one person is counted once no matter how many pages they read. Over a longer range it’s the sum of the daily counts, so someone who visited on three days in the month counts three times.

That isn’t laziness, it’s the privacy model. A visitor is identified by a hash of their IP and browser, salted with a secret that is thrown away and regenerated every night. Tomorrow the same person produces a completely different hash, so there is nothing that can link them back to today. That’s what makes cookie-free, consent-free tracking legitimate rather than a technicality. The cost is that “unique people this month” is a question the data genuinely cannot answer, and we’d rather say so than print a number that looks precise and isn’t.

Pageviews are exact over any range.

Does it honour Do Not Track and Global Privacy Control?

Yes, and it’s on by default. If a visitor’s browser sends DNT: 1 or Sec-GPC: 1, the tracker refuses to fire for them, and the collection endpoint refuses the pageview even if something sends one anyway. Those visits are not recorded anywhere. This costs you some traffic in the dashboard, which is the point: an opt-out you can switch off isn’t an opt-out. If you have a specific reason to override it, the vireo_honor_opt_out filter can return false.

Why are my numbers lower than another plugin’s?

Most analytics plugins count some automated traffic as visitors: uptime monitors (StatusCake, UptimeRobot, Pingdom), SEO crawlers (Ahrefs, Semrush, MJ12), AI crawlers (GPTBot, ClaudeBot, PerplexityBot) and testing tools. Vireo filters those out and shows you what it removed, by category, so you can check the difference yourself. If you’d rather count some of them, the vireo_bot_ua_pattern filter changes the pattern.

Can I migrate from Jetpack Stats?

Yes. Settings, then Import data, pulls your daily pageviews, top posts and referrers from the WordPress.com Stats API for whatever date range you choose. When Jetpack is connected, the import reads the stats through that connection with nothing to fill in. Otherwise you paste in your WordPress.com API key and the site address the stats are recorded under, and Jetpack doesn’t need to be active or connected. Jetpack Stats has no visitor counts, so imported days show pageviews only.

Can I migrate from Google Analytics?

Yes. Settings, then Import data, brings your history across: daily pageviews and visitors, your pages, your referrers and which pages they sent readers to, countries, devices, outbound clicks, downloads, form submissions and your own custom events. It reads the Analytics Data API directly, so you need a Google service account key and your numeric property ID rather than the G- measurement ID. Sessions, conversions and the events GA4 collects on its own (page views, scrolls, session starts) do not come across.

Can I migrate from Plausible Analytics?

Yes. Export your site from Plausible (Site settings, then Imports & Exports), then upload the zip under Settings, then Import data. Daily pageviews and visitors, pages, referrers, countries, device types, goals and custom events come across, with outbound clicks, file downloads and 404s landing in the same reports as Vireo’s own. No API key is needed, and the uploaded file is deleted as soon as it has been read. Browsers, operating systems, entry and exit pages and custom properties are not imported.

Can I ask an AI assistant about my stats?

Yes. Vireo runs an MCP server at /wp-json/vireo-analytics/mcp, so Claude Code, Claude Desktop, Cursor and other MCP clients can ask about traffic, what changed, which pages are growing, what people searched for, which AI assistants send readers, broken links and more. Open Settings, Search Console & API and copy the ready-made configuration for your client. The assistant signs in with an application password you create on your profile, sees only what that user can see in the dashboard, and can read, never change anything. Nothing is sent anywhere: your assistant connects to your site directly.

Does Vireo share anything with MainWP?

No. Free Vireo Analytics never answers a MainWP dashboard. Sites that want their numbers in a MainWP dashboard can do it with Vireo Analytics Pro.

Can I show my most popular posts?

Yes. Add the Popular posts block anywhere blocks work, including block theme templates, or use the [vireo_popular_posts] shortcode or the Popular posts (Vireo) widget on classic themes. Choose how many posts, the period (last 7, 30 or 90 days, or all time), which post types, and whether to show featured images and view counts. It uses the same bot-filtered counts as your dashboard, lists only published posts that aren’t password-protected, adds no tracking, and is cached so it stays fast. To show a single post’s views, use the Post views block or [vireo_views].

Does it work with caching plugins?

Yes. Tracking runs on every page load via a lightweight POST beacon, including cached pages. When you first activate the plugin, you may need to wait for your cache to regenerate before every page starts tracking. Once that happens, tracking is universal.

My theme or landing page doesn’t count visits. Why?

The tracker loads in the footer through wp_footer(). Some themes, page builders and landing-page templates leave that call out, so the tracker never loads. Add <?php do_action( 'vireo_print_tracking_script' ); ?> just before </body> in that template. It’s safe on pages that also call wp_footer(): the tracker only prints once.

My site is headless. Can it count visits to my Astro or Next.js front end?

Yes. Under Settings, then Other sites, enter the front end’s address under “Headless front end”. Pages on that site can then send pageviews to this WordPress site; anything from another address is refused. Paste the script tag shown under the setting into every page of the front end. It counts Astro view transitions on its own, and with data-spa="history" it counts page changes on other single-page front ends. Each pageview is matched to the WordPress post at the same path, so a front end that keeps the permalink structure needs nothing else, and Top pages, the per-post view counts and Search Console per post all work as they do for a theme. One front end per site.

Two things stay out of reach. Crawlers are counted when they fetch a page from WordPress, so the crawler and AI-bot numbers do not include requests made to the front end. And Core Web Vitals are not collected from the front end yet.

How does it compare to Google Analytics?

Google Analytics shows you more (segmentation, audiences, attribution modelling) but requires a cookie banner, sends your visitors’ data to Google, and has become increasingly complex. Vireo Analytics answers “how many people visited what, from where, on what device”, which is what most WordPress site owners actually look at. For site owners who don’t need enterprise-grade attribution modelling, the tradeoff is usually worth it.

Does it track logged-in admins?

By default, no. There’s a setting at Vireo Analytics → Settings to enable admin tracking if you want to see your own visits (useful for testing).

How long is data kept?

Raw visitor hashes and referrer rows are aggregated into daily rollups after 24 hours. Daily rollups are kept indefinitely unless you set a retention limit in Settings → Retention. The default retention is 730 days (two years).

Will it slow down my site?

The tracking beacon is fired asynchronously after the page is interactive, using the browser’s navigator.sendBeacon() API where available. The pageview is recorded by a standalone endpoint that boots WordPress without loading plugins or your theme. Hosts that block direct PHP inside wp-content fall back to admin-ajax automatically. On a well-hosted site you will not notice a difference.

Screenshots

Changelog

0.31.0

  • Change: buttons, form controls and the admin screens follow the WP RSS Aggregator v5 admin style, so Vireo sits next to it without a visual break.
  • Change: the Astro install snippet and the update notice name the @jgnpm/vireo-astro package, translated in all nine languages.

0.30.1

  • Translations: every string added in 0.30.0 is translated in all nine languages, including the new Other sites and Troubleshooting settings tabs.

0.30.0

  • Change: the top of the Overview is one card: the headline and its cause, the AI read when Pro is active, then the week’s facts. On wide screens the week sits beside the headline.
  • New: What changed leads with the channels (Search, Other sites, Direct, AI assistants, Social, Email) as before and after, biggest change first, each opening to the sites that moved. Pages and sources that moved follow on one shared scale, small moves fold into one line, a page published in the period is listed as new, and suspected junk referrers are left out.
  • New: every card header names the range it covers, with both periods’ dates on hover. The range and filters stay pinned under the admin bar while scrolling, as one chip naming the range on phones and tablets.
  • New: referrers show the source’s logo from a bundled icon set, with nothing fetched from outside the site. Browsers and operating systems get theirs too.
  • Change: today is drawn as a day still in progress: a dashed last segment on the sparklines, a lighter bar marked “so far”, and Average daily traffic over complete days only.
  • Change: the daily chart’s scale fits the current period; a prior-period day above it is marked at the top instead of shrinking every bar.
  • Change: Top countries is a table with flags, changes and visitors. Technology shows device types, browsers and operating systems side by side.
  • Change: a share that moved by a point or more shows its change as a percentage with an arrow, and the tooltip spells out the points and the earlier share.
  • New: the dashboard widget switches its 7, 30 and 90 day figures between pageviews and visitors and remembers the choice, draws today lighter, and folds www. into the bare host in its referrer list.
  • New: a Shopify store can be a connected site. Choose A Shopify store when you connect it and Vireo gives you a custom pixel to add under Settings, Customer events in the Shopify admin; the store’s visits show on the dashboard under its own name. The pixel sets no cookies, keeps nothing in the browser and sends no customer details. It also sends completed checkouts, which Vireo Analytics Pro adds to Revenue as orders.
  • New: links from your pages to a connected Shopify store carry the page they were clicked on, so Pro can credit a store order to the post that sent the buyer.
  • Fix: with Automatic, the visitor’s address is read from Cloudflare’s CF-Connecting-IP only when the request came through Cloudflare. Behind any other proxy on the same server or network it follows X-Forwarded-For from the nearest hop back, and X-Real-IP is read only when you pick it.
  • Fix: country headers other than Cloudflare’s are believed only from proxy ranges you name with the vireo_geo_trusted_proxies filter, and Cloudflare’s only from Cloudflare.
  • New: a Proxy addresses setting next to Visitor IP source. A named header such as X-Forwarded-For is now believed only when the request arrives from a private network, Cloudflare or an address listed there, so a visitor reaching the server directly can’t choose their own address. Sites behind another CDN should add its ranges.
  • Fix: the daily pageview limit per address treats an IPv6 network (/64) as one address.
  • Fix: the daily limit on new pages applies to pages that aren’t a real post, and a post ID only earns the per-post allowance on that post’s own address. Site Health says when the limit is reached and how to raise it with the vireo_max_new_paths_per_day filter.
  • Fix: pages of a connected site count against the daily limit on new pages like the site’s own.
  • Change: the email sent when recording stops is on for new installs. Sites that were already running keep it off until they turn it on under Settings.
  • Fix: when Jetpack Stats is turned off, the Jetpack import says to turn it on while the import runs, in place of WordPress.com’s raw error.
  • Fix: All time opens with the total and the day it starts from, and a range before Vireo started recording says so with the date, in place of the new-install “Collecting data” line.
  • Change: Settings has two new tabs. Other sites holds connected sites and the headless front end, and Troubleshooting holds “Why wasn’t my visit counted?” and the bot filter test, so Tracking is only about what gets counted. Links to the old places still open the right tab.
  • Fix: the Privacy check’s “Open setting” links stay on one line.

0.29.4

  • Security: public dashboards and the referrers shortcode list a referring site once it has sent at least five visitors on two or more days, so a one-off spam referrer stays off public pages. The public list says so while it’s empty.
  • Security: abilities whose results carry text that visitors chose, such as referrer hosts, page paths, link labels, search queries and event values, tell AI assistants to treat that text as data, and their results follow declared output schemas.
  • Fix: blocking a referrer refreshes the dashboard straight away and keeps the site’s other cached data.
  • Fix: the public dashboard no longer logs a PHP warning when it rebuilds.
  • Translations: every string is now translated in all nine languages: German, Spanish, French, Italian, Japanese, Dutch, Portuguese (Brazil and Portugal) and Russian.

0.29.3

  • Fix: search engines, social networks, AI assistants, email and the site’s own subdomains are no longer shown as suspected junk referrers, including on sites that have just started using Vireo or keep only a short stats history.

0.29.2

  • New: add-ons can add their own sections to the Search Console & API settings tab.
  • Fix: when the Search Console or Google Analytics Data API is switched off in the Google Cloud project, the error names the API and links the page that turns it on.
  • Fix: referrers whose visits are all single pageviews spread thinly across many pages now show as suspected junk, with the Block button beside them.

0.29.1

  • Fix: imported Jetpack history matches Jetpack’s own daily pageview totals, including views Jetpack doesn’t credit to a single post.

0.29.0

  • New: add-ons can register extra overview filters. The filter bar, its chips and Clear all, the cached results and the totals, Top pages and Referrers cards pick them up. While one is active the Visitors figure and the daily chart show pageviews only.
  • Fix: the daily chart draws its days when an add-on adds a series to it.

0.28.1

  • Fix: the import pages fit narrow phone screens, including the Plausible and backup file pickers and the summary above each form.

0.28.0

  • New: while an import runs, its progress replaces the form, with Stop and Stop and undo beside it. Stop keeps the days already imported, and Stop and undo removes what the run wrote.
  • New: comparisons work on imported history. A range and its prior period that are both imported show their change as usual, on the dashboard and in the dashboard widget.

0.27.2

  • New: Astro sites show their setup snippet under Settings, next to the HTML one, for both connected sites and the headless front end.
  • New: each connected site shows when it last reported a pageview.
  • New: a notice appears on a connected site whose tracker is older than the one this version ships, with the steps to update it.

0.27.1

  • New: a Black Friday notice on the Overview for sites without Pro, 17 November to 1 December 2026. It links to the pricing page, can be dismissed per user, and is hidden when Pro is active.
  • Translations: German, Spanish, French, Italian, Japanese, Dutch, Brazilian and European Portuguese and Russian are complete again.

0.27.0

  • Changed: automatic chart notes are on by default after you upgrade. Switch them off under Settings, General, Chart notes.
  • New: bot stats list AI assistants that fetch a page because a reader asked (ChatGPT-User, Claude-User, Perplexity-User, MistralAI-User, Amzn-User, Meta-ExternalFetcher and Google’s user-triggered agents) apart from the AI crawlers that read the web on their own. The crawler-to-reader ratio counts crawlers only, and the bot stats ability returns ai_user_fetch_requests next to ai_crawler_requests. Days recorded before this update keep their fetcher requests under AI crawlers.
  • New: “Why wasn’t my visit counted?” under Settings, Tracking. One click checks the browser you are using against your excluded roles, IP addresses, paths and countries, Do Not Track and Global Privacy Control, the bot filter and consent, loads a page to confirm the tracker is in it and that no optimisation plugin delays it, and tests that the collector answers. It lists each reason with the setting to change, or confirms the visit would be counted. Nothing about you is stored.
  • New: more ways to leave visits out of your numbers. Settings, Tracking, Exclusions now takes specific users (by username or ID), capabilities for logged-in people, user agent text for your own uptime checkers and monitors, and browser language prefixes. They apply to pageviews, events and speed measurements, and are included in settings backups.
  • Fixed: every cell in a CSV, Excel or TSV export now gets the spreadsheet formula guard, including the date and country columns that were written as they came from the database.
  • New: automatic chart notes. Vireo pins the likely cause of a spike or dip on the chart: a post or page published or substantially updated, a plugin activated or updated, a theme switched or updated, a WordPress update, and changes to Vireo’s own settings. Only titles, names and version numbers are noted. A burst of updates on one day becomes one note, and the notes appear in the REST API and the get-annotations ability marked with source “auto”. Turn them off under Settings, General, Chart notes.
  • New: a Privacy check tab under Settings. It reads the site’s current settings and lists IP shortening, Do Not Track and Global Privacy Control, data retention, consent mode, excluded roles and IP addresses, and what is stored, each marked Good or Worth a look with a link to the setting. Below it, a “what this site collects” statement written from the same settings can be copied into a privacy policy, with a link to the suggested policy text.
  • New: form submissions and signups from Jetpack Forms, SureForms, Kadence Blocks forms, WS Form, MailPoet forms and Mailchimp for WP forms are recorded as form_success events, with the form’s id and title and nothing the visitor typed. New FluentCRM contacts who join through a public sign-up are counted too. Spam, drafts and submissions that failed validation are not counted.
  • Fixed: deleting the plugin now removes its cached dashboard figures and two leftover settings, including on sites that also run Pro.
  • New: choose the export format. The CSV export now offers Excel-friendly CSV (UTF-8 with a byte order mark and semicolons, which Excel opens correctly in many European locales) and a tab-separated file, and stays plain CSV by default.
  • New: the Shortcodes screen can list extra reports added by other plugins through the vireo_shortcode_reports filter. Only aggregate totals can be added, and visitors see one only when its author allows it and Public counters is on.
  • Fixed: Site Health no longer shows raw database error text.
  • New: on a site connected to Jetpack, the Jetpack Stats import reads your stats through that connection, with no API key to paste in.

0.26.1

  • Changed: the dashboard uses the width of large screens, with sections side by side from about 1700px.

0.26.0

  • New: a Shortcodes screen under Vireo Analytics builds a report shortcode for you with a live preview. Pick popular posts, a post’s view count, site visitors or top referrers, then copy the result into a page. Top referrers are new as [vireo_top_referrers], and the popular posts and view shortcodes take a label.
  • New: most-clicked links and buttons. Turn on Clicked links and buttons under Settings, Auto-events, and the Campaigns tab lists the internal links and buttons visitors click most, with the page they were on and the change since the previous period. Nothing visitors type and no query strings are recorded. It’s off until you turn it on.

0.25.1

  • Fixed: the Revenue and Ad spend screens in Vireo Analytics Pro open again.

0.25.0

  • New: import your history from Matomo. Connect a self-hosted Matomo or Matomo Cloud with its address, site ID and an auth token, or read a Matomo for WordPress install straight from this site’s database. Daily pageviews and visitors, pages, referrers, countries and device types come across.
  • New: import your history from Fathom Analytics with an API token: daily pageviews and visitors, pages, referrers, countries, browsers, operating systems and device types.
  • New: import your history from Simple Analytics with an API key: daily pageviews and visitors, pages, referrers, countries and device types.
  • New: import your history from Cloudflare Web Analytics with an API token, account ID and website: daily visits and pageviews, pages, referrers, countries, browsers, systems and device types.
  • New: import your history from Clicky with the site ID and sitekey: daily visitors and pageviews, pages, referrers, countries and browsers. With the Clicky plugin installed, the site ID is filled in for you.
  • New: import your history from Post Views Counter. Each day’s views come across for the whole site and for every post, and the import is found automatically on sites that use the plugin.
  • New: every new import has Undo this import and skips days already imported, like the other sources.
  • New: the Top countries, Technology and hourly cards now work while the dashboard is filtered by source (Direct, Search, AI assistants, Social, Email, Other sites). They’re shown by source from the first day after the update.
  • New: fix a broken link from the Broken links report. Redirect sends visitors to another page on your site with a permanent (301) redirect, and the link is marked Fixed. Redirects go into Safe Redirect Manager, Redirection or Rank Math when one is active, and into Vireo Analytics otherwise, where they’re listed under Redirects from this report with a Remove button.
  • New: connect your own MaxMind account under Settings, Geo-location and Vireo downloads the GeoLite2 Country database, checks it, and keeps it up to date every day.
  • New: backups carry your settings. Restoring a backup can bring back exclusions, retention, the email digest, auto-events, blocked referrers and the redirects made from the Broken links report, validated the same way the Settings screen saves them. Backups also hold the by-source country, technology and hourly figures. API keys, license keys and connected sites stay on this install.
  • Fixed: Burst and SlimStat imports place each day correctly across daylight saving time changes.
  • Fixed: Matomo for WordPress imports use your site’s timezone for each day and bring in days that have page totals.
  • Fixed: Fathom Analytics days with very many pages keep each page’s exact daily visitors.
  • Fixed: when an API source returns a partial day, the import stops and says so, so only complete days are marked as imported.
  • Fixed: a redirect from the Broken links report that would loop back through other redirects is refused.
  • Changed: the Cloudflare, Matomo, Clicky and Google Analytics 4 imports remove the saved API credentials once the import completes.
  • Changed: shared dashboard links keep their range and filters. The range carries into the post, referrer and event screens, which share one set of presets, and phones get a range menu on each of them.
  • Changed: a change chip appears once the previous period has data to compare with, and All time shows totals without a comparison.
  • Changed: large numbers read in exact form up to 999,999, then 1.2M and 1.2B. Pages and hosts in other alphabets show in their own characters.
  • Changed: Settings and the importers share the dashboard’s header and accent. Unsaved edits are protected when you leave Settings, and a rejected key stays in its field.
  • Changed: larger tap targets for checkboxes and radio buttons on phones, an undo after removing a note, and names for the built-in events.
  • Changed: backups restore public sharing, email recipients and the front-end address only when you choose to bring them back.

0.24.2

  • Fixed: on a site that serves many URLs through one page, such as property listings under a single Properties page, the dashboard widget listed every one of them under that page’s title. Pages that share a title now show their own paths.

0.24.1

  • Fixed: an import that brought in no views, for example after an API key from the wrong account, no longer marks its days as imported, so running it again with the right key imports them. The import now says when a source had no new views.
  • Translated: the new import screens, including import history, Undo this import and Replace these days, in all nine languages.

0.24.0

  • New: Undo this import. Each import on a source’s history list can be taken back out, leaving Vireo’s own counts and your other imports as they are, and its days can then be imported again.
  • New: every importer skips the days already imported, from any tool, so running an import again only adds what’s missing, and a run that stopped partway picks up where it left off.
  • New: Replace these days, for Plausible. Upload a corrected export and its figures replace the earlier ones for the same days.
  • New: sites running Analytify are pointed to the Google Analytics 4 import.
  • Changed: each day’s visitor secret is created a day ahead, so recording a pageview reads from the database and doesn’t write to it. Old secrets are still deleted on schedule.
  • Fixed: on sites with a persistent object cache, recording a pageview no longer repeats a database write after the first one each day.

0.23.0

  • New: a Shorten IP addresses setting in the Geo-location settings. When it’s on, Vireo removes the last part of each visitor’s address before it tells visitors apart, looks up their country or stores anything. It’s built for the condition in the French regulator CNIL’s guidance on analytics without consent. Off by default.
  • Changed: the Google Analytics 4 and Jetpack importers bring in the whole history, with no dates to pick. Running an import again skips the days already imported.

0.22.1

  • Fixed: a goal on the form_success event, or on any other event recorded by a form plugin or by code on the server, now counts completions. Before, only events sent from the browser completed goals.
  • New: a vireo_form_success action that runs after each accepted form submission is counted, with the form’s id and title.

0.22.0

  • New: each post’s stats screen shows its Search Console clicks next to the visits from Google that Vireo counted, with the usual reasons the two differ.
  • New: after Vireo’s first week, the Overview sums up what it kept out of your numbers and explains the most unusual referrer, such as a payment page sending buyers back to your site.
  • Changed: referrer labels use plain words. “Top referrers” is now “Where visitors come from”, and “Referral” is now “Other sites”.

0.21.0

  • New: first visits from hosting and cloud networks with no referrer are counted as bots under Hosting networks. You can switch this off under Settings, Exclusions.
  • New: a vireo_chart_extra_series filter for drawing extra series on the dashboard widget and Overview traffic charts.
  • Changed: 404 pages no longer count as pageviews. Vireo still records them in the 404 report.
  • Changed: explanatory notes under the dashboard cards are gone. The useful ones show when you hover over the figure.

0.20.1

  • Fixed: when Jetpack Stats refuses an import, Vireo now shows the reason, such as an API key from a WordPress.com account that isn’t an administrator of the site, instead of “Unexpected (non-JSON) response”.

0.20.0

  • New: an Email channel in Top referrers and the source filter. Links tagged utm_medium=email or utm_medium=newsletter are counted there under their utm_source instead of as direct traffic, along with visits from Gmail, Outlook, Yahoo Mail, Proton Mail and Fastmail on the web and from the Gmail and Outlook Android apps. Earlier Gmail app visits move from Referral to Email.

0.19.1

  • New: a Settings link in Vireo’s row on the Plugins screen.
  • Fixed: the Jetpack and GA4 import forms now default to ending the day before Vireo’s own data starts, matching the notice beside them, and that notice is clearer.
  • Translations: German, Spanish, French, Italian, Japanese, Dutch, Brazilian and European Portuguese and Russian are complete again.

0.19.0

  • New: form submissions from Ninja Forms, Formidable Forms and Forminator are recorded as form_success events, with the form’s id and title and nothing the visitor typed. Drafts, spam, failed submissions and builder previews are not counted.
  • Changed: the MainWP child-site integration moves to Vireo Analytics Pro. The free plugin no longer answers a MainWP dashboard, and the vireo_mainwp_enabled filter now belongs to Pro.

0.18.0

  • New: a last-hour pageview count on the dashboard.
  • New: the [vireo_views] shortcode can show views for the whole site or an archive.
  • New: group the chart by week, month or year.
  • New: this week, last week, last year and all time date presets, and a default period you can save.
  • New: an optional public dashboard, off until you switch it on in Settings.
  • New: reset all statistics from Settings.
  • New: wp vireo aggregate, prune and migrate commands.
  • New: suggested privacy policy text for the Privacy Policy Guide.
  • New: add data-vireo-event to any element to record its clicks as events.
  • New: AMP support.

0.17.1

  • Fixed: the dashed previous-period line on the Overview chart drops to the baseline on days with no visits, instead of skipping them and drawing a diagonal across the gap.

0.17.0

  • New: a Pages tab that lists every page with traffic in the date range you pick, with pageviews, visitors and average time. Sort by any column, search by title or path, and page through the full list.
  • New: a “View all pages” link on the Overview’s Top pages card opens the Pages tab for the same range.

0.16.4

  • Fixed: on sites that imported history, Vireo could take the first imported day as the day it started recording, so the Overview and dashboard widget still compared against the gap. It now works this out from what Vireo itself collected, and corrects a wrong date saved by 0.16.2 or 0.16.3.

0.16.3

  • Changed: the dashboard widget uses the full width when there’s room, with today’s and the 7, 30 and 90 day figures in one row and a 30-day chart beside your top pages and referrers.
  • Changed: the widget chart shows pageviews as bars and visitors as a line, with zero days visible and more date labels.
  • Fixed: the widget no longer shows a drop for periods that start before Vireo began recording, and no longer shows an empty badge when there’s nothing to compare.

0.16.2

  • Fixed: after importing history from another analytics tool, the Overview no longer reports a drop for a period that starts before Vireo began recording. It says when Vireo started recording, and comparisons begin once a full period is in.

0.16.1

  • Changed: the plugin’s homepage link now points to vireowp.com, and the statistics tag replaces cookieless.

0.16.0

  • Added: AI visibility scan, under Search & AI beside the AI assistants card. Press Run the scan and Vireo fetches a page of your site, your robots.txt, llms.txt and sitemap the way an AI crawler would, and requests the page as GPTBot, ClaudeBot and PerplexityBot. It scores crawler access, readable content, structured data and discovery files, and every failed check says what to change. The scan’s own requests carry a one-time token and are left out of the crawler figures, the missing pages report and your pageviews.
  • Changed: the readme now says who Vireo is for (bloggers, publishers, shops, small businesses and agencies) and backs its search tags in the description.

Earlier versions are listed in changelog.txt in the plugin folder.