How to check website traffic on WordPress
Self-hosted WordPress does not count visitors on its own, so the answer depends on what you add. Here are five ways to see visitors, page views and traffic sources, what each one misses, and how to pick the right one for one site or forty.

The short answer
To check website traffic on WordPress, add a tool that counts visitors, because a self-hosted WordPress site does not do it by itself. The five common ways:
- Jetpack Stats for a quick visitor count inside wp-admin.
- Google Analytics with Site Kit by Google for the deepest reports.
- A privacy-friendly plugin such as WP Statistics or Independent Analytics, which keeps the data on your own site without cookies.
- Your hosting control panel or server logs, which need no plugin but count bots too.
- A management dashboard such as WPCentrify, when you need traffic for many sites in one place.
Once one is running, open its overview report to see visitors, page views and where they came from.
Does WordPress track visitors on its own?
No. A self-hosted WordPress site from WordPress.org has no visitor counter built in. The dashboard shows your posts, comments and updates, but not how many people visited. Sites hosted on WordPress.com are different: they come with stats built in, provided by the same Jetpack Stats that self-hosted sites can add as a plugin.
So the first step is choosing what to add. Each option below counts in its own way, and that choice decides which visits you see and which you miss.
Way 1: Jetpack Stats
Jetpack Stats is the quickest way to see visitor numbers inside wp-admin. It is made by Automattic, the company behind WordPress.com.
- In wp-admin, go to Plugins > Add New and search for Jetpack Stats (or install the full Jetpack plugin).
- Activate it and connect the site to a WordPress.com account when asked.
- Open Stats from the Jetpack menu. Counting starts from this moment.
What you get: the free version shows views, visitors, referrers and your top posts and pages, according to Jetpack's own pricing page. Paid plans add things like UTM tracking, device stats and city-level locations.
Watch out for: the numbers are processed on WordPress.com, not on your own server, so mention it in your privacy policy. Jetpack's free and paid terms were checked on 10 October 2026 and change from time to time.
Way 2: Google Analytics with Site Kit by Google
Google Analytics 4 gives you the most detail: traffic sources, campaigns, conversions, devices, countries and much more. Site Kit by Google is Google's own free WordPress plugin, with more than five million active installs. It connects Analytics and Search Console and shows a summary in your dashboard, for the whole site and for individual posts.
If you add the Google tag yourself instead of through Site Kit, see how to add Google Analytics and other tracking codes to WordPress without counting visits twice.
- Go to Plugins > Add New, search for Site Kit by Google, then install and activate it.
- Click Start setup, sign in with your Google account and allow access.
- Connect Google Analytics during setup, or later from Site Kit's settings.
- Open Site Kit > Dashboard to see visitors, sessions, top pages and how people found you.
Watch out for: Google Analytics sets cookies. In the EU, the UK and other places that require consent, you need a consent banner, and visitors who decline it or use an ad blocker are not counted. New data can take up to two days to finish processing. And add the Google tag only once: if your theme or another plugin already adds it, every visit is counted twice.
Way 3: A privacy-friendly plugin that keeps the data on your site
If you want numbers without cookies or a third-party account, use a plugin that counts visits itself and stores them in your own WordPress database. Two popular free options on WordPress.org:
- WP Statistics (500,000+ active installs) says it uses cookie-less tracking and stores everything in your database, with reports for visitors, views, referrers and top pages.
- Independent Analytics (100,000+ active installs) says it does not use cookies or contact external servers, with visitors, views, sessions, referrers and a pages report.
Install either from Plugins > Add New, activate it and open its reports menu. Neither can show traffic from before the day you install it.
Watch out for: every visit becomes rows in your database, so a busy site builds up a lot of data over time. Check how long each plugin keeps raw data. The privacy claims above are the vendors' own, checked on their WordPress.org pages on 10 October 2026.
Way 4: Your hosting control panel or server logs
This way needs no plugin at all. Many hosts show visits in the control panel: cPanel hosts often include AWStats, and managed WordPress hosts usually have their own traffic or analytics page.
Watch out for: server logs record every request, including search engine crawlers, uptime monitors and other bots, so the totals come in high. And when a cache or CDN serves a page, the request may never reach your server, so some real visits never appear. Use this for a rough trend, not for a figure you put in front of a client.
Way 5: Check traffic for every site you manage in one dashboard
If you look after many WordPress sites, logging into a different analytics account for each one every month is the slow part. A management dashboard can show all of them side by side.
This is what we built Traffic Analysis in WPCentrify to do. (Disclosure: WPCentrify is our product.) It gives you traffic analytics for every site you manage, next to the rest of the work, if you already manage multiple WordPress sites from one place.
- Visitors, page views and sessions, defined the way Google Analytics defines them, so the two can be compared.
- Counted without cookies, in the visitor's browser, so cached pages are counted too and no consent banner is needed for it.
- Bots filtered out, with the totals shown, so you can see what was removed rather than take it on trust.
- Your own visits excluded. Add your office or client addresses and they stop counting.
- Sources by channel, plus a per-page breakdown and totals across every site.
- A Google Analytics comparison. Paste an export in and see, day by day, where the two agree and why they differ.

To start, connect a site, open it and go to the Traffic tab. Data collects from the moment it is switched on, and the figures can go straight into your client reports.
Which way should you use?
For one personal site, Jetpack Stats or a privacy plugin is plenty. If you run campaigns or need conversion data, use Google Analytics. If you are responsible for many sites, use a dashboard that puts them all in one view. Many people run two side by side: one for depth, one for a clean visitor count.
| Way | Setup | Where the data lives | Main weakness | Best for |
|---|---|---|---|---|
| Jetpack Stats | A few minutes, plus a WordPress.com account | WordPress.com | Fewer reports on the free version | A quick visitor count on one site |
| Google Analytics with Site Kit | About 15 minutes, plus a Google account | Uses cookies, so it needs consent where required, and ad blockers stop it | Deep reports, campaigns and conversions | |
| WP Statistics or Independent Analytics | A few minutes | Your own WordPress database | Counts only from the day you install it | Cookie-free stats with no third-party account |
| Hosting panel or server logs | None | Your server | Counts bots and can miss cached visits | A rough trend with zero setup |
| WPCentrify Traffic Analysis | Connect the site, open the Traffic tab | WPCentrify | Needs a WPCentrify plan: Studio and up, or the $12 Growth pack on Solo | Many sites and client reports |
Vendor details checked on each vendor's own site on 10 October 2026. Setup times are typical, not guaranteed.
How to see traffic for a single page or post
- Google Analytics 4: open Reports, then Engagement, then Pages and screens, and search for the page path.
- Site Kit: shows stats for individual posts as well as the whole site.
- Jetpack Stats: your top posts and pages are listed with their views.
- WP Statistics and Independent Analytics: both have a pages report you can sort.
- WPCentrify: the per-page breakdown shows which pages and posts on a site get the traffic.
Where your visitors come from
Most tools group traffic sources into channels. These are the common ones:
- Organic search: visits from Google, Bing and other search engines. The search terms themselves are in Google Search Console, not in Google Analytics.
- Direct: no source was passed. That includes typed addresses and bookmarks, but also many apps, some email clients and private browsing, so a large Direct share usually means hidden sources, not loyal fans.
- Referral: links from other websites.
- Organic and paid social: links from social networks, unpaid or from ads.
- Email: links in newsletters, if they carry a UTM tag such as
utm_medium=email. - Paid search, display and affiliate: advertising and partner links, again identified by UTM tags.
If a campaign shows up as Direct, the fix is almost always a missing or inconsistent UTM tag on the link.
Why WordPress traffic numbers never agree
Ask three tools how many people visited last month and you will get three answers. The difference is not random: each method is wrong in its own predictable direction.
- Google Analytics runs low. Ad blockers stop the script and some people decline the cookie banner. Those visits are never recorded.
- Server logs run high. They count crawlers, uptime monitors, prefetches and automated browsers as if they were people.
- Caching hides visits from the server. When a cache or CDN serves the page, server-side counters never see the request.
- Definitions differ. Some tools count a person once per day and forget them overnight. Google Analytics can remember a browser for up to two years, so its visitor totals over a month are not the same measure.
How to compare your figures with Google Analytics
Compare the same dates in the same time zone, day by day rather than as monthly totals. Expect a cookie-free tool to show slightly more page views than Google Analytics, because ad blockers stop Google Analytics. Make sure both exclude the same things, such as your own visits, admin screens and error pages. Once the gaps have reasons, the conversation with a client gets short.
A quick checklist before you report traffic to a client
- Exclude your own team's visits and the client's office.
- Use the same date range and time zone as last month's report.
- Check that bots are filtered, and say so in the report.
- Note when tracking started, so a new site's first month is not read as a drop.
- Say which tool the figures come from and why it may differ from others.
- Lead with the two questions clients actually ask: how many people came, and where they came from.
Questions about checking WordPress traffic
Add a tool that counts visitors, because self-hosted WordPress does not do it on its own. Jetpack Stats, Google Analytics with Site Kit, or a privacy plugin such as WP Statistics or Independent Analytics will all show a visitor count in your dashboard. Open the tool's overview report and pick a date range.
Not on a self-hosted site from WordPress.org. The dashboard shows posts, comments and updates, but no visitor numbers. Sites hosted on WordPress.com have stats built in, provided by Jetpack.
Use the statistics in your hosting control panel, such as AWStats on many cPanel hosts, or read your server logs. Both work with no setup, but they count bots as well as people and can miss visits served from a cache, so treat them as a rough trend. You can also add the Google Analytics tag to your theme by hand.
Jetpack offers a free version that shows views, visitors, referrers and your top posts and pages. Paid plans add more, such as UTM tracking, device stats and city-level locations. Check Jetpack's pricing page for current terms, because they change.
Because each tool counts differently. Ad blockers and declined cookie banners stop Google Analytics, so its totals run low. Server logs count bots, so theirs run high. Tools also define a visitor differently: some count a person once per day, while Google Analytics can remember a browser for up to two years. Compare the same date range day by day.
In Google Analytics 4, open Reports, then Engagement, then Pages and screens, and search for the page path. Jetpack Stats lists views for each post under Top posts and pages, and plugins such as WP Statistics and Independent Analytics have a pages report.
If the tool sets cookies, as Google Analytics does, places such as the EU and UK require consent before it runs, so you need a consent banner there. Tools that count without cookies often avoid that, but rules differ by country, so check what applies to you. This is not legal advice.
Yes, with a management dashboard. WPCentrify Traffic Analysis shows visitors, page views, sessions and sources for every site you connect, with totals across all of them, and puts the figures in your client reports.
A well-built analytics script is small and loads without blocking the page, so most visitors will not notice it. Plugins that store every visit in your own database add some work to the server on busy sites. WPCentrify Traffic Analysis counts in the visitor's browser and works on cached pages.
Related reading
Traffic analytics
Cookie-free visitors, page views and traffic sources for every site you manage.
See the featureClient reports
Traffic lands in the monthly report next to updates, backups and uptime.
See reportsCookie consent on many sites
What a working cookie banner needs, and how to check yours actually blocks trackers.
Read the postAI and SEO tools: Google Search Console for multiple sites · AI search visibility · all AI and SEO tools
See traffic for every site in one place
Visitors, page views, sessions and sources for every WordPress site you manage, counted cookie-free, with bots filtered out and the figures ready for client reports.
Plans from $15 a month, or start free on one website.