FAQ’s have been quite a popular topic on the forums lately (and for good reason)
They really help with SEO, and also are very helpful to consumers.
Recently we’ve just designed and implemented a new version of FAQ with expanding and collapsing on https://www.realestateewebmasters.com and we’ll be rolling that out soon (likely next release) to Renaissance.
Being the SEO / product nerd that I am… I wanted to do more with it!
So @hatzopoulos and I have gotten together to start prototyping a new FAQ’s module with the goal of making FAQ’s easier to implement and far more useful.
Let me explain:
The idea is to get the FAQ’s into a database. That way, we can do things like program searches against them, create snippets with them, dynamically tag and link them, organize them by category, produce JSON for schema implementation and generate XML sitemaps.
This is a great idea. I do think having a spot for images will be helpful though.
I’ve seen community pages with a ton of content but the page gets too long. It takes a long time to scroll to get to the listings. If you could create an FAQ snippet, you could build out a community FAQ for an area you are focused on.
FAQ on steroids, love it! This will be great for agents to make their own too. They don’t know HTML/CSS and their time is better spent selling. A few thoughts:
An FAQ is going on all our community pages for sure.
The module could have the option for us to title it. In other words, FAQ is not a hard coded title. We would use this in several places as more of list than an FAQ. For example spring cleaning, or prep your home for sale lists.
The sample from @AmyPye with icons looked good. Optional of course! I see it particularly useful when it’s used more for a list. It’s a subtle way of grouping your items. For example on the prep home for sale list, I might use broom icon for cleaning items, a hammer for repair items, etc.
Make it available on the upcoming intranet. For the intranet, we don’t really need all the tags, etc, just having the ability for accordions on the intranet is good enough.
One small UI note is having a word counter. I think the best length for FAQ answers is around 60 words or less because this hits the ideal length for appearing in People Also Ask and other rich results.
Long shot idea: Have a field for entering target keywords. Then you have a system that runs searches based on a few variations of those keywords, then pulls all the People Also Ask questions that appear and offers them as suggestions for FAQ questions.