Name a host and the router reads a few of its pages: the schema.org
markup first, the words second. Out comes an ALP meta with every page anchor checked
against the pages it points to. Nothing is stored here; what you do with the file is
up to you.
What the router read
Axis
Value
From
Anchors, checked against the pages
Axis
Page
State
The meta
What to do with it
Read it. Everything in it is a claim about your site; change what is wrong and drop what you do not want to promise.
Publish it at /.well-known/alp.json on the host, served as application/json.
The router's crawler reads the file from there, checks the anchors against your pages, and picks up a changed file within a day. A meta a site publishes itself scores higher than one the router wrote on its behalf.
The list of hosts the crawler visits is kept by hand while the index is a preview.
A few calls a minute per client; a host asked for again within ten minutes gets the same answer. The router reads at most six pages and keeps to robots.txt.