Put a feedback button on every doc page. When something's unclear, readers tell you right there — and the page URL rides along automatically.
Per-page feedback · live in 60 seconds
Step 3 doesn't say where to find the API key.
An example payload here would help a lot.
Worked first try — thank you!
This one’s really live.
Give it a tap — every note arrives with the page URL attached.
Anchor a feedback link to any page so readers flag gaps exactly where they hit them.
Use data-sayso on a ‘Feedback’ link in your docs so the panel opens right where the reader is stuck.
Each submission carries the page URL, so you know precisely which doc to fix.
Tag by section and see which guides generate the most confusion.
Create a project, copy the snippet, drop it before </body>. You're live in under a minute.
Visitors tap the launcher, pick a type, and say their piece. It's that low-friction — so they actually do.
Read, tag, and resolve from your dashboard. Turn scattered comments into a ranked to-do list.
One snippet, three ways to open it. Use whichever fits — or mix them.
A tidy launcher sits in the bottom-right corner. Works out of the box — nothing to wire up.
<script src=".../w.js" data-sayso="PROJECT_ID" defer></script>Add data-sayso to any link or button and the panel opens right next to it.
<button data-sayso>Feedback</button>Hide the default launcher and open only from your own triggers.
<script … data-sayso-launcher="false">No seats, no metered surprises. One flat plan when you outgrow free.
For your first project.
$0
For when one project isn’t enough.
$100 /year
$8/mo billed yearly · save 58%
For teams that need more than the basics.
Yes. Use the floating launcher site-wide, or anchor a ‘Feedback’ link per page with data-sayso so it opens inline next to it.
Always. Every submission records the page URL automatically, so docs feedback is never ambiguous.
One line of HTML. Create a project, copy the <script> tag, paste it before your closing body tag. The widget renders in a Shadow DOM so it never collides with your styles.
No. w.js is a tiny vanilla script with zero dependencies, served with long cache headers. It loads after your page is interactive and stays out of the way.
One link per page away from docs that fix themselves.