BYTETOOLS

JSON-LD Use Cases: Which Schema for Which Page

Reach for JSON-LD whenever a page represents a real-world thing a search engine could feature β€” a local business, an event, a recipe, a person, or your site itself β€” and you want it eligible for the matching rich result. The trick is matching the right schema type to the right page. Here are the concrete scenarios where each type earns its place, drawn from the six the generator covers: WebSite, WebPage, LocalBusiness, Person, Event and Recipe.

Local business: the storefront that wants a knowledge panel

A neighborhood dental clinic wants its name, address, phone and opening hours to appear in a business knowledge panel and on maps. LocalBusiness schema on the contact or homepage supplies exactly that structured detail. The worked flow: pick LocalBusiness, fill in the practice name, full address, phone and hours, and paste the generated block into the page head. Because the same details are visible on the page, the markup is compliant and eligible for the local rich treatment.

Events: a workshop that wants a date card

A studio running a weekend photography workshop wants its listing to show a date-and-location card in search. Event schema β€” with name, start and end datetimes in ISO 8601, and venue β€” makes the page eligible for event rich results and inclusion in Google's event experiences. This is the go-to for concerts, webinars, classes and conferences.

Recipes, authors and site search

PageSchema typeRich result it unlocks
A cooking blog postRecipeRecipe card with image and time
An author or founder bioPersonEntity understanding, knowledge graph
Your homepageWebSiteSitelinks search box
A key landing pageWebPageClearer page understanding

A food blogger marking up a soup recipe fills in the Recipe fields so search can show a card with cook time. A consultancy adds Person schema to its founder's bio so search engines connect the name to the brand. A publisher adds WebSite schema so Google can offer a sitelinks search box straight from the results.

Worked example: a multi-entity page

Consider an event page on a venue's site. It is simultaneously a WebPage, sits under a breadcrumb trail, and describes an Event. The practical approach is to generate the Event block here, then add BreadcrumbList separately, and let the WebPage context tie them together. One page, several focused JSON-LD blocks β€” each describing something genuinely on the page. For the Article, FAQ, Product, Organization and Breadcrumb types, dedicated ByteTools generators handle those specific jobs.

Try the JSON-LD Generator β€” free and 100% in your browser.

Frequently asked questions

Which schema type should a homepage use?

WebSite is the common choice β€” it can enable a sitelinks search box. Many sites also add Organization or LocalBusiness on the homepage to define the brand or business entity behind the site.

Can one page use more than one of these types?

Yes. A page can legitimately be a WebPage that also describes an Event or a Person. Generate each block separately, keep every block focused on one entity, and include only what the page actually shows.

When is Person schema worth adding?

Use it on author bios, founder pages and profile pages where identifying the individual helps search engines connect that person to your organization and content. It supports entity understanding rather than a flashy card.

Do I need Recipe schema for a general food article?

Only if the page contains an actual recipe with ingredients and steps. Recipe schema on a page without a recipe violates the guidelines. For a general article, use the Article schema generator instead.

Related free tools

Built by ByteVancer

ByteTools is a free product of ByteVancer, a software and web development studio building web apps, SaaS and custom software. If you want structured data engineered into every template of your site, explore how ByteVancer can build SEO-ready platforms for you.