What traveller.org publishes for search engines and for AI answer engines, what happens on its own, and the one thing not to do in Search Console.
Two kinds of machine look at this site now, and it is built for both.
Both are fed automatically by the build. There is no separate SEO tool, no plugin, and nothing to keep up to date by hand.
You can open every one of these yourself; they are ordinary public addresses.
/llms.txt — the site in one page for an answer engine: what the archive is, its
sections, and every country with its photograph and gallery counts./llms-full.txt — the deep version: the full text of every journal letter, the
banknote library, and the gallery inventory./sitemap.xml — every public page, for search engines./robots.txt — what crawlers may look at.All four are rebuilt every time the site is published, from the same data the pages come from. They cannot fall behind the site, and no one has to remember them.
Each page also carries, generated from its own record: a description, the title and picture used when the page is shared, a canonical address, and — on the home page, gallery pages and journal entries — a small machine-readable block describing what the page is (a photo gallery and how many photographs, a journal entry and its date).
Routinely, nothing. The list below is the whole of it.
Do not press anything on the “Page with redirect” or “Duplicate” reports, or
on the old-site addresses under “Crawled — currently not indexed”. Those reports
emptying out is the goal — they are the old site being forgotten, exactly as intended —
and asking Google to index those addresses works against it. The same goes for the whole
second property in Search Console — the http:// one, the plain (non-https) www address
of the old site: it is a museum, and it is meant to decay quietly.
The owner’s manual carries the full reading of those reports, and the reason each one looks alarming while being the machine working correctly.
The site deliberately blocks no answer-engine crawler. Publishing llms.txt and then
blocking the crawlers that read it would cancel out the site’s entire answer-engine
presence — it is the single change most likely to make the archive invisible to AI
answers. If anyone ever suggests adding those blocks, that is the trade being made.
Some things are kept out on purpose, and their absence is not a fault:
llms.txt and llms-full.txt, absent from every count, and marked so search engines
do not list them. They open only for someone holding the address or signed in as a
friend.robots.txt./llms.txt — it is almost always that the
change has not been published yet. Publish, wait for the site to rebuild, and look
again.