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 minutePC 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 & 11Set og:url to the stable, absolute URL your site considers the page’s identity, and use that same identity consistently across duplicate URL variants. Then inspect the HTML actually served to crawlers and refresh the preview with the destination platform’s current tools if an old preview persists.
What og:url does
The Open Graph Protocol defines og:url as the canonical URL used as an object’s permanent ID in the graph. It belongs in the document’s HTML <head>. The protocol identifies four required basic properties: og:title, og:type, og:image, and og:url.
As an Amazon Associate I earn from qualifying purchases.
That makes og:url more than a link to repeat in a preview: it tells Open Graph consumers which URL identifies the object. If the same page is reachable through variants such as tracking parameters, session URLs, or duplicate routes, choose the one stable public URL intended to represent it rather than assigning each variant a different identity.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the URL that represents the page
Decide your preferred URL form before adding metadata. Be consistent about HTTPS, hostname (such as www or no www), path, and trailing slash. Use the selected URL in og:url, and check that the page’s canonical link and redirects do not point to a different intended identity.
#1 Best Overall
For search, Google describes canonicalization as selecting the most representative URL among duplicate pages; redirects and rel="canonical" annotations are among the signals it considers. Search canonicalization and social preview handling are separate systems, so consistency is a sensible implementation goal, not a guarantee that every platform will behave identically. See Google’s canonicalization guidance.
Add the Open Graph metadata
Put the properties in the page head and use an absolute, stable URL for og:url. For example:
<head>
<title>Example article</title>
<link rel="canonical" href="https://example.com/articles/example/">
<meta property="og:title" content="Example article">
<meta property="og:type" content="article">
<meta property="og:image" content="https://example.com/images/example.jpg">
<meta property="og:url" content="https://example.com/articles/example/">
</head>Replace the example values with the page’s actual title, type, publicly accessible image URL, and chosen identity. Keep the canonical link and og:url aligned when they are meant to identify the same page. LinkedIn also has image requirements specific to its platform; consult its current guidance rather than assuming one image rule covers every network: LinkedIn Help on Open Graph.
Check for duplicate URL variants
Review the URLs that can reach the same content. Do not treat these as interchangeable if your site has already selected a preferred identity.
| Check | What to verify |
|---|---|
| Stability and access | The chosen URL is stable and publicly accessible, not a temporary session or tracking URL. |
| Intended identity | The URL matches the page identity selected by your site’s canonicalization plan. |
| Redirects | Alternate forms resolve consistently rather than sending visitors or crawlers to conflicting destinations. |
| Metadata | The served page emits the same intended identity in og:url. |
Inspect what crawlers receive
- Open the public page and inspect its served HTML, not only the CMS editor or template source. Confirm the expected Open Graph tags appear in the document head.
- Check the page’s canonical link and redirect behavior, including the variants that may have been shared. Look for a CMS template, plugin, or rendering layer that could insert or overwrite metadata.
- Use a platform-specific inspector where available. The Open Graph Protocol documentation links to Facebook’s Object Debugger; LinkedIn documents its Open Graph and image requirements in its help page.
- If the preview is still old after fixing the markup, re-inspect the page and use the target platform’s current refresh procedure.
Do not assume that changing og:url immediately updates an existing preview. The sources above do not establish a universal cache lifetime or guaranteed refresh delay; behavior and refresh procedures are platform-specific.
Or skip the browser setup
If you need to inspect a page visually after checking its metadata, ScreenshotNeo can capture a screenshot or PDF with one request. It accepts and removes known cookie-consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed. Its MCP server lets AI agents take screenshots, and its free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Example cURL request (replace the URL and API key):
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/articles/example/ -o shot.webpSee the ScreenshotNeo API documentation for request options. Learn more at ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.
Quick Recap
Best Value
Common problems and fixes
- The wrong URL appears in the preview: Inspect the publicly served head and check whether a CMS, plugin, or rendering layer emits a conflicting
og:url. Align it with the intended stable page identity. - Tracking or session URLs seem to create separate identities: Use the stable public URL for the page’s
og:urlwhen those variants represent the same content, and review redirect and canonical behavior. - The metadata is missing from inspected HTML: Confirm the tags are actually rendered into the document head delivered to crawlers, rather than only present in an editor or client-side state.
- A corrected tag does not change an existing preview: Recheck the served markup, then follow the destination platform’s current inspector or refresh procedure. No universal refresh time is established.
- The image works on one network but not another: Check the target platform’s specific image requirements; LinkedIn explicitly has its own requirements.
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.
