Drop the stale google_site_verification token - #104
Merged
Conversation
The token verified the old ultimatecoder.github.io property via the HTML-tag method that jekyll-seo-tag renders from this key. Ownership of the site is now verified through a DNS TXT record on the jaysinh.dev apex, as a Search Console Domain property, which covers blog.jaysinh.dev and every other subdomain. That leaves the meta tag inert: the property it belonged to now 301s to the custom domain, and nothing reads the token. Remove it rather than leave a dead credential in the config. Verified the built _site/ no longer emits the google-site-verification meta tag while the rest of the jekyll-seo-tag output — canonical and description — is unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
What
Removes
google_site_verificationfrom_config.yml.Why
That token verified the old
ultimatecoder.github.ioproperty using the HTML-tag method, whichjekyll-seo-tagrenders from this config key.Site ownership is now verified by a DNS TXT record on the
jaysinh.devapex, registered as a Search Console Domain property — which coversblog.jaysinh.dev, the apex, and any future subdomain. The DNS record is entirely independent of anything in this repo.That leaves the meta tag inert: the property it belonged to now 301s to the custom domain, and nothing reads the token. Better removed than left in the config as a dead credential someone later mistakes for load-bearing.
Verification
_config.yml,_config_production.yml:_site/index.htmlno longer containsgoogle-site-verificationjekyll-seo-tagoutput unchanged — canonical stillhttps://blog.jaysinh.dev/, description intact./scripts/testgreen: 174 external + 73 internal linksNo effect on the live site's Search Console status, which rests on the DNS record.
🤖 Generated with Claude Code