Skip to content

Wire Search Console and Bing ownership verification - #229

Merged
carsonSgit merged 1 commit into
mainfrom
feat/site-verification
Nov 7, 2026
Merged

carsonSgit merged 1 commit into
mainfrom
feat/site-verification

Conversation

@carsonSgit

@carsonSgit carsonSgit commented Nov 7, 2026 •

Copy link
Copy Markdown
Owner

Both properties verify via a <meta> tag in the head. Rather than committing tokens, app/layout.tsx reads them from two build env vars:

Variable Emits
NEXT_PUBLIC_GOOGLE_SITE_VERIFICATION <meta name="google-site-verification" content="…">
NEXT_PUBLIC_BING_SITE_VERIFICATION <meta name="msvalidate.01" content="…">

Unset means no tag at all, so a preview deploy or a fork never claims ownership of the apex domain. Both are documented in .env.example, and README gains a Search engines section covering the tokens, where to get them (Search Console URL prefix property → HTML tag; Bing Webmaster Tools → add site → HTML meta tag), and the DNS TXT alternative that needs no deploy.

Verified

  • Built with both vars set → both tags present in out/index.html, out/uses.html and the case-study pages
  • Built with neither set → 0 occurrences, so no accidental claim
  • npx tsc --noEmit clean, npx biome ci . clean

What is left for you

The tokens are per-account, so this cannot be finished from the repo: set each one as a Vercel env var (Production) and redeploy, then hit Verify in each console. DNS TXT skips the redeploy if you prefer that.

@vercel

vercel Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
carsonspriggs Ready Ready Preview Nov 7, 2026 7:53pm UTC

Both properties verify with a meta tag in the document head. Rather than
hard-coding tokens into the repo, `app/layout.tsx` reads them from two build
env vars:

  NEXT_PUBLIC_GOOGLE_SITE_VERIFICATION -> <meta name="google-site-verification">
  NEXT_PUBLIC_BING_SITE_VERIFICATION   -> <meta name="msvalidate.01">

Unset means the tag is not emitted at all, so a preview deploy or a fork never
claims ownership of the apex domain. README documents both, plus the DNS TXT
alternative for whenever a deploy is not the right place to make the change.
@carsonSgit
carsonSgit force-pushed the feat/site-verification branch from 06bed24 to 178aad3 Compare November 7, 2026 19:52
@carsonSgit
carsonSgit merged commit e902fff into main Nov 7, 2026
4 checks passed

This branch was successfully deployed

1 active deployment
Preview — 178aad3d Deployed Nov 7, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant