# Improving onebox for our documentation pages

**URL:** <https://meta.discourse.org/t/improving-onebox-for-our-documentation-pages/185679>\
**Category:** Support\
**Created:** [April 5, 2021, 7:28pm UTC](https://meta.discourse.org/t/improving-onebox-for-our-documentation-pages/185679 "2021-04-05T19:28:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsha](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jsha/32/48894_2.png) [@jsha](https://meta.discourse.org/u/jsha)\
**Post date:** [April 5, 2021, 7:28pm UTC](https://meta.discourse.org/t/improving-onebox-for-our-documentation-pages/185679/1 "2021-04-05T19:28:03Z")

</div>

In the Let’s Encrypt forum we often link to documentation. I’d love to improve the experience. For instance, below is an example of the onebox that gets generated:

[![image](https://global.discourse-cdn.com/meta/original/3X/4/2/42d6835fdaf018feed1625c19909b07c4fe50aec.png)](https://letsencrypt.org/docs/account-id/)

In particular, I’d like to omit the “Last updated … See all Documentation” text. I know Google supports a [`data-nosnippet` HTML attribute](https://developers.google.com/search/docs/advanced/robots/robots_meta_tag) to inhibit snippeting of certain elements. Is there anything equivalent for Discourse’s onebox?

Also, I’d like to selectively inline a larger chunk of the page text, when the URL points to our own site ([letsencrypt.org](http://letsencrypt.org)). Is that possible?

Thanks,  
Jacob

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [April 5, 2021, 7:54pm UTC](https://meta.discourse.org/t/improving-onebox-for-our-documentation-pages/185679/2 "2021-04-05T19:54:09Z")

</div>

Adding some [OpenGraph](https://ogp.me/) tags on those pages should be enough. In particular add:

`og:title`  
`og:image`  
`og:description`

At the moment we are falling back to the `twitter` tags in the head but their quality is low. You may want to move away from auto-generated description tags, as the twitter tag description has way too much noise at the moment:

```xml
<meta name="twitter:description" content="Last updated: Jul 30, 2019 | See all Documentation When reporting issues it can be useful to provide your Let&amp;rsquo;s Encrypt account ID. Most of the time, the process of creating an account is handled automatically by the ACME client software you use to talk to Let&amp;rsquo;s Encrypt, and you may have multiple accounts configured if you run ACME clients on multiple servers.
Your account ID is a URL of the form https://acme-v02.">

```