> For the complete documentation index, see [llms.txt](https://attr.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attr.sygnal.com/sa5-seo/json-ld/article-1.md).

# JSON-LD Video ❺🧪

{% hint style="danger" %}
**EXPERIMENTAL ALPHA** ⑤

DO NOT USE this in production code, as it may be removed. We'll see if this approach works. Testing with Google is in progress.&#x20;

**STATUS**

Testing Google response to our script generated JSON-LD.&#x20;
{% endhint %}

## Overview <a href="#display-captions-in-webflows-lightboxes" id="display-captions-in-webflows-lightboxes"></a>

Focusing in on the `VideoObject` schema.&#x20;

{% embed url="<https://developers.google.com/search/docs/appearance/structured-data/video>" %}

## Variants

* Article
* NewsArticle
* BlogPosting

<https://developers.google.com/search/docs/appearance/structured-data/article>

## Usage Notes <a href="#usage-notes" id="usage-notes"></a>

Place this code in your site or page level **/body** code.

{% code overflow="wrap" %}

```html
<script>
var article = new window.sa5.LdJsonArticle();
article.headline = `Article headline`;
article.addAuthor (`Bob Hershel`);
article.publisher = `Sygnal`;
article.generate();
</script>
```

{% endcode %}

### .headline

### .addAuthor()

### .publisher

### .generate()

Renders the JSON-LD as a script element and appends it to the `<body>`.&#x20;

{% hint style="success" %}
The build script can be split into multiple parts so that they can execute in the most appropriate locations on the page. For example, if you have a list of content that is generated from a Collection List, part of the script can separately assemble that part.&#x20;
{% endhint %}

## References

{% embed url="<https://developers.google.com/search/docs/appearance/structured-data/video>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://attr.sygnal.com/sa5-seo/json-ld/article-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
