How RankKit SEO's schema works
RankKit SEO builds one connected JSON-LD graph for every page automatically. Learn which nodes it outputs, where they come from and how to change them.
On this page
Schema (structured data) tells search engines and AI assistants what a page is about: who runs the site, what kind of page it is, who wrote it and where it sits in the site. Google uses it for rich results and knowledge panels.
RankKit SEO outputs schema on every page without any setup. It prints a single JSON-LD block in the page head, as one @graph whose nodes point at each other by @id. You change what it says through your settings, the post's schema type and, when you need more, the Schema manager.
What every page gets
| Node | When it appears | Where the data comes from |
|---|---|---|
Organization or Person |
Every page | Settings → Identity: name, logo or photo, social profiles. With Local SEO on, the organization also gets a LocalBusiness type with address, phone and opening hours. |
WebSite |
Every page | Site name and URL, plus a SearchAction for your site search. |
WebPage |
Every page except search results and 404 pages | Title, description, dates and the featured image. On category, tag and archive pages and the blog page it becomes CollectionPage. |
BreadcrumbList |
Every page below the home page | The same trail as RankKit SEO breadcrumbs. |
Article, BlogPosting or NewsArticle |
Posts whose schema type is one of these | Headline, dates, word count, author, publisher, image, category and focus keywords. |
Product |
Products (with WooCommerce) | Price, currency, stock status, SKU and ratings. See WooCommerce SEO. |
FAQPage |
Pages with FAQ content | Questions from the FAQ block and from core Details blocks (the summary is the question). |
HowTo, table of contents |
Pages with the How-to or Table of contents block | The block contents. |
Who runs the site matters most for Google's knowledge panel, so check RankKit SEO → Settings → Identity first. See Site identity.
Choose the schema type of a page
Each page has a schema type that decides its main node.
Default per content type. Go to RankKit SEO → Settings → Content types. Each content type has a Default schema setting. Out of the box, posts use Article, WooCommerce products use Product and everything else uses Web page.
Per page. In the block editor, click the RankKit SEO button in the editor toolbar to open the RankKit SEO panel and choose Schema. In the Schema Type card, pick a type under Page type (the content type's default is marked "(default)") and click Generate Schema. The page node is then built from the post's title, author, dates, image and content. In the Classic Editor and Elementor, pick the Schema type on the Advanced tab; its first option, Default (…), follows the content type setting.
The types you can choose:
| Option | Output |
|---|---|
| Web page | WebPage |
| Article, Blog post, News article | WebPage plus an Article, BlogPosting or NewsArticle node |
| Product | WebPage plus a Product node |
| About page, Contact page, Collection page, Profile page, Item page, Q&A page, Checkout page, Search results page, Medical web page | The page node takes that WebPage subtype |
| No schema | No page node for this page |
Add more schema to a page
The automatic graph covers the basics. For a recipe, an event, a review, a job posting or a video, open the Schema section of the RankKit SEO panel, pick the type under Rich result and click Generate Schema. The item is added pre-filled with variables, ready to complete; see Add and edit schema on a page. You can also import schema from a live page there. An Article item you add there replaces the automatic Article node instead of adding a second one.
To check the final result, use the schema validator on RankKit SEO → Schema.
RankKit SEO Pro RankKit SEO Pro adds schema templates: write schema once and apply it to every page that matches a set of conditions, filled from ACF, Meta Box, Pods or ACPT fields. Pro also imports schema from pasted JSON-LD code or a
.jsonfile. See plans.
Turn schema off
Schema output is a module. To switch it off, go to RankKit SEO → Dashboard, find the Modules card and turn off Schema. Do this only if another plugin or your theme already prints the structured data you want, since two sets of schema for the same page confuse search engines.
FAQ
Do I need to add schema to every page by hand?
No. Every page gets the Organization or Person, WebSite, WebPage and BreadcrumbList nodes automatically, and posts get Article schema. Add items in the Schema manager only for content that has its own rich result type, such as recipes, events or products.
Why is there no Article schema on my page?
The page's schema type is not Article, Blog post or News article. Check the page type in the Schema section of the RankKit SEO panel (or the Advanced tab in the Classic Editor), and the Default schema of that content type under Settings → Content types.
Where does the FAQ schema come from?
From the RankKit SEO FAQ block and from core Details blocks in the page content. RankKit SEO adds FAQPage to the page node and lists each question with its answer. You can also add an FAQ item in the Schema manager, but if the page already has FAQ schema from blocks, that item is skipped so the questions don't appear twice.
Was this page helpful?
Related guides
Add and edit schema on a page
Use the Schema manager to add Recipe, Event, Product, FAQ, Job posting and other schema to a page, with every type and field explained.
Site identity: organization or person
Tell search engines who runs your site, an organization or a person, with its name, logo and social profiles, for schema and knowledge panels.
FAQ, How-to and Table of contents blocks
Add FAQ, How-to and Table of contents blocks that output FAQPage, HowTo and navigation schema, with no JavaScript and a tiny stylesheet.
Check and import schema
Validate the final JSON-LD a page outputs, fix errors before Google sees them, and import schema from another page's URL or from pasted code.
Still need help?
Email us with your WordPress and RankKit SEO versions and what you tried. Pro customers get priority replies.