How to Create a Poll in WordPress (Free, Works With Caching)

Card: How to Create a Poll in WordPress

A poll is the cheapest bit of interaction you can add to a WordPress post. One question, a few buttons, and readers get to say something without writing a comment. Done well, it tells you what your audience actually thinks. Done badly, it’s a box nobody clicks, or worse, a box that quietly breaks the moment your caching plugin kicks in.

Video: Make a Quick Poll and Show the Results
Video: Make a Quick Poll and Show the Results (0:51)

Below: the question, placement, results, repeat votes and what to do with the numbers. Then the ways to build one, including the free plugin we make.

What makes a good poll?

Most bad polls fail before anyone votes.

  • Ask one thing. “Which do you use for backups and how often?” is two questions. Split it or drop half.
  • Keep it to 2 to 5 options. Past five, people skim, and the last options get fewer votes simply for being last.
  • Make the options cover the ground. If lots of readers would answer “none of these”, add it. Otherwise they leave or pick at random.
  • Word it neutrally. “Is Gutenberg finally good enough?” leans. “How do you build most of your pages?” doesn’t.
  • Use a single-choice question unless you really need more. With “pick all that apply”, percentages add up to more than 100%, which confuses readers who expect a pie.

Where should the poll go?

Put it where the reader has just formed an opinion. In a tutorial, that’s usually right after the main section, not at the very top before they know what the post is about. In a news or opinion post, near the end works, because people have read your take and want to weigh in.

Sidebars and footers get far fewer votes. Fine for a site-wide “what should we write next?” poll, but don’t expect much.

Should voters see the results?

Usually yes. Seeing the results is the reward for voting, and a plain “thanks for your vote” feels like shouting into a well.

There are good reasons to hide them, though:

  • Early results can steer later voters. If option B is at 70% after ten votes, some people just pile on.
  • Small numbers look silly. “100% of voters (1 vote)” doesn’t inspire confidence.
  • You want a follow-up post to be the reveal.

The middle ground is showing results only to people who have voted. They get the reward, and the tally can’t sway anyone before they choose.

Why do so many polls break on cached pages?

This is the problem most guides skip. Page caching (WP Rocket, LiteSpeed Cache, your host’s built-in cache, Cloudflare) works by saving one copy of the page and serving it to everyone. That’s great for speed and terrible for anything personal.

A poll is personal. It needs to know whether this visitor has voted, and it needs to show current numbers. If the plugin decides that on the server, the cache freezes whatever the first visitor saw. Everyone gets the results, or nobody ever does, and the counts stay stuck at whatever they were when the cache was built.

The fix is to keep the page HTML identical for every visitor and let a bit of JavaScript in the browser work out the personal part, fetching fresh numbers from a URL that is never cached. If you’re testing a poll plugin, test it with your cache on, logged out, in a private window.

How do you stop people voting twice?

You can make it harder, but on a public, anonymous poll you can’t make it impossible.

Method What it stops Where it fails
Cookie or browser storage Casual repeat votes from the same browser Private windows, a second browser, clearing site data
IP address limit One person hammering the button from one connection Blocks whole offices, schools and mobile networks that share one address, and a VPN gets around it
Require login Almost all repeat voting Most casual readers won’t create an account to answer one question

For a light poll on a blog post, browser-based memory is usually the right trade. Nobody is gaming “which editor do you prefer?”, and you don’t want to lock out a whole university because one student voted first. If the result actually matters, say a vote among members, require login and limit it to one entry per user. If it really, really matters, it isn’t a poll anymore, it’s an election, and a WordPress plugin is the wrong tool.

Spam bots are a separate problem from repeat voters. A poll is a form, so the usual form protections apply. Our guide to stopping WordPress form spam covers those.

What do you do with the results?

The worst thing you can do is nothing.

  • Write the follow-up. “We asked 400 readers which backup plugin they use” is a post people link to.
  • Quote it in the original post. Update the article with a line about what readers said. It makes the page feel alive.
  • Be careful with small samples. Thirty votes tell you about your readers, not “WordPress users”.

Also remember a poll is still data collection. If your poll plugin stores IP addresses or anything else per vote, it belongs in your privacy policy like any other form. Our WordPress GDPR compliance checklist has the rest.

What are the ways to add a poll in WordPress?

There are three broad routes.

A dedicated poll plugin

Plugins built only for polls tend to have the most poll-specific options. The downside is one more plugin to update, and some decide everything on the server, which is exactly what breaks behind a page cache. Test that before you commit.

A form builder with a poll mode

Your contact form plugin may handle polls too. A poll is just a form with one choice question and a results view, so you keep one plugin and one place for entries. The catch: some form builders only show results in the admin, and some put visitor-facing results behind a paid tier. If you’re picking one, our roundup of the best WordPress form builder plugins is a starting point.

An embed from a third-party service

Hosted survey tools let you build the poll on their site and paste an embed code into a Custom HTML block. Nothing to install and no caching trouble. In exchange, the votes live on their servers, the embed loads their scripts on your page, and it rarely matches your theme.

How to create a poll with Trinity Forms (free)

  1. Start from the template. Go to Trinity Forms → Templates and click Use template on Quick poll. It creates a form with one required question (“Which do you prefer?”) and three answers, Option A to C, with a Vote button and poll mode already on. It also switches off the notification email, so you don’t get one email per vote.
  2. Edit the question and options. Rename them to your real question. A Radio, Select or Checkbox group question shows bars. A Rating or Range slider question shows an average instead.
  3. Check the poll setting. Under Restrictions (in both the block editor and the Visual Builder) there’s a Poll section with the checkbox Poll: after a vote, show the results instead of the form. The template ticks it for you. You can tick it on any existing form too.
  4. Add it to a post with the Trinity Forms Form block.

After someone votes, the form is replaced by bars showing each option’s percentage and vote count. When they come back later in the same browser, they see the results instead of the form.

On repeat votes, here’s exactly what it does. By default the vote is remembered in the visitor’s browser (localStorage, not a cookie), and there’s no IP check. So a private window or a different browser can vote again. That’s on purpose: it doesn’t lock out people who share a network. If you want something stricter, the same Restrictions tab has Per logged-in user and Per IP address entry limits, plus Only logged-in users may see and submit this form. On a poll, hitting either entry limit shows the results rather than an error message.

On caching: the poll’s page HTML is the same for every visitor, and the live numbers are fetched by the browser from a URL that tells caches not to store it. So it works behind full-page caching. If JavaScript is turned off, the form simply shows.

If you want results somewhere other than right after the vote, there are three options:

  • the {poll_results} merge tag in a confirmation message (or {poll_results:field_id} for one question)
  • the [trinity_forms_poll_results id="12"] shortcode
  • the Trinity Forms Poll Results block, which has a toggle labelled Show the results only after the visitor votes

Answers typed into free-text fields are never shown to visitors, only choice and rating questions. For you, the full tallies are under Trinity Forms → Results. Every vote is also a normal entry under Entries, where the bulk actions include Export selected to CSV.

Frequently asked questions

Can I add a poll to WordPress without a plugin?

Only by embedding one from an outside service, usually by pasting its embed code into a Custom HTML block. WordPress itself has no poll block, so anything that stores votes on your own site needs a plugin.

Why does my WordPress poll show the wrong results to visitors?

Almost always page caching. The cache saved one version of the page, either before or after someone voted, and now serves it to everyone. Use a poll that loads results in the browser, or exclude the page from your cache.

Can I stop people voting more than once?

You can make it harder with browser memory, IP limits or a login requirement, but an anonymous public poll can always be voted on twice by someone determined enough. Pick the method that matches how much the result matters.

How many options should a poll have?

Two to five works best. Fewer than two isn’t a choice, and more than five makes people skim, so the options at the bottom get fewer votes just because of where they sit.