How to Change a Website Link Thumbnail

To change the thumbnail that appears when people share a webpage, set that page’s Open Graph og:image tag to the publicly reachable image you want platforms to show. If you only need to change one LinkedIn Page post, an admin can choose a different image in the post composer without changing the page metadata.

Open Graph is a set of metadata that helps platforms interpret a webpage when it is shared. Its basic properties include og:title, og:type, og:image, and og:url; og:description is optional and generally recommended. These tags belong in the page’s <head>. Open Graph Protocol documentation.

1. Choose which thumbnail you want to change

What you want to change	Use this method	Scope
The preview image for a webpage wherever its URL is shared	Change the page’s `og:image` through your CMS or page source	Page-level metadata; platforms may cache previews
The image on one LinkedIn Page post	Choose an image in the LinkedIn Page post composer	That post’s preview; does not necessarily change the website metadata

Start with the website-level setting if you want a durable change for a particular page. If you only need a one-off LinkedIn post image, use the composer override.

2. Change the website’s Open Graph image

Check your CMS or SEO plugin first

Open the page you intend to share in your CMS.
Look for a page-specific setting called Social image, Open Graph image, or similar in the SEO or sharing panel.
Select or upload the image that should represent this page. Check for a per-page override if the CMS only shows a site-wide default.
Save or publish the page, then inspect its rendered HTML to confirm the og:image value changed.

CMS controls can be backed by a plugin. For example, WordPress plugin documentation describes using a featured image as an Open Graph source and manually selecting an image. The exact controls depend on your CMS and installed plugins. WordPress.org plugin directory.

Set the tags in the page head

If your CMS does not provide a social image field, add metadata to the page template or its server-rendered head. Replace the example URLs and text with values for the page being shared. The image URL must be publicly reachable by the platform fetching the preview.

<head>
  <title>Product documentation</title>
  <meta property="og:title" content="Product documentation">
  <meta property="og:type" content="website">
  <meta property="og:url" content="https://example.com/docs">
  <meta property="og:image" content="https://example.com/images/docs-share.jpg">
  <meta property="og:description" content="Guides and reference for the product.">
  <meta property="og:image:alt" content="A preview of the product documentation">
</head>

Use an absolute HTTPS URL for og:image. Open Graph also defines optional image properties such as dimensions and alt text. If you include image dimensions, make sure they match the actual image file. Keep the title, description, URL, and image specific to the page being shared.

Check the image’s size and accessibility

Image requirements differ across platforms. LinkedIn’s website-sharing help specifies a minimum image size of 1200×627 pixels. Its Page-post guidance recommends a 1.91:1 image, such as 1200×627 pixels. Treat these as LinkedIn requirements and guidance, not universal dimensions for every platform. LinkedIn Help: website sharing and LinkedIn Help: Page posts.

Use an image URL that does not require a logged-in session.
Check that the server returns the image rather than a login page, error page, or redirect loop.
Choose a crop that still makes sense at the target platform’s preview shape.
If the image is on a CDN, verify that the public URL serves the updated file. Changing an image while keeping its URL may leave a cached copy in circulation.

3. Change the image for one LinkedIn Page post

LinkedIn documents an image override for Page admins. This changes the preview for the post you publish; it does not necessarily update the Open Graph metadata on your website.

Open the LinkedIn Page in super admin or content admin view.
Start a post and paste the webpage URL.
Click Edit below the post text box.
Choose an image with the image icon. You can also edit the article title.
Set the audience and publish the post.

For a LinkedIn Page post preview, LinkedIn recommends 1200×627 pixels at 1.91:1. Its website-sharing guidance specifies a minimum of 1200×627 pixels. Check the current guidance for the surface you are posting to, since preview behavior and requirements may differ.

4. Verify the page metadata and preview

Open the shared page’s rendered source and search for og:image. Confirm its value is the intended public image URL.
Check that og:title, og:description, and og:url describe the same page and that the URL is canonical for that page.
Open the image URL directly in a private browser window. Confirm it loads without authentication and shows the correct image.
Use the target platform’s current sharing debugger or post inspector, if available, to request or inspect a refreshed preview.
Share the URL again and check the resulting preview. If the old image remains, allow for platform caching and check the inspector again later.

Preview caches can be aggressive, and refresh behavior varies by platform. Do not assume that changing the HTML updates every already-created post immediately. A third-party overview describes this caching issue; verify refresh steps using the platform’s current tools. OpenGraphImage overview.

5. Or skip the browser setup

To inspect the rendered page as a screenshot, make one request to ScreenshotNeo. It is a website screenshot API and MCP server for developers. The example captures the page so you can visually check what loads; it does not change the page’s Open Graph metadata or force a social platform to refresh its cache. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/docs -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/docs"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/docs' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server includes take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000 screenshots.

Troubleshooting

Symptom	Likely cause	What to check or change
The old thumbnail still appears	The platform has a cached preview, or the page still emits the old tag	Inspect the rendered `og:image`, then use the platform’s current debugger or inspector if available. Check again after the platform refreshes its cache.
No thumbnail appears	The image URL is private, broken, blocked, or returns something other than an image	Open the URL without signing in. Check redirects, access restrictions, and the server response.
The wrong page’s image appears	A site-wide default or template value overrides the page-specific value	Inspect that page’s rendered head and configure the per-page social image in the CMS or template.
The image is cropped badly	The source image’s aspect ratio does not suit the platform’s preview	Prepare a crop for the target platform. For LinkedIn, use its documented 1200×627 guidance.
Changes appear in source but not in the preview	The rendered tags changed, but the platform has not fetched them again	Use the platform’s available sharing inspector to check or refresh the scrape. Do not treat a successful source edit as proof every cached preview has updated.
One LinkedIn post has the desired image but other shares do not	The post composer override applies to that post only	Set the website’s `og:image` as well if the page-level default should change.

Performance, reliability, and cost

Open Graph metadata is a small part of the page head, so changing the tag usually does not require a browser-side script. Put the correct value in the server-rendered HTML or CMS output so a platform crawler can read it when it fetches the page. A social preview is still dependent on the platform being able to reach both the page and image.

Keep the image URL stable when the image is unchanged. If you replace the file but keep the same URL, a platform or CDN may still serve a cached version; if you change the URL, update og:image too. Neither approach guarantees an immediate preview refresh because cache behavior belongs to the platform.

This method has no separate API cost: it uses your existing website or CMS. A social post composer override costs no website code change but must be repeated for each post. ScreenshotNeo is optional and useful for checking what a browser capture shows; its pricing is Free for 1,000 shots a month, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan.

FAQ

Does changing the featured image always change the link thumbnail?

No. A CMS or plugin may use the featured image as its Open Graph image, but check the rendered og:image value to confirm what the page publishes.

Can I use a different thumbnail for each page?

Yes. Set a page-specific social image or emit a distinct og:image on each page.

Will the LinkedIn post override update other platforms?

It applies to the LinkedIn Page post flow. Other platforms read their own previews from the webpage metadata and may use their own refresh behavior.

Does a screenshot change the link preview?

No. A screenshot helps you inspect the page visually. To change a shared thumbnail, update the page metadata or use a platform’s post-specific image control.