Two domains, one language, and one certificate short

A domain doesn't have to choose anymore.

The original plan was one canonical domain, with everything else forwarding to it. That plan got dropped: koonsultancy.com and coonsultancy.com now both simply run live, same content, same webspace — a canonical tag tells search engines which of the two to index, so it doesn't turn into a duplicate-content mess. The permanent mailbox came back online in the same move, off a temporary stand-in address.

English became the default, not just the fallback.

The game had already switched to English as its starting position a day earlier; the site properly caught up today. Not just the JavaScript fallback that decides what a blank visitor sees once the page has loaded, but the raw source itself: title, meta description, structured data, and the visible text across some nineteen pages — so a search engine, and a visitor for that one split second before its own script runs, actually sees English too, not a flash of Dutch first.

Dutch hasn't gone anywhere — it just became the alternate instead of the default, still one click away on the language toggle.

Search Console, minus one false alarm.

Both domains got verified as their own property through a DNS record, and the sitemap went in for each. One of them came back 'couldn't fetch' on the first try — mildly alarming for about five minutes, until it turned out to be nothing more than the second domain's certificate still settling in. A plain browser visit loaded it without issue, and the second submission went through without complaint.

The domain that didn't make the cut.

Type a domain into a browser these days and it tries https:// first, whether you asked for that or not. Fine for the two live domains — not fine for the domains that only forward, since a plain domain forward never bothers with a certificate for the domain doing the forwarding. Discovered on exactly the domain that still carries real old bookmarks, not just the defensive registrations nobody visits anyway.

The hosting provider's 'internal redirect' briefly looked like the fix: point the domain at a folder inside the same webspace instead of an address outside it. Turned out to only solve where a domain points, not which names sit on the certificate — the warning stayed put. A third certificate was on the table and got turned down: two free ones is the plan, and paying for a certificate on a domain that only exists to send people somewhere else isn't worth it.

So that's where it stays: fine over plain http, a warning over https, and no real risk either way — that domain never does anything more than a redirect.

And, unrelated to any of that, a small polish pass.

The leaderboard turned out to be missing from the main navigation entirely — reachable only through one homepage tile, while its neighbour Community sat right there in the menu. Added, between Blog and Community, same order as the homepage tiles.

Checking that on mobile turned up something else: the open menu gave its last item its own divider and padding on top of the container's own — nearly a whole extra, empty row below the list. Fixing it in one pass didn't quite work: that first attempt tipped the balance the other way, so the first item lost its own padding for the same reason. Top and bottom now both keep exactly the container's own padding, nothing more.