Blogging Survey Template

A blogging survey helps an editor or community organizer understand the people doing the writing. This version asks about one blog, recent publishing activity, and the support a contributor would find useful next. Send it before planning workshops, editorial check-ins, or shared resources. Keep the writer’s purpose in view: a personal journal and a business blog may need very different support.

Publishing frequency alone does not explain whether a blogging routine is working. Someone documenting a project may post only when there is an update; someone explaining a difficult topic may need more research time. Ask about purpose before interpreting the number of posts.

Nardi, Schiano, Gumbrecht, and Swartz’s Why We Blog (2004) describes reasons people write, including to “articulate ideas through writing”. The study interviewed 23 bloggers and examined their blogs. The author’s blogging research collection links to the paper. This small, early study helps frame questions about purpose; it does not describe today’s blogging market or validate this questionnaire.

Use the SurveyLegend example to connect a reported obstacle with a practical response. Difficulty choosing a topic might suggest an idea session. Trouble preparing images calls for different help. Let writers describe what would be useful instead of assuming everyone needs a higher posting target.

Answer about the blog you write for most often, using the past 30 days for recent activity. If you have not published yet, choose the options that fit your current stage. Every question is optional. Do not include private drafts, client information, login details, or another person's personal information.

Name the contributor group and the 30-day reference period in the invitation. Ask people with several blogs to use the one they write for most often. Keep “I have not attempted a post” so a new or paused contributor does not have to invent a recent experience.

Match the purpose and audience choices to your group without removing “Something else.” In a workplace, explain whether responses are used to plan support and who will read them; avoid silently turning a voluntary writing-needs survey into a performance ranking.

Ask contributors for an example of useful support without requesting unpublished work. SurveyLegend’s open-ended questions guidance helps with that invitation. If your decision concerns readers finding or using the blog, collect their experience separately with the website feedback template.

Copy this prompt into an AI assistant to draft the questions. Review the draft, then build and customize the survey in SurveyLegend before sharing.

Group responses by the main purpose of blogging before comparing publishing activity. A zero-post response may reflect a pause, a research-heavy post, or a problem with the workflow; read the obstacle and support answers before deciding. Separate new contributors from those who attempted a post recently. Build a short support plan that names the reported barrier, the proposed resource or conversation, and when the group will review it. Topic ideas, editorial feedback, technical help, and time to write are different needs. Do not infer audience satisfaction from the writer’s preferred feedback channel, or equate a higher post count with better content. Reuse the same reference period for a later check and record changes in group membership.