Skip to content

chore: add Google Search Console verification file - #11

Merged
belminpre merged 1 commit into
mainfrom
gsc-site-verification
Oct 21, 2026
Merged

belminpre merged 1 commit into
mainfrom
gsc-site-verification

Conversation

@belminpre

@belminpre belminpre commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Adds public/googleb37bb49ca3715dcb.html so it is served at https://weirdanimals.net/googleb37bb49ca3715dcb.html (Vite copies public/ to the dist root; Netlify serves static files before the /* SPA rewrite, as robots.txt already shows).

Purpose: verify the URL-prefix property https://weirdanimals.net/ in Google Search Console under test-automations@prerender.io, so the e2e pro fixture account can connect Search Performance (GSC) to this domain. No app code changes.

After merge + Netlify deploy: open the URL above (expect the one-line google-site-verification: body), then click Verify in Search Console.

🤖 Generated with Claude Code


Part of COR-1054 (COR-1055).

Serves googleb37bb49ca3715dcb.html at the site root so test-automations@prerender.io can verify https://weirdanimals.net/ in Search Console (Search Performance e2e fixture, URL-prefix property).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@netlify

netlify Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for weirdanimals ready!

Name Link
🔨 Latest commit ad261cf
🔍 Latest deploy log https://app.netlify.com/projects/weirdanimals/deploys/6ad8be4987e499caa202cc67
😎 Deploy Preview https://deploy-preview-11--weirdanimals.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@belminpre

Copy link
Copy Markdown
Contributor Author

Test plan

What changed — one static file, public/googleb37bb49ca3715dcb.html, containing the single line google-site-verification: googleb37bb49ca3715dcb.html. Vite copies public/ to the dist root, so after the Netlify deploy it is served at https://weirdanimals.net/googleb37bb49ca3715dcb.html. No app code, routing, or build config changes. Scope: the site root only.

Preconditions — the PR is merged and the Netlify production deploy for weirdanimals.net has finished (Netlify → project weirdanimals → Deploys shows the new commit as Published). Nothing to run locally.

1. [staging] Verification file is served verbatim at the site root

Setup · nothing; the file must come from the deployed dist.
Do ·

curl -s -D - https://weirdanimals.net/googleb37bb49ca3715dcb.html

Expect · HTTP/2 200, content-type: text/html, body exactly google-site-verification: googleb37bb49ca3715dcb.html (one line, no HTML document around it).
Negative check · curl -s https://weirdanimals.net/googleDOESNOTEXIST.html | head -c 200 returns the SPA index.html markup (<!doctype html> …) — that is the /* catch-all, proving the 200 above came from the real file, not the rewrite.

2. [prod-only] Google Search Console accepts the verification — human checkpoint

Do · signed in as test-automations@prerender.io, Search Console → Add property → URL-prefix https://weirdanimals.net/ → HTML file method → Verify.
Expect · "Ownership verified". Keep the file after verification (Google re-checks periodically; removing it drops ownership).

Deployed-build check — merging deploys automatically through Netlify's Git integration (production branch main); the fingerprint is step 1's 200 with the exact body. Before the deploy finishes the same URL returns the SPA index.html with 200, so check the body, not the status.

Acceptance criteria with no block — none; there is no ticket (this is a fixture prerequisite for the Search Performance e2e account, tracked on the monostack side under COR-1039 / the SP perf-testing plan).

Automated coverage

Behavior Covered by Command Gap
File served at the root none — static asset, no test in this repo — step 1 is the only check; the existing robots.txt in public/ is the precedent that the pattern works

Risks / not covered

  • Low risk: one static file, no code path. The only way it fails is a Netlify rewrite ordering change (/* with force = true) — not touched here.
  • The [[headers]] for = "/*" block adds X-Frame-Options/nosniff to the file; Google's verifier ignores them.

Ticket: none · commit ad261cf590b26ddad19acfbb77103e725e377acd · regenerate with /test-plan 11 (repo prerender/weird-animals)

@belminpre
belminpre merged commit 38eb931 into main Oct 21, 2026
5 checks passed
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