Your link shows the wrong image, or no preview at all, on WhatsApp. Check the title, description and image your page gives the app, then fix what's missing.
ChatGPT
Claude
Google
GrokYou send a customer your website link. WhatsApp shows an old logo, the wrong picture or a plain address with no useful preview.
The page can look perfectly good when opened and still share badly. The preview uses information the website gives to the app.
Why does my website look wrong on WhatsApp?
The app may be reading missing, outdated or inaccessible preview information.
Your website can show a poor WhatsApp preview because its page title, description or preview image isn't configured correctly. The app may also be showing an older saved preview or be unable to fetch the page or image.
Open Graph tags are the small pieces of page information that describe how a link should appear. You don't need to write the code yourself to check whether the right values exist.
The Open Graph specification describes the main fields.
| Field | What it tells the app |
|---|---|
| og:title | The preview headline |
| og:description | A short description |
| og:image | Which image to use |
| og:url | The page's preferred address |
| og:type | What kind of page it is |
Start with the exact link you shared. Your homepage and a blog article may have different values, so checking one doesn't prove the other works.
How do you check the preview?
Use a preview tool and a fresh WhatsApp test.
Paste the full page address into the Facebook Sharing Debugger. It can help reveal missing tags, an unreachable image or outdated values.
The debugger tests Facebook's fetch and preview. It doesn't guarantee that WhatsApp will show the identical result, so repeat the test in WhatsApp too.
Ask your developer to show the page's actual Open Graph values. They should describe this page, not an old brand, a test project or a generic homepage.
Check the image address separately in a private browser window. It should open the intended image without login, an expired download link or a certificate warning.
If the page is also slow to open normally, use our mobile website speed checks. Slow responses can make fetching the preview less reliable, but speed isn't the only possible cause.
What should you change on the website?
Fix the page information and image access before redesigning the graphic.
1) Give the page its own title and description
A service page should describe that service. A blog post should share its own headline and summary.
If every page uses the homepage's values, the preview can look unrelated to the link. Ask your developer or CMS editor where those values are set and whether the page-specific version overrides the default.
Keep the description short and readable. A preview should tell someone what they'll find, not repeat a list of keywords.
2) Use a public image address
The preview image needs to be available to the service fetching it. Use a stable, full URL, such as https://example.com/images/article.jpg.
A file path on your laptop or an image inside a signed-in editor isn't enough. Temporary upload links can also expire.
Ask the developer to check access from outside your owner account. If a bot-protection rule blocks the fetch, adjust the relevant rule carefully rather than disabling protection across the site.
3) Start with a simple, lightweight image
A landscape JPG or PNG is a practical starting choice for broad sharing compatibility. An image around 1200 by 630 pixels gives you a familiar social-card shape.
Treat that as a design choice, not a universal WhatsApp requirement. Don't rely on an unverified file-size cutoff or assume that one format always fails.
Compress the file while keeping the headline or subject clear. If the current image fails, try a simpler test image at a public address. That tells an image problem apart from a page-access problem.
Leave generous space around text and the logo, because each app crops and sizes the preview its own way.
4) Make the information available when the page is fetched
Some websites add preview tags only after browser scripts run, and a service fetching the initial page may never see them.
Ask your developer whether the tags appear in the returned page source. Custom frameworks and builders have different ways of setting that information.
An AI-generated site can include a complete visual design while leaving this setup unfinished. That doesn't require rebuilding the site; give the builder the exact page and incorrect preview values.
Why does the old image remain after a fix?
The app or service may have saved an earlier result.
Confirm first that the live page source points to the new image. Then fetch it again in the debugger where available and try a fresh share in WhatsApp.
A versioned image filename can help distinguish old and new files when the image itself was replaced. However, adding a random query to every page link isn't a guaranteed way to clear every app's cache.
An existing message may keep its earlier appearance. Use a new share for the test rather than judging only by a message sent before the repair.
If only one person sees no preview, compare another device or account. Client privacy settings, app behaviour and connection conditions can affect display.
If your links give the wrong first impression, we can fix what your website sends to sharing apps. For a custom-coded site, we'll quote the fix once we've seen how deep the problem goes; builder sites such as Framer or Webflow are outside our repair work. Book a free intro call with nothing to commit to, or contact hi@aruno.studio, WhatsApp or Telegram @mihaipostelnicu.
A website audit can organise wider presentation issues. If the page is missing from search as well, follow the separate Google visibility checks.
Which mistakes should you avoid?
Check the actual values instead of applying several fixes at once.
| Mistake | What to do instead |
|---|---|
| Change the design before checking tags | Confirm which image the page points to |
| Use an editor-only image link | Use a public, stable image URL |
| Keep several conflicting tag sets | Ask which set is actually served |
| Treat Facebook as proof of WhatsApp behaviour | Test both separately |
| Disable all bot protection | Identify and adjust the relevant access rule |
After the repair, test the homepage and one article or service page. Each should show information matching its own destination.
A useful brief for your developer is:
This page shares with the wrong image. Please check its live Open Graph title, description and image URL, confirm that the image is publicly accessible, and test a fresh share after the change.
Add the full address and screenshot so they can reproduce the same result.
Frequently asked questions
Do I need a separate preview image for every page? Not always. A default image can work for general pages, while article-specific images make blog links easier to distinguish.
Why does Facebook look correct but WhatsApp doesn't? They can fetch and save previews differently. Facebook's debugger is useful evidence, but you still need a WhatsApp test.
How much does fixing a preview cost? Updating a CMS field is different from repairing how the site generates tags. Ask which part is wrong before requesting a redesign.
How long does the fix take? Editing tags can be quick. Cached previews and access problems may need further testing before you see the result everywhere.
Your shared link should describe the page behind it. Check the information the app receives.
Share this article:
