You publish a new post, product page, or launch update. Then you paste the URL into Slack, LinkedIn, X, or iMessage and see it: a plain gray box, a bare URL, or a card with the wrong image from three redesigns ago. That is why links show gray boxes - the platform sharing your page cannot find, fetch, or trust the preview data it needs.
A gray preview is not a cosmetic issue. It makes a valuable link look unfinished next to posts with clear headlines, recognizable branding, and strong imagery. For a founder sharing a launch, a marketer distributing content, or an agency managing client sites, that lost visual context can mean fewer clicks before anyone has even read the copy.
Why Links Show Gray Boxes on Social Platforms
Most sharing platforms do not build a preview from what a visitor sees in their browser. They send a crawler to your URL, read metadata in the page's HTML, and generate a card from that information. The main standard is Open Graph, often shortened to OG.
The core fields are simple: an OG title, description, URL, site name, and image. When `og:image` is missing, unreachable, too small, blocked, or cached incorrectly, platforms have little to work with. Some will select an image from the page. Others will show a generic gray placeholder. Some will display only a domain and a text snippet.
The difference matters because each platform has its own fallback behavior. LinkedIn may show a text-heavy card. Slack may show a neutral attachment block. X may reduce the preview to a link if its card tags are incomplete. WhatsApp and iMessage can be especially frustrating because their preview behavior depends on what their crawler saw at the moment the link was first shared.
So the gray box is usually a symptom, not the root problem. Your page may be visually complete for people while being nearly invisible to crawlers.
The Most Common Causes of a Gray Link Preview
There is no usable OG image
A page can have a featured image and still have no usable social image. A WordPress theme, CMS setting, or SEO plugin may not output `og:image` consistently. On custom sites, the tag may exist on the homepage but not on blog posts, documentation pages, category pages, or dynamically generated product URLs.
A usable image also needs to meet platform expectations. Social cards generally perform best with a wide image around 1200 by 630 pixels. Tiny thumbnails, portrait assets, SVGs, unusual formats, and images with extreme file sizes can fail or produce awkward crops. The platform may not explain the failure. It may simply give you gray.
The crawler cannot access the image or page
Sharing crawlers are not regular visitors. If your server blocks unknown bots, requires a login, uses overly strict firewall rules, or prevents image hotlinking, the crawler may get an error while your own browser works perfectly.
This also happens when images are stored behind a protected CDN, generated with temporary URLs, or served from a staging environment that requires authentication. A page that says “200 OK” to you may return a redirect, challenge page, or forbidden response to a social platform.
Your site renders metadata too late
JavaScript-heavy sites can look excellent in a browser but provide an almost empty initial HTML response. If the OG tags are added only after client-side JavaScript runs, many crawlers will never see them.
This is common with single-page apps and custom front ends. The fix is not to add a prettier image in the page body. The OG tags must be present in the server-rendered HTML for every shareable URL.
The image URL is wrong, relative, or redirected
An OG image needs a stable, absolute URL. A relative path such as `/images/card.png` may work in your site but not in every crawler. Redirect chains can also cause trouble, especially when an image moves between HTTP and HTTPS, between domains, or through a CDN rule.
Use a direct HTTPS image URL that returns the actual image file quickly. Avoid sending crawlers through several redirects just to reach a preview asset.
The platform is showing an old cached version
You fixed the tags. You changed the image. You shared the link again. Nothing changes.
That is caching, and it is normal. Platforms cache page metadata and image previews to avoid re-crawling every URL every time it appears in a conversation or feed. The cache may last hours, days, or longer depending on the platform and how often the URL is shared.
A cache is helpful until it preserves the exact broken version you are trying to replace. In that case, use a multi-platform preview checker to inspect what crawlers see and request a refresh where the platform supports it. Do not assume a new browser tab means a social crawler has a new preview.
How to Diagnose a Gray Social Card
Start with the actual URL being shared, not a similar page. A missing trailing slash, campaign parameter, redirect, language variation, or canonical URL can lead to a different response and a different preview.
Then check the page source, not only the visual page. Search for `og:title`, `og:description`, and `og:image`. Confirm that every value is populated, that the image URL is absolute, and that opening that image URL in a private browser window returns the intended file without a login or error.
Next, test the URL across the platforms your audience uses. One platform passing does not prove the setup is sound everywhere. X, LinkedIn, Slack, Facebook, WhatsApp, and iMessage interpret metadata differently and cache on different schedules.
If the card still appears gray, check redirects and bot access. Look for redirects from non-www to www, HTTP to HTTPS, or one locale to another. Review firewall, CDN, and security-plugin logs for blocked crawler requests. If you use a CMS plugin, verify that another plugin or theme is not outputting duplicate OG tags with conflicting image values.
Fix the System, Not Just This One Link
It is tempting to fix a broken preview by manually uploading one image or changing one metadata field. That works for an important launch page. It breaks down when you publish every week, maintain a large documentation library, or manage several client sites.
Manual design workflows create a second publishing process: write the page, design the social card, upload it, attach it, test it, and repeat. Developer-built image pipelines can solve the scale problem, but they often turn a simple marketing update into an engineering request.
A better approach is to connect your page data to a branded OG image design once. The title, author, featured photo, price, date, category, or domain can then populate a consistent layout for every current and future URL. Every page gets its own OG image, without someone opening a design tool for every page.
That is where a tool such as getwowlink fits: it can generate, host, and map branded Open Graph images to your existing site content while leaving your SEO workflow in place. Your WordPress, Ghost, Webflow, Next.js, or custom site keeps publishing pages. The preview layer stops being a manual afterthought.
There is still a trade-off. Highly editorial campaigns may deserve custom art direction, and a product launch might need a one-off visual. Automation is not a reason to make every card identical. It is a way to ensure the baseline is always on-brand, accurate, and share-ready.
Build Cards People Recognize Before They Read
A working preview is the minimum. A useful preview gives the reader enough confidence to click.
Keep the headline readable at a small size. Use contrast that survives dark interfaces and compressed messaging apps. Include your brand mark or domain when it helps recognition, but do not turn the card into a banner ad. If a featured image carries the story, let it lead. If the page is a technical guide or changelog, a strong title and clean system can outperform a generic stock photo.
Also consider page types. A blog post, documentation article, pricing page, event page, and product update do not need the same card layout. Section-specific designs can preserve consistency while giving each content format the right visual hierarchy.
The goal is not merely to replace a gray box with a colorful one. It is to make every shared URL look like it came from a team that pays attention. The next time someone pastes one of your links into a crowded feed or channel, the card should make the click feel like the obvious next step.
