Search Results

By definition, every LocalBusiness is also an Organization, and every LegalService is also a LocalBusiness. Schema.org types inherit all their parent types: LocalBusiness: Thing > Organization > Loc …

You have to provide multiple MortgageLoan items. Why? Even if multiple interestRate values would represent alternatives (which, probably, isn’t the case), there is no way to convey which interestRate …

The error in the SDTT The property name (author) in the error line is not indented, i.e., not on the same level as the AggregateRating properties like ratingValue, ratingCount etc. That is a signal …

Schema.org uses content negotiation to provide the JSON-LD context file. If you request http://schema.org while sending the request header that you accept/prefer application/ld+json, this is what hap …

JSON-LD is just the syntax. The semantics come from a vocabulary (or multiple vocabularies), which defines the properties and types you can make use of in JSON-LD. You are using the Product type fro …

You need to have regular breadcrumbs in your HTML. To make them machine-readable, you either add attributes to this HTML (using Microdata or RDFa) or you add an invisible data block that duplicates th …

Google’s documentation for subscription and paywalled content doesn’t mention that files are supported. If files are supported, I would expect the following to work (based on the documentation for th …

Theoretically, it’s sufficient to specify only the @id: "author": {"@id": "http://example.com/about/#bob"} If a consumer already knows the entity with this @id URI (e.g., after having crawled the " …

Same @id? If items have the same @id, they are the same. These two snippets are semantically equivalent: [ { "@context": "http://schema.org", "@type": "Organization", "@id": "https://e …

This is the correct use of referencing entities via their URI in @id. It doesn’t matter what the URI’s domain is. It doesn’t even have to be a resolvable URI, not even a HTTP(S) URI -- but it’s the be …

The organization is neither named "Company Brand Page", nor is its URL /pages/brands. These property values apply to the page, not to the organization. Schema.org provides the WebPage type. For cate …

You open two brackets without closing them, and they aren’t needed in the first place, so you have to remove them: } ] These are between the two Hotel nodes: between the ] (from amenityFeature) an …

I never came across a case where the SDTT only fetches the head. My guess would be that something was off about one of the servers (yours or Google’s). While Google Search supports JSON-LD added via …

It should be fine to use different syntaxes on the same page. It has one drawback, though: If you want to connect entities specified in different syntaxes, you can’t nest them. You have to use URIs i …

The third ListItem and the Product have the same URI (in @id).¹ This means they are the same thing. If the structure allows it (like in your case), Google’s SDTT displays an item only once, even if i …