Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To refresh a Facebook link preview, submit the exact page URL to Facebook’s Sharing Debugger, inspect the Open Graph values Facebook scraped, fix the tags on your page, and submit the URL again. If the interface shows Scrape Again, use it after the fix. The debugger can reveal whether Facebook is seeing an old title, description, image, or canonical URL, but it cannot repair your page source for you.
Meta’s current labels, login requirements, and availability can change. The Open Graph protocol identifies Facebook’s parser/debugger, while a June 22, 2026 guide describes the current workflow as the Facebook Sharing Debugger with scraped values, warnings, and a Scrape Again action. Treat the exact buttons you see as subject to change.
![Marketing Magic: How I produced 7 billion views, 50 million social media followers and $250,000,000 in yearly revenue without paid advertising! ... ... Manuel Suarez [Hardcover] Manuel Suarez](https://m.media-amazon.com/images/I/41DEmJulOkL._SL160_.jpg)
What the Facebook Open Graph Debugger checks
When someone shares a URL, Facebook’s crawler reads metadata in that page’s <head>. The debugger shows what the crawler found rather than what your content-management-system editor intended to publish. That distinction explains many “Facebook is showing the wrong image” reports: the page may contain an old tag, a blocked asset, or several competing tags.
Recommended Free Tools
The Open Graph protocol defines four basic properties for an object:
#1 Best Overall
| Property | Purpose | What to verify |
|---|---|---|
og:title |
The headline used for the shared object. | It is the intended title and appears only once unless you have a deliberate reason to provide alternatives. |
og:type |
Describes the object, such as an article or website. | The value matches the page you are sharing. |
og:image |
Points to the image Facebook should display. | The URL is absolute, public, and points to the intended file. |
og:url |
The canonical URL and permanent identifier of the object in the social graph. | It matches the canonical version you want Facebook to associate with the share. |
og:description is optional in the protocol but generally recommended. Image metadata can also include MIME type, width, height, a secure alternate URL, and alternative text. The protocol says that a page specifying og:image should also specify og:image:alt.
If the same property appears more than once, the first value from top to bottom is preferred when values conflict. A later, “correct” og:image will not reliably win over an earlier wrong one.
How to use the debugger
-
Open the Sharing Debugger
Find Meta’s Facebook Sharing Debugger and open it in a browser. The official page’s current labels and access requirements are not stable enough to assume a particular login screen, so follow the prompts shown to you.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Submit the exact URL
Paste the full page address, including the correct protocol (
httpswhere applicable), path, query string, and trailing slash when your site treats those forms as different URLs. Submit the URL rather than your home page or a shortened redirect.Rank #2
-
Read the scraped values and warnings
Compare the title, description, image, type, and URL displayed by the tool with the source you intended to publish. Record warnings before changing anything. A warning about an image is more useful when you know which image URL Facebook actually fetched.
-
Fix the page source
Edit the template, SEO plug-in, CMS fields, or server-rendered HTML that generates the page’s
<head>. Save and deploy the change. Do not rely on changing text in a social post; the source tags are what the crawler reads. -
Request a fresh scrape
Submit the same URL again. If the interface presents Scrape Again, select it after the new HTML and image are publicly available. A fresh scrape does not guarantee that every existing post or preview changes immediately; old shares can retain the data they already stored.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Build valid Open Graph metadata
A minimal article head can look like this:
<meta property="og:title" content="How to repair a Facebook link preview">
<meta property="og:type" content="article">
<meta property="og:url" content="https://www.example.com/guides/facebook-preview">
<meta property="og:image" content="https://www.example.com/images/facebook-preview.jpg">
<meta property="og:image:alt" content="A browser showing a corrected link preview">
<meta property="og:description" content="A practical guide to checking and refreshing Open Graph metadata.">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">Use the syntax your framework emits, but ensure these tags are present in the server response that an unauthenticated crawler receives. Client-side JavaScript that inserts tags after page load may not be available to a social crawler.
Rank #3
Keep the canonical URL consistent
Set og:url to the canonical address you want associated with the object. Check redirects, HTTP-to-HTTPS upgrades, host aliases, and trailing-slash rules. If the debugger was submitted the non-canonical variant while the page advertises another URL, compare both versions and standardize your links.
Remove competing tags
View the raw HTML, not only the CMS preview. Themes, SEO extensions, and custom templates can each output their own og:title or og:image. Because the first repeated property is preferred, put the intended value first only as a temporary diagnostic; the durable fix is to remove the duplicate source.
Make the image fetchable
Use an absolute image URL and test it in a private browser window. Check that the response is an image, not an HTML error page or a login redirect. The image host must allow the crawler to reach it without a session cookie. If you use a CDN, verify that the deployed object exists in every region your site serves and that an access rule is not blocking automated requests.
Why a preview can remain wrong
Cached metadata
A previous crawl may be what the debugger is showing. Correct the source, then request another scrape. Do not infer a universal cache duration from third-party claims; the practical test is whether the new scrape displays the changed values.
Inaccessible or slow assets
A page can return successfully while its image times out, redirects repeatedly, requires authentication, or is blocked by a firewall. Test the exact image URL independently and inspect server logs for denied or incomplete requests.
Crawler restrictions
Review robots, WAF, CDN, and rate-limit rules that distinguish bots from ordinary browsers. A rule that blocks Facebook’s crawler can leave the debugger with incomplete metadata even when the page works for you.
Duplicate or conflicting metadata
Search the rendered source for every occurrence of og:title, og:description, og:image, and og:url. The protocol’s first-value rule makes duplicate tags a concrete, protocol-backed cause of an unexpected result.
Redirects and URL variants
Debug the address that people actually share. A redirect can lead Facebook to a different document, while query parameters can identify a separate cache entry. Decide which URL is canonical and use it consistently in internal links, structured metadata, and campaigns.
A diagnostic workflow for the most common symptoms
| Symptom | What to compare | Likely check |
|---|---|---|
| Old title or description | Debugger’s scraped text versus current page source. | Deploy the changed tags, then request a fresh scrape; look for a second SEO plug-in outputting the old value. |
| Wrong image | Image URL shown by the debugger versus the intended URL. | Find earlier og:image tags, verify the image is public, and test the exact URL without cookies. |
| No image or an image warning | Image response and server logs. | Check redirects, MIME type, firewall rules, timeouts, and whether the URL returns a real image. |
| Changes work in a browser but not in Facebook | Raw server HTML versus JavaScript-rendered DOM. | Render the tags server-side or through the CMS output that the crawler receives. |
| Debugger shows a different page | Submitted URL, redirects, and og:url. |
Remove accidental redirects and align the shared URL with the canonical URL. |
Verify the fix before announcing it
- Fetch the page while logged out and inspect the raw
<head>. - Confirm one intentional value for each core property.
- Open the image URL directly and verify it does not require authentication.
- Check that the canonical URL and
og:urlagree. - Submit the exact URL again and use Scrape Again when available.
- Test a newly created share separately from an older post; previously stored previews may not be rewritten.
Or skip the browser setup
The debugger is the right tool for seeing which Open Graph tags Facebook scraped. If you also need a repeatable visual capture of the corrected page—for QA, an issue tracker, or an AI workflow—ScreenshotNeo can take the screenshot through one HTTP request. It does not replace the metadata inspection above; it gives you an automated image or PDF of the rendered result.
API documentation: https://screenshotneo.com/docs/
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Replace the example target with the page you have just fixed. ScreenshotNeo removes cookie-consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed as clean shots, and response headers identify the page verdict and billing result. Its MCP server lets Claude, Cursor, or another MCP client call take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000 shots. Start with the free ScreenshotNeo account.
Operational and cost considerations
For a one-off correction, the Facebook debugger and a source inspection are sufficient. For a site with frequent publishing, add a deployment check that fails when required tags are missing, duplicated, relative, or inconsistent with the canonical URL. Keep image files at stable URLs so a content update does not silently point old shares at a deleted asset.
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 problemsSeparate metadata correctness from visual correctness. The debugger reports what Facebook parsed; a screenshot service can show whether the rendered page has an obstructing banner, a broken layout, or content hidden behind a consent layer. Capture only after the page is publicly reachable, and record the URL, deployment revision, and scrape result so a later regression can be traced.
Frequently asked questions
Frequently Asked Questions
Is the Facebook Sharing Debugger the same as the Facebook Object Debugger?
The Open Graph protocol reference identifies Facebook’s official parser and debugger as the Facebook Object Debugger. A June 2026 guide uses the current name “Facebook Sharing Debugger.” Meta’s branding and interface can change, so follow the current label shown on the official tool.
Will scraping a URL change previews in posts that were already published?
Not necessarily. A new scrape verifies the current page data, but an existing post can retain the preview it stored when it was created. Check a newly created share after confirming the corrected scrape.
Should I add several og:image tags for different layouts?
Only when you intentionally support multiple images and understand the ordering. When values conflict, the first repeated property is preferred, so remove accidental duplicates rather than hoping a later tag will override the first.
Outdated 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 matchPC 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 & 11Can I diagnose an image problem without changing the page?
Yes. Open the exact image URL while logged out, inspect its response and redirects, and compare it with the image URL shown by the debugger. This isolates access failures from metadata errors.
Does ScreenshotNeo validate Facebook’s Open Graph tags?
No. ScreenshotNeo captures the rendered page for visual QA. Use Facebook’s debugger to inspect the metadata Facebook scraped, and use ScreenshotNeo when you need an automated screenshot or PDF of the page after the fix.
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.
