Every region gets its own page
Earlier today visits learned which region they happen in, and the region got a governor: the pilot who has flown there on the most days. Both lived only as a line on other pages. Now each region has its own page, at an address like /region/de-hh for Hamburg or /region/fr-ile-de-france for the Paris region.
What is on a region page
The top of the page says what the region is and which country it belongs to. Below that are the numbers: how many pilots have flown over it, how many pilot-days that adds up to, and how many cities and airports in it have been visited. A day counts once per pilot. If you visited a city and an airport in the same region on the same day, that is one region day, which is the same rule the governor seat uses.
Then come the people. The governor card shows who holds the seat and since when. Under it there is a short list of regulars and a list of who flew there recently. If you switched your visits to private in your account, you are counted in the numbers but your name is never listed. The page says how many pilots chose that.
The last part is about places. You get the cities and airports in the region that pilots visit most, each with how many pilots and days it has, and a link to its own page where one exists. Next to them is a row of the larger cities in the region that have a landing page, so a new region still has somewhere to send you.
How to get there
The region name under a city on the map is now a link. So is the region shown next to each city in your city log on /my/cities. The governors tab on /mayors links every governor row to the region page as well.
For search engines and assistants
A region page only asks to be indexed once at least three different pilots have flown over it. Below that it is a name and a rule, and there are more than three thousand regions. The text is written on the server in all twelve languages the site speaks. There is a short FAQ, and a share card shows the region with its numbers. Pilot names appear only in the page body and never in the card or the structured data.