` and meta tags: ```blade <head> <title>{{ $title }}

--- title: Structured Data description: JSON-LD script block emitter (XSS-safe via JSON_HEX_TAG) visibility: guest draft: false --- # Structured Data Emit safe, valid JSON-LD (` ``` ## Schema Examples ### Article schema ```blade ``` Rendered output: ```html ``` ### Organization schema with social profiles ```blade ``` Rendered output: ```html ``` ## Security Every string value is encoded with `JSON_HEX_TAG`, which converts `<` and `>` into `<` and `>`. This means a user-controlled value containing `` cannot break out of the JSON-LD block — a real XSS vector that hand-rolled `@json()` does NOT defend against. The component also passes `JSON_UNESCAPED_SLASHES` (URLs stay readable: `https://example.com` instead of `https:\/\/example.com`) and `JSON_UNESCAPED_UNICODE` (native characters: `Café` instead of `Café`). Slashes are safe because `JSON_HEX_TAG` already neutralizes the `<` that would be needed for tag injection. ## Pairing with Page Layouts Mount one or more structured-data blocks in your layout's `` — typically alongside the `` and meta tags: ```blade <head> <title>{{ $title }}

``` ## Validation Test your output with [Google's Rich Results Test](https://search.google.com/test/rich-results) or [Schema.org Validator](https://validator.schema.org/) — paste the rendered URL and confirm the JSON-LD is detected with no errors. ## Typed builders `Schema` is a set of **typed JSON-LD builders for your app** — you call them directly, wherever the data lives. (One of them, `faqPage`, can additionally be fed by the [faq](/components/faq) component; that is a convenience on top, not what the builders are for.) Hand-writing schema.org arrays is where rich results go to die: a price with a currency symbol, an availability written as a bare word, a rating with no count. The `Schema` builders encode those rules once. ```php use Pushery\WireKit\Schema\Schema; ``` ```blade {{-- 1. Fragments nest — the context is stamped once, at the top --}} ``` | Builder | Emits | | --- | --- | | `Schema::product(...)` | `Product` — nests `offers`, `aggregateRating`, `review` | | `Schema::offer(...)` | `Offer` — price as a bare string, availability expanded to its URL | | `Schema::aggregateRating(...)` | `AggregateRating` — `reviewCount` is required for a rich result | | `Schema::review(...)` | `Review` — nests the author and the rating | | `Schema::faqPage(...)` | `FAQPage` — from a `question => answer` map or a list of rows | | `Schema::article(...)` | `Article` | | `Schema::breadcrumbList(...)` | `BreadcrumbList` — positions numbered for you | | `Schema::webSite(...)` | `WebSite` — the site itself | | `Schema::organization(...)` | `Organization` — who is behind it, with `sameAs` profiles | | `Schema::softwareApplication(...)` | `SoftwareApplication` — a library, app or SaaS product | | `Schema::node(...)` | **Any** schema.org type, unmodeled | | `Schema::graph(...)` | Combines several nodes into one `@graph` | Every builder takes an `extra:` array for properties it does not model — and those **override** the modeled ones, so you are never boxed in. ### Describing the site itself A marketing page usually describes more than one thing: the site, the organization behind it, and the product it offers. `graph()` combines them into one connected document instead of a pile of separate scripts, and `@id` lets the nodes reference each other: ```blade ``` The context is stamped once at the top of the `@graph`, never on the individual nodes. ### Any other type `node()` is the escape hatch: it builds any schema.org type with the same null-pruning and the same `@type`-first shape, so you never have to wait for a builder to exist. ```blade ``` ### What the builders fix for you - **Price is a string, with no symbol and no separator.** `price: 49.9` emits `"49.9"` — `"€49,90"` is the single most common reason a Product rich result is rejected. - **Availability is a URL, not a word.** `availability: 'InStock'` emits `https://schema.org/InStock`. Passing the full URL also works. - **Null properties are dropped.** An empty key is worse than a missing one. - **The context is stamped exactly once**, at the top level — so nesting an Offer inside a Product needs no context-stripping. ::: warning **Only describe what the page actually shows.** Structured data that claims content the visitor cannot see is a Google policy violation and gets the rich result withdrawn — permanently, for the whole site in bad cases. Emit an `FAQPage` only where the questions are really rendered, an `AggregateRating` only where the rating really is on screen. ::: ## Props | Prop | Type | Default | Description | | --- | --- | --- | --- | | `data` | `array` | `[]` | Associative array serialized to JSON-LD. Nested arrays and objects are supported. | ## Keyboard Interaction This component is purely presentational and does not respond to keyboard input. ## See Also - [Schema.org](https://schema.org) — full type catalog - [Google Search Central — Structured Data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data)