---
title: "SEO metadata and social images"
url: "/help/buuk/seo-metadata-and-social-images"
updated: "2026-11-13T13:32:04.387Z"
---
# SEO metadata and social images

Search engines and link previews never see your article the way readers do. They read the page's HTML metadata — a title, a short description, a canonical URL, and a social image — and decide from that what the page is and how it looks when someone shares it.

Buuk generates that metadata for every published page and gives you the few fields worth writing yourself.

## Set the brand fields once

In **Customize**, the Brand panel holds the three fields SEO and previews lean on:

- **Site title** — shows in the header, the browser tab, and the metadata for the home and section pages.
- **Site description** — the summary search results and AI answers use when describing your docs.
- **Site image** — the preview image for link previews on Slack, X, and LinkedIn. PNG, JPG, SVG, or WebP, up to 5 MB.

These feed every landing page. The help center home, topic sections, guides, the FAQ, the changelog, and the API reference all use your site title, description, and image in their page metadata.

## What is automatic

Each published page generates its metadata when the page is requested:

```html
<title>Sitemap and robots</title>
<link rel="canonical" href="https://app.getbuuk.com/help/your-slug/sitemap-and-robots">
<meta property="og:title" content="Sitemap and robots">
```

- A title per page — articles use their own title.
- A description — the first 160 characters of the article body, or the published translation's excerpt when a reader locale applies.
- A canonical URL, so search engines rank one address per page instead of every path that can reach it.
- Open Graph and Twitter card tags. When a page has an image, the card is the large-image format; otherwise it falls back to a compact summary.
- Crawl instructions. Public pages are marked index and follow; private help centers are marked noindex so they stay out of search results.

Nothing changes the page itself. Editing the article title is all it takes to update the title tag and the social card with it.

## Generated social images

Buuk renders a 1200×630 PNG for each page. Article pages get a card that shows the article title, its section name, and your site's hostname at the top — so links shared in chat or on social show what the page is about, with no upload from you.

Articles always have a generated card. The **Site image** is what the other pages — home, sections, guides, FAQ, changelog, API reference — use in previews.

## Translations and hreflang

When an article has published translations, Buuk emits hreflang alternates that point at the same URL with `?lang=` for each locale, plus an `x-default`. Search engines can rank the right language per reader without separate URLs.

## Related

- Where the brand fields live: [Branding and custom domain](./branding-and-custom-domain).
- What readers see once a page is live: [Publish your help center](./publish-your-help-center).
- Serving docs from your own hostname: [Custom domain](./custom-domain).
- Per-locale titles and bodies: [Translations](./translations).