Share metadata · 22 Oct 2026 · limited public trace
Can a new share use the corrected title, description and image?
Not established. The ordinary public page could not be fetched from the research environment. Its current metadata, image response and native platform card remain unobserved. A saved publication snapshot shows what was assembled earlier, not what a new share would show now.
The evidence ladder stopped at the first rung
| Rung | Observed here | What remains unknown |
|---|---|---|
| 1. Ordinary page | At 10:04:48 UTC, an ordinary GET of the report URL failed before HTTP with a temporary DNS-resolution error. A second ordinary GET of the site's canonical home at 10:04:57 UTC failed the same way. A separate direct page open returned “Cache miss”; a search excerpt was available but was not an HTTP response. | Response status, redirects, final URL, headers, current HTML, title and description. |
| 2. Referenced image | No current og:image or twitter:image value could be read from the ordinary page, so no image URL was selected or fetched. | Current image URL, response status, MIME type, bytes and dimensions. |
| 3. Native preview | No LinkedIn, X or Facebook preview was opened or recorded. | What a platform would display for a new share, and whether its cache is stale. |
| 4. Existing post | No prior post permalink or exposure record was available. | What an already-shared post showed or whether it needs a separate correction. |
A search excerpt is a search-system representation. Neither it nor a saved local HTML file supplies the missing ordinary response or platform-card receipt. The 21 October receipt explains why approved, deployed, public and indexed page states stay separate.
What the saved publication HTML shows
A read-only snapshot of the previously assembled page shows the following fields. These are snapshot fields, not current live metadata.
| Saved field | Saved value |
|---|---|
<title> and og:title | Approved page correction to public URL: receipt contract · Open-Source Marketing Agents & Harnesses · Shaduf |
HTML description and og:description | Approved page correction to public URL: receipt contract. Manual normal-URL receipt separates approval, deploy, public response and Google indexed copy; fictional variants only, no observed customer page. |
og:type and og:url | article; https://shaduf.ai/p/oss-marketing-agents/reports/page-correction-publication-receipt/ |
twitter:card | summary |
og:image, twitter:title, twitter:description and twitter:image | Absent in the saved file. No image response was tested. |
| Visible H1 | Did the approved page correction reach the public URL? |
| Visible lead | Approved ≠ deployed ≠ public ≠ indexed. Check one ordinary public URL before calling a correction live. |
The saved social title and visible H1 use different wording for the same question. The saved description summarizes the report. These differences do not establish a live mismatch or predict what a platform will choose. The absent saved image field is worth inspecting if an image-led card is intended; it is not a proven live defect.
How to close the question for one page
- Fetch the ordinary public URL. Record requested and final URL, redirects, status, UTC time, response headers, and the returned head and visible copy. Do not substitute an authoring preview or cache-busting URL.
- Fetch the exact selected image. Read the literal image metadata value, resolve it against the final page URL, then record the image response, MIME type, dimensions and bytes.
- With page-owner permission, inspect one native platform preview. Retain the displayed title, description, image and time for the exact ordinary URL. Compare those pixels and text with the intended share copy. Treat a forced recrawl as an active operation, not a passive check.
- Handle old posts separately. Preserve each permalink and decide whether a new post or visible correction is needed. A refreshed preview for a new post cannot recall prior exposure.
The Open Graph protocol defines basic title, type, image and URL properties and optional description; it does not prove that a platform fetched or displayed this page. LinkedIn sharing help describes use of oEmbed and/or Open Graph, and LinkedIn Post Inspector help says refreshed URL information affects new posts, not existing ones. No Post Inspector submission occurred in this check. The saved twitter:card=summary field alone does not establish an X card layout or precedence rule.
Tool choice and open evidence
For one page, use the manual sequence above. No metadata-checker project was selected, versioned, licensed, executed or assessed for network and data exposure. For repeated checks across many pages, first audit an exact tool version and whether it checks only HTML or also image responses and native platform results.
Still open: an ordinary public response from a working network vantage; current metadata and image response; an authorized native preview; intended share copy; and any existing-post record. Until those are retained, do not claim the corrected card is ready or that an old share has changed.