Page publication receipts · 21 Oct 2026 · documentation synthesis
Did the approved page correction reach the public URL?
Approved ≠ deployed ≠ public ≠ indexed. Check one ordinary public URL before calling a correction live. A saved edit, successful build or Google live test answers a different question.
One-page receipt: what to retain
Choose a distinctive exact sentence from the approved copy. Then collect the narrow evidence for each stage. Keep unknown fields unknown rather than filling them from a deploy notice.
| Stage | Record | What it establishes |
|---|---|---|
| Approved | Exact marker; approved artifact/version or digest; intended URL, canonical and robots policy; approver and time. | The copy and policy to compare. Approval does not put it on a server. |
| Source / deploy | CMS revision or repository commit and actual publish source/path; build or deployment identifier, result and time. | The publishing process ran. It does not show what the public URL returned. |
| Public URL | Independent normal-URL fetch: requested and final URL, redirect chain, status, UTC time, vantage and request variant; exact returned marker or absence; excerpt and response/body digest. | Whether this checked public variant served the approved copy at that time. |
| Policy / cache | Returned HTML and HTTP canonical/robots; Cache-Control, Age, Vary, ETag or Last-Modified, plus CDN header if present. | Whether the response has intended index signals and clues for a stale variant; not a universal cache purge. |
| Google indexed copy | When access exists: URL Inspection indexed view, last crawl, Google-selected canonical and indexed/rendered content where available. | A separate, potentially delayed observation. A live test or public 200 does not establish indexed copy. |
For any mismatch, record an exception owner and next check. Compare the exact sentence with context; a digest only compares like representations. Source Markdown, built HTML and compressed response bytes need not hash alike. GitHub Pages publishing source · HTTP caching standard · Google URL Inspection
Run the manual check first
- Compare the approved artifact and marker with the saved source and deployment result. On GitHub Pages, a branch/folder or Actions artifact is configured as the publishing source and a workflow deploys the site. A successful deployment status supports the deploy stage only. Other CMSs need their own revision and release records. GitHub Pages deployment status API
- From outside the authoring preview, fetch the ordinary, unmodified public URL, follow redirects, and retain the final response and timestamp. Check status, final URL, exact text marker, canonical and robots directives.
- If geography, device, login or CDN edge can change copy, check the relevant authorized variants and state coverage. A cache-busting query or hard refresh can diagnose a stale path, but it is not the normal-URL receipt.
Age estimates a cached response's age; no Age header does not prove origin contact. Vary may select different stored responses. RFC 9111 permits fresh cache reuse and conditional revalidation. One fresh fetch does not prove every variant was purged. RFC 9111, sections 4–5
Fictional correction: three possible receipts
All versions, copy, times, headers, URL and states in this table are invented. They show how to stop a claim at its actual evidence boundary, not what happened on a live offer page.
| Observed state in this example | Next check | Owner / stop |
|---|---|---|
Public match. Approved v2 says “Offer ends 30 November”; CMS r42 and deploy d42 succeed. At 10:15 UTC, a normal fetch of https://example.test/offer returns final /offer, 200, that sentence, intended self-canonical and no noindex. Index status was not checked. | Retain response, headers, time and variant. Inspect indexed copy separately only if search visibility matters. | Web owner closes the observed variant receipt. Do not claim all visitors or Google have v2; search owner keeps index state unknown. |
Stale variant. Same v2 and d42, but at 10:16 UTC one CDN vantage returns v1 “Offer ends 15 November”, 200 and Age: 600. | Recheck the ordinary URL from affected and other authorized vantages; compare origin/deploy artifact and cache settings. If appropriate, invalidate that cache under site policy, then refetch the ordinary URL. | Web/CDN owner keeps publication open for the known stale variant. One fresh response does not prove a universal purge. |
| Public v2; Google unknown. Normal URL matches v2, but URL Inspection is unavailable or the last indexed crawl predates release. | With property access, compare indexed and live views, last crawl, Google-selected canonical and indexed content where available. Request indexing only if warranted. | Search owner records indexed copy unknown. Do not turn a live-test “available” result into an indexed-v2, impression or rank claim. |
Google is a separate boundary
URL Inspection's default indexed view describes Google's most recently indexed version, not necessarily the current page. Its live test asks whether a page can likely be indexed; it does not prove inclusion, selected canonical or the intended copy served to users. The live test follows redirects but does not disclose the final URL it tested. An indexing request is not an inclusion guarantee. Independently inspect HTML robots, X-Robots-Tag and canonical signals in the public response; an HTML canonical is a preference, not a selection guarantee. URL Inspection · robots directives · canonical methods
This receipt concerns whether a correction was served. It does not establish traffic or causal search effects. The 20 October page-priority report covers what to diagnose before a content edit. If email or social already links to the page, retain the sent artifact, URL, timestamp and exposure record; fixing the page cannot retract a sent message or public post. See the 15 October channel-receipt report.
Do not add a monitor for one correction
Repeat the manual receipt for the one page. If many owned public URLs need recurring checks, a reviewed post-deploy script could fetch each final public URL and compare the approved marker, status and policy fields while keeping response receipts. Comparing only a source tree or build artifact remains a source/deploy check. No monitor project, executable, licence or data/network exposure was selected or audited here. Before choosing one, verify its exact version, licence, target permissions and outbound behavior, then test normal-final-URL and relevant-variant coverage. An alert is an exception signal, not approval, cache parity, Google indexation or ranking proof.
Still needed for a real decision: approved artifact and marker; authorized final URL; source and deploy identifiers; an independent public response with variant scope and headers; and Search Console access only if indexed state matters. Without them, this is a decision contract, not a claim that a customer page changed.