Feedjit defined the live traffic feed, the scrolling list of who just arrived and where from. It closed in 2018: its founders posted a notice that the service was shutting down and pointed people to Google Analytics, and its WordPress plugin was later closed on WordPress.org. Sites that still carry the old code are loading nothing. This is the same idea, rebuilt and free.
The widget everyone remembers, from a service that closed in 2018. Everything below was checked against feedjit.com in November 2026, but pricing and limits move, so confirm anything that matters on their own page before deciding.
| FeedPulse | Feedjit | |
|---|---|---|
| Price | Free, with no paid tier. The live feed is FeedPulse's flagship widget. | No longer available. The service shut down in 2018 |
| Signup | None to install. Paste and it starts. | Not possible; there's no service left to sign up to |
| What you get | A live feed with country flag, referrer and page, styled by you. | Was a live visitor feed with location and referring sites |
| Required link back | A small FeedPulse credit line stays under the widget. That's the deal: free forever, the credit link stays. | The classic widget linked back to feedjit.com |
| Cookies & privacy | Country only, no cookies. The raw IP is never stored. | Showed each visitor's city and referrer publicly in the feed |
| Customisation | Your CSS, plus built-in themes. It's HTML, not a locked iframe. | Was a handful of preset colour schemes |
| Where the data lives | Aggregate history in the optional owner dashboard. | Gone with the service. There's nothing to export now |
| Removing it | Delete the snippet. Nothing left behind. | If the old code is still on your site, delete it: it no longer loads anything |
Feedjit showed city-level detail, which is more granular than we show, and for some people that granularity was the whole appeal. We deliberately stop at country level, because publishing a visitor's city is the part most likely to fail a privacy review.
Feedjit is gone. If you want the live traffic feed back on your site, free, maintained and privacy-conscious, that's what this is.
For years Feedjit was the live traffic feed on blogs: a sidebar list that read like 'a visitor from Manila arrived from Google'. In spring 2018, shortly before the EU's GDPR came into force, its founders posted a closing notice and suggested site owners move to Google Analytics' real-time reports. The WordPress plugin was later closed on WordPress.org at the author's request. If an old post or theme still contains the Feedjit script, it isn't doing anything except making a request that goes nowhere.
The thing people loved about Feedjit was also its riskiest feature: a public list of individual visitors with their city and where they came from. On a small site, a city plus a time plus a referrer can be enough to recognise a person. The FeedPulse feed keeps the live feeling, with arrivals appearing as they happen alongside a flag, the referring site and the page, but stops at country level, and the raw IP address is never written to our database. It's less detailed by design.
Search your theme, sidebar widgets and any old HTML blocks for 'feedjit' and delete what you find. Then add the FeedPulse live traffic feed in the same spot; most blogs put it in a sidebar or footer. It starts empty and fills up as visitors arrive. There's no history to import, because Feedjit's data went with the service, so the feed simply picks up from today.
No FeedPulse widget sets a cookie. When a widget counts a visit, the server turns the visitor's IP address into a fingerprint using a salt that changes every UTC day, uses that fingerprint to avoid counting the same person twice within 24 hours, and never writes the raw IP address to the database. Once a day's salt expires, even we can't map a fingerprint back to an address. Location is resolved to country level only. Some widgets keep a random session ID in the browser's sessionStorage, which disappears when the tab closes, and a few remember a small preference in localStorage, such as the 'ignore my own visits' switch or the name someone typed into a comment. Whether your site needs a consent banner depends on where your visitors are and on the rest of your setup, so treat this as information for your own privacy notice, not legal advice.
Every FeedPulse widget shows a small credit link back to FeedPulse underneath it. That link is how a product with no paid tier pays for itself. It's the only thing we ask for, and it's the same for everyone because there is only one plan. If a vendor's free tier also carries branding, that's a fair like-for-like comparison. If you need a widget with no third-party link at all, a paid tool or something you build yourself is the honest answer.
Open the free live traffic feed page, set the options and copy the snippet. Paste it where the old Feedjit code sits today, usually a theme footer, a sidebar or a Custom HTML block, and publish. Load the page in a private window to confirm the widget renders, then delete the Feedjit code so you aren't loading both. If Feedjit holds history you care about, export or screenshot it first: FeedPulse starts counting on the day you install it and can't import another service's data. Finally, if the old tool needed an entry in your cookie banner or privacy notice, review whether that entry still applies.
The Feedjit column was checked against feedjit.com and its own help and pricing pages in November 2026. The FeedPulse column was checked against our own widget code, not our marketing copy. Prices, limits and plan names change, so confirm anything that affects your decision on feedjit.com before you rely on it. If something here is out of date, tell us through the contact page and we'll correct it. There are no affiliate links on this page, and nobody paid to be compared.
Feedjit is gone. If you want the live traffic feed back on your site, free, maintained and privacy-conscious, that's what this is. Feedjit showed city-level detail, which is more granular than we show, and for some people that granularity was the whole appeal. We deliberately stop at country level, because publishing a visitor's city is the part most likely to fail a privacy review.
Yes, and it's the reason FeedPulse exists. The live traffic feed is free with no paid tier, needs no signup, sets no cookies and shows country rather than city. The one thing it won't do is publish a visitor's city.
In its closing notice, published around the GDPR deadline in 2018, Feedjit's founders said the service was closing and recommended Google Analytics as a replacement. Blog posts from the time link the decision to the cost and risk of running a free, hobby-scale tracking service under the new data protection rules.
Nothing. There is no paid tier, no card on file and no account. Widgets have no traffic cap. A few SEO tools that pay for their data per lookup have a small daily fair-use allowance per visitor, which resets every day.