Fixing Base44 link previews on Slack, LinkedIn, WhatsApp and X

A Base44 link preview comes from the Open Graph and Twitter tags Base44 writes into each page, built from your app’s title, description and logo unless you set them per page. When a preview looks wrong, it’s usually because every page is sharing the app-wide defaults, or because the platform cached an old version. Set per-page titles, descriptions and images on the SEO & GEO page, publish, then ask each platform to re-fetch.

The same tags feed search results, so this overlaps with the meta tags guide.

Where Base44’s preview tags come from#

From Base44’s SEO documentation: Base44 “sets social metadata so links to your app show a sensible title, description, and image when shared on social platforms. Social card images are automatically resized to 1200 × 630.” Those previews “use the title, description, and logo you configure in your app’s settings.”

Since April 2026 you can set titles, descriptions and Open Graph images per page from the SEO & GEO page. Social previews are listed among the features “designed for apps on custom domains”, which is one more reason to connect one.

Check what a page sends:

curl -s -A 'Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)' https://yourdomain.com/pricing \
  | grep -oE '<meta (property|name)="(og|twitter):[^"]*"[^>]*>'

You want og:title, og:description, og:image, og:url and twitter:card at minimum.

Why previews go wrong#

Every page shows the same card. Without per-page values, every page uses the app-wide title, description and logo. Set them on the pages people share: homepage, pricing, articles, product pages.

The image is a stretched logo. Base44 resizes your logo to 1200 × 630. A square logo stretched to that ratio makes a poor card. Upload an image designed for 1200 × 630, with any text large enough to read at thumbnail size.

Record pages share one preview. A template page that shows many records, like /Product?id=123, gets one set of tags for all of them. Ask the AI to set og:title, og:description and og:image from the loaded record, as described in the meta tags guide.

The preview is cached. Platforms store previews for days or longer. A fix you published won’t appear until they fetch the page again.

Do link-preview bots get Base44’s rendered page?#

Yes, once it exists. In our crawler test, facebookexternalhit, Twitterbot, LinkedInBot, Slackbot, Discordbot and WhatsApp all received Base44’s rendered page on pages where a render existed. Before that, they got Base44’s generated summary block.

For app-wide tags that doesn’t matter much, since Base44 writes them into the page head in both versions. It matters for tags your page sets from loaded data, like a product’s own title and image. Those only appear in the rendered version. If a record page’s preview shows the generic card, the page had no cached render when the bot fetched it.

Refreshing previews on each platform#

Base44’s canonical tags keep content parameters and drop tracking ones, so a ?v=2 you add for cache-busting may show up as a separate canonical URL. Use it for testing, then share the clean URL.

What to do next#

1. Upload a proper 1200 × 630 image and set it on your homepage.
2. Set per-page titles, descriptions and images on the pages people share.
3. Give record pages data-driven preview tags.
4. Refresh each platform’s cache with the tools above.