Add Google site verification and clean up unused assets

[mostlyerror]

Summary

• Add Google Search Console site verification meta tag via Next.js metadata.verification.google in the root layout
• Remove unused CLAUDE.md project instructions file
• Remove unused headshot images (ben-headshot-2.jpg, ben-headshot-3.jpg)

Test plan

• Verify the site builds successfully (npm run build)
• Check the rendered HTML includes <meta name="google-site-verification" content="mctBV1WZrCRIsZnxrBM0gupkErmYQpkgWZCWOXg4ehs">
• Confirm Google Search Console accepts the verification
• Verify no pages reference the deleted headshot images

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
goodrobotco.com	Ready	Preview, Comment	May 24, 2026 8:09am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 26ef304f-850d-4841-97ae-61ed12a4535b

📥 Commits

Reviewing files that changed from the base of the PR and between 26a859b and 5353192.

⛔ Files ignored due to path filters (2)

• public/ben-headshot-2.jpg is excluded by !**/*.jpg
• public/ben-headshot-3.jpg is excluded by !**/*.jpg

📒 Files selected for processing (2)

• CLAUDE.md
• app/layout.tsx

💤 Files with no reviewable changes (1)

• CLAUDE.md

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated site verification configuration for improved search engine integration.

Walkthrough

The PR removes internal developer guidance from CLAUDE.md and adds a Google site verification token to the Next.js layout metadata object. These are two independent configuration and documentation updates with no overlapping logic or functional dependencies.

Changes

Documentation and Site Configuration Updates

Layer / File(s)	Summary
Developer guidance documentation removal CLAUDE.md	CLAUDE.md is deleted entirely, removing guidance on repository commands, architecture patterns, Tailwind rules, testing, git workflow, and deployment details.
Google site verification metadata app/layout.tsx	Next.js metadata export adds a verification section with a Google site verification token for search engine verification.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main changes: adding Google site verification and removing unused assets (CLAUDE.md and headshot images).
Description check	✅ Passed	The description is directly related to the changeset, detailing the Google verification addition, file removals, and providing a comprehensive test plan.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-google-site-verification

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}