How to check site traffic on WordPress, and read it like a store owner

Last updated: November 4, 2026

Say you installed WordPress and WooCommerce three weeks ago, published ten products, posted the link twice, and now you want one answer: is anyone coming? You open the WordPress dashboard and find nothing about visitors at all. That is normal. WordPress does not count traffic by itself. To check site traffic on WordPress you add a stats plugin, connect an outside service, or read the server logs. Each route gives you a different number for the same day, which is the second thing nobody warns you about.

This guide shows four ways to check traffic, how to see which pages and sources get it, why every tool disagrees with every other tool, and which numbers a store owner should read instead of raw page views.

Does WordPress have website analytics built in?

No. A self-hosted WordPress site records nothing about visitors unless a plugin or service is added. Sites hosted on WordPress.com include Jetpack Stats, which is why some tutorials show a Stats menu that your site does not have. On your own hosting you choose a plugin, Google Analytics 4 or the server's own logs.

The WordPress.com support page for Stats says the feature is "enabled by default for all websites hosted on WordPress.com". For self-hosted sites the same feature comes through the Jetpack plugin, enabled under Jetpack > Settings > Traffic. Per the Jetpack Stats documentation, it "counts a page view each time someone loads a page on your site", and the stats logs are retained by Automattic for 28 days. That last point matters if you want visitor data to stay on your own server.

Four ways to check traffic on a WordPress website

Use Jetpack Stats for a quick count tied to WordPress.com, a stats plugin for traffic inside your own database, Google Analytics 4 for deep marketing reports outside WordPress, or hosting logs for raw requests. Most store owners end up with one in-dashboard plugin for daily use and GA4 only if they run ads.

Plugin facts above are category descriptions checked against each tool's own site in November 2026. Features differ between plugins and plans.

How to check traffic with a plugin, step by step

Install the plugin, activate it, wait for a few visits, and open its dashboard page. Within a day you will have views, visitors, top pages, countries and referrers. Set the plugin to ignore your own logged-in visits so you do not count yourself.

1. In WordPress go to Plugins > Add New, search for the plugin, install and activate it.
2. Open the plugin's settings and turn on the option to exclude administrators or logged-in users, if offered.
3. Visit your own site in a private browser window to confirm a visit is recorded.
4. Come back the next morning. Read visitors, views, top pages and referrers for yesterday.
5. After a week, compare days of the week. Most stores have a clear weekly rhythm within the first month.

With StorePinger, the free plan shows live visitors on a world map, visitors by country, today's visitors and page views, and a dashboard widget, with no outside account. The data stays in your WordPress database and no cookies are set by the tracker. The live visitors page shows what that looks like.

Can I track who visits my website?

You can see where visitors are, what pages they open, what device and browser they use, and which site or search sent them. You cannot see a name or an email address for a visitor who has not given it to you, and no legitimate analytics tool offers that. Visitors who log in or place an order are the exception, because they identified themselves.

What a store can see, per visit: the country or city (looked up from the IP address), the landing page, the pages in order, the source, the device, whether something went into the cart, and whether an order was paid. On StorePinger Pro that sequence is a visitor journey, and a paid order ties the journey to a customer record you already hold in WooCommerce. The IP address itself is used for the location lookup and is not stored.

The question "can I track who visits my website" often means "can I see a company name". Some business-to-business tools attempt that from network data. For a consumer store it is not useful and not worth the privacy cost.

How to check if a page gets traffic

Open the pages report in your stats plugin, sort by views for the last 30 days, and find the page. If it is missing, it had no views in that period. For a product page, also check the product's cart additions and orders, because a page with 40 views and 4 orders is doing more work than one with 400 views and none.

A worked example, not a customer result. In the last 30 days, product A had 400 views, 12 cart additions and 2 paid orders. Product B had 40 views, 8 cart additions and 4 paid orders. Product A's conversion rate is 2 divided by 400, or 0.5%. Product B's is 4 divided by 40, or 10%. The page getting traffic is A. The page that converts is B. The action is to send A's traffic to B's layout: look at the photos, the price display and the shipping message on B, and copy what is different.

How do I see where my WordPress traffic is coming from?

Open the referrers or sources report in your stats plugin. It groups visits by the site or search engine that sent them, and most tools split search, social, direct and referral. For your own emails and posts, add UTM parameters to the links, or they show up as direct and you will think email sends nothing.

Three things to know about source reports before you trust one. First, "direct" is a catch-all for any visit with no referrer, which includes links from apps, from some email clients and from bookmarks, so a large direct share usually means untagged links rather than loyal fans typing your address. Second, visits from AI assistants such as ChatGPT and Perplexity arrive with a referrer and some tools show them under referral while others name them. Google Analytics 4 added an AI Assistant channel for this, and StorePinger names them in its sources report. Third, paid and organic visits from the same site look the same unless the tool reads ad click IDs or UTM tags. The UTM tracking guide covers the tagging in detail.

A worked example, not a customer result. A store's sources report shows 1,000 visits: 450 Google search, 300 direct, 150 Instagram, 60 ChatGPT, 40 other. The owner sends a weekly email to 2,000 subscribers and sees no email row. After tagging the email links, next week's report shows direct at 120 and email at 180. Nothing changed about the visitors. The labels did.

What about hosting logs and server-side stats?

Your hosting panel usually offers raw access logs or a log analyser. They count every request, including bots, images and scripts, so the numbers are much higher than any plugin shows. Use them to confirm the site is being crawled or to spot an attack, not to measure customers.

To find them, look in your hosting control panel for "access logs", "raw logs" or a tool such as AWStats or GoAccess. Each line is one request with the time, the IP address, the path and the user agent. A single human page view can produce twenty lines, one for the page and the rest for images, styles and scripts, which is why log totals look so large next to a plugin's count.

Logs have one real use for a store owner: they are the only count that cannot be blocked by a browser. If a plugin shows a sudden drop and the logs do not, a script is being blocked or a cache plugin changed. If both drop, the traffic is gone. Reading them for anything else is a job for a developer with a log tool.

Why do my traffic numbers differ between tools?

Because each tool counts a different thing. One counts page loads including bots, one counts browser events after consent, one counts server requests, and each defines a "visitor" its own way. Differences of 10 to 30 percent between two tools on the same day are normal and are not a bug in either.

• Bots. Crawlers from search engines, SEO tools and scrapers make up a large share of raw requests on a small site. Logs count them. Most plugins filter the known ones. Per Google's documentation, "traffic from known bots and spiders is automatically excluded" in GA4 and cannot be turned off.
• Consent and ad blockers. A tool that needs cookies and consent loses every visitor who declines or blocks. A tracker that sets no cookies is still blocked by some privacy extensions.
• Caching. A page served from a full-page cache may not run server-side counting. Client-side trackers still fire. This alone explains many "plugin A says 300, plugin B says 180" complaints.
• Definitions. A "visitor" can be a unique id per day, per session or per 30 days. A "session" can end after 30 minutes of silence or at midnight.
• Your own visits. Admin visits are excluded by some tools, included by others, and you visit your store more than anyone.
• Time zones. A tool on UTC and a tool on your local time split the day differently.

Pick one tool as your reference and read it consistently. Use a second tool only to confirm direction, never to reconcile totals. The WooCommerce Analytics vs Google Analytics guide applies the same logic to orders.

What should a store owner read instead of page views?

Read visits by source, visits that added to cart, paid orders, and conversion rate, in that order. Page views tell you people arrived. The other four tell you whether the store works and which channel to feed. A store with 1,000 visits and 5 orders has a 0.5% conversion rate and a checkout problem, not a traffic problem.

Conversion rate is the one to write down weekly. If 1,000 people visit and 20 buy, that is 2%. If visits double and orders stay at 20, conversion halved and the new traffic is the wrong traffic. If visits stay at 1,000 and orders go to 30, something on the site improved. The conversion funnel shows which step changed.

How often should you check your traffic?

Five minutes a day on the live view, ten minutes a week on the reports, and an hour a month on sources, cities and products. Checking a dashboard several times a day teaches nothing a daily email would not, and it is the habit most likely to make you change things that were working.

The daily check is a glance: is anyone here, are carts moving, did a campaign land. The weekly check is the trend: visits, orders and conversion rate against last week. The monthly check is the decisions: which source to fund, which city to target with ads, which product to push. A sales report email covers the daily and weekly checks for most owners without opening a dashboard at all.

Common mistakes

• Counting yourself. Exclude logged-in admins or use a private window for testing.
• Trusting a count that includes bots. A traffic spike at 3 am from one network is a crawler, not customers.
• Running two trackers and arguing with the difference. Pick one reference tool.
• Reading views instead of visitors. One person reading six pages is six views and one visitor. Both numbers are fine, but do not mix them week to week.
• Installing GA4 without a consent setup. In many regions it is required, and without it the numbers are both incomplete and a compliance problem. The Google Analytics alternative page covers the in-WordPress route.
• Ignoring sources. Total traffic going up while the one source that converts goes down is the most common way a store grows its visits and shrinks its sales.
• Caching the cart and checkout. It breaks counting on those pages and breaks order attribution. Exclude them in your caching plugin.

Conclusion

Checking site traffic on WordPress starts with accepting that WordPress will not do it for you, and ends with choosing one tool and reading it the same way every week. For a store, install an in-dashboard plugin first, because it is free, needs no outside account, keeps the data on your own server and shows the live view that tells you in minutes whether a post or an email landed. Add Google Analytics 4 only when you start paying for ads. Then stop reading page views and start reading visits by source, carts and paid orders, because those are the numbers the store runs on. The StorePinger features page shows all of them together inside WordPress, starting with the free live visitors view.