Repository navigation
Wire Search Console and Bing ownership verification - #229
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
carsonSgit
force-pushed
the
feat/site-verification
branch
from
November 7, 2026 19:50
fc8a04c to
06bed24
Compare
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
force-pushed
the
feat/site-verification
branch
from
November 7, 2026 19:52
06bed24 to
178aad3
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both properties verify via a
<meta>tag in the head. Rather than committing tokens,app/layout.tsxreads them from two build env vars: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
out/index.html,out/uses.htmland the case-study pagesnpx tsc --noEmitclean,npx biome ci .cleanWhat 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.