Free Schema Markup Generator
Build valid LocalBusiness, Article, FAQPage, and Organization JSON-LD. FAQPage and Article are the highest-leverage signals for AI search citation in 2026.
LocalBusiness fields
JSON-LD output
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"address": {
"@type": "PostalAddress",
"addressCountry": "NO"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "09:00",
"closes": "17:00"
}
]
}Ready-to-paste <script> tag
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"address": {
"@type": "PostalAddress",
"addressCountry": "NO"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "09:00",
"closes": "17:00"
}
]
}
</script>Paste this inside the <head> of the page you are marking up. WordPress users: use a plugin like Rank Math or "Insert Headers and Footers".
Validate before deploying
Want to know if your schema actually helps AI search? Run the AI Search Readiness scan.
What each field turns into
The form writes JSON-LD as you type, and fields you leave empty are dropped from the output. Two are not empty when the page loads: country starts as NO, and opening hours start as 09:00 to 17:00, Monday to Friday. Both show up in the output before you type anything, so change them or clear them. A few other fields map less obviously than their labels suggest:
| You fill in | It becomes | Watch for |
|---|---|---|
| Business type | @type, for example Plumber or Restaurant | Pick the most specific type that is true. LocalBusiness is the fallback, not the goal |
| Street address, city, postal code | A nested PostalAddress object | Must match the address on the page and in your Google Business Profile, character for character |
| Country (ISO) | addressCountry | Two-letter code (US, GB, DE). Prefilled with NO |
| Opens and closes | openingHoursSpecification, Monday to Friday | Prefilled. Weekend hours need adding to the output by hand |
| Services, one per line | hasOfferCatalog with an entry per service | Keep the names identical to the services described on the page |
| Average rating, review count | aggregateRating, only when both are filled in | Only if the reviews are visible on the same page. Google also stopped showing review stars that a business marks up about itself (Google, 2019) |
| Social URLs | sameAs array | Profiles you control. This is how search engines tie the entity together |
Before you paste it
Run the output through Google's Rich Results Test and the Schema.org validator. The first tells you whether Google will use it for a rich result. The second tells you whether it is valid schema at all. They can disagree, because Google supports only part of the schema.org vocabulary.
After deploying, give the Rich Results Test your live URL instead of the code snippet. It renders the page, so it also finds markup that a JavaScript framework injects after load, and it lists every structured-data item it detected. Two items of different types (an Organization and an Article) are fine. Two LocalBusiness items usually mean a plugin and your theme both add one.
Plenty of sites have none at all. A May 2026 research scan by ismycodesafe (internal data) parsed the homepage HTML of 448 sites, after dropping failed fetches and bot-protection pages, and 299 of the 448 had no JSON-LD in the HTML.
A note on FAQPage
Since August 2023 Google shows FAQ rich results mainly for well-known government and health sites (Google Search Central). The markup is still read, and answer engines use it to understand question-and-answer content, but don't add it expecting expandable FAQs under your search result. The questions in the markup must be visible on the page. To check an existing page, use the FAQPage validator.
Which schema for which page?
LocalBusiness on contact pages and homepages of any service business with a physical location or service area. Use the most specific subtype (Plumber, HVACBusiness, etc.) when possible.
Article / BlogPosting on every blog post or editorial page. AI engines need author, datePublished, and dateModified to weight citation trust.
FAQPage on any page with a Q&A section.
Organization on the homepage and about page. Defines the entity behind the site for AI search engines that build entity graphs.
Claude AI helped me with phrasing and proofreading in this article.