Build structured data for an Article, Organization, or BreadcrumbList. Describe visible page content with the fields the selected type needs.
How to use
Select the schema type and enter a JSON object. For Article, supply headline, author, and url. Copy the output into a structured data script.
Example
An Article input with a headline, author name, and full page URL creates an Article object with a Person author.
FAQ
Does valid output guarantee a rich result?
No. Required fields and URL syntax are checked, but eligibility and visible content still need review against Google's rules.
Related tools
A practical task
Select the type that describes the visible entity. An organization page needs organization facts, while an article needs its actual headline and author. Do not label a general landing page as a different entity merely to obtain more fields.
Another useful question
Where should the generated object go?
Place it in an appropriate structured data script in your page template. Keep it synchronized with visible names, authors, and URLs as the content changes.
Settings and formats
| Field | Values |
|---|---|
| Schema type | Article (Article); Organization (Organization); BreadcrumbList (BreadcrumbList) |
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Structured data | Structured data describes entities and facts in a machine readable format. It must match visible page content. A valid JSON document is not proof of eligibility for a search feature or a promise of richer display. |
| Strict JSON syntax | JSON needs double quotes around keys and string values. Objects use braces and arrays use square brackets. Comments and trailing commas belong to other formats, so remove them before treating a source as JSON. |
| Strings and values | The JSON string "12" differs from the number 12, and "false" differs from false. Type changes affect comparisons and imports. Keep identifiers as strings when their leading zeros or exact digits matter. |
| Syntax and schema | A document can be syntactically valid yet contain the wrong fields or types for an application. Syntax checks confirm the format; schema and business rules determine if the receiving system can use the data. |
| Visible FAQ content | A useful FAQ answers questions that remain after the main instructions. Keep answers specific and based on real facts. Adding FAQ markup does not compensate for an unanswered question or an inaccurate service policy. |
| Metadata and page content | A title and description should summarize the page a visitor will actually find. Search engines can choose other wording for a query. Clear, distinct summaries are more useful than repeating a keyword in every available field. |