Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChange the page’s Open Graph metadata in its HTML <head> (or in the CMS field that generates those tags), publish the page, and then submit the live URL to the relevant social-platform inspector. The essential tag is:
<meta property="og:image" content="https://example.com/images/new-social-preview.jpg">The URL must be absolute, use HTTPS, and be reachable by a crawler. A practical cross-platform image target is 1200 × 630 pixels. LinkedIn’s current help documentation lists 1200 × 627 pixels as its minimum, so keep important text and logos away from the edges.
What the Open Graph image controls
When someone shares a page, social networks read metadata in the page source to build the link preview. The Open Graph protocol defines og:image as “An image URL which should represent your object within the graph.” It is a metadata tag, not an image displayed in the page body.
Changing the file in your media library is not enough unless the page’s og:image value points to that file. Likewise, changing a CMS editor preview does not prove that the deployed HTML has changed. Always verify the published URL.
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 problems#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
Use a crawler-friendly file
- Use a publicly reachable absolute URL such as
https://example.com/images/article-preview.jpg. - Serve the actual image file, not an HTML error page, login screen, or redirect chain that blocks crawlers.
- Use JPG or PNG unless your target platforms and delivery stack are known to support another format.
- Keep important text, faces, and logos inside a safe area because platforms can crop previews differently.
Pick dimensions that travel well
Use 1200 × 630 pixels (about a 1.91:1 ratio) as a practical general-purpose target. LinkedIn documents 1200 × 627 pixels as its minimum. These are useful targets, not a universal guarantee: platform rendering and file-size limits can change, and each network may crop or resize the image.
Add or replace the tags in the page head
Minimal implementation
Place the tag between <head> and </head> in the generated HTML:
<meta property="og:image" content="https://example.com/images/new-social-preview.jpg">Recommended structured properties
Add the structured properties when your platform or CMS allows them:
<meta property="og:image" content="https://example.com/images/new-social-preview.jpg">
<meta property="og:image:secure_url" content="https://example.com/images/new-social-preview.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Short description of the preview image">og:image:secure_url repeats the HTTPS image address for consumers that look for it. The type, dimensions, and alt text describe the image and can help a consumer process it correctly. Keep the values accurate for the file that is actually served.
Handle multiple images deliberately
The protocol permits multiple og:image tags. When values conflict, the first image is given preference. If an old image appears before the new one, remove the stale tag or move the intended image to the first position. Do not assume that adding a second tag overrides the first.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Change the image through your site system
Custom HTML or a template
- Open the template or component that emits the document head.
- Replace the existing
og:imagevalue with the new absolute HTTPS URL. - Update the structured properties so width, height, MIME type, and alt text match the new file.
- Deploy the template and purge any page or CDN cache that could still serve the old head.
CMS or site builder
Use the page’s social-sharing, social image, or Open Graph image field rather than editing a generated HTML view. The field may be in the page’s SEO or sharing settings. Save and publish the page, then inspect the deployed source; an editor preview alone is not evidence that the crawler-facing markup changed.
In WordPress, the exact location depends on the SEO or social-sharing plugin in use. Look for a page-level “Social,” “Open Graph,” or “Social image” panel and set the image there. In Wix, use the page’s social-sharing settings and its documented 1200 × 630 workflow. In both systems, confirm that the setting generates one preferred og:image tag in the final head.
Compare the implementation choices
| Approach | Control over generated HTML | Per-page updates | Absolute URL and structured properties | Cache control |
|---|---|---|---|---|
| Hand-edited template | Highest; you control every tag | Usually harder unless the template accepts page data | Fully controllable | You must manage deployment and CDN invalidation |
| CMS social-image field | Depends on the CMS or plugin | Usually easiest for editors | Available when the CMS exposes the fields; verify the output | Depends on the CMS, page cache, and CDN |
| Static/generated metadata | Controlled by the build or rendering system | Requires a content update and rebuild | Fully controllable if the generator emits the properties | Requires a rebuild plus any edge-cache purge |
Publish, inspect, and refresh the preview
- Open the deployed page in a browser and view the page source, not only the editor preview.
- Search the source for
og:image. Confirm the tag is inside<head>, the intended URL appears first, and there are no stale duplicates. - Open the image URL directly. Confirm it returns the image, over HTTPS, with the expected dimensions and MIME type.
- Submit the live page URL to Facebook Sharing Debugger and LinkedIn Post Inspector. These inspectors request a fresh scrape after a metadata update; Wix also recommends this workflow.
- Share the URL again after the inspector reports the new image. A previously generated post may retain its old preview even after the page metadata is correct.
Troubleshoot an old or missing image
| Symptom | Likely cause | Fix |
|---|---|---|
| The old image is still shown everywhere | A social cache or CDN cache still has the prior response | Verify the deployed source, purge your page/CDN cache, then run the live URL through the platform inspector again. |
| The new tag exists but the old image wins | Multiple og:image tags exist and the stale one comes first |
Remove the duplicate or move the intended tag to the first position. |
| No image appears | The URL is relative, private, blocked, or returns an error page | Use a public absolute HTTPS URL and test it directly without a login session. |
| The image is cropped badly | The platform uses a different crop or aspect ratio | Use a 1200 × 630 working canvas, keep key content away from edges, and preview on the target platform. |
| The image metadata is ignored | The tags are outside <head>, not present in server-rendered HTML, or changed only in an editor preview |
Inspect the deployed page source and fix the template/CMS output. |
| The file looks wrong despite the right URL | The server sends a different file, MIME type, or cached version | Check the response headers and dimensions, then invalidate the cache and retest. |
| One network updates while another does not | Each platform maintains its own scraper cache and rendering rules | Run the URL through that network’s own inspector and allow for separate caching. |
Use a stable URL and plan for future updates
Changing the image at the same URL can leave old pixels in a CDN or social cache. A versioned filename such as article-preview-v2.jpg gives the metadata a new resource URL, while a cache purge is still useful. Conversely, do not change a filename until the replacement is deployed; a crawler that reaches the new tag before the file exists may cache a failure.
If your page is generated dynamically, make the image value part of the page’s canonical data model and ensure the server-rendered response contains it. Client-side code that inserts a meta tag after load may not be seen by every crawler. Test the raw response and the final browser view separately.
Rank #3
Or skip the browser setup
ScreenshotNeo can capture the deployed page so you can inspect the rendered result without maintaining your own browser automation. It does not replace changing og:image; you still edit and publish the metadata as described above. It is useful for checking what a visitor sees after the update.
One GET request returns a PNG, JPEG, WebP, or PDF. Cookie and consent banners are accepted or removed before capture, along with more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo documentation for all options, including full-page and element capture, device and retina settings, custom CSS or JavaScript, waits, request blocking, cookies and headers, geolocation, caching, signed links, asynchronous webhooks, bulk capture, and the usage API.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/article' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is included on every plan. Create a free ScreenshotNeo account to try it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
FAQ
Does changing the page’s featured image automatically change the Open Graph image?
Only if your CMS or plugin uses that field to generate the og:image tag. Verify the published source rather than assuming the fields are connected.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Can I use a relative image path?
Use an absolute HTTPS URL. It removes ambiguity for crawlers and is the form expected by the protocol examples.
Why does a new post still show the previous preview?
Social platforms cache previews independently. Re-scrape the live URL with the platform’s inspector and check that your own CDN is not serving stale HTML or image bytes.
Should I add several Open Graph images as fallbacks?
You can, but the first og:image is preferred when values conflict. Multiple tags are not a reliable way to force different networks to choose different images.
Frequently Asked Questions
Does changing the page’s featured image automatically change the Open Graph image?
Only if your CMS or plugin uses that field to generate the og:image tag. Verify the published source rather than assuming the fields are connected.
Can I use a relative image path?
Use an absolute HTTPS URL. It removes ambiguity for crawlers and is the form expected by the protocol examples.
Why does a new post still show the previous preview?
Social platforms cache previews independently. Re-scrape the live URL with the platform’s inspector and check that your own CDN is not serving stale HTML or image bytes.
Should I add several Open Graph images as fallbacks?
You can, but the first og:image is preferred when values conflict. Multiple tags are not a reliable way to force different networks to choose different images.
Quick 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.
