Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To change the image shown when a page is shared, update that page’s og:image metadata in the HTML <head>, publish the change, check the live page and image URL, then ask the social platform to fetch the page again. Changing the image in a site editor alone does not guarantee that the published page—or a platform’s cached preview—has changed.
What the Open Graph image controls
Open Graph metadata tells services how to represent a web page when it is shared. The Open Graph Protocol identifies og:image as the image URL representing the page, and lists it among four required properties alongside og:title, og:type, and og:url. The metadata belongs in the page’s HTML <head>, not in the visible page content.
A basic set of tags looks like this:
<head prefix="og: https://ogp.me/ns#">
<meta property="og:title" content="Example page title">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page">
<meta property="og:image" content="https://example.com/images/page-social.jpg">
<meta property="og:image:alt" content="Short description of the image">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="627">
</head>Replace the example values with information for the actual page. Use an absolute image URL, including its scheme and hostname, rather than a site-relative path such as /images/page-social.jpg. The page’s og:url should identify the canonical page being shared; it is not the image URL.
Recommended Free Tools
The protocol also defines structured image properties, including og:image:url, og:image:secure_url, og:image:type, og:image:width, og:image:height, and og:image:alt. The alt property describes the image; it is not a caption to display on the page. Use the standard og:image property as the image declaration, and provide accurate structured details where they are useful and correct.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Choose and prepare the replacement image
Make the image suit a landscape social preview: keep the main subject, logo, and any essential wording comfortably inside the frame so a platform’s card layout has room to crop or pad it. Avoid relying on small text that may become unreadable in a compact preview. JPEG or PNG are practical formats for broad compatibility.
For LinkedIn shared links, its published guidance gives a minimum image size of 1200 × 627 pixels, recommends a 1.91:1 ratio, and sets a maximum file size of 5 MB. The guidance was last updated two years before September 29, 2026; treat those as LinkedIn-specific requirements, not a universal guarantee for every service or every card layout. LinkedIn also says images under 401 pixels wide display as thumbnails.
Before publishing, make sure the file is the intended version, has the correct orientation, and is actually available at the URL you plan to put in the tag. If you overwrite an existing file while leaving its URL unchanged, a social service may continue to use a cached copy; using a new filename for a replacement image can make it easier to distinguish the new asset from the old one.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
Update the tag in the source that generates the page
Find the place that controls the HTML head for the page you intend to share. The edit may live in a shared template, a CMS field, a plugin’s social settings, a framework’s route metadata, or a server-rendered component. Change the value of the page’s intended og:image to the new public image URL.
Keep the related metadata aligned. The title and description should describe the same page as the image, and og:url should reflect the canonical page URL. A visually attractive image for the wrong page—or metadata that points at a different canonical URL than the one being shared—can produce a confusing card.
Plain HTML or a shared template
Find the relevant <meta property="og:image" ...> element in the page or common head template and replace its content value. If a shared template supplies the tag, confirm whether it needs a page-specific override; otherwise every page may inherit the same image.
WordPress or another CMS
Open the social or SEO settings for the specific post or page and change its social-sharing image. The field’s name and location depend on the CMS and any installed theme or SEO plugin. Save or publish the content, then inspect the generated source: the decisive check is what the production page returns, not what an editor field displays.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Framework metadata
Update the route’s Open Graph metadata configuration or the framework’s image-convention file, depending on how the project generates metadata. Rebuild and deploy when required by the framework or hosting setup. Do not assume a client-side change is enough: verify that the live page response contains the metadata in its HTML head.
More than one image
The Open Graph Protocol allows image properties to be supplied as an array. If you publish multiple image entries, put the preferred image first. Check the order in the rendered HTML, since a template or plugin may add another image tag before or after the one you edited.
Rank #4
Publish and verify the live page
- Open the exact production URL you plan to share. Check the canonical URL and any redirects so you test the same page that recipients will open.
- Inspect the returned HTML source. Use the browser’s view-source feature or fetch the production page and search its HTML head for
og:image. Confirm the value is the new absolute URL and that the title, type, and canonical URL are appropriate. - Check the image URL independently. Open it without being signed in or relying on a browser session. Confirm it returns successfully, is the intended image, and is served as an image rather than an error page or an HTML login screen.
- Check crawler access. The image should be publicly retrievable over HTTPS without authentication, crawler denial, hotlink blocking, or a protected-directory restriction. A person viewing the page in a logged-in browser does not prove that a social crawler can fetch the file.
- Request a fresh platform scrape. Use the destination service’s link-preview or debugger workflow when available, then share the canonical page URL again. Each platform may cache page metadata and images separately.
The Open Graph Protocol defines metadata for a page; it does not ensure that every platform will render the same crop, card dimensions, or preview treatment. Use the destination platform’s own preview as the final visual check.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Diagnose a preview that is stale, missing, or wrong
The old image still appears
- Confirm the production HTML—not just a CMS preview—contains the new
og:imagevalue. - Check whether the image URL itself is unchanged and whether a cached image might still be associated with it. Test the image response directly; if appropriate, publish the replacement at a new filename and update the tag.
- Request a fresh scrape through the platform’s link-preview or debugger tool. A CMS change does not automatically invalidate a platform’s cached scrape.
- Make sure you refreshed the exact page URL that was shared. A redirect, alternate hostname, or different canonical URL may be treated as another page.
No image appears
- Try the image URL without a logged-in browser session. Remove authentication requirements and check for hotlink protection or a protected directory.
- Verify HTTPS, redirects, response status, and the response’s image MIME type. The URL should return the image file, not an error, challenge, or login page.
- Check that crawler access is not blocked. LinkedIn specifically warns that an otherwise qualifying image may fail to appear if a site blocks LinkedIn from retrieving it or stores it in a protected location.
- Recheck the live page source for a valid absolute URL. A malformed or relative URL can work differently from what you intended when rendered on the page.
The wrong image appears
- Search the rendered head for duplicate
og:imagetags. A theme, plugin, shared template, or page-specific override may be outputting a second value. - Inspect the exact URL that was posted and compare it with the page’s canonical
og:url. The preview may belong to a different URL variant than the one you edited. - If multiple image tags are intentional, verify that the desired one is first in the rendered markup.
The image is cropped, tiny, or hard to read
- For LinkedIn, check the 1200 × 627 minimum and recommended 1.91:1 ratio in its published guidance, and remember that images under 401 pixels wide display as thumbnails.
- Keep logos, faces, and essential text away from the outer edges. The platform controls the final card rendering, so a safe central composition is more robust than edge-to-edge detail.
- Check the actual returned file rather than relying on its filename; an older, smaller, or differently cropped file may still be hosted at the URL.
Or skip the browser setup
If you need a screenshot to visually inspect the deployed page after changing its metadata, ScreenshotNeo can return a page capture from one GET request. It does not edit Open Graph metadata or force a social network to refresh its preview; use it as a convenient check of the page you deployed. For API parameters and response details, see the ScreenshotNeo documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/page -o shot.webpScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan.
Sign up for 1,000 free screenshots a month, with no card required.
Frequently Asked Questions
Can I use the same Open Graph image on every page?
You can, but a page-specific image is more informative when pages cover distinct subjects. If a shared template supplies one default, verify that important pages can override it and that the rendered tag reflects the intended page.
Does og:image:alt replace the page’s normal alt text?
No. It describes the social-preview image in Open Graph metadata; it does not replace the HTML alt text on an image element in the visible page.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
