Launched this week

FeedPulse

Launched this week

Free embeddable widgets + SEO checkers, no paid tier

2 followers

Free embeddable widgets + SEO checkers, no paid tier

2 followers

Visit website

18 free embeddable widgets (flag counter, live traffic feed, GitHub stars, npm downloads, visitor globe + more) and 12 free SEO tools — 10 checkers (DA, DR, SERP, backlinks, Lighthouse) plus 2 generators. One-line embed. No cookies. No signup.

Free

Launch tags:Marketing•SEO•Developer Tools

Launch Team

Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free

Promoted

Maker

📌

Hi PH! Maker of FeedPulse here.

I built this because I missed the era when small sites had visible, fun, free widgets — Flag Counter, the old StatCounter, Feedjit — and every modern replacement either trial-walls the good features, sells visitor data, or quietly disappears.

FeedPulse is a free-forever set of 18 embeddable widgets (live traffic feed, online-now counter, hit counter, flag counter, click heatmap, GitHub stars badge, npm downloads badge, visitor globe + more) plus 12 free SEO tools — 10 checkers (DA, DR, SERP, backlinks, Lighthouse) and 2 generators. One line to embed. No cookies, no signup, no paid tier.

Every number a widget shows is traceable: feed-pulse.com/data-sources lists exactly where each data point comes from, and the FAQ on the homepage explains why the free-forever math actually works.

On performance, since this crowd checks: every public page scores 100 on SEO and 98-100 on desktop performance in Lighthouse. Mobile performance is 85-88 and that's my current fix — there's a hydration issue inflating LCP that I'm working through this week. Run PageSpeed Insights on any page and you'll see the same numbers I do.

Three things I'd love feedback on:

The widget gallery — which widget should I build next? (There's an idea box on /widgets I read weekly.)
The SEO checker results vs whatever you use today — are the values close enough to be useful?
The privacy posture — strict enough? I'm open to going stricter.

Happy to answer anything about the stack (FastAPI + React + Mongo + Cloudflare), the SEO play, or the free-forever economics. Thanks for taking a look!

Report

24d ago

Forum Threads

p/feedpulse-2

•

24d ago

FeedPulse is coming soon on PH

Launching Oct 20.
Spent this week on performance. Here are the real numbers rather than the rounded ones: SEO 100, Accessibility 100, desktop Performance 98 to 100, Best Practices 96, mobile Performance 85 to 88. Best Practices is capped at 96 by a React hydration mismatch firing on every page, and that same bug is behind a mobile LCP of 3.7 to 4.1 seconds. Not fixed yet. It's next on the list.

The stranger break this week was in the SEO pipeline. My static prerenderer was snapshotting English URLs with the wrong language in the head, because a saved locale was leaking out of localStorage and one headless browser profile was being shared across twelve locales. Google was getting French titles on English pages for weeks before I caught it. The build now fails outright if a page's language, title or canonical doesn't match its route.

Happy to go into either one in detail.

View all

Hi PH! Maker of FeedPulse here.

Every number a widget shows is traceable: feed-pulse.com/data-sources lists exactly where each data point comes from, and the FAQ on the homepage explains why the free-forever math actually works.

Three things I'd love feedback on:

The widget gallery — which widget should I build next? (There's an idea box on /widgets I read weekly.)
The SEO checker results vs whatever you use today — are the values close enough to be useful?
The privacy posture — strict enough? I'm open to going stricter.

Happy to answer anything about the stack (FastAPI + React + Mongo + Cloudflare), the SEO play, or the free-forever economics. Thanks for taking a look!