Civicord · UK · Browse / Conservative and Unionist Party / North East / Pearce Branigan

Campaign site for Pearce Branigan (Conservative and Unionist Party — North East), scraped April 2025, audited September 2026.

Pearce Branigan

View evidenceBefore and afterPropose a correctionIs this your record? Claim itReply if this is wrongMore change stories ↗See what you followQuery The Graph

Snapshot audit, not a current availability check. HTTP success and surname matches do not prove campaign content survived. On-chain fields are on Sepolia testnet; full content is not stored on-chain.

URLs responding — Pearce Branigan's recorded URLs returned successful HTTP responses at the 2026-09-07 audit. This does not establish that campaign content survived.

Conservative and Unionist Party: 65% responding across the party · this candidate: responding.See the cohort ↗

  1. Apr 2025scraped
  2. Sep 2026audited
  3. PendingSepolia

Before and after

April site-wide text vs the 2026-09-21 homepage fetch of https://www.pearcebranigan.uk: 9 sentences still present, 3 no longer found, 28 new. These are candidates for review, not proof a sentence was withdrawn.The April text covers the whole scraped site; the later text is one homepage fetch. A sentence can be missing from that homepage and still exist on another page. A missing sentence is not matched to a replacement.

Before · April 2025

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.

After · 21 September 2026

Not found on the homepage fetch.

https://www.pearcebranigan.uk

Gap: no replacement sentence is matched. The April text covers the whole scraped site; the later text is one homepage fetch. A sentence can be missing from that homepage and still exist on another page.

Before · April 2025

When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies.

After · 21 September 2026

Not found on the homepage fetch.

https://www.pearcebranigan.uk

Gap: no replacement sentence is matched. The April text covers the whole scraped site; the later text is one homepage fetch. A sentence can be missing from that homepage and still exist on another page.

Before · April 2025

Cookie PolicyMarketing cookies allow us to understand the effectiveness of our marketing campaigns.

After · 21 September 2026

Not found on the homepage fetch.

https://www.pearcebranigan.uk

Gap: no replacement sentence is matched. The April text covers the whole scraped site; the later text is one homepage fetch. A sentence can be missing from that homepage and still exist on another page.

New on the later homepage, not matched to a removed sentence

Propose a correction

If a URL, name, or sentence on this record is wrong, send a sourced request. It is queued for a person to review. It does not change the audit, the April scrape, the sentence comparison, or the Sepolia record.What is verified, and what is not.

Review queue

Requests stored for this record. A request is not an edit.

    Is this your record?

    If you are Pearce Branigan or work on their campaign, you can claim this record. Say how a reviewer could verify it — a campaign-domain email, a link on the live site, or your Democracy Club profile. A claim is queued for a person to check; it grants no edit access and changes nothing until verified.

    Content chronology

    transformedLow text overlap with the compared archived page — inspect both sources · 5% of April tokens still found

    Websites

    Respondinghttps://www.pearcebranigan.uk

    What changedSurname absent from the response body — a weak signal that needs review

    • HTTP result: Responding (HTTP 200) at the 2026-09-07 audit
    • ↳ Redirect destination at audit: https://www.conservatives.com/
    • Candidate-name signal: surname not found in the response body (heuristic only)

    Source evidence and excerpts

    These are short excerpts from the April 2025 scrape, not the later wording and not complete archived pages. Original filenames identify the stored extracts. Browse the Campaign Lab source dataset ↗

    Open the compared Wayback capture ↗

    Scrape excerpts — April 2025 · 8 shown
    PageCharsOpening excerpt
    content_14.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_7.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_15.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_5.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_11.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_6.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_17.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_10.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    Agent viewInspect the data and verify the recordGraph live

    The audit ledger above is a static snapshot. The buttons below run live queries against The Graph and the ledger JSON — only when you click them. Nothing fetches automatically and nothing here is mocked.

    1 Free ledger JSON

    /api/candidates/94344.json

    Static audit record — websites, status, ENS hint.

    2 WebMCP join

    Preferred agent tool — live Graph + ledger verdict.

    compare_onchain_to_ledger(id="94344")
    -> { onchain, ledger, verdict[] }

    3 The Graph (live)

    On-chain p94344.civicord.eth via/api/graph (Studio proxy) — person id, not seat slug.

    {
      candidate(id: "94344") {
        id ensName status url personName textRecordCount
        registeredAt registeredAtBlock owner
      }
      _meta { block { number } hasIndexingErrors }
    }

    Live queries run on demand; a failure is shown honestly, never replaced with a cached response. Verify independently: ENS ·resolver ·Subgraph Studio ·/api/graph ·openapi.yaml ·source

    Jurisdiction

    Reading…

    Reading the public record…

    Reading /api/… — the same static JSON an agent pays for.

    ↑↓ move · ↵ open · Esc close