What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To prevent a broken or outdated link thumbnail after a domain change, make the redirect destination, canonical URL, Open Graph page URL, and image URL agree. Use a permanent server-side redirect for a lasting move, ensure the final page and its og:image are publicly fetchable, then check the shared URL with the platform’s own preview inspector when available. A browser displaying the image does not prove a social crawler can retrieve it.
Why redirects break link thumbnails
A redirect tells a request to go somewhere else; it does not by itself guarantee that every sharing platform will use the destination page’s metadata or retrieve its image. Problems arise when the old URL redirects to a different page than expected, the final page advertises a conflicting canonical or Open Graph URL, or the image cannot be fetched by the platform’s crawler.
As an Amazon Associate I earn from qualifying purchases.
Open Graph defines og:url as the object’s permanent identifier and og:image as its representative image. Check those values on the final page returned after the redirect, not only on the old URL. Open Graph Protocol
Use a redirect that matches the move
For a durable domain or page move, Google recommends a permanent server-side redirect when possible. Its guidance lists HTTP 301 and 308 as permanent redirects, and 302, 303, and 307 as temporary. Google treats permanent redirects as a signal that the target should become canonical; temporary redirects do not send the same signal. These are Google Search interpretations, not a guarantee that every social-sharing crawler handles redirects identically. Google Search Central: Redirects and Google Search
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
| Redirect type | Use when | Google Search interpretation |
|---|---|---|
| Permanent: 301 or 308 | The page or domain has moved for good. | A signal that the destination should become canonical. |
| Temporary: 302, 303, or 307 | The move is temporary and the source URL should remain the intended result. | Does not provide the same canonical signal as a permanent redirect. |
Google says server-side redirects have the strongest chance of being interpreted correctly among the methods it lists, and recommends them for permanent moves. Its canonical guidance describes HTTP redirects as the quickest way to affect canonicalization. Those recommendations apply to Google Search. Google Search Central: Consolidate duplicate URLs
Diagnose and fix the preview in order
- Choose one preferred destination. Decide which protocol, host, and page URL should remain public—for example, HTTPS and either the
wwwor apex host. Google recommends choosing a preferred URL and redirecting alternate versions to it. Make internal links point consistently to that destination. - Trace every redirect hop. Request the exact old page URL and note each status code and
Locationdestination. Confirm that the chain ends on the intended page, not a loop, unrelated homepage, login screen, or unexpected host variant. Checking each hop is a practical diagnostic; the cited sources do not establish social crawlers’ redirect limits. - Inspect the final page’s HTML head. Verify that the response after redirects contains the intended
og:title,og:image, andog:url. Setog:urlto the preferred final page URL, and keep it consistent with the canonical URL and other canonical signals. Google cautions against contradictory canonical URLs sent through different methods. Open Graph Protocol · Google canonical guidance - Check the image URL independently. Open the exact
og:imageURL and confirm it returns the intended image without requiring a signed-in browser session or access to a protected directory. Ensure the platform’s crawler is not blocked from fetching it. LinkedIn identifies crawler blocking and protected image hosting as reasons a preview image may not appear. LinkedIn image specifications and sharing guidance - Check the relevant platform’s image requirements. Requirements differ, so do not assume one size or limit applies everywhere. LinkedIn’s documented sharing-module requirements list a maximum file size of 5 MB, minimum dimensions of 1200 × 627 pixels, and a recommended 1.91:1 ratio. These are LinkedIn specifications, not universal rules.
- Inspect the exact URL you plan to share. Use the platform’s official preview inspector or debugger when available, then check what it reads. A browser’s rendered page is not necessarily the same as crawler output.
When the browser shows the image but the preview does not
The image can load for you while remaining unavailable to a sharing crawler. Check whether the file requires authentication, sits behind protected access, or is blocked from the crawler. Also confirm that the final page points to that same image with og:image and that the preview inspector is checking the exact URL you share. LinkedIn explicitly warns that crawler blocking or a protected image location can prevent its preview image from appearing. LinkedIn Help
Rank #2
If the preview still shows the old thumbnail
Recheck the redirect destination, final HTML metadata, and image accessibility first; then inspect the exact URL again with the platform’s own tool, if available. A stale preview may involve caching, but cache lifetimes and current debugger workflows vary and are not established here. Do not assume a particular refresh interval.
Recommended Free Tools
Or skip the browser setup
For a quick visual check of the final destination, ScreenshotNeo can capture the page through one GET request. Use this cURL example with the URL you want to inspect:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo 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, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server offers screenshot and page-information tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. A screenshot helps inspect the page visually, but it does not replace checking the HTML metadata or the social platform’s own preview output.
Sign up for ScreenshotNeo’s 1,000 free screenshots a month, with no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Does a 301 redirect guarantee the new thumbnail will appear?
No. It is a permanent-move signal for Google Search, but it does not guarantee identical handling by each social-sharing crawler or ensure that the destination’s image is fetchable.
Rank #4
Are LinkedIn’s image dimensions required by every platform?
No. The 5 MB maximum, minimum 1200 × 627 pixels, and recommended 1.91:1 ratio are LinkedIn sharing-module specifications, not universal requirements.
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.
