文章浏览量计数器（Post Views Counter）

For many frequently asked questions check the Post Views Counter Docs. Post Views Counter gives you per-post Views and site-wide Visits inside WordPress. It is fast, easy to use and privacy-first, with counting data stored on your server and control over what, who and when you count. Google Analytics may be more than you need when you want content view statistics for editorial decisions.

Of course – many sites use both. Post Views Counter handles on-site, per-post view counts inside WordPress (no third-party scripts), while Google Analytics covers marketing funnels and acquisition.

A View belongs to the content being viewed and is counted according to your counting settings. A Visit starts with a browser’s first counted view and covers subsequent counted content views within the fixed Count Interval. Viewing another eligible post within that window adds a View without starting another Visit. Later views do not extend the window.

Post Views Counter follows the counting rules you choose: which content to count, which visitors to include or exclude, and how often to count them again. These rules may differ from your Google Analytics setup, so the totals are not expected to match. Crawlers you exclude are not counted, and analytics tools filter bots their own way. PHP mode cannot count a view when a cached page is served without running WordPress (see the page cache question below). The time windows also differ. PVC starts a fixed Visit window with the first counted view, using your Count Interval – 24 hours by default. Later views do not extend it. Google Analytics 4 uses an inactivity timeout, which defaults to 30 minutes.

A Visit belongs to your site, not to a post – one Visit often covers several posts. Post Views Counter shows Views for each post and Visits as site-wide totals. Traffic Signals still notice when the visits that start on a post change unusually.

Visits start accumulating when Visit counting becomes available; earlier Views do not automatically become Visits. Setting Count Interval to 0 stops new Visits but preserves previously counted totals. If browser storage is unavailable, Views can still be counted but Visits are not inferred. Right after an update, the chart can briefly say that Visit data is not available while the database is prepared.

If pages are served from a cache – by a caching plugin, your host or a CDN – use the JavaScript or REST API counter mode. These modes count from the visitor’s browser, so cached pages can still be counted. PHP mode counts while WordPress builds the page, so a page served from a cache without running WordPress is not counted.

Views from visitors you exclude in Exclude Visitors (for example logged-in users, specific roles or guests) or Exclude IPs are not counted. With a non-zero Count Interval, PVC uses cookies to avoid counting repeat views of the same content within that window. Blocking or clearing cookies can allow repeat Views. To test counting, open a counted post as a visitor your exclusions allow. A private window does not bypass IP or guest exclusions.

Post Views Counter counts views and visits inside WordPress without third-party tracking scripts. Views and Visits are stored as aggregate totals on your server. To apply the Count Interval, it uses a first-party cookie in the visitor’s browser. Pro also offers cookieless browser storage; its optional Strict Counts feature caches IP-derived data associated with content and timestamps to limit repeat counts.

If you’re using the free version, please post your question in the WordPress.org support forum. If you’ve purchased Post Views Counter Pro, your license includes one year of updates and premium support. You can contact us directly through our dedicated support channel available after logging into your account at Post Views Counter, and our team will get back to you.