Select Page

A simple guide to adding FAQ Schema to your website

Adding FAQ Schema can seem like an overwhelming technical challenge on many levels, especially if you don’t have a dedicated technical SEO resource. Afterall, not only do you have to know Javacript to create the FAQ schema code, but you have to maintain that code so that it’s content always matches the on-page content, and you should only ask a question once on your entire site, so you have to avoid conflicts.

We’ve broken this FAQ schema tutorial in to two specific segments.

First, we’ll cover how to implement FAQ Schema on your website.  Secondly, we’ll give you some methods to track your FAQ schema implementations to help reduce conflicts and help you keep your schema up to date so it remains effective!

How to Implement FAQ Schema (Plugin)

If you’re using any half decent CMS there’s a good chance there’s a plugin available that will help you add FAQ Schema to your content in a visual interface. Even better, these plugins will generally speaking update the code as your writers add content.

Make sure you choose a plugin that adds a JQuery snippet for the FAQ Schema (not inline). While Google has stated they won’t prioritize one implementation over another, JQuery is the standard for Schema implementation, and it’s a little faster too.

Also make sure that the Schema plugin works with how you implement Schema, many plugins provide blocks for the default WordPress Gutenberg editor, but you may need specific plugins for some page builders such as Divi or Avada.  There are some universal plugins that use shortcodes, but these may be a little harder to implement.

You can install plugins easily through either the WordPress admin interface, or by purchasing the plugin from a website and uploading according to their instructions.

WordPress FAQ Schema Plugins


RankMath is one of the leading full SEO plugins (Either choos this or Yoast) and it includes Gutenberg FAQ schema functionality in it’s free tier. While I personally prefer Yoast, Rank math is cheaper and still highly functional  They also boast a faster code base, however I’ve found both to be pretty lightweight!


Yoast is one of the most complete SEO plugins on the market (and it’s FAQ schema implementation is included free of charge). It’s Gutenberg module in it’s free tier.

Hero WordPress FAQ

A simple visual builder that allows you to add FAQ blocks anywhere to your site with a shortcode. This starts at $49 a month, and while it’s shortcode system makes it a little more labor intensive, it does help you manage and avoid conflicts in their interface.

Manually Adding FAQ Schema

Manually adding FAQ schema used to be much more difficult, especially with the wider adoption of JQuery as the go-to schema implementation. Fortunately some great tools have popped up to handle the code writing, so you only have to worry about the maintenance.  My favorite tool is the Technical SEO Schema Generator which helps you generate JQuery FAQ Schema quickly and simply.

As with any manual implementation though, if there is a major overhaul of Schema (unlikely at this point, but still a possibility) or if the content is updated without checking the scema code, you may be left with some significant cleanup on your hands.

Once you have the schema code you simply have to insert it in the header code section of that page (ideally) and Google will associate that schema JQuery with the content on your page. 

Maintaining FAQ Schema

Maintenance of your FAQ schema is a royal pain in the ass, but it’s also something you want to start doing imediately. FAQ schema rules are pretty strict, and with JQuery, eve more so.

1) Your FAQ schema must match on page content to trigger (so if the page content is changed, the Schema will not attatch to it)

2) You cannot use the same question twice on one website, so you have to make sure no duplicates exist.

Breaking these rules can impact your rich snippet rankings, so you’ll want to avoid these issues.

Let’s dive in to how you can avoid these problems.

Keeping Content and FAQ JQuery Schema in Sync

Making sure your Schema code matches the code seems simple enough, and with the right plugins or software this is pretty well controlled.  However if you are manually adding the Schema JQuery you never know when a writer is going to come through and change on page content.  there are two concurrent solutions to help here, education, and monitoring.


Make part of the content process oriented around a schema process. If FAQ sections are being changed, they must ensure (either they, or the SEO team) update the JQuery. Highlight just how valuable rich rankings are, and why it’s a priority.

If you are using a spreadsheet or similar to track Schema FAQ questions we recommend training your writers to keep that up to date with any changes as well.


Even with the best training, mistakes are made.  Whether or not you train, you can set up a tool such as Content King to let you know when changes are made to the website.

Avoiding Schema FAQ Duplication

Our number one recommendation for FAQ schema is to keep a tracking doc of pages with schema, and at a bare minimum, questions asked.

When any FAQ schema is changed or added, those changes should be added to this document.

Make sure to add a relevant “tag” column to sort questions, this makes it more searchable.  

Once you have this document any new FAQ schema should be crosschecked against this document to make sure that new questions are not duplicating old questions.

This process is far from fun, but it can help you maintain your rich snippet positions, and hile it’s more likely that Google wil simply “choose” which snippet to display, it may simply remove your current ranking. At some point we’re hoping that Google will get better at dealing with these duplications, but for now it’s better to keep a clean house than rely on the algorythm.