What Is A Response Post?

Written By Mike Allison  |  Blog  |  0 Comments

Response Posts

When starting a new website/blog, you're going to need a content plan that includes a couple of types of posts. 

They are,

  • Staple posts.
  • Response posts. 

In this post, I am focusing on the second type, called Response Posts. I will cover Staple Posts in another article. 

This post will answer the following four questions:

  1. What Is A Response Post?
  2. How Many Response Posts Should I Create?
  3. How Should I Format A Response Post?
  4. How Long Should Response Posts Be? 

What Is A Response Post?

A response post directly answers a specific question and generally has low competition. Many blogging experts suggest writing response posts first when creating content for a new website.

New sites do not have any history or authority with Google, and therefore Google has no reason to rank your new website and its content (yet). 

Since response posts often have the least competition, it's a good idea to write them first to answer specific search queries that are most underserved by bloggers. 

Response posts should help you 

  • drive some traffic to your website.
  • rank quickly in the SERPs. 
  • build authority with Google. 

How Many Response Posts Should I Create?

For a new website, consider writing a minimum of 10 response posts to get things rolling. If you want to write more than 10, that's okay, too, but 10 is a good number to begin.

Because response posts tend to rank quickly in Google search, they will help your new website get noticed much quicker, and you'll begin seeing your website traffic building. 

Response posts are easy and quick to complete. They're short enough that readers can quickly and easily absorb them, and there's a good chance that Google will feature your snippet when people search for that specific question.

How Should I Write A Response Post?

When writing a response post, you should plan to have at least three subheadings. Subheadings break your post into sections, and each section covers one facet of your topic.

Have you noticed the subheadings in this post? The first one is "How Many Response Posts Should I Create?" and the second is "How Should I Write A Response Post?"

Each section answers a question related to the overall topic, "What Is a Response Post?"

Now, I've said you should have at least three subheadings, but don't hold back. If you need more than three subheadings and sections for your response post, go for it. 

How Long Should Response Posts Be?

Response posts should be around 1,000 words long, but they can be longer if necessary. 

Remember, your blog posts should be as long as necessary to provide a thorough answer and reference for the reader who has come to your site. 

Readers won't be satisfied if they come to your site to find the answer to a specific question and discover that you haven't answered their question thoroughly. They might even feel duped.

If the answer you have provided is not thorough enough, they will have to search for another site to find a complete response to their question. That can be frustrating because it wastes time and may turn people off of your website. 

One of your goals as a blogger/website owner is to build trust with your audience, and thoroughly answering their questions is one of the quickest ways to do that. 

\Once your audience trusts you, they'll keep coming back to your site, will subscribe to your newsletter or email list, and if you are selling products, they will be more inclined to buy from you. 

Summary

Response posts,

  • directly answer a specific question.
  • drive traffic to your new site.
  • rank quickly in the SERPs.
  • build your website's authority with Google.
  • are approximately 1,000 words long but can be longer, if needed, to thoroughly answer your reader's questions. 
  • have a minimum of 3 subheadings/sections but can have more if needed. 
  • are the first content pieces to create for a new website. 
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>