Search verification (GSC / Bing)
Tokens are not invented by agents. The domain owner / PM must create properties in Google Search Console and Bing Webmaster Tools, then paste the verification values into
src/lib/site.ts (gscVerification, bingVerification) or add DNS TXT records in the Cloudflare dashboard for rea.run.
Preferred: DNS TXT (Cloudflare)
- Open Cloudflare → zone rea.run → DNS.
- In Google Search Console, add domain property
rea.runand copy the TXT record Google shows. - In Bing Webmaster Tools, add the site and copy Bing’s TXT (or meta) instruction.
- Create the TXT records exactly as shown. Do not reuse tokens from other domains (dotsbase, dshbase, Memoh, retatrutidecalc, etc.).
- Click verify in GSC/Bing after DNS propagates.
Alternative: HTML meta tag
- Choose URL-prefix property for
https://rea.run/. - Copy the
contentvalue from the meta tag Google/Bing provide. - Set
SITE.gscVerification/SITE.bingVerificationinsrc/lib/site.ts, commit, deploy. - Confirm the live homepage HTML contains the meta tags, then verify.
After verification
- Submit https://rea.run/sitemap-index.xml in both tools.
- Optional: set
SITE.ga4Idonce a GA4 property exists (same: do not invent IDs). - Add the site to the SEO control dashboard when that workflow is ready (phase 0 “中控加站”).
Do not commit API keys or paste secrets into chat. Meta verification strings are public by design once deployed; DNS TXT values should still be treated carefully and never shared from other zones.