SR
SEO Registry
For employers

Verify SEO candidates
against a real audit.

Look up a candidate by name in the public registry, or check the verifiable badge URL on their CV. Each tier maps to a specific seniority level via a published rubric. Or run candidates through the test directly with the hiring kit.

Why the credential means something

A real signal, not a checkbox.

01

Audited, not examined.

An SEO Registry tier is earned by auditing a real (deliberately broken) Next.js e-commerce site for hours, not by passing a multiple-choice test. The signal is closer to a portfolio review than a certification exam.

02

Manual-only, by design.

The test site blocks crawlers, audit suites, and AI agents at the network level. Candidates can't pipe the test through GPTBot or paste in a Sitebulb report — the credential measures auditing skill, not tool ownership.

03

Standardised across candidates.

Every credential is graded against the same private master answer key by the same rubric. A Specialist held by candidate A means the same thing as a Specialist held by candidate B. No reviewer drift.

Two ways to verify

Look them up. Or have them prove it.

Most candidates put their badge URL on their CV or LinkedIn — visit it directly to confirm name, tier, and date. For candidates who haven't shared a badge, look them up in the public registry by name. Candidates who opted out of public listing won't appear there; you'll need to ask them for the badge URL directly.

What you'll see
  • Candidate name as registered
  • Tier earned (Apprentice / Practitioner / Specialist / Guru)
  • Score: issues found out of total planted
  • Submission date — credentials are dated, not lifetime
  • Country (if the candidate added one)

Candidates' submitted findings are private — only the tier is verifiable. Hiring teams running the test themselves see findings on their dashboard.

Tier-to-seniority rubric

By seniority, not by gut feel.

RoleExpected tierHiring signal
Junior SEOApprentice or higherBelow: re-train. Above: promotable.
Mid-level SEOPractitioner or higherBelow: at-risk. Above: ready for senior brief.
Senior SEOSpecialist or higherBelow: probably a generalist. Above: the real thing.
Principal / Head of SEOSpecialist or GuruBelow: investigate. Guru: rare and hire on the spot.

Tier thresholds adjust to seniority — we don't expect a junior candidate to find Guru patterns, and we don't celebrate a senior who only finds Apprentice-tier issues.

Or run the test in your own pipeline

The hiring kit.

For teams who want their own copy of the test as part of an interview loop. Anonymous candidate links, a private results dashboard, side-by-side comparison, and the same scoring rubric the public registry uses.

Anonymous candidate links

Each candidate receives a unique URL. No login required. No PII shared with us beyond what they choose to submit.

Private results dashboard

A simple grid view of every candidate's score, tier, and findings. Sortable by tier, by pillar coverage, by submission time.

Scoring rubric, scaled to seniority

Junior, Mid, Senior, and Lead presets. We tell you whether the score is in-line, below, or above the bar for the role.

Side-by-side comparison

Compare any two candidates' findings. We flag where one caught an issue the other missed.

Bulk-invite by CSV

Upload a list of candidate emails, send all invitations in one click, track who has and hasn't submitted.

No cost

No seat pricing, no candidate cap. The hiring kit runs on the same public-good infrastructure as the public credential.

The dashboard

One screen. Every candidate.

seoregistry.org/hiring/your-team
CandidateSubmittedScoreTierAction
Candidate #422 days ago47 / 60SpecialistView findings
Candidate #413 days ago55 / 60GuruView findings
Candidate #405 days ago29 / 60PractitionerView findings
Candidate #395 days ago34 / 60PractitionerView findings
Candidate #386 days ago16 / 60ApprenticeView findings
Two paths

Verify, or run the test.

Either look up an existing candidate's tier in the public registry, or sign up as a hiring team to run the test inside your own interview loop.