A documentation page earns one narrow question, and the page path.

The question, and the context

<form action="https://freelyform.com/f/FORM_ID" method="POST">
  <input type="hidden" name="_subject" value="Docs feedback">
  <input type="hidden" name="page" value="/reference/webhooks/retries">

  <label for="feedback">Did this page answer your question? What was missing?</label>
  <textarea id="feedback" name="feedback" rows="3" required></textarea>

  <label for="email">Email (optional, if you want a reply)</label>
  <input id="email" name="email" type="email" autocomplete="email">

  <button type="submit">Send feedback</button>
</form>

Why the path never gets asked for

The reader does not think of the page as a path, and asking them to type one is a field that will be wrong. Send it as a hidden value; the referrer already carries it for a normal page load. In a single-page docs app the referrer stays constant, which is exactly when the hidden field is required rather than optional.

What to do with the answers

• Group by page and read the longest pages of complaints first.
• Fix the missing step in the page, not in a FAQ somewhere else.
• When the same complaint arrives twice, add it to a changelog entry so readers see the loop closing.

Why this earns its own page in the library

Documentation feedback is the cheapest quality signal a technical product has, and it is the one most often replaced with a thumbs widget that produces a number. The difference between the two is one open field — and the willingness to read it every week.