Skip to content

chore: add the Google Search Console verification file - #14

Merged
lintdeveloper merged 1 commit into
mainfrom
chore/google-search-console
Aug 29, 2026
Merged

lintdeveloper merged 1 commit into
mainfrom
chore/google-search-console

Conversation

@lintdeveloper

Copy link
Copy Markdown
Owner

Serves google50fd13fe6cb8e96f.html from the site root. File method because js.org owns the DNS, so a Domain property isn't available.

Also caught: a note written as docs/public/README.md rendered as a page at /public/README and entered the sitemap — markdown under docs/ is page source regardless of subdirectory. Moved to DEPLOYING.md, which srcExclude keeps unpublished.

docs/public/google50fd13fe6cb8e96f.html, served from the site root as Search
Console requires. The file method rather than DNS because js.org owns the DNS
for the subdomain, so a Domain property is not available — only a URL-prefix
property verified by file or meta tag.

docs/DEPLOYING.md now documents what docs/public/ is for, and warns that Search
Console silently unverifies a property when its proof 404s. Losing search data
with no visible cause is the kind of thing that goes unnoticed for months.

Also caught while doing it: a note written as docs/public/README.md rendered as
a real page at /public/README and entered the sitemap. Markdown anywhere under
docs/ is page source, subdirectory or not — so a private note about the build
was about to be submitted to Google. The note moved into DEPLOYING.md, which
srcExclude keeps unpublished, and the warning is written down there.
@lintdeveloper
lintdeveloper merged commit 302237a into main Aug 29, 2026
11 checks passed
@lintdeveloper
lintdeveloper deleted the chore/google-search-console branch August 29, 2026 19:48
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