Add Five Structured Data Types to Boost Your Small Site

Organization schema, tell the world who you are

Organization markup tells machines the legal name of the business, the web address, a logo URL, and basic contact points. When the data is present, assistants can match a query about the company to a concise profile and may display a knowledge panel. The markup also helps crawlers separate the brand from unrelated sites that mention the same name. Use JSON-LD in a script tag to keep the HTML clean.

To add the markup, place a script element in the head of each page that represents the business. Include at least the @type, name, url, and logo fields. Optional fields such as contactPoint, sameAs, and address give extra context but are not required for basic visibility. After publishing, run the page through a structured-data testing tool to see if the fields are recognized.

• @type, name, url, logo are required
• Add contactPoint or sameAs for richer data
• Validate with a testing tool

WebSite schema, define the site as a whole

WebSite markup defines the whole domain as a single entity. It includes the site name, the primary URL, and optionally a searchAction that describes how a user-entered query can be sent to the internal search endpoint. This signals to assistants that the site can answer questions directly, and it may enable a quick-search box in some AI chat interfaces. The markup is lightweight and does not interfere with page content.

Add the JSON-LD block to the home page, because that is the page most crawlers start from. Required fields are @type, name, and url; you can also add potentialAction with target and query-input to describe the search URL pattern. Test the page with a validator that shows the detected WebSite object and any warnings about missing fields.

• Place on the home page
• Include @type, name, url
• Add potentialAction for site search

Article schema, make each post easy to quote

Article markup tells machines that a page holds a news story, blog post, or similar piece of content. The key properties are headline, author, datePublished, image, and mainEntityOfPage. When present, assistants can pull the headline and author name into a generated answer, and they can cite the exact URL as the source. The markup also helps search features highlight the article in a carousel or a top-stories list.

To implement, insert a JSON-LD script on each article page. Fill in the headline exactly as it appears on the page, use the author’s full name, and provide an ISO-8601 date for publication. If an image is shown, add its absolute URL and set the width and height if possible. After publishing, run the URL through a structured-data tester to confirm the Article object is recognized.

• Add headline, author, datePublished
• Provide image URL with dimensions
• Validate the Article object

FAQPage schema, let assistants answer directly

FAQPage markup lets you list question and answer pairs in a format that assistants can read directly. Each entry contains a question field and an answer field, both as plain text. When the markup is detected, the assistant may quote the answer without opening the page, and the source is shown as a citation. This can increase visibility for common queries that match your expertise.

Add the markup to a dedicated FAQ page or to any page that already contains a list of questions. Use a JSON-LD array under the @type FAQPage, with each item set to @type Question and its acceptedAnswer set to @type Answer. Test the page with a validator that lists each question and answer and flags missing required fields.

• Create an array of Question items
• Each question needs an acceptedAnswer
• Validate all Q&A pairs

BreadcrumbList schema, show navigation path

BreadcrumbList markup describes the path a visitor takes to reach a page, using a list of items with position, name, and URL. Machines use this to understand the hierarchy of the site and can include the breadcrumb trail in a generated answer. The markup also helps search results show a navigation trail, which can improve click-through rates.

Implement by adding a JSON-LD script on each page, preferably near the top of the HTML. Include the @type BreadcrumbList and an itemListElement array where each element has @type ListItem, position, name, and item (the page URL). After publishing, verify with a structured-data testing tool that the breadcrumb items appear in the correct order and that no required field is missing.

• Add @type BreadcrumbList
• List each step with position, name, item
• Check order with a testing tool

Questions people ask

Do I need to add all five types to every page?

No. Add Organization markup to every page that represents your brand, WebSite to the home page, Article to each content page, FAQPage to pages that contain question lists, and BreadcrumbList to pages where a navigation path is useful. Adding only the relevant types keeps the HTML tidy and still gives machines the signals they need.

How can I verify that my markup is being read correctly?

Use a free structured-data testing tool. Paste the page URL or the raw HTML, and the tool will show each detected schema type and any missing required fields. Look for green check marks or messages that confirm the object is recognized. Run the test after each change to be sure the markup stays valid.

What if a search engine or AI assistant does not show my data?

The markup is only a hint. If the content is thin, duplicated, or not relevant to the query, the assistant may ignore it. Keep the underlying page useful, up-to-date and clearly written. You can also experiment by tweaking field values or adding optional details, then re-test to see if the hint improves visibility.