← All certificatesCERTIFICATE / 4566455c-6e69-43d2-9bf0-8dd264773450
You are viewing a preserved historical record.View the current certificate →

Publication evidence certificate

Google Desktop Discover: My Client’s 10,458% Traffic Surge & What Desktop Expansion Means

Site signatureSignature verified

This record’s cryptographic signature was checked against the site signing key in its supplied Website Identity evidence. Signing-time authorization remains indeterminate. This does not verify the author’s identity, ownership, or the truth of the content.

Review signature checks

https://brianwinum.com/google-desktop-discover-my-clients-10458-traffic-surge-what-desktop-expansion-means/

Source author

As attributed by the publisher

Source publisher

Publisher-submitted attribution

First published by source

Publisher-reported date

The evidence behind this record

Submission signature

The submission was authenticated using the key enrolled for the source site.

Verified

Manifest digest

The retained manifest bytes match the SHA-256 digest in the signed submission.

Verified

Publisher site control

A signed public HTTPS challenge verified control of the source site during enrollment. This does not verify author identity, ownership, or continuing control.

Verified at enrollment

Native ContentLedger evidence

The record-scoped Bundle v3 passed the current portable verifier. Manifest bytes and source attribution match this certificate. Signing authorization remains a separate limitation.

Valid with limitations

Native record signature

Cryptographic signature result for the submitted record; this does not independently establish publisher or author identity.

Verified

Independent timestamp

Repository acceptance is a repository clock time. Submitted timestamp structures do not establish a verified Bitcoin attestation.

Not independently verified

Live source content

The source page has not been fetched or compared with the submitted content fingerprint.

Not checked

A history that stays intact.

04 public records

Select a public record to inspect its metadata and evidence. Records hidden by an earlier withdrawal remain unavailable after republication.

  1. 04

    Publication revision recordedLatest

    a51b8d33-8065-4a1f-bf54-54504bf636fb
    View record 04
  2. 03

    Publication revision recorded

    37b32c70-1f57-4a5a-8b5b-c21053c79859
    View record 03
  3. 02

    Publication revision recorded

    58f845f6-db71-458b-b195-f73c71c8ad41
    Viewing record
  4. 01

    First publication recorded

    67f7c3ec-81ff-4dab-b972-fd56dffc60e9
    View record 01

Inspect the recorded evidence

Record 02

Download the retained submission and repository receipt. These files document the checks shown above.

Manifest bytes · SHA-256

874421d2f208e35adb00d02ca847c8e207320e62a8d68113cd61280d297beb85

Identifies the manifest file, not a fresh comparison with the live article.

Submission bytes · SHA-256

98a769b171c871a8db783ae7e27926befcea3ce516ca52300fe8750f35f59bd5
Inspect manifest metadata
{
  "$schema": "https://brianwinum.com/?wal_manifest_schema=2",
  "digests": [
    {
      "algorithm": "sha-256",
      "canonicalization": "wp-contentledger-content-v1",
      "scope": "canonical-content",
      "value": "5c61acc7bf9b374e6bea934ed709ddd5217d1195c4752fdb53c8a75e5a3f7e57"
    }
  ],
  "entryId": "urn:uuid:a9976af2-46ae-4b4f-a7c9-e61beb40602a",
  "evidenceScope": [
    "canonical-content-integrity",
    "publisher-controlled-recording"
  ],
  "generator": {
    "name": "WP ContentLedger",
    "version": "0.13.29"
  },
  "limitations": [
    "Origin evidence does not by itself prove legal ownership, original authorship, first publication, or third-party preservation.",
    "Internet Archive status and later evidence artifacts are maintained separately so this immutable manifest is never rewritten."
  ],
  "manifestVersion": "2.0",
  "provenance": {
    "evidenceCapturedAt": "2026-11-03T21:51:25+00:00",
    "recordSource": "bulk",
    "sealedFromPreviouslyCapturedEvidence": false
  },
  "sealedAt": "2026-11-03T21:51:25+00:00",
  "subject": {
    "author": {
      "name": "Brian Winum",
      "url": "https://brianwinum.com/author/brian-winum/"
    },
    "canonicalUrl": "https://brianwinum.com/google-desktop-discover-my-clients-10458-traffic-surge-what-desktop-expansion-means/",
    "dateModified": "2026-07-28T19:24:06+00:00",
    "datePublished": "2025-04-21T09:00:00+00:00",
    "description": "Discover is coming to desktop, and most publishers aren't ready. Here's the optimization blueprint that produced a 10,458% traffic increase for one of my YMYL clients.",
    "featuredImage": "https://brianwinum.com/wp-content/uploads/2026/07/google-desktop-discover-traffic-surge-desktop-expansion-featured-robot-cleaning-examining-desktop-branded.webp",
    "language": "en-US",
    "postType": "post",
    "publisher": {
      "name": "Brian Winum",
      "url": "https://brianwinum.com/"
    },
    "taxonomies": {
      "category": [
        {
          "name": "Blog",
          "slug": "blog"
        },
        {
          "name": "SEO",
          "slug": "seo"
        }
      ],
      "post_tag": [
        {
          "name": "EEAT",
          "slug": "eeat"
        },
        {
          "name": "Google Discover",
          "slug": "google-discover"
        },
        {
          "name": "Reddit",
          "slug": "reddit"
        },
        {
          "name": "Twitter",
          "slug": "twitter"
        }
      ]
    },
    "title": "Google Desktop Discover: My Client’s 10,458% Traffic Surge & What Desktop Expansion Means",
    "type": "WebPage"
  }
}

This record documents submitted publication metadata and evidence. It does not establish legal ownership, original authorship, accuracy of the source material, or an independently verified publication time.