Without PushFeedback
- You guess which pages need updating
- Support tickets pile up for the same confusing sections
- Users leave the docs and never tell you why
- You can't tell if your last rewrite actually helped
Feedback widget for documentation
Find out which docs pages your users actually hate
Drop in a widget. We'll tell you which pages confuse readers, which sections drive support tickets, and what to fix first. AI groups feedback into themes so you don't have to read every comment.
Free up to 25 entries. No credit card. Works with Docusaurus, MkDocs, Sphinx, Antora, and more.
docs.yourcompany.com/api/auth
Authentication
POST /v1/auth/token
Authorization: Bearer ...
Share your feedback
Powered by PushFeedback
Was this page helpful?
The token example doesn't show how to refresh it...
Email address (optional)
200+ docs teams use PushFeedback to ship better docs
“We used to update docs based on gut feeling. Now we have a list.”
Most docs teams update
the wrong pages.
Your analytics show traffic, not understanding. A page can have 10,000 monthly views and still confuse 8 in 10 readers. Without targeted feedback, you're prioritizing based on gut feeling, traffic stats that don't tell you what's broken, and the loudest voice in last week's standup.
With PushFeedback
- See which pages get negative feedback most often
- Annotated screenshots show exactly where readers get stuck
- AI groups feedback into themes so you can fix root causes
- Track sentiment over time and prove your docs are improving
The honest pitch
Yes, you could build this yourself.
Here's what you'd actually be signing up for.
A feedback widget takes an afternoon with Cursor or Claude. The rest of the iceberg takes a year. We've been building it since 2023.
Build it yourself
est. 3-6 months + foreverWhat you'd actually need to ship
Basic widget (form, send button)1 day
Database, auth, admin dashboard1-2 weeks
Screenshot capture and annotation1-2 weeks
AI categorization and theme detection1 month
Multi-site filtering, team roles, retention1 month
Stay GDPR-ready (DSARs, audits, law changes)forever
Slack, Jira, GitHub, webhook integrations2-4 weeks
Browser compat, accessibility, mobile2 weeks
Maintenance, security, feature requestsforever
Build cost
$37K–$75K
Senior engineer at $150K fully-loaded × 3-6 months
Plus running cost
$30–$200 / month
Database, AI inference, screenshot storage, error monitoring
PushFeedback
5 minutes + zero maintenanceWhat you actually need
- All of the above, working today
- 5 minutes to install, free up to 25 entries
- GDPR-ready, plus security and uptime handled
- New features ship every month
- Cancel anytime, export your data
Professional plan
$24 /month
Less than a single engineering hour
We respect engineers who'd rather build. Just make sure you're trading the right hour for the right problem. Building a widget feels productive. Building feedback infrastructure is a year of yak-shaving that pulls you away from your actual product.
What you actually find outForget feedback dashboards.
Forget feedback dashboards.
Get an action list.
/01
Your most-hated pages, ranked
A live leaderboard of which docs pages confuse readers most. Sort by negative feedback, sentiment trend, or volume.
This week · negative ▼
1/api/auth/refresh-tokens
2/guides/installation
3/api/webhooks/setup
4/tutorials/quickstart
/02
Their words. Their screenshots.
Readers annotate exactly where they got stuck. No more guessing what "this is unclear" means.
“This step assumes I already created an API key. Where do I do that?”
Anna · 2h ago
/03
AI themes. Not 500 comments.
AI groups feedback into recurring themes, surfaces sentiment shifts, and recommends what to fix first.
Auth examples missing refresh logic23 mentions
Mobile screenshots out of date18 mentions
Webhook setup unclear after step 412 mentions
+ 4 more themes→
/04
A widget that fits your docs
Match your brand colors, position, and theme. Inline or floating. GDPR-compliant with no tracking cookies.
AI ReportsAI does the reading.
AI does the reading.
You do the fixing.
Every Monday, your team gets a report: top 3 themes this week, sentiment trend on key pages, recommended fixes ranked by impact. The kind of analysis a senior tech writer would do, except it doesn't take half a day.
Weekly report · Mar 17 - Mar 24
312 new feedback entries · 8 themes · 4 priority fixes
Sentiment
+12%
Top recurring themes
P1
Auth examples missing refresh-token logic
23 mentions · /api/auth/* · sentiment: -68%
P1
Mobile screenshots out of date
18 mentions · /guides/* · sentiment: -54%
P2
Webhook setup unclear after step 4
12 mentions · /api/webhooks · sentiment: -41%
Recommended actions
Add refresh token example to /api/auth/tokens — would resolve 23 mentions and likely reduce 5 weekly support tickets.
Update 6 mobile screenshots in /guides/installation. Last refresh: 14 months ago.
Rewrite step 4-6 of webhook setup. Most users dropped feedback at step 5.
Built for the docs teamWhatever you write,
Whatever you write,
find what's tripping people up.
API DOCS
Endpoints, examples, errors
Find which endpoints are missing examples, which auth flows trip people up, which error responses leave readers stuck.
"This endpoint returns 404"
"The authentication example doesn't work"
USER GUIDES
Steps, screenshots, assumptions
Spot screenshots that no longer match the UI, missing steps, and instructions that assume too much.
"This screenshot doesn't match my interface"
"Step 4 is missing"
TUTORIALS
Where readers get stuck
See where readers get stuck, which prerequisites you forgot to mention, and which sections need more depth.
"I got stuck at this part"
"This assumes I know Y"
Integrations
Works with your docs stack.
Drop in via npm, CDN, or copy-paste. Most teams are live in under 10 minutes.
Plus Astro, Fumadocs, MadCap Flare, Paligo, Starlight, VitePress, VuePress, Webflow, LearnDash, and any site you can paste a script tag into. See all integrations →
Frequently asked questions
You can. A basic widget is an afternoon's work. The dashboard, AI categorization, multi-site filtering, GDPR compliance, integrations, and ongoing maintenance are not. Most teams who try end up with a half-finished tool that nobody on the team checks. PushFeedback is the version that actually gets used, because we've built and tested it on 200+ docs teams.
No. The widget loads asynchronously and adds under 30KB. We're obsessed with performance because slow docs sites are exactly the kind of pages users would be giving you feedback about.
Route it to Jira, Slack, GitHub, or your tool of choice. Mark it as resolved, assign it to a writer, or close the loop with the user directly. Nothing rots in a dashboard.
The free plan never expires. You get up to 25 feedback entries to test the product on your docs site. Upgrade when you're ready to scale.
If you can paste a script tag, you can install PushFeedback. We have native plugins for Docusaurus, Mintlify, WordPress, and others if you'd rather not touch HTML at all.
Built for GDPR compliance: a configurable consent checkbox you tie to your own privacy policy, no tracking cookies, and no personal data collected unless the user explicitly opts in. EU-hosted infrastructure available. Full DSAR support and data export at any time.
Stop guessing which docs pages need work. Your readers know.
They just need a way to tell you. Get the widget on your docs site in 5 minutes and have your first feedback by tomorrow morning.
- 25 entries free
- No credit card
- Setup in 5 minutes
- Cancel anytime