I Retired My "85% Knowledge Panel Probability" Claim. Then Google Built the Entity Anyway.

Still no Knowledge Panel. Keep reading — that part matters.

What Google actually built

You can reproduce this:

curl "https://kgsearch.googleapis.com/v1/entities:search?query=ookyet&limit=10&key=YOUR_API_KEY"

{

  "result": {

    "@id": "kg:/g/11z806my44",

    "name": "Qifeng Huang",

    "@type": ["Person"]

  }

}

Three details in that tiny response taught me more than anything I shipped in 2025.

The /g/ MID is machine-minted. You can't register one, buy one, or submit one. Google's entity reconciliation creates it when enough independent sources agree that a person exists. This is the mechanical prerequisite for a Knowledge Panel — the entity has to exist in the graph before anything can be displayed about it.

The node's name is my real name, not my handle. My site declares name: "ookyet". The node says "Qifeng Huang" — pulled from the high-authority anchors (LinkedIn, ORCID), not from my self-declaration. Third-party corroboration outweighs anything you say about yourself. Expected, and honestly a relief: the graph is working as designed.

The Knowledge Graph holds 8 distinct people named Qifeng Huang. Query any of them by real name and you get a crowded namespace. Query ookyet and exactly one node comes back — mine. A coined handle turns out to be a cross-namespace disambiguation key: every external signal converts cleanly because Google never has to ask "which one?"

What I got wrong in the last post

The percentage. There is no such metric.

Google does not expose a "Knowledge Panel probability," a candidate state, or a trigger score. Anyone quoting you a percentage — including 2025 me — computed it from their own weighted checklist and dressed it up as measurement. I've since rewritten the . The panel, if it comes, is a bonus rendered on top of work that already paid out.

Everything above is documented in the open-source repo — including the retired strategies, kept as documented failures with dates, because the failures are the useful part: github.com/ookyet/web3-identity-seo

I'll write the next chapter when the node grows a url.