Schema Markup Generator

Pick a type, fill in the form and copy valid JSON-LD. Required and recommended properties follow Google's structured data documentation, checked in October 2026, and the checks tell you what is missing.

Properties: LocalBusiness

Loading the form...

JSON-LD

Checks

    Your entries stay in this browser only. Nothing is sent to a server.

    What schema markup does

    Schema markup is a block of structured data that tells search engines what a page is about in a format they do not have to guess: this is a coffee shop at this address, open these hours; this is a product that costs this much and is in stock. Google uses it to show rich results, like prices and stars under a product or a breadcrumb path instead of a URL, and to understand entities for the knowledge panel. Markup does not raise rankings by itself. It makes a result eligible for a richer display, and it removes ambiguity.

    Which types still get rich results in 2026

    Google has been retiring rich result types for three years. Before you spend time on markup, check that the type still does something in Google Search. This is the state of the types in this generator, from the Search Central structured data gallery and its changelog, checked in October 2026:

    TypeGoogle rich resultRequired by Google
    LocalBusinessYes, business details in the knowledge panelname, address
    OrganizationYes, logo and company detailsNone, all recommended
    Person (ProfilePage)Used for profile pages, no Person result on its ownmainEntity with name
    Article, BlogPosting, NewsArticleYes, better title, image and date in resultsNone, all recommended
    ProductYes, price, availability and ratingname, plus one of offers, aggregateRating, review
    BreadcrumbListYes, breadcrumb path in the resultitemListElement with at least 2 items
    EventYes, for events at a physical place (Event documentation)name, startDate, location with address
    VideoObjectYes, video results and key momentsname, thumbnailUrl, uploadDate
    WebSiteSite name only. Sitelinks search box removed starting November 21, 2024name, url (home page only)
    FAQPageNo. Not shown starting May 7, 2026Documentation removed in June 2026
    HowToNo. Not shown on desktop since September 13, 2023, on mobile since August 2023Documentation removed

    Required versus recommended properties

    Required properties decide whether a page is eligible at all. Leave one out and the Rich Results Test reports an error and the result will not show. Recommended properties do not block eligibility, but they decide how much Google can show. A LocalBusiness with only a name and address is valid. One with hours, phone, coordinates and price range is the one that answers the searcher's question. Fill every recommended property that is true for the page and leave the rest empty. Never mark up something that is not visible to people on the page.

    How to add JSON-LD to your site

    Copy the code with the script tag and paste it into the HTML of the page it describes, in the head or anywhere in the body. In WordPress, use a header and footer code plugin or the custom code field your theme or SEO plugin provides, and check that the plugin is not already printing the same type, because two conflicting Organization blocks are a common mistake. In Google Tag Manager, a Custom HTML tag works, but Google has to render JavaScript to see it, so putting it in the HTML is more reliable. Then run the page through the Rich Results Test and watch the Enhancements reports in Search Console over the next weeks.

    Mistakes I see most in audits

    • Ratings nobody can see. Product stars in the markup with no reviews on the page. Google calls this out in its guidelines, and it can lead to a manual action.
    • Self-serving reviews. A business marking up reviews of itself on its own LocalBusiness or Organization page. Those are not eligible for review stars, even when they come from a review widget.
    • Relative URLs and missing time zones. Image and page URLs must be absolute. Dates without an offset are read in Googlebot's time zone, which can shift an event by a day.
    • Markup that disagrees with the page. A price, phone number or opening hours in the JSON-LD that differ from the visible text. Update both together.
    • Old types left running. FAQ and HowTo blocks still added by plugins on every page. They are harmless, but they no longer earn anything in Google Search.

    Test before you publish

    The Rich Results Test tells you whether Google can show a rich result for the code or URL and which properties are missing. The Schema Markup Validator checks the code against the full schema.org vocabulary, which is useful for types Google does not use. Paste the copied code into either one. The checks in this generator follow the same rules, so a page that passes here should pass there, but the test on the live URL is the one that counts.

    Questions people ask

    Is this schema markup generator free?
    Yes, with no sign-up and no limit. Everything runs in your browser, so the details you type are never sent to a server. They are kept in your browser so you can come back to them.
    Does schema markup improve rankings?
    Not directly. It makes a page eligible for rich results such as prices, stars and breadcrumbs, which can improve the click-through rate, and it helps Google understand which business or person a page is about.
    Does FAQ schema still work in 2026?
    Not in Google Search. Google stopped showing FAQ rich results on May 7, 2026 and removed the documentation in June 2026. The markup is still valid schema.org, so it does no harm, but it will not earn a rich result.
    Where do I put JSON-LD on the page?
    Anywhere in the HTML of the page it describes, in the head or the body. Google reads both. Put each type only on the page it is about: Organization and WebSite on the home page, Product on the product page.
    Why does the Rich Results Test show a warning when there is no error?
    Warnings are missing recommended properties. The page is still eligible. Fill them if the information is true and visible on the page, otherwise leave them out.