Organisation
The identity behind the website
Gather the business name, website URL and any existing entity @id. Add official profiles and logo details only when they identify the same organisation.
Build from facts
Give your content a clear structure.
Turn verified page details into JSON-LD. Choose a supported template, enter the facts and prepare markup you can review before adding it to your site.
Build your markup
Schema Markup Generator
Choose the type that matches your content.
Build Organisation, LocalBusiness, Article or Breadcrumb markup. Fields stay in this browser tab. The generator produces code; it does not install it or change your website.
02 / Review your markup
Review what you’re describing.
Choose a type and enter the facts shown on your page.
Your implementation code
How to add and check your markup
Check whether your SEO plugin already defines this entity. Extend its graph or reuse its @id rather than publishing duplicate or conflicting markup. Use the script-block format when adding JSON-LD to HTML, or JSON-only when your integration expects JSON.
Copy JSON-LD only, then choose Paste JSON-LD in the Schema Viewer & Validator. Check the final page with the Schema.org validator and any relevant Google rich-result test before publishing. This tool does not install markup on your site.
Put it to work
Start with what the page actually describes.
Choose the closest supported starting point. These templates cover useful basics, not every subtype or search-feature requirement.
Local business
A real business location
Prepare the public address and country code. This starter uses the general LocalBusiness type; a more specific subtype may suit the final implementation.
Article
A published piece of content
Use the visible headline, credited author, actual publication date and publisher. Reuse the publisher’s existing organisation ID where available.
Breadcrumb
The visible route to this page
Enter two to ten items in order, from the broadest page to the current one. Labels and URLs should reflect the page’s navigation trail.
From code to website
A short implementation handoff.
Generating the code is one step. Keep these decisions with it so the person implementing it knows where it belongs.
Page facts
Use the names, dates and URLs supported by the page.
Do not fill gaps with invented addresses, authors or claims.
Existing output
Check the theme and SEO plugin before adding code.
Extend or connect the existing graph where possible, rather than introducing competing identities.
Output format
Choose JSON-only or an HTML script block.
Use the format your integration expects. JSON pasted into a page’s visible content is not the same as installing structured data.
Final verification
Inspect the rendered page after implementation.
Check the resulting markup, not only the generated file. Templates or plugins may alter what is published.
The builder’s required fields are its minimum inputs. They are not a complete checklist for Google eligibility, and generating code does not guarantee a rich result.
Before you move on
Keep the markup accurate as the page changes.
Validate before publishing
Inspect the generated JSON-LD, then use broader vocabulary and relevant search-feature tests.
Keep one clear source of truth
Record which integration owns the entity and its stable ID so future edits do not create conflicting copies.
Update facts when the content changes
Review names, URLs, dates and navigation when the page is edited. Structured data needs the same care as the visible content.
Your questions
Before you add the code.
Will this add the markup to my WordPress site?
No. You can copy or download the output, then implement it through the appropriate template, plugin or integration. Check existing output before adding a new block.
Does this support Product, FAQ or every schema type?
This builder currently supports Organisation, LocalBusiness, Article and Breadcrumb. Other types need a different implementation; choosing an unrelated template will not describe your page correctly.
Are my entries stored or sent to AI?
This generator builds its output in your browser tab. It does not upload or save your entries, and it does not call AI. Reloading clears the input.
Does a generated result qualify for a rich result?
No. The final page must be assessed against the requirements for the relevant search feature. A generated snippet is a starting point, not an eligibility decision.
Need the markup built into your templates?
We can help connect structured data to the content you already manage, so the website and its markup stay consistent as your business changes.
Send an enquiry