ci: ping IndexNow after prod deploy - #1706
Merged
Merged
Conversation
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.
After each successful prod deploy, immediately call
/api/cron/indexnowso Bing re-crawls changed pages within minutes rather than waiting up to an hour for the cron tick.Requires
CRON_SECRETas a GitHub Actions secret (same value as the Vercel env var).Context: IndexNow infra is already fully implemented (key file, cron route, diff-tracking against KV). The only things missing are:
INDEXNOW_KEYenv var in Vercel → set toc8990214444052b9ffa16b263e66e91eCRON_SECRETenv var in Vercel + as GitHub secret