> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Social Share Cards

> Every Hiveku site ships a proper share image by default — what platforms show when your links are shared, and how to customize it per page

When someone shares a link to your site — on Facebook, LinkedIn, X, Slack, iMessage — the platform fetches your page and looks for a share image (an Open Graph image). Sites without one get an ugly fallback: a cropped logo, a gray box, or nothing.

Every Hiveku site ships a share card by default. You don't have to do anything to get one, and anything custom you add always wins.

## What You Get by Default

* A **branded 1200 x 630 share card** carrying your site's name, generated at deploy time for every page.
* Correct social metadata across the board — share image, canonical URL, and Twitter card tags — on server-rendered **and** static sites.
* Pages that customize *other* social fields (say, a per-page share title) still get the image — the site's default card fills in wherever a page doesn't bring its own.

The default is deliberately shy: it only appears when your project has **no custom card of its own**. The moment you add one — a custom share image file, an image set in your page's SEO settings, or share images defined in your site's code — the default steps aside for it.

## Customizing

<Tabs>
  <Tab title="Per page">
    Each page's SEO settings include social share fields — title, description, and an **OG Image URL**. Set an image there and that page shares with it. See [SEO basics](/how-tos/seo) for where the SEO settings live.
  </Tab>

  <Tab title="Whole site">
    Ask the AI: attach the image you want and say "use this as the share card for the whole site." It wires the image up so every page without a page-specific card uses yours.
  </Tab>

  <Tab title="Per page, via the AI">
    Attach an image and name the page: "use this as the share image for the pricing page." Page-specific cards always beat the site-wide one.
  </Tab>
</Tabs>

Changes take effect on your **next deploy** — share cards are assembled when your site builds.

## Checking How a Link Will Look

Paste your URL into the platform's own preview tool:

* **Facebook** — Sharing Debugger
* **LinkedIn** — Post Inspector
* **X** — Card Validator

These tools show exactly what the platform sees, and double as a cache refresh (see below).

<Warning>
  Social platforms cache their scrape of your page — often for weeks. If you change your share card and an old preview keeps appearing, that's the platform's cache, not your site. Run the URL through the platform's debugger tool to force a fresh scrape.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="A shared link shows no image at all">
    Confirm the site has been deployed since you set a custom image — cards are added at deploy time. Then check the URL in the Facebook Sharing Debugger; it reports exactly which image tag it found (or didn't).
  </Accordion>

  <Accordion title="The wrong or an old image appears">
    Almost always the platform's scrape cache. Use the debugger tool for that platform to re-scrape. If the debugger shows the *new* image but shares still show the old one, wait — some surfaces update on a delay.
  </Accordion>

  <Accordion title="One page shows the default card, but I set a custom site-wide one">
    That page probably defines its own social metadata without an image, in a way that overrides the site-wide card. Ask the AI to "make sure every page inherits the site share image" — it will find and update the offending page.
  </Accordion>
</AccordionGroup>

## What's Next?

<CardGroup cols={2}>
  <Card title="SEO Basics" icon="magnifying-glass" href="/how-tos/seo">
    Titles, descriptions, and the rest of your pages' metadata
  </Card>

  <Card title="Deployments" icon="rocket" href="/publishing/deployments">
    When and how your changes reach the live site
  </Card>
</CardGroup>