Advanced JSON-LD Schema Generator

The Advanced JSON-LD Schema Generator lets administrators create structured data from a visual form instead of writing JSON-LD by hand. The generated JSON-LD can be saved as a reusable schema template, copied, tested, and inserted into the front end of the site.

The add-on is useful when a site needs custom schema for articles, breadcrumbs, events, FAQs, how-to content, jobs, local businesses, organizations, people, products, recipes, videos, and website search markup.

Installation

1. Log in to the WordPress admin dashboard.

2. Go to Plugins > Add New.

3. Click Upload Plugin.

4. Choose the add-on ZIP file.

5. Click Install Now.

6. After installation finishes, click Activate Plugin.

After activation, a new admin menu item named Advanced Schema appears in the WordPress dashboard. It has two submenus:

• All Templates
• Add New Schema Template

Advanced JSON-LD Schema Generator – Main Menu

All Templates

Here, you can view saved schema templates, search templates, edit templates, or move templates to Trash.

You can also click on the “Schema Builder” button to create a new template.

Advanced JSON-LD Schema Generator – All Templates

Edit, or Remove Templates

Edit a Template

1. Navigate to Advanced Schema > All Templates.

2. Click the template title.

3. Update the form fields, placement settings, or template title.

4. Click Save or Update.

Remove a Template

1. Navigate to Advanced Schema > All Templates.

2. Hover over the template title.

3. Click Trash.

4. Clear any cache and test the affected page to confirm the schema is no longer printed.

Schema Builder

Here, you can open the Schema Builder and create a new schema template. A template has the following areas:

Builder Area	Purpose
Schema selector	Choose the type of Schema.org markup you want to create.
Form panel	Enter details such as title, URL, image, author, address, offer, rating, steps, or other schema-specific fields.
JSON-LD preview	Shows the generated JSON-LD script as the form is completed.
Action buttons	Test in Google, open Schema.org Validator, copy code, save the template, or reset the form.
Apply Schema panel	Connect the saved schema template to a post type or content item.

Schema Types Included

You will find a total of 14 Schema Types in the add-on, and you can select any as per your type.

Schema Type	Best Used For
Article	Blog posts, news articles, guides, and editorial content. Includes Article, NewsArticle, and BlogPosting options.
Breadcrumb	Pages that need a BreadcrumbList trail.
Event	Online, offline, or mixed events with date, time, location, performer, and ticket offers.
FAQ Page	Pages with visible questions and answers.
How-to	Step-by-step instructional content.
Job Posting	Job listing pages.
Local Business	Physical business locations, offices, or stores.
Organization	Company or brand identity markup.
Person	Author, team member, expert, or profile pages.
Product (Simple)	Standard product pages with offer, rating, and review fields.
Product (WooNinjas)	Advanced product schema designed for WooNinjas-style software products with aggregate offers and plan-level pricing.
Recipe	Recipe pages with ingredients, cooking time, nutrition, steps, ratings, and reviews.
Video	Pages with video content that need VideoObject markup.
WebSite	Website identity and sitelinks search box markup.

1. Article Schema

The Article Schema is used for blog posts, news articles, guides, tutorials, and other written content. It helps search engines understand the article title, URL, author, publisher, images, and publish/update dates.

Use this schema when the page is mainly informational content, such as a blog post, company update, news article, or educational guide.

Article @type

Choose the article type that best matches the content.

• Article: Use for general articles, guides, and informational content.
• NewsArticle: Use for news updates, announcements, or time-sensitive content.
• BlogPosting: Use for standard blog posts and tutorials.

URL

Enter the full URL of the article page.

• Use the live page URL starting with https://.
• This should be the same page where the article content is published.

Headline

Enter the main headline of the article.

• This should usually match the page title or blog post title.
• Keep it clear, natural, and within the character limit shown in the field.

Image URL

Add the direct URL of the article image.

• This can be the featured image, banner image, or another main image used in the article.
• Make sure the image URL is public and accessible.

Add Image

Use the + Image button to add another image field.

• Add more images only if they are important to the article.
• Remove extra image fields if they are not needed.

Short Description

Enter a brief description of the article.

• Summarize the article in one or two clear sentences.
• Keep it relevant to the actual content on the page.

Author @type

Select whether the author is a Person or an Organization.

• Choose Person for an individual writer.
• Choose Organization if the article is published by a company, brand, or team.

Author

Enter the author name.

• If the author type is Person, add the person’s name.
• If the author type is Organization, add the company or team name.

Author URL

Enter the author profile URL.

• This can be an author archive, team member page, or company profile page.
• Use a full URL starting with https://.

Publisher

Enter the name of the publisher.

• This is usually the website, company, or brand that published the article.
• Keep it consistent with the visible site branding.

Publisher Logo URL

Enter the direct URL of the publisher’s logo.

• Use the official logo image.
• Make sure the logo URL is public and accessible.

Date Published

Select the original publish date of the article.

• This should be the date when the article first went live.
• Keep it consistent with the date shown on the page, if visible.

Date Modified

Select the latest update date of the article.

• Use this when the article has been updated after publishing.
• Leave it empty if the article has not been modified.

JSON-LD Preview

The preview box shows the generated schema markup.

• As you complete the fields, the plugin creates the JSON-LD code automatically.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to choose where the schema should be applied.

Select Post Type

Choose the content type where the schema should be added.

• This may include posts, pages, products, downloads, or other available post types.
• Select the correct type so the related content appears in the next dropdown.

Select Post/Page/Product

Choose the exact content item where this schema should appear.

• Select the article page that matches the schema details.
• The schema information should match the visible content on that page.

Save or Publish

After completing the fields, save or publish the schema template.

• Once saved, the plugin will apply the generated schema to the selected content.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

2. Breadcrumb Schema

The Breadcrumb Schema is used to show the path of a page within your website structure, such as Home > Blog > Article Title. It helps search engines understand how the page fits into the site hierarchy and can improve the way breadcrumb paths appear in search results.

Use this schema when you want to define a clear navigation trail for a post, page, product, or custom post type. Each breadcrumb item should represent one step in the path and should be entered in the correct order.

Page #1’s Name

This field is used for the label of the first breadcrumb item.

• Enter the name exactly as users would see it, such as Home, Blog, Shop, or another top-level page.
• Keep the wording short and clear so the breadcrumb path is easy to understand.

URL #1

This field is used for the link of the first breadcrumb item.

• Enter the full URL for the page name you added in Page #1’s Name.
• Make sure the URL is correct and starts with https://.

Example:

Field	Value
Page #1’s Name	Home
URL #1	https://example.com/

Page #2’s Name

This field is used for the second breadcrumb item in the path.

• Enter the next step in the page hierarchy, such as a category, section, or parent page.
• This should follow the logical structure of the site and come after the first breadcrumb item.

URL #2

This field is used for the link of the second breadcrumb item.

• Enter the full URL that matches the second breadcrumb name.
• Each breadcrumb name should always match its correct destination URL.

Example:

Field	Value
Page #2’s Name	Blog
URL #2	https://example.com/blog/

Add URL

The Add URL button lets you add more breadcrumb items.

• Use this when the page has a longer path, such as Home > Resources > SEO > Article.
• Add each new breadcrumb step in the correct order so the final schema reflects the real page path.

Remove Item

Each breadcrumb row includes a remove option.

• Use it to delete a breadcrumb item if it was added by mistake or is no longer needed.
• This helps keep the breadcrumb path clean and accurate.

JSON-LD Preview

The preview panel shows the generated breadcrumb schema code.

• As you enter breadcrumb names and URLs, the plugin automatically creates the JSON-LD markup.
• This lets you review the structured data before saving or publishing the schema template.

Apply Schema to Post/Page

This section is used to assign the breadcrumb schema to a specific content item.

Select Post Type

Use this field to choose the content type where the breadcrumb schema should be applied.

• This may include posts, pages, products, downloads, or other custom post types on the site.
• Select the correct type first so the next field can load the related content items.

Select Post/Page/Product

Use this field to choose the exact content item where the breadcrumb schema should appear.

• After selecting the post type, choose the specific post, page, or product from the dropdown.
• This ensures the breadcrumb schema is attached to the correct page.

Save or Publish

After entering the breadcrumb items and selecting the target content, save or publish the schema template.

• Once published, the breadcrumb schema will be added to the selected page automatically.
• It is a good idea to test the page afterward with Google’s Rich Results Test or Schema Markup Validator to confirm everything is working correctly.

3. Event Schema

The Event Schema is used for events such as webinars, workshops, classes, conferences, meetups, product demos, and live sessions. It helps search engines understand the event name, date, time, location format, performer, ticket details, and event status.

Use this schema when a page is created for a specific event, and you want to provide structured event details in JSON-LD format.

Name

Enter the official name of the event.

• Use the same event title shown on the page.
• Keep it clear and specific, such as Live WordPress SEO Workshop or WooCommerce Training Webinar.

Event’s Description

Add a short description of the event.

• Explain what the event is about and who it is for.
• Keep it brief, useful, and aligned with the visible page content.

Image URL

Enter the direct URL of the event image.

• This can be the event banner, featured image, or promotional graphic.
• Make sure the image URL is public and accessible.

Start Date

Select the date when the event begins.

• Use the actual event start date.
• This should match the date shown on the event page.

Start Time

Enter the event start time.

• Use the format shown in the field.
• Make sure the time matches the event’s official schedule.

End Date

Select the date when the event ends.

• For a single-day event, this may be the same as the start date.
• For multi-day events, use the final event date.

End Time

Enter the event end time.

• Use the format shown in the field, such as 17:30.
• This helps search engines understand the full event duration.

Event Status

Select the current status of the event.

• Use this field to show whether the event is scheduled, canceled, postponed, or moved online.
• Choose the option that accurately reflects the event’s current state.

Attendance Mode

Select how people can attend the event.

• Use this field to define whether the event is online, offline, or mixed.
• This is useful for webinars, in-person events, and hybrid events.

Performer @type

Select the type of performer for the event.

• Choose the option that best represents who is performing, presenting, or leading the event.
• This may be a person, organization, group, or another supported performer type.

Performer’s Name

Enter the name of the performer, speaker, host, or organization.

• Use the official name shown on the event page.
• For webinars or training sessions, this can be the speaker, instructor, or hosting company.

Add Ticket Type

Use the Add Ticket Type button to add a ticket along with its name, price, and URL.

• Add a separate ticket type for each option, such as General Admission, VIP Package, or Early Bird Ticket.
• This helps define the available event offers in the schema.

Currency

Select the currency used for the event ticket price.

• Choose the correct currency, such as the US Dollar (USD).
• Make sure the selected currency matches the price shown on the event page.

JSON-LD Preview

The preview panel shows the event schema code as it is generated.

• As fields are completed, the plugin builds the JSON-LD markup automatically.
• Users can review the output before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Event schema to a specific page, post, product, download, or custom post type.

Select Post Type

Choose the content type where the Event schema should be used.

• This may include posts, pages, products, downloads, or other available custom post types.
• Select the post type first so the correct content list can load.

Select Post/Page/Product

Choose the exact page or item where the Event schema should appear.

• This should be the event page or the page that contains the event information.
• Make sure the schema matches the visible content on that page.

Save or Publish

After completing the event fields, save or publish the schema template.

• Once published, the Event schema will be added automatically to the selected content.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

4. FAQ Page Schema

The FAQ Page Schema is used for pages that contain a list of questions and answers. It helps search engines understand that the page is an FAQ-style page and identifies each question along with its matching answer.

Use this schema when the page includes real FAQ content, such as product FAQs, service FAQs, help pages, or support content. Each question should have a clear answer, and the schema should match the visible content on the page.

Question #1

This field is used to enter the FAQ question.

• Add the question exactly as it appears on the page.
• Keep it clear, natural, and easy to understand.
• Each question should cover one specific topic.

Answer

This field is used to enter the answer for the question.

• Write a clear and direct answer that matches the visible page content.
• Keep the answer helpful and relevant to the question.
• Avoid adding content that does not appear on the page.

Add Question

The Add Question button lets you add more FAQ items.

• Use it to create multiple question-and-answer pairs.
• Add each FAQ item separately so the schema reflects the full FAQ section correctly.

Remove Question

Each question row includes a remove option.

• Use it to delete a question if it was added by mistake or is no longer needed.
• This helps keep the FAQ schema accurate and clean.

JSON-LD Preview

The preview panel shows the generated FAQ schema code.

• As you add questions and answers, the plugin automatically builds the JSON-LD markup.
• This helps you review the schema before saving or publishing it.

Apply Schema to Post/Page

Use this section to assign the FAQ schema to a specific post, page, product, or custom post type.

Select Post Type

Use this field to choose the content type where the FAQ schema should be applied.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the correct type first to load the related content items.

Select Post/Page/Product

Use this field to choose the exact item where the FAQ schema should appear.

• After selecting the post type, choose the correct page or post from the dropdown.
• Make sure the selected content matches the FAQ questions and answers you entered.

Save or Publish

After adding the FAQ items and selecting the target content, save or publish the schema template.

• Once published, the FAQ schema will be added automatically to the selected page.
• It is a good idea to test the page afterward with Google’s Rich Results Test or Schema Markup Validator tool to confirm the FAQ markup is working properly.

5. How-to Schema

The How-to Schema is used for pages that explain a process through step-by-step instructions. It is useful for tutorials, setup guides, repair guides, recipes, onboarding steps, and instructional content.

Use this schema when the page teaches users how to complete a specific task. The steps added in the schema should match the instructions shown on the page.

Name

Enter the title of the how-to guide.

• Use the same or a similar title shown on the page.
• Keep it specific, such as How to Set Up WooCommerce Bookings or How to Add Schema Markup in WordPress.

Description

Add a short summary of what the guide helps users do.

• Explain the purpose of the tutorial in one or two clear sentences.
• Make sure the description matches the actual page content.

Total Time

Enter the estimated time needed to complete the process.

• Add the time in minutes.
• For example, enter 30 if the task takes around 30 minutes.

Estimated Cost

Enter the expected cost required to complete the task.

• Use this when the process requires a paid product, tool, material, or service.
• Leave it blank if there is no specific cost.

Currency

Select the currency used for the estimated cost.

• Choose the correct currency, such as USD.
• This should match the cost entered in the estimated cost field.

Image URL

Enter the direct URL of the main image for the how-to guide.

• This can be the featured image, tutorial banner, or main instructional image.
• Make sure the image URL is public and accessible.

Add Supply

Use the Add Supply button to add materials or items needed for the task.

• Add supplies such as documents, files, parts, ingredients, or physical items.
• Only include supplies that are actually required to complete the process.

Add Tool

Use the Add Tool button to add tools needed for the task.

• Add tools such as software, plugins, devices, or equipment.
• For example, a WordPress tutorial may include WordPress, WooCommerce, or a specific plugin as tools.

Step #1: Instructions

Enter the instructions for the first step.

• Explain what the user needs to do in this step.
• Keep the instructions clear, action-based, and easy to follow.

Step Image URL

Enter an image URL for the specific step.

• Use this when the step has a related screenshot or visual example.
• Make sure the image supports the instruction and is publicly accessible.

Step Name

Enter a short name for the step.

• This can be a brief label such as Install the Plugin, Open Settings, or Configure Booking Rules.
• Keep it short and descriptive.

Step URL

Enter the URL related to the step, if available.

• This can be a section link, tutorial page link, or relevant page URL.
• Leave it blank if the step does not need a separate URL.

Add Step

Use the Add Step button to add more instructions.

• Add each step in the correct order.
• The final schema should follow the same process shown on the page.

Remove Step

Each step includes a remove option.

• Use it to delete a step that was added by mistake.
• This helps keep the how-to process accurate and clean.

JSON-LD Preview

The preview panel shows the generated How-to schema code.

• As you complete the fields, the plugin automatically builds the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the How-to schema to a specific post, page, product, or custom post type.

Select Post Type

Choose the content type where the How-to schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact content item where this schema should appear.

• Pick the page or post that contains the how-to guide.
• Make sure the schema fields match the visible instructions on that page.

Save or Publish

After adding the guide details, tools, supplies, and steps, save or publish the schema template.

• Once published, the How-to schema will be added automatically to the selected content.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

6. Job Posting Schema

The Job Posting Schema is used for job listing pages. It helps search engines understand the job title, company details, employment type, work location, salary range, requirements, and application-related information.

Use this schema when the page is created for a specific job opening. The information entered here should match the visible job listing on the page.

Job’s Title

Enter the official job title.

• Use the same title shown on the job listing page.
• Keep it clear, such as SEO Specialist, WordPress Developer, or Customer Support Agent.

Identifier

Enter a unique job identifier.

• This can be an internal job ID, reference number, or listing code.
• Use it if your company tracks job openings with unique IDs.

Job’s Description

Add the full job description.

• This field supports HTML, so you can include formatted content if needed.
• Add the role summary, main duties, expectations, and key details that appear on the job page.

Company

Enter the name of the company hiring for the role.

• Use the official business or brand name.
• This should match the company name shown on the job listing.

Company URL

Enter the company website URL.

• Use the full website link starting with https://.
• This helps connect the job listing with the hiring organization.

Company Logo

Enter the direct URL of the company logo.

• Use the official logo image.
• Make sure the image URL is public and accessible.

Industry

Enter the industry related to the job.

• Examples include Software Development, Digital Marketing, Education, or eCommerce.
• Keep it accurate and relevant to the role.

Employment Type

Select the type of employment.

• Use this field to define whether the job is full-time, part-time, contract, temporary, internship, or another available option.
• Choose the option that matches the actual job offer.

Work Hours

Enter the expected work hours for the role.

• This can include schedule details like 9 AM to 5 PM, 40 hours per week, or Flexible hours.
• Keep it consistent with the job page.

Date Posted

Select the date when the job was published.

• Use the original posting date.
• This helps search engines understand how current the job listing is.

Expire Date

Select the date when the job listing expires.

• Use the application deadline or the date when the job should no longer be considered active.
• Keep this updated if the hiring timeline changes.

Remote Job

Check this option if the job is remote.

• Use it only when the role can be performed remotely.
• If the job is location-based or office-based, leave it unchecked.

Country

Enter the country where the job is based.

• Use the country related to the work location.
• For remote jobs, use the hiring company’s country or the location requirement, if one exists.

State

Enter the state, province, or region for the job location.

• This is useful for local or hybrid jobs.
• Leave it blank only if it does not apply.

Street

Enter the street address of the job location.

• Use this for office-based or location-specific roles.
• Make sure it matches the address shown on the job page, if available.

City

Enter the city where the job is located.

• Use the official city name.
• For remote roles, use this only if a specific location is still required.

Zip Code

Enter the postal or ZIP code for the job location.

• This helps complete the structured location details.
• Use the correct code for the address entered above.

Salary or Min Salary

Enter the minimum salary or base salary for the job.

• Use numbers only where possible.
• This should match the salary information shown on the job listing.

Max Salary

Enter the maximum salary for the role.

• Use this when the job has a salary range.
• For example, if the range is $50,000 to $70,000, enter 50000 as the minimum and 70000 as the maximum.

Currency

Select the salary currency.

• Choose the correct currency, such as USD.
• This should match the salary shown on the job page.

Per

Select the salary payment period.

• Use this to define whether the salary is hourly, daily, weekly, monthly, or yearly.
• Choose the option that matches the job compensation details.

Responsibilities

Add the main responsibilities for the role.

• Mention the key tasks the employee will handle.
• Keep the content clear and aligned with the job description.

Skills

Add the required or preferred skills.

• Include practical skills, software knowledge, tools, or technical abilities.
• Use skills that are actually relevant to the job.

Qualifications

Add the qualifications needed for the role.

• This can include certifications, degrees, training, or professional requirements.
• Keep it specific to the job opening.

Education Requirements

Add the required education level, if applicable.

• Mention degrees, diplomas, or subject areas required for the role.
• Leave it blank if education is not required.

Experience Requirements

Add the experience needed for the job.

• Mention years of experience, previous roles, or related background.
• For example, 2+ years of WordPress development experience.

JSON-LD Preview

The preview panel shows the generated Job Posting schema.

• As you complete the fields, the plugin creates the JSON-LD code automatically.
• Review the preview before saving or publishing.

Apply Schema to Post/Page

Use this section to assign the Job Posting schema to a specific content item.

Select Post Type

Choose the content type where the job schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact content item where the schema should appear.

• Select the job listing page from the dropdown.
• Make sure the selected page contains the same job details added in the schema.

Save or Publish

After completing the job details, save or publish the schema template.

• Once published, the Job Posting schema will be added to the selected page automatically.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

7. Local Business Schema

The Local Business Schema is used for businesses with a physical store, office, clinic, branch, or service location. It helps search engines understand the business name, type, address, phone number, website, opening hours, location coordinates, and social profiles.

Use this schema on pages that represent a local business location, such as a contact page, location page, service area page, or branch page.

LocalBusiness @type

Select the main business type from the dropdown.

• Choose the option that best describes the business.
• This helps search engines understand whether the business is a store, office, service provider, restaurant, clinic, or another local business type.

More Specific @type

Enter a more specific business type if the dropdown does not fully describe the business.

• Use this field when you want to define the business more clearly.
• For example, a general local business may be further described as a dental clinic, law office, marketing agency, or repair shop.

Name

Enter the official business name.

• Use the same name shown on the website, Google Business Profile, and branding.
• Keep the spelling consistent across all business listings.

Image URL

Enter the direct URL of a business image.

• This can be a storefront photo, office image, brand image, or location photo.
• Make sure the image URL is public and accessible.

@ID URL

Enter a unique URL that identifies this business entity.

• This is usually the main business page or location page URL.
• It helps search engines connect this schema to the correct business location.

URL

Enter the website URL for the business.

• Use the full URL starting with https://.
• This should usually be the homepage, contact page, or specific location page.

Phone

Enter the business phone number.

• Use the phone number customers should call.
• Keep the format consistent with the phone number shown on the page.

Price Range

Enter the general price range for the business.

• You can use values like $, $$, $$$, or a short range such as $50-$200.
• This gives users and search engines a general idea of pricing.

Street

Enter the street address of the business location.

• Add the street number and street name.
• This should match the address shown on the website and local listings.

City

Enter the city where the business is located.

• Use the official city name.
• Make sure it matches the visible address on the page.

Zip Code

Enter the postal or ZIP code for the business address.

• Use the correct code for the physical location.
• This helps complete the structured address.

Country

Enter the country where the business is located.

• Use the full country name or accepted country format.
• Keep it consistent with the business address.

State/Region

Enter the state, province, or region of the business location.

• This is useful for local and regional search.
• Make sure it matches the full address.

Latitude

Enter the latitude coordinate of the business location.

• This helps define the exact map location.
• Use the correct coordinate from Google Maps or another trusted map source.

Longitude

Enter the longitude coordinate of the business location.

• This works with latitude to identify the exact location.
• Make sure both coordinates point to the correct business address.

Open 24/7

Check this option if the business is open all day, every day.

• Use it only if the business is truly available 24 hours a day, 7 days a week.
• If the business has fixed hours, leave it unchecked and add opening hours instead.

Add Opening Hours

Use the Add Opening Hours button to add business hours.

• Add the days and times when the business is open.
• Use this instead of Open 24/7 when the business has a regular weekly schedule.

Social Profiles

Select the social media platforms connected to the business.

• Available options include Facebook, Twitter, Instagram, YouTube, LinkedIn, Pinterest, and others.
• Add only official business profiles that are active and relevant.

JSON-LD Preview

The preview panel shows the generated Local Business schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Local Business schema to a specific page, post, product, or custom post type.

Select Post Type

Choose the content type where the Local Business schema should be used.

• This may include pages, posts, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact page where this schema should appear.

• For most websites, this will be the contact page, homepage, or location page.
• Make sure the selected page contains the same business details entered in the schema.

Save or Publish

After completing the business details, save or publish the schema template.

• Once published, the Local Business schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

8. Organization Schema

The Organization Schema is used to describe a company, brand, agency, nonprofit, institution, or other organization. It helps search engines understand the organization’s name, website, logo, contact details, and social media profiles.

Use this schema on pages that represent the business or organization, such as the homepage, about page, contact page, or brand profile page.

Organization @type

Select the main organization type.

• The default option is Organization.
• Use this when the entity is a company, agency, brand, institution, or general organization.

More Specific @type

Enter a more specific organization type if needed.

• Use this field when the default organization type is too broad.
• For example, you may enter a more specific type, such as Corporation, EducationalOrganization, NGO, or another relevant Schema.org type.

Name

Enter the official organization name.

• Use the same name shown on the website and branding.
• Keep the spelling consistent with other online profiles and business listings.

Alternate Name

Enter another name the organization is known by.

• This can be a short name, abbreviation, old brand name, or commonly used variation.
• Leave it blank if the organization does not use an alternate name.

URL

Enter the main website URL of the organization.

• Use the full URL starting with https://.
• This is usually the homepage or main brand website.

Logo URL

Enter the direct URL of the organization’s logo.

• Use the official logo image.
• Make sure the image URL is public and accessible.

Add Contact

Use the Add Contact button to add contact details for the organization.

• Add contact information such as support, sales, billing, or customer service.
• Use this when the organization has specific contact points that users may need.

Social Profiles

Select the social media platforms connected to the organization.

• Available options include Facebook, Twitter, Instagram, YouTube, LinkedIn, Pinterest, and others.
• Add only official social profiles that belong to the organization.

JSON-LD Preview

The preview panel shows the generated Organization schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Organization schema to a specific post, page, product, or custom post type.

Select Post Type

Choose the content type where the Organization schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact page where the Organization schema should appear.

• Select the page that best represents the organization.
• Make sure the selected page contains organization-related information.

Save or Publish

After completing the organization details, save or publish the schema template.

• Once published, the Organization schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

9. Person Schema

The Person Schema is used to describe an individual person, such as an author, team member, employee, speaker, expert, instructor, or public profile. It helps search engines understand the person’s name, profile URL, photo, social profiles, job title, and company.

Use this schema on author pages, team member pages, profile pages, staff pages, or any page focused on a specific person.

Name

Enter the person’s full name.

• Use the same name shown on the page.
• Keep the spelling consistent with the person’s profile, author bio, and social profiles.

URL

Enter the person’s profile URL.

• This can be an author page, team member page, personal website, or public profile page.
• Use the full URL starting with https://.

Picture URL

Enter the direct URL of the person’s image.

• Use a clear profile photo.
• Make sure the image URL is public and accessible.

Social Profiles

Select the social media platforms connected to the person.

• Available options include Facebook, Twitter, Instagram, YouTube, LinkedIn, Pinterest, and others.
• Add only official profiles that belong to the person.

Job Title

Enter the person’s job title or professional role.

• Examples include SEO Specialist, WordPress Developer, Instructor, Founder, or Support Manager.
• This should match the role shown on the page.

Company

Enter the company or organization the person is associated with.

• Use the official company name.
• This helps connect the person with their workplace, brand, or organization.

JSON-LD Preview

The preview panel shows the generated Person schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Person schema to a specific post, page, product, or custom post type.

Select Post Type

Choose the content type where the Person schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact page where the schema should appear.

• Select the profile page, author page, team member page, or related content item.
• Make sure the selected page contains the same person’s details entered in the schema.

Save or Publish

After completing the person’s details, save or publish the schema template.

• Once published, the Person schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

10. Product (Simple) Schema

The Product (Simple) Schema is used for a basic product page with standard product details and simple offer information. It helps search engines understand the product name, image, brand, description, identifiers, price, ratings, and reviews.

Use this schema for simple products, digital products, downloads, plugins, services sold as products, or any product page that does not need complex variants.

Name

Enter the product name.

• Use the same product name shown on the page.
• Keep it clear and consistent with the product title.

Image URL

Enter the direct URL of the product image.

• This can be the product image, featured image, or product banner.
• Make sure the image URL is public and accessible.

Brand

Enter the product brand name.

• Use the official brand, company, or product line name.
• For example, if WooNinjas owns the product, the brand can be WooNinjas.

Product’s Description

Add a short description of the product.

• Explain what the product is and what it does.
• Keep it aligned with the visible product page content.

Identification Properties

Select the product identifiers you want to include.

• Available options include GTIN-8, GTIN-13, GTIN-14, MPN, and SKU.
• Use these only when you have real product identifier values. For most software products, SKU or MPN may be more relevant than GTIN.

Offer @type

Use this field to choose how the product offer should be defined.

• Select Offer when the product has one clear price, one product page URL, and one availability status.
• Select Aggregate Offer when the product has multiple offers, pricing options, sellers, plans, or price ranges.
• If no offer is needed, leave it set to None.

Offer

Choose Offer when the product has a single price or one main purchase option.

Use the related fields as follows:

• URL: Add the product page or purchase page URL.
• Currency: Select the currency used for the product price, such as USD.
• Price: Enter the current product price.
• Price Valid Until: Select the date until which the price is valid, if applicable.
• Availability: Select the product availability status, such as in stock, out of stock, preorder, or another available option.
• Item Condition: Select the product condition, such as new, used, refurbished, or another available option.

Aggregate Offer

Choose Aggregate Offer when the product has multiple offers or a price range.

Use the related fields as follows:

• URL: Add the main product page URL where users can view the available offers.
• Currency: Select the currency used for the prices.
• Price: Enter the lowest price or starting price for the product.
• High Price: Enter the highest available price for the product.
• Number of Offers: Enter the total number of available offers, plans, sellers, or pricing options.

This is useful for products with multiple pricing plans, different sellers, package options, or variable pricing.

URL

Enter the product page URL.

• Use the full URL starting with https://.
• This should be the page where users can view or buy the product.

Currency

Select the currency used for the product price.

• Choose the same currency shown on the product page.
• For example, select USD if the product price is shown in US dollars.

Price

Enter the product price.

• Use the current product price shown on the page.
• Make sure the price matches the selected currency.

Rating Value

Enter the average product rating.

• This is usually a number such as 4.5 or 5.
• Only use this if the product page shows real ratings.

# of Ratings

Enter the total number of ratings.

• This should match the number of ratings shown on the product page.
• Do not add fake or estimated rating counts.

Best Rating

Enter the highest possible rating value.

• For most rating systems, this is usually 5.
• Use the same scale that appears on the product page.

Worst Rating

Enter the lowest possible rating value.

• For most rating systems, this is usually 1.
• This helps define the full rating scale.

Add Review

Use the Add Review button to add review details.

• Add reviews only if the product page includes real customer reviews.
• Review information should match the visible review content on the page.

JSON-LD Preview

The preview panel shows the generated Product schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the output before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Product schema to a specific post, page, product, download, or custom post type.

• Once saved, the schema will be applied automatically to the selected content item.
• Choose the page where the product details are actually displayed.

Select Post Type

Choose the content type where the Product schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the correct post type first so the related content list can load.

Select Post/Page/Product

Choose the exact product page or content item where the schema should appear.

• Make sure the selected page contains the same product details entered in the schema.
• The schema should always match the visible product information.

Save or Publish

After completing the product details, save or publish the schema template.

• Once published, the Product schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

11. Product (Advanced) Schema

The Product (Advanced) Schema is used for products that need more detailed structured data, especially products with multiple pricing options, plans, packages, or aggregate offers. It helps search engines understand the product details, identifiers, ratings, price range, availability, and individual offer options.

Use this schema when a simple product schema is not enough, such as software products with multiple plans, plugins with annual/lifetime pricing, SaaS tools, product bundles, or products with different offer types.

Product Name

Enter the official product name.

• Use the same name shown on the product page.
• Keep it clear and consistent with the visible product title.

Description

Add a short product description.

• Explain what the product is and what it does.
• Keep the description aligned with the content shown on the product page.

@ID Global Identifier

Enter a unique URL or identifier for the product.

• This is usually the product page URL with a unique ID reference.
• It helps search engines identify the product as a specific entity.

Main Image URL

Enter the direct URL of the main product image.

• Use the product image, featured image, or main product banner.
• Make sure the image URL is public and accessible.

Canonical Product URL

Enter the main product page URL.

• Use the full product URL starting with https://.
• This should be the preferred page where users can view or purchase the product.

Brand

Enter the product brand name.

• Use the company, store, or product brand behind the product.
• For example, if the product belongs to WooNinjas, enter WooNinjas.

Category

Enter the product category.

• Use a relevant category such as SoftwareApplication, WordPress Plugin, Digital Product, or another suitable product category.
• Keep it accurate and related to the product type.

Rating Value

Enter the average rating for the product.

• Use the real rating shown on the product page, such as 4.7 or 5.
• Only add this if the product has visible ratings.

Review Count

Enter the total number of reviews or ratings.

• This should match the number shown on the product page.
• Do not add fake or estimated review numbers.

Select Identifiers

Choose the product identifiers you want to add.

• Available options include GTIN-8, GTIN-13, GTIN-14, MPN, and SKU.
• Use only the identifiers that actually apply to the product.

Low Price

Enter the lowest available product price.

• Use this when the product has multiple plans or pricing options.
• For example, if pricing starts at $79, enter 79.

High Price

Enter the highest available product price.

• Use this to show the top end of the product’s price range.
• For example, if the highest plan is $299, enter 299.

Currency

Select the currency used for the product pricing.

• Choose the same currency shown on the product page.
• For example, select US Dollar if the prices are listed in USD.

Offer Count

Enter the total number of available offers, plans, or pricing options.

• Use this for products with several pricing tiers.
• For example, if the product has Single, 5 Sites, and Unlimited plans, enter 3.

Availability

Select the current product availability.

• Use this to show whether the product is in stock, out of stock, available online, or another supported status.
• Choose the option that matches the product page.

Individual Offers

Use this section to add each product offer separately.

• Add each pricing plan, package, license type, or offer as its own item.
• This helps describe the available purchase options more clearly.

Offer Name

Enter the name of the individual offer.

• Use names such as Single – Annual, 5 Sites – Annual, Unlimited – Lifetime, or similar plan names.
• Keep the offer name consistent with the pricing table on the product page.

Price

Enter the price for the individual offer.

• Use the actual price shown for that offer.
• Make sure the price matches the selected currency.

Unit

Enter the pricing unit for the offer.

• Use values such as YEAR, MONTH, or LIFETIME, depending on how the product is sold.
• For example, use YEAR for annual license pricing.

Add Offer

Use the Add Offer button to add more individual offers.

• Add one offer for each plan or package available on the product page.
• Keep the offer list accurate and consistent with the visible pricing section.

Remove Offer

Use the remove option to delete an offer that is not needed.

• This is useful if an offer was added by mistake.
• It helps keep the schema clean and accurate.

JSON-LD Preview

The preview panel shows the generated Product Advanced schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Product Advanced schema to a specific post, page, product, download, or custom post type.

Select Post Type

Choose the content type where the schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact page where this schema should appear.

• Select the product page that contains the same details entered in the schema.
• Make sure the schema matches the visible product content and pricing.

Save or Publish

After completing the product details, aggregate offer information, and individual offers, save or publish the schema template.

• Once published, the Product Advanced schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

12. Recipe Schema

The Recipe Schema is used for recipe pages that include cooking instructions, ingredients, preparation details, nutrition information, images, videos, ratings, and reviews. It helps search engines understand the recipe content in a structured format.

Use this schema when the page contains a full recipe, including the recipe name, description, ingredients, cooking steps, timing, servings, and other food-related details.

Name

Enter the recipe name.

• Use the same recipe title shown on the page.
• Keep it clear and specific, such as Chocolate Cake, Chicken Alfredo Pasta, or Homemade Pizza Dough.

Recipe’s Description

Add a short description of the recipe.

• Explain what the recipe is and what users can expect.
• Keep it brief and aligned with the visible content on the recipe page.

Keywords

Enter keywords related to the recipe.

• Add terms such as the dish type, ingredients, flavor, or meal category.
• Example: cake, dessert, chocolate.

Image URL

Enter the direct URL of the recipe image.

• This can be the main recipe image, featured image, or food photo.
• Make sure the image URL is public and accessible.

Add Image

Use the Add Image button to add more recipe images.

• Add extra images if the recipe page includes multiple useful photos.
• Only include images that are related to the recipe.

Video: Content URL

Enter the direct URL of the recipe video file, if available.

• Use this when the video file is hosted directly.
• Leave it blank if there is no direct video file URL.

Video: Embed URL

Enter the embed URL of the recipe video.

• Use this for videos hosted on platforms like YouTube or Vimeo.
• This helps connect the recipe schema with the video tutorial.

Creator

Enter the name of the recipe creator.

• This can be the chef, author, website owner, or brand that created the recipe.
• Use the same name shown on the page.

Date Published

Select the date when the recipe was published.

• Use the original publish date of the recipe.
• This should match the date shown on the page if one is visible.

Preparation Time

Enter the preparation time in minutes.

• This is the time needed before cooking starts.
• For example, enter 15 if preparation takes 15 minutes.

Cooking Time

Enter the cooking time in minutes.

• This is the time needed to cook or bake the recipe.
• For example, enter 30 if cooking takes 30 minutes.

Category

Select the recipe category.

• Use the option that best describes the recipe type.
• This may include categories such as dessert, main course, appetizer, snack, or another available option.

Cuisine

Enter the cuisine type.

• Use a cuisine such as Italian, Mexican, Chinese, American, or another relevant cuisine.
• Leave it blank if the recipe does not belong to a specific cuisine.

Servings

Enter the number of servings the recipe makes.

• Use a clear value such as 4, 6, or 8 servings.
• This should match the serving size shown on the recipe page.

Add Ingredient

Use the Add Ingredient button to add recipe ingredients.

• Add each ingredient needed to make the recipe.
• Include ingredient names and quantities when available.

Nutrition: Serving Size

Enter the serving size used for the nutrition details.

• Example: 1 slice, 1 bowl, or 100g.
• This helps define what the nutrition values are based on.

Nutrition: Calories

Enter the calories per serving.

• Use the calorie value shown on the recipe page.
• Leave it blank if calorie information is not provided.

Nutrition: Fat

Enter the fat amount in grams.

• Use this field if the recipe includes nutrition details.
• Make sure the value matches the visible nutrition information.

Add Step

Use the Add Step button to add cooking instructions.

• Add each recipe step in the correct order.
• The steps should match the instructions shown on the page.

Rating Value

Enter the average recipe rating.

• Use the real rating shown on the page, such as 4.8 or 5.
• Do not add ratings unless they are visible on the recipe page.

# of Ratings

Enter the total number of ratings.

• This should match the rating count shown on the page.
• Avoid using estimated or fake rating numbers.

Best Rating

Enter the highest possible rating.

• For most rating systems, this is usually 5.
• Use the same rating scale shown on the page.

Worst Rating

Enter the lowest possible rating.

• For most rating systems, this is usually 1.
• This helps define the full rating range.

Add Review

Use the Add Review button to add recipe reviews.

• Add reviews only if the recipe page includes real user reviews.
• Review details should match the visible review content.

JSON-LD Preview

The preview panel shows the generated Recipe schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Recipe schema to a specific post, page, product, or custom post type.

Select Post Type

Choose the content type where the Recipe schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact recipe page where the schema should appear.

• Select the post or page that contains the same recipe details entered in the schema.
• Make sure the schema matches the visible recipe content.

Save or Publish

After completing the recipe details, ingredients, steps, nutrition, and ratings, save or publish the schema template.

• Once published, the Recipe schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

13. Video Schema

The Video Schema is used for pages that contain video content. It helps search engines understand the video name, description, upload date, duration, thumbnail, video file URL, embed URL, and timestamp behavior.

Use this schema when a page includes a tutorial, product demo, course video, webinar recording, review video, or any other video content.

Name

Enter the video title.

• Use the same title shown on the page.
• Keep it clear and specific, such as How to Set Up WooCommerce Bookings or LearnDash Quiz Tutorial.

Video’s Description

Add a short description of the video.

• Explain what the video covers.
• Keep it aligned with the visible video content on the page.

Upload Date

Select the date when the video was uploaded or published.

• Use the original publish date of the video.
• This should match the date shown on the page or video platform, if available.

Minutes

Enter the minute portion of the video duration.

• For example, if the video is 8 minutes and 30 seconds long, enter 8 here.
• Use the actual video length.

Seconds

Enter the seconds portion of the video duration.

• For example, if the video is 8 minutes and 30 seconds long, enter 30 here.
• This works with the minutes field to define the full video duration.

Thumbnail URL

Enter the direct URL of the video thumbnail image.

• Use the main video thumbnail or preview image.
• Make sure the thumbnail URL is public and accessible.

Add Image

Use the Add Image button to add another thumbnail image field.

• Use this if the video has more than one relevant thumbnail image.
• Only add images that represent the video content.

Content URL

Enter the direct link to the video file.

• Use this when the video file is hosted directly, such as an .mp4 file.
• Leave it blank if you only have an embedded video link.

Embed URL

Enter the video player or embed link.

• Use this for videos hosted on platforms like YouTube, Vimeo, or another video platform.
• This should point to the playable embedded version of the video.

SeekToAction Target URL

Enter the video timestamp URL pattern.

• Use this if the video page supports timestamp links.
• The placeholder format is usually similar to https://example.com/video?t=.
• This helps search engines understand how users can jump to specific points in the video.

JSON-LD Preview

The preview panel shows the generated Video schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the Video schema to a specific post, page, product, or custom post type.

Select Post Type

Choose the content type where the Video schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• Select the post type first so the related content list can load.

Select Post/Page/Product

Choose the exact page or post where this schema should appear.

• Select the content item that contains the video.
• Make sure the schema details match the visible video on that page.

Save or Publish

After completing the video details, save or publish the schema template.

• Once published, the Video schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

14. WebSite Schema

The WebSite Schema is used to describe the main website and its internal search feature. It helps search engines understand the website name, website URL, and how users can search content directly on the site.

Use this schema on the homepage or another main site-level page when the website has an internal search function.

Website’s Name

Enter the name of the website.

• Use the official site or brand name.
• Keep it consistent with the name shown on the website.

URL

Enter the main website URL.

• Use the full URL starting with https://.
• This is usually the homepage URL.

Internal Site Search URL

Enter the URL pattern used by the website’s internal search function.

• This is the search URL before the user’s query.
• For example: https://example.com/search?q=
• Make sure this URL matches how search works on your website.

Optional: String in the Search URL After the Query

Use this field if the search URL has extra text after the search term.

• Some websites add extra parameters after the query.
• Leave this field blank if the search URL ends directly after the search term.

JSON-LD Preview

The preview panel shows the generated WebSite schema code.

• As you complete the fields, the plugin automatically creates the JSON-LD markup.
• Review the preview before saving or publishing the schema template.

Apply Schema to Post/Page

Use this section to assign the WebSite schema to a specific post, page, product, or custom post type.

• Once saved, the schema will be applied automatically to the selected content item.
• This schema is usually applied to the homepage or main website page.

Select Post Type

Choose the content type where the WebSite schema should be used.

• This may include posts, pages, products, downloads, or other custom post types.
• For most websites, select Pages if the schema will be added to the homepage.

Select Post/Page/Product

Choose the exact page where this schema should appear.

• Select the homepage or the main page that represents the website.
• Make sure the website name, URL, and search URL match the actual website setup.

Save or Publish

After adding the website and search URL details, save or publish the schema template.

• Once published, the WebSite schema will be added automatically to the selected page.
• Test the page with Google’s Rich Results Test or Schema Markup Validator tool to confirm the markup is working correctly.

Validation Workflow

After creating a schema template, always validate the generated markup before relying on it on a live page. This helps catch missing fields, incorrect values, and schema formatting issues before search engines crawl the page.

1. Complete the schema form with the required and relevant field values.
2. Review the JSON-LD Preview to check for missing, incorrect, or incomplete values.
3. Click the Google icon to test the schema on Google’s Rich Results Test.
4. Click the code braces icon to validate the schema on Schema.org.
5. Review any errors or warnings shown by the testing tools, then update the schema fields where needed.
6. Save or publish the schema template.
7. After publishing, test the live page URL again to confirm the schema is correctly added to the selected post, page, product, or custom post type.

FAQs

Does this add-on write JSON-LD for me?

Yes. You fill in the form fields, and the add-on creates the JSON-LD output in the preview panel.

Can I use more than one schema template on the same page?

Yes, but only when each schema type has a real purpose and does not duplicate another schema source. Duplicate or conflicting markup can create validation issues.

Does this add-on guarantee Google rich results?

No. The add-on creates structured data. Google decides whether a page qualifies for rich results.

Can I test schema before saving?

Yes. Use the Google icon for Google Rich Results Test and the code braces icon for Schema.org Validator.

Can I copy the generated code?

Yes. Use the copy button to copy the full script tag.

Can I use this with WooCommerce products?

Yes. Use Product (Simple) or Product (Advanced). Check that another plugin is not already outputting product schema for the same product page.

Does automatic schema output work on archive pages?

No. The current output logic runs on singular content only.

Can non-admin users create schema templates?

The current AJAX save and lookup actions require manage_options, so administrator access is recommended.

Changelogs

1.0.0

• Initial Release.