What Schema Markup Generator Does
Schema Markup Generator adds structured data to a specific page or funnel step. Structured data helps search engines and AI systems identify important page information, such as:
Business details.
Products or services.
Articles or blog posts.
FAQs.
Events.
Reviews.
Organization information.
Schema is page-specific. Adding schema to one page does not add it to other website pages or funnel steps.
Key Benefits of Schema Markup Generator
Schema Markup Generator helps you create structured data without needing to write code. Key benefits include:
140+ schema types for common page types and business needs.
Form View for guided, no-code schema setup.
JSON View for advanced JSON-LD editing.
Built-in validation before saving.
Multiple schemas per page when a page needs more than one schema type.
Publish control so schema goes live only after the page or funnel step is published.
How to Open a Website or Funnel Page
Go to Sites.
Click Websites or Funnels.
Choose the website or funnel you want to update.
How to Create or Edit a Website
To create a new website, click + New Website. To edit an existing website, click the three-dot menu beside the website and select Edit.
How to Open the Page Editor
Open the website or funnel.
Select the page or funnel step you want to optimize.
Click Edit.
How to Open Schema Markup Settings
Inside the page editor:
Click the SEO & AI search optimization icon in the top toolbar.
In the left panel, open Schema markup.
How to Add a New Schema
In the Schema markup section, click + New Schema.
Select Add Schema.
How to Start Schema Setup
In the Add Schema Markup window, click + Add Schema.
How to Choose a Schema Type
Use the schema type dropdown to select the schema that matches the visible page content. Common options include:
Organization.
Local Business.
Article.
Product.
Event.
How To.
FAQ Page.
Q&A Page.
Website.
Form View vs JSON View
Use Form View when you want a guided no-code setup. Use JSON View when you want to paste or edit JSON-LD directly.
How to Complete Schema Details
After selecting a schema type, fill out the required and recommended fields. Use information that appears on the page. Do not add fake, hidden, or misleading details.
How to Validate and Save Schema
Click Validate & Save after entering schema details. If validation fails, fix the highlighted fields or JSON formatting issues before saving.
Required Fields and Validation Errors
Some schema types require specific fields. For example, a local business schema may require address details such as city, state or region, ZIP code, and country.
How to Publish Schema
Saving schema stores it on the page. To make schema live, click Save and then Publish in the page editor.
Using Form View and JSON View
Form View and JSON View are available from the schema editor. Use Form View for guided fields. Use JSON View when you need direct control over the schema code.
Supported Schema Types
Schema Markup Generator supports many schema types, including:
Organization.
Website.
BreadcrumbList.
Article.
BlogPosting.
FAQPage.
QAPage.
HowTo.
VideoObject.
Person.
Product.
LocalBusiness.
Event.
Offer.
Review.
AggregateRating.
Recipe.
ImageObject.
Service.
Course.
Child schema types may also be available under broader categories.
Best Practices
Use the schema only for information that is visible on the page. Choose the most specific schema type available. Keep the schema updated when business hours, pricing, address, contact details, products, or services change. Add schema to important pages such as the homepage, contact page, service pages, product pages, blog posts, and FAQ pages. Use multiple schemas on the same page only when each schema accurately matches the page content.
Most Useful Schema Types for Local Businesses
Local Business is useful for businesses with a physical location or service area. The product is useful for items sold on the page. Service is useful for service pages. Review is useful for real customer reviews that are visible on the page. FAQ Page is useful when the page includes visible questions and answers. Event is useful for workshops, classes, sales events, or scheduled sessions.
Good to Know
Schema is page-specific. The schema does not automatically carry over to other pages or funnel steps. The schema may appear in the editor or preview after saving, but it is only live after publishing. The schema is not automatically added just because a page was created with AI.
Common Issues and Fixes
Validation fails
Review the highlighted fields and complete any missing required details. For JSON View, check that the JSON-LD formatting is valid.
The schema is saved but not visible on the live page
Publish the page or funnel step after saving the schema.
The wrong schema type was selected
Edit the schema and choose a type that matches the visible page content.
A schema field does not apply to the page
Leave optional fields blank when they do not apply. Do not add inaccurate information just to complete a field.
FAQ
Do I need technical knowledge to use Schema Markup Generator?
No. Form View is designed for no-code schema setup.
When should I use JSON View?
Use JSON View when you want to paste or directly edit JSON-LD.
How does schema selection differ between manual setup and AI-generated schema?
Manual setup uses the schema types available in the dropdown. An AI-generated schema can create any valid schema type based on the page content.
Can AI generate schema types that are not available in the manual list?
Yes. AI can generate valid schema types that may not appear in the manual schema list.
Where does the schema get published on my page?
The schema is published as JSON-LD when the page or funnel step is published.
Why do I see schema in preview but not on the live page?
Saving stores the schema, but publishing makes it live.
Can I add more than one schema type to a single page?
Yes. You can add and manage multiple schemas on one page.
Can I paste the schema from another tool?
Yes. Use JSON View to paste JSON-LD, then click Validate & Save.
What does the Validate & Save check?
Validate & Save checks for missing required fields, incorrect fields, and formatting issues.
Should the schema match what is visible on the page?
Yes. The schema should only describe real content that visitors can see on the page.













