8.3.8 Google Search Console — motir.co property setup + verification (manual)

Type: manual · Executor: human · Create the Google Search Console property for motir.co, choose the verification method (the meta-tag token wired by 8.3.7, or DNS), and confirm verification. Provide the verification token as the env var 8.3.7 reads, submit the sitemap (/sitemap.xml), and confirm the property is verified + indexing.

Dashboard/SaaS work — no code beyond the env token (which 8.3.7 consumes).

✅ DONE 2026-08-27 — verified by DNS on a DOMAIN property. There is NO meta-tag token.

The card offered two methods; DNS was taken, which changes what this card hands 8.3.7 — see the 8.3.7 note below.

Property: motir.co, type Domain (not URL-prefix), owner zhuyue11@gmail.com. Method: DNS TXT at the apex — google-site-verification=0qj6BfE6tIjXBQo8zSZHtfGxbLcCUbtNStGC_m55XUA written at Spaceship (the zone's home — nameservers launch1/launch2.spaceship.net) as a NEW apex TXT record, alongside the existing v=spf1, not an edit to it. Verified on the first attempt after the record was confirmed live on 1.1.1.1 / 8.8.8.8 / 9.9.9.9.

Why Domain and not URL-prefix: a Domain property covers motir.co AND every subdomain. That is what made the property useful on day one — motir.co itself serves nothing yet (no A record; motir-marketing is unprovisioned, 8.3.10), while app.motir.co is live on Fly. A URL-prefix property for https://motir.co/ would have had nothing fetchable in it at all.

Sitemap submitted: https://app.motir.co/sitemap.xml → Success, 10 URLs (/explore, /explore?rank=*, /p/MOTIR/{board,items,tree,roadmap,changelog}). It showed "Couldn't fetch" for a few minutes first — Google's queue, not a fault: the file is well-formed urlset XML and Googlebot gets 200 application/xml over both IPv4 and IPv6.

What this card did NOT do, and who owns it: the marketing sitemap https://motir.co/sitemap.xml cannot be submitted until that site exists. Added as an acceptance criterion on MOTIR-1455 (8.3.10), which already owns the apex DNS and the Fly deploy — one more console action in the session that makes the host real. No new card; the property is already verified, so it is a submit, not a setup.

Coverage reporting populates over the following days on Google's crawl cadence — not a gate on this card.

Found in passing, now MOTIR-3726: app.motir.co/robots.txt 404s — motir-core has no app/robots.ts.

Acceptance criteria

• GSC property for motir.co created and verified. ✅ Domain property, DNS-verified.
• Verification token supplied as the env var 8.3.7 reads (or DNS method confirmed). ✅ DNS method — no meta-tag token exists.
• Sitemap submitted; property reporting coverage. ✅ app.motir.co/sitemap.xml Success/10 URLs; the motir.co sitemap defers to 8.3.10.

No PR — type: manual, marked done on the user's confirmation.

Context refs

• feeds 8.3.7 (the verification.google env token + sitemap at app/sitemap.ts) — superseded: DNS supplies no token; 8.3.7 wires the env var and leaves it unset
• depends: motir.co domain attach/SSL is story 8.5
• the apex TXT this card added is recorded in MOTIR-2596's zone table