Web Properties Hub

Every public web property, what serves it, and where its operations are documented. All of these are tracked by the search-visibility exporter, so SEO questions about any of them can be answered from Prometheus on docker2.

The properties

Property	What serves it	Docs
wiki.wikantik.com	Wikantik on docker1, via cloudflared	Wikantik Development Hub
www.wikantik.com (+ apex)	Static site, nginx on the cloudflare host	Marketing Site Operations
thelocalwiki.com, berlin., sandiego.	Google Blogger (custom domains)	The Local Wiki Blogger Sites
jakefear.com	CrafterCMS delivery engine on docker2 — one Engine, vhost by Host header, behind the crafter-proxy	Host: docker2
maiiavorobiova.com	Same CrafterCMS engine on docker2 (second vhost)	Host: docker2
wiki.jakefear.com	Tracked in search-visibility; serving stack not yet documented (confirm before assuming)	—

Publishing paths

• Wiki content → MCP authoring tools (Wikantik Content vs Code Deployment)
• Marketing pages → git + bin/deploy-marketing.sh (Marketing Site Operations)
• Blogger posts → Blogger Agent Workflow
• CrafterCMS sites → Crafter Studio authoring on docker2 (:8084), blue/green delivery pair
• Roller blog → in development; see Roller Blog Platform

SEO posture

Search-visibility data (impressions, clicks, position, query→page) for all properties lives in the webmaster_* Prometheus metrics; the working method for SEO passes — read the data, fix titles/metas/intent coverage, request re-indexing — is recorded in the wikantik SEO history. IndexNow covers Bing/Yandex; Google needs manual GSC Request Indexing.

See Also

• Software Projects Hub
• Content Pipeline Hub — how content gets made
• Host: docker2 — Monitoring Central and CrafterCMS