How this tool works
Serializes supplied fields into JSON-LD using schema.org types. It emits syntax for editing and validation, not a Google eligibility verdict.
How to use it
- Choose the type that matches the actual page or organization.
- Enter verified names, URLs, dates, and image details.
- Compare the markup with visible content and validate it before publishing.
Limits to keep in mind
Correct syntax does not guarantee rich results. Google requires applicable content and guidelines; this tool does not validate facts or eligibility.
Frequently asked questions
Will schema markup improve rankings?
This tool makes no ranking prediction. Structured data helps describe page information and can enable eligible rich appearances.
Will Google show a rich result?
There is no guarantee, even when markup is correct and eligible.
Is JSON-LD the right format?
JSON-LD is the format Google recommends for structured data and is the one this tool produces. Place it on the page it describes and keep it consistent with visible content.
How do I check my markup after adding it?
Run the live URL through Google’s Rich Results Test and the Schema Markup Validator, then watch the enhancement reports in Search Console for errors.
What structured data describes
Structured data is a standard way of labeling the information on a page so that software can understand it. Instead of leaving a search engine to guess that a name is an author and a date is a publication date, you state it in a defined vocabulary from schema.org. The format most search engines recommend is JSON-LD, a block of script that sits on the page without changing how it looks.
The Article and Organization Schema Generator turns the details you enter into a JSON-LD block. For an article, those details are the headline, address, dates, image and author. For an organization, they describe the business, such as its name, website and logo. The output is syntax for you to review and validate. The tool does not look at your page, and it does not judge whether you qualify for any special search appearance.
Select an accurate type
Choose the type that matches the real page. Use Article, or one of its more specific forms, for a news story, blog post or guide that has an author and a date. Use Organization for information about a company, brand or publisher, typically on the homepage or an about page, not repeated on every page unless it makes sense for your site.
Do not use a type just because it seems to attract rich results. Marking an ordinary page as something it is not can violate structured data guidelines and may lead to a manual action that removes eligibility for enhanced features. Ask a simple question: if a visitor read this page, would they agree with every statement in the markup? If the answer is no, the markup needs to change, not the page.
Use visible and correct properties
Every property should match something a user can see on the page, or accurately describe the page or site. The headline should match the visible title, the author should be the real author shown on the page, and the dates should be the true publication and update dates in a consistent format. Use absolute URLs for the page address, images and logos.
Google recommends including useful properties such as headline, image, author, date published and date modified for articles, and clear identifying properties for organizations such as name, URL and logo. Images should be crawlable and in a supported format. Avoid filling fields with keywords or invented information. Accurate, modest markup is more valuable than a long block of properties that do not reflect the page.
Install the JSON-LD on your page
Copy the generated block, which begins with a script tag of type application/ld+json, and paste it into the head or the body of the page it describes. Many content management systems have a field for custom code in the head, and SEO plugins often manage structured data on their own. If a plugin already outputs Article or Organization markup, do not add a second copy, because duplicate or conflicting markup creates confusion.
Place Organization markup on the page that best represents the business, usually the homepage, and connect article markup to it through the publisher or author fields where that makes sense. Keep the markup in step with the page. If you change an author name or update the article, update the structured data too. Out-of-date markup is a common source of warnings in reports.
Validate before and after publishing
Test the generated code with Google's Rich Results Test, which shows whether the page contains markup that is eligible for supported search features, and with the Schema Markup Validator, which checks general schema.org syntax. Both can test a code snippet before it goes live and a public URL after publishing.
Fix errors first, because they can prevent a feature from working at all. Warnings often point to recommended but optional properties, which you can add if you have accurate information. After publishing, watch the enhancements and structured data reports in Google Search Console, where problems found across many pages are grouped together. Remember that passing a test shows the code is valid, not that Google will use it.
Understand eligibility and limits
Correct markup does not guarantee a rich result or a ranking improvement. Google decides whether to show enhanced features based on content quality, relevance and its own policies, and the set of supported features changes over time. Some types that were once common no longer produce visible enhancements for most sites.
This tool outputs syntax. It does not validate facts, check that your image URL loads, confirm that dates are accurate, or know whether your site is eligible for any feature. Use structured data to help search engines understand your content, not as a shortcut. Pages with clear, helpful content and honest markup are in the best position to benefit from whatever features are available.
Maintain markup over time
Structured data is part of your site's maintenance. Review it when you redesign a site, change authors, rename your brand, replace a logo, or move to a new domain. A logo URL that returns an error, or an organization name that no longer matches the site, is easy to miss unless you check.
Keep a short record of where each block comes from, whether a plugin, a template, or a manual snippet, so that changes do not create duplicates. Use the Search Console reports as an early warning, and retest key pages after theme or plugin updates. A small amount of regular checking keeps structured data accurate and avoids the problems that come from outdated markup.
More SEO Tools · Browse the tools catalogue