We scanned your whole web estate. Credit first, then five findings.

Give AI a first-party answer → when a contractor's assistant asks “who issues the CHST, and is it accredited?”, it cites you

The moment hiring runs through AI, whoever the machine reads becomes the authority it quotes — publishing the canonical, machine-readable answer keeps that authority with BCSP instead of drifting to whatever third party happens to answer first.

Make “is this current?” checkable by software → you stay the source of truth when a machine does the asking

Today the authoritative status sits behind a human form and the badge is a picture; a signed, instantly-checkable credential means an employer's system confirms a holder in one call — so verifiers already trusting BCSP get their yes from BCSP, not a copy.

Streamline the everyday pages → the verifier and the candidate who came to you don't bounce first

A 20 MB homepage, missing image alt text, a slow directory, and a bot wall on the jobs board quietly cost you the person already at your door — this is maintenance-grade work a standing crew keeps down, not a redesign.

Ask an AI "who issues the CHST, and is it accredited?" and there's no first-party structured answer to cite. llms.txt is 404, the homepage has zero schema.org, and the only structured data on cert pages is HubSpot's auto VideoObject, describing the video, not the credential.

$ curl -s -o /dev/null -w '%{http_code}' bcsp.org/llms.txt
404
$ curl -s bcsp.org | grep -c 'application/ld+json'
0
$ curl -s bcsp.org/…-chst | grep -o '"@type":"[^"]*"'
"VideoObject"  "MediaObject"      # media only, nothing about the credential

Whoever publishes the canonical answer becomes the citation AI assistants return. That should be you.

The directory is excellent for a person. But the authoritative "is this current?" sits only behind a human form, scoped "for informational purposes only" with "no warranties." No machine-consumable surface returns a yes/no.

directory.bcsp.org: "Detailed Search" form (PHP app)
$ curl -s directory.bcsp.org | grep -c 'application/ld+json'
0
disclaimer (verbatim): "…provides our credential holders with a digital
badge and directory for informational purposes only… makes no warranties…
about the accuracy and authenticity of the information."

When software makes the query, the source of truth drifts to whoever answers it. It should stay here.

My badge holds everything a verifier needs, delivered as HTML for a person's eyes. No JSON, no API, no downloadable proof. The step: the same payload as a signed credential (Open Badges 3.0 / W3C VC) any verifier confirms cryptographically.

badge today:  hosted HTML profile, human-read (my STS-18969 lives here)
badge as VC:  a signed object an agent verifies against BCSP's key:
              { credential: STS, status: active, expires: 2026-12-31,
                issuer: BCSP (ANAB 0646), proof: <signature> }

The payload already exists; only the packaging is human-only. BCSP is placed to be the authoritative issuer for the whole profession.

Absent only because the channel is new: llms.txt, credential JSON-LD (the invisible structured labels search engines and AIs read), a .well-known descriptor. Each is a static file or one schema block, no platform change. All drafted in the kit.

We re-crawled the whole public estate with metrics on. The site works, but it isn't streamlined, and each of these quietly costs visitors:

The homepage weighs 20.7 MB (120 requests). Credential pages average ~1.7 MB; the blog page is 8.1 MB. On a phone connection that's seconds of staring. Compressing images alone would transform it.

~30 images per page ship without alt text (30 of 81 on the homepage, 30 of 34 on typical credential pages), a template-level accessibility gap, likely one shared block, one fix.

The credential directory took 5.5 seconds to load and has no h1 heading; the mentor site also lacks one. The jobs board greeted a normal first-time browser with a bot-challenge wall instead of the page.

homepage        20.7 MB · 120 requests        blog       8.1 MB
directory.bcsp.org   5,552 ms first load · no h1
alt text missing     ~30 imgs/page (template block)
jobs.bcsp.org        403 challenge on first visit

None of this is broken: it's unmaintained-fast, not unusable. It's exactly the kind of list a standing web crew burns down in a week and keeps down forever. Engineer-ready notes accompany every line.