With this plugin, you can easily see how many people have viewed a Post
It only runs on Posts and after some time has passed through an Endpoint, so it doesn’t affect CWV, and the page loads quickly.
The post meta that we store the value in is “views”.
More information in Spanish about the plugin in the link Show the most viewed Articles, without affecting the loading speed
SUPPORT
Need help or have a suggestion?
Please use the official WordPress.org Support Forum for any issues related to the plugin.
Official Website
For additional information or to get in touch with the development team, please visit our official website.
Like the plugin?
Please leave a 5-star review and help others discover Bubuku Post View Count.
ABOUT BUBUKU_CODE
We develop custom solutions for WordPress focused on performance, accessibility, and maintainable code. Our work includes plugins, themes, and integrations designed to improve the daily workflow of marketing and content teams.
Privacy
This plugin never persists the visitor’s raw IP address or User-Agent string. To avoid duplicate views and limit abuse, it stores keyed, non-reversible HMAC tokens derived from the post, network address and User-Agent in a dedicated table for up to 30 minutes; expired tokens are deleted automatically. All reporting data is aggregated: total views and last-viewed date per post, a daily view count per post, and — if you enable the optional session dimensions — a daily breakdown per post of device-width bucket and approximate referrer category (never the raw screen width or referrer URL/host).
If a visitor’s browser sends the “Do Not Track” (DNT) or Global Privacy Control (Sec-GPC) signal, the plugin skips recording the optional session dimensions (device width and referrer category) for that visit. This is enabled by default and can be turned off in Settings Post View Count. The view count itself is unaffected either way, since it never stores anything that identifies the visitor.
If you enable the optional “AI crawler tracking” setting (off by default), hits from known AI crawlers are counted in their own table, aggregated by day and bot name — never at the individual-request level and never mixed with human view data.