Take the 2022 WordPress Survey

The 2022 WordPress Survey is now open to anyone using WordPress – from beginners to professional developers and everyone in between. This annual survey helps project leaders and contributors learn more about how and why the software is being used.

This year’s survey is available in the seven most frequently installed languages based on the number of WordPress downloads, including FrenchGermanItalian, JapaneseRussian, and Spanish.

The survey begins with some questions about basic demographics and moves on to a mix of interesting questions that fall more under the topic of market research than previous years. It asks why you use WordPress instead of other tools/platforms, what you think are the most essential three plugins when building sites, and what are the best and most frustrating things about WordPress. The survey also asks whether respondents have used blocks in the new Site Editor and which Site Editor they prefer. It will be interesting to see the data from these questions.

The last eight questions are for contributors, and even with those it takes less than five minutes to complete. Although some information from the 2022 survey may be shared in the annual State of the Word address, the survey will be open through the end of 2022.

The analysis from the 2021 survey results will be shared in early 2023 and WordPress will publish the 2022 results sometime next year.

6

6 responses to “Take the 2022 WordPress Survey”

  1. Hi Sarah! Quick note… the survey will close on Dec 31, 2022 (not 2023). Thanks for helping amplify this opportunity for folks to provide feedback on all things WP.

  2. Interesting survey design. Almost no questions about Block Editor frustrations. Seems designed to produce a predictable and pro BLOCK WP response.

  3. Its a shame there arent more questions for developers or agency people. The frustrations I have with WP these days is that if I create a custom solution for a client site in Dec 2021 it will probably be broken by deprecated WP methods or declarations by Dec 2022. Of course it might NOT be broken, but it might be – so my solution is rendered unstable and I have to explain to a client “this might break and I can’t predict why” and then convince them to assign budget for addressing these random changes in implementation.

    • That is one of the reason why – at least in my bubble – many of the more technically-versed agencies switched to headless WP. Keep the WordPress instance hidden and protected, e.g. by Basic Auth, and only expose a (static) build.

      Then you don’t need to worry as much about security updates, because the instance is much more secure by design already. Of course, this has other implications and needs other budgets from a client.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Newsletter

Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: