You publish a post, a few people share it, and maybe one person leaves a comment. Whether everyone else found it useful, you don't know. Most readers never comment, and the ones who do often talk about the topic rather than the post.
Below are the main ways to get feedback on blog posts, what each one is good for, and a setup you can copy today.
The short answer
Ask on the post itself. Add one short question at the end of every post, such as "Was this post useful?", followed by an optional "What would make it better?". Readers answer in one tap and you see the answers for each post. Use comments, newsletter replies and analytics alongside it for what a short question can't tell you.
Six ways to get feedback on a blog post
Each way hears from different readers and tells you something different.
| Way | What you hear | The catch |
|---|---|---|
| A question at the end of the post | Whether this post helped, from many readers | Short answers, unless you add a comment box |
| Comments | Opinions and questions from a few readers | Most readers never comment, and comments need moderating |
| Replies to your newsletter | Longer thoughts from subscribers | Only subscribers, and only the ones who reply |
| Social media | Reactions and shares | Mostly about the headline, and spread across platforms |
| Analytics | Visits, time on page and where readers came from | Shows what readers did, not what they thought |
| Asking a few readers directly | Detailed, honest opinions | Takes time, and you only hear from a handful of people |
Of these, only a question on the post asks many readers what they thought of that specific post. The others add detail around it, so start with the question and keep the rest.
What to ask at the end of a blog post
Two or three questions are enough. Ask them in this order:
-
"Was this post useful?"
Yes / No. It takes one tap, so most readers who answer anything answer this, and it gives you one figure per post that you can compare.
-
"What would make it better?"
Multiple choice with a few options, such as "More examples", "More detail", "Shorter" and "Something else". It turns a No into something you can fix.
-
"What should I write about next?"
Optional free text, last. Readers who have already tapped once are much more likely to write something.
Tip: Use the same questions on every post. If each post asks something different, you can no longer compare them.
Where to put the question
Put it straight after the last paragraph, before the comments and the related posts. That's where readers decide whether the post was worth it, and they see the question before they move on.
On long posts, a side tab or a small button that stays on screen also reaches readers who stop halfway. Avoid a pop-up that covers the post while people are still reading it.
Example
Example: a travel blog
Say you write a travel blog with guides to cities. You add "Was this guide useful for planning your trip?" to every guide, followed by "What was missing?" with the options "Prices", "Where to stay", "Getting around" and "Something else".
After a few weeks, most of the No answers on your older guides picked "Prices". The prices date from your first visit. You update the five busiest guides first, add the month you checked the prices, and watch whether their Yes answers go up.
How to read the feedback
- Wait until a post has at least 10 answers before you compare percentages.
- Compare posts on similar topics, and posts of the same kind, such as guides with guides.
- Look for the same reason coming up on several posts. That is a pattern, not one reader's opinion.
- Read the comments once a week, or once a month on a smaller blog.
- Write down what you changed and when, so you can compare the answers before and after.
Turn feedback into better posts
Most feedback leads to one of a few changes:
- Update posts whose readers say the details are out of date.
- Add the section readers say is missing, or link to the post that covers it.
- Write the follow-up posts readers ask for, using their words in the headline.
- Link from your most useful posts to the ones readers rarely find.
Where Asklet fits
Asklet adds the questions to every post with one snippet in your post template. It works on WordPress, Ghost, beehiiv, Webflow, Framer and custom sites. Answers come back per post, with the comments next to the numbers. Readers answer without signing in, and the widget sets no cookies, so it needs no consent banner.
You can start on the Free plan: one website, 10 live pages and 100 responses a month, with no card needed.
Your next steps
-
Add "Was this post useful?" to the end of every post
Put it in your post template, so new posts get it too.
-
Add one follow-up and an optional comment
A few options plus "Something else", then a free-text question last.
-
Place it before the comments and related posts
Add a side tab on long posts for readers who stop halfway.
-
Read the answers on a fixed day
Weekly on a busy blog, monthly on a smaller one.
-
Update the busiest post readers say could be better
Note the date, and compare its answers a few weeks later.
Try these steps on your own site. Asklet adds the questions to every page with one snippet. Free plan, no card needed. Compare the plans.
Start freeCommon questions
How do I get readers to give feedback on my blog?
Make it quick and ask about the post they just read. A one-tap question at the end of the post usually gets more answers than a request to comment or to fill in a form, because it takes a second and needs no account.
Are blog comments a good way to get feedback?
They are good for discussion, but they only hear from the few readers who choose to comment, and comments often talk about the topic, not the post. Use them alongside a short question that every reader can answer.
How many questions should I ask at the end of a post?
One to three. Start with a Yes / No question, add one follow-up that asks for the reason, and make any free-text question optional.
Do I need my readers' email addresses to get feedback?
No. With Asklet, readers answer anonymously on the post, without signing in or leaving any contact details.
Related
More from the blog
- Privacy and law EU cookie consent changes: where the Digital Omnibus stands in October 2026 9 min read
- Privacy and law Session replay and pixel lawsuits: what website owners should know 9 min read
- Privacy and law How to make a feedback widget accessible, and what the European Accessibility Act asks 9 min read