Repository navigation
chore: add Google Search Console verification file - #11
Conversation
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>
✅ Deploy Preview for weirdanimals ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Test planWhat changed — one static file, Preconditions — the PR is merged and the Netlify production deploy for 1. [staging] Verification file is served verbatim at the site rootSetup · nothing; the file must come from the deployed Expect · 2. [prod-only] Google Search Console accepts the verification — human checkpointDo · signed in as Deployed-build check — merging deploys automatically through Netlify's Git integration (production branch 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
Risks / not covered
Ticket: none · commit |
Adds
public/googleb37bb49ca3715dcb.htmlso it is served athttps://weirdanimals.net/googleb37bb49ca3715dcb.html(Vite copiespublic/to thedistroot; Netlify serves static files before the/*SPA rewrite, asrobots.txtalready shows).Purpose: verify the URL-prefix property
https://weirdanimals.net/in Google Search Console undertest-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).