fix(seo): repair main's gitleaks failure; drop docs.webhook.co from IndexNow#783
Merged
Conversation
choraria
force-pushed
the
lane/indexnow-docs-cleanup
branch
from
July 23, 2026 14:34
488c48e to
6974653
Compare
TWO fixes. The first is urgent: main is currently RED on gitleaks at 74e921e (#782), and I caused it. 1. gitleaks. In #782 I put `// gitleaks:allow` on the lines ABOVE the INDEXNOW_KEY constant. That does nothing -- the directive must sit on the SAME LINE as the finding. #782 went green only because the .gitleaksignore fingerprint covered its BRANCH commit, and a squash-merge mints a NEW commit SHA, so the suppression evaporated the moment it landed and main went red. The file's own header warns that fingerprints are commit-bound; the squash case is the same trap. Fixed by moving the directive onto the line, and adding a fingerprint for the squash commit that is now frozen in main's history. Both are needed: the directive for any future commit that touches the line, the fingerprint for the one already written. Verified with the gitleaks CLI locally, reproducing RED on the old tree first and confirming clean after -- not by watching the check flip colour. 2. docs.webhook.co dropped from IndexNow. The key file shipped in #782 as a deliberate experiment, since Mintlify documents .txt as Enterprise-only. Measured after deploy: https://www.webhook.co/<key>.txt -> 200, serves the key https://docs.webhook.co/<key>.txt -> 404 "Asset not found" So docs cannot host a key file and apps/docs/<key>.txt was dead weight. Removed, and docs dropped from SITEMAP_FOR_HOST and the test's KEY_FILE_DIRS with a comment recording why, so nobody repeats it. Bing coverage for docs comes from Bing Webmaster Tools' GSC import instead. www is unaffected and already submitted: 36 URLs, HTTP 202.
choraria
force-pushed
the
lane/indexnow-docs-cleanup
branch
from
July 23, 2026 14:48
6974653 to
489c0b1
Compare
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
🔴 First: main is red, and I caused it
mainis currently failing gitleaks at74e921ed(#782). Root cause:In #782 I put
// gitleaks:allowon the lines above theINDEXNOW_KEYconstant. That does nothing — the directive must sit on the same line as the finding. #782 went green only because the.gitleaksignorefingerprint covered its branch commit, and a squash-merge mints a new commit SHA, so the suppression evaporated the moment it landed..gitleaksignore's own header warns that fingerprints are commit-bound and break on rebase. The squash case is the same trap, and it is now written down there.Fix: directive moved onto the line, plus a fingerprint for the squash commit now frozen in main's history. Both are needed — the directive for any future commit touching the line, the fingerprint for the one already written.
Verified with the gitleaks CLI locally, reproducing RED on the old tree first and confirming clean after — not by watching the check flip colour. I also isolated which change does the work: with the directive present my commit's diff re-adds the key line and the scan is clean, which could not happen if the same-line form didn't work.
Second: docs.webhook.co dropped from IndexNow
The docs key file shipped in #782 as a deliberate experiment — Mintlify documents
.txtas Enterprise-only, so this was unknown rather than assumed. Measured after deploy:GET /<key>.txtwww.webhook.co200, serves the key ✅docs.webhook.co404 Asset not found❌So docs cannot host a key file and
apps/docs/<key>.txtwas dead weight. Removed, and docs dropped fromSITEMAP_FOR_HOSTand the test'sKEY_FILE_DIRSwith a comment recording why, so nobody repeats the experiment.Consequence worth flagging: Bing coverage for the 150 docs URLs now depends entirely on the Bing Webmaster Tools GSC import, which needs no key file. That raises its priority from optional to the only route.
Status of the submission
www.webhook.co: 36 URLs submitted, HTTP 202 (accepted). Unaffected by this PR.
Test plan
docs.webhook.cocleanly andwww --dry-runstill resolves 36 URLs.