Kite treats share images as a system, not a one-off design task. Every page on a site Kite builds already has a share image, because a page without one falls back to a branded card drawn from your brand name, tagline, and colors. That means no link from your site shows up blank, even on a page published this morning.
From there, Kite makes custom images for the pages that deserve one, using the colors, fonts, and imagery it recorded when it researched your brand. It sets the image alongside each page's share title and description, so the whole preview tells the same story. When you ask, Kite scans your site for pages missing a share image and fixes them. When your branding changes, the default card updates with it.
1
Give every page a branded image automatically
Every page on a website Kite builds gets a share image without anyone setting one. Kite's sites choose each page's image in a fixed order. A page uses its own image if it has one. If it doesn't, it uses the default share image set for the whole site. If there's no site default either, it uses a share card the site generates from your brand settings.
That card is 1,200 by 630 pixels. It shows your company name in large type with your tagline underneath, set on your primary brand color with a short stripe in your accent color. The text color switches between dark and light depending on how light your brand color is, so the card stays readable. The card comes from the same brand settings the rest of your site uses, so it never shows a name or a claim your site doesn't already state.
Blog posts and other articles have one more option in that order. If a post has a featured image and no separate share image, the featured image becomes its share image. A post with a strong header photo gets a preview that matches it without any extra work.
The automatic card is the same on every page that doesn't have its own image. That's a good floor. Your links always look like they came from your company. For the handful of pages you share most, a custom image does more. If you don't have a site yet, see Launch a marketing website for how Kite builds one with share images, titles, and descriptions in place from the start.
2
Make custom images for the pages people share most
Kite designs a custom share image for any page you name, and it uses your brand system to keep each image consistent with the rest of your marketing. During onboarding, Kite records your colors, typography, logo, and the style of imagery your brand uses. When it makes a share image, it generates or edits an image to fit that system, or it works from images you supply and photos already on your site.
The pages worth a custom image are usually the ones that get shared on purpose:
- your homepage
- launch and product pages
- pricing
- landing pages for campaigns or events
- blog posts you plan to promote
A custom image can say something the default card can't. For a launch page, that might be the product name and a one-line promise. For a webinar landing page, it might be the topic, the date, and the speaker's photo. The important text belongs near the center of the image, because LinkedIn, Slack, and X each trim the edges a little differently.
When Kite writes a blog post for your site, it can make the post's featured image too, and that image doubles as the share image unless you want a different one.
3
Set the share title and description that go with the image
A share image is one part of a preview, and Kite sets the other parts so they match. Most platforms show the image above a title and a short description. Kite writes those for each page, and on a site it builds, a page with no share description gets one taken from its own opening text. Every page also carries your site name, so the preview shows where the link comes from.
Kite's sites state every share image as a full web address, even when the image was saved with a short path. A short path like /images/launch.png works in a browser but can't be fetched by a platform that doesn't know which site it belongs to. Kite's sites also mark each page that has an image for X's large-image card, so the image appears full width in a post instead of as a small square beside the link.
4
Find the pages that are missing a share image
Kite can scan your website and list the pages that are missing a share image, title, or description. The scan reads the tags on each page it visits, the same tags a platform reads when someone shares the link, so it catches the pages that would show up blank. To run it, ask Kite to audit your site. The same scan checks the other technical basics that affect how search engines and AI systems read your pages, which Check your website's readiness for AI agents covers in more detail.
On a site Kite builds, it fixes what it finds through the site's content editor. Each change waits as an unpublished change you can preview, and it goes live when you publish. If you'd rather set a share image yourself, the content editor has a field for it on every page.
If you're moving an existing website to Kite, the share images you already have come with it. Kite copies each page's existing image to its own image hosting, so the preview keeps working after your old host is gone. Pages that never had an image pick up the site default or the branded card.
5
Fix a link that still shows the old image
If a link shows the wrong image after you've changed it, the platform is almost always showing a copy it saved earlier. LinkedIn, Facebook, Slack, and X store a link's preview the first time anyone shares it, and they reuse that copy for days or weeks. Updating the image on your page doesn't change what they've stored.
There are really two saved copies to deal with. The platform saves the preview for your page, and it also saves the image file under the image's web address. If the new image keeps the old address, the platform can keep showing the old picture even after it reads your page again. Kite builds the fix for that into the automatic card. When your brand name, tagline, or colors change, the card's address changes too, so a platform that reads your page sees a new address and fetches the new card. A new custom image is saved at its own new address, so it works the same way.
The saved preview for the page is the other half. For a link that's already been shared, ask the platform to look at the page again. LinkedIn's Post Inspector and Facebook's Sharing Debugger both fetch a page fresh and update the saved preview. Kite can tell you which tool to use and what to check if the preview still looks wrong, such as an image that's too small, an image blocked from crawlers, or a page that requires a login.
