Not every page, blog post, or piece of content needs to have FAQs. In many cases, FAQs are excessive and could hurt your SEO. All of us get excited when we see new traffic coming in, myself included, but FAQs should be used to add value.
I’m writing this guide to keep myself, my team, and you focused on when to use FAQs for SEO and the user experience on your page.
This post has two sections:
Blog post schema has a fantastic function called “has part” where you can nest your FAQ schema as part of the page and topic. But just because you can nest FAQs into your posts, it does not mean you should. Here are a few types of blog posts where I see a lot of FAQs, and my recommendations on using or avoiding them.
When you’re explaining a concept you may need FAQs when the answer has no natural fit in the copy.
If the questions are part of the original answer, adding a dedicated FAQ just to get a “People also ask” answer is excessive. From what I’ve seen, you can just as easily get an answer box instead by using proper headers, sub headers and adding the information as passages. The added bonus here is I’ve seen more click throughs from answer boxes than I have from “People also ask” answers.
Google and other search engines are getting really good at finding answers within text. If the answer to the question is part of your explanation of the concept, product, theory or theme, let the answer build your topical relevance under the header tags, and let the search engines find the answer within your copy. By providing the answer within the text you’re also showing your expertise with the visitor and building their trust.
If there is no way to tie in an important piece of information into your instructions, then you may want to add a couple…