{"id":18,"date":"2026-09-09T04:25:32","date_gmt":"2026-09-09T04:25:32","guid":{"rendered":"https:\/\/nirohelp.com\/docs\/18\/doc-voting\/"},"modified":"2026-09-16T14:16:39","modified_gmt":"2026-09-16T08:16:39","slug":"doc-voting","status":"publish","type":"nirohelp_doc","link":"https:\/\/nirohelp.com\/docs\/knowledge-base\/doc-voting\/","title":{"rendered":"Reader voting on docs"},"content":{"rendered":"\n

Each doc can show a helpful \/ not-helpful pair of buttons under the article. They appear when Settings \u2192 Documentation \u2192 Display \u2192 Show rating buttons<\/strong> is ticked, which it is by default.<\/p>\n\n\n\n

\"Show<\/figure>\n\n\n\n

Who can vote<\/h2>\n\n\n\n

Anyone who can load the page. Readers do not have to be logged in.<\/p>\n\n\n\n

Votes can only be cast from your own site – a vote arriving from anywhere else is rejected – so the buttons are not open to being scripted from another website.<\/p>\n\n\n\n

What is recorded<\/h2>\n\n\n\n

Two running totals on the doc: upvotes and downvotes.<\/p>\n\n\n\n

Nothing about the voter is recorded.<\/strong> No name, no account, no address, no identifier of any kind. Only the two counters exist.<\/p>\n\n\n\n

There is no duplicate-vote protection<\/h2>\n\n\n\n

This is worth being explicit about, because it is easy to assume otherwise.<\/p>\n\n\n\n

After someone votes, the buttons on that page are disabled. That is the whole of it. No cookie is set and nothing is remembered. Reloading the page re-enables the buttons, and the same visitor can vote as often as they like.<\/strong><\/p>\n\n\n\n

Treat the counts as a rough signal of engagement rather than a poll result. If you need one vote per reader, that needs custom work \u2014 and even then, anything short of requiring a login is per-browser rather than per-person.<\/p>\n\n\n\n

Using the numbers<\/h2>\n\n\n\n

Two things worth doing with them:<\/p>\n\n\n\n