Overview
Ask about visibility, topics, prompts, and competitors right from the terminal while working on the site.
What you can do
These are the jobs the integration is built for.
Check visibility before shipping content changes
While editing pages or copy in the repo, ask Claude Code which tracked prompts are at risk and whether competitors recently moved ahead. Use the answer to decide if the change you are about to commit targets a real AI search gap.
Turn a losing prompt into a concrete edit list
Pick one prompt where mentions dropped, pull competitor context from Beamtrace, and have Claude Code propose specific file or section updates. Keep the whole loop inside your terminal session next to the codebase.
Build an improvement branch from live metrics
Start a fix branch with a short brief generated from current visibility scores, topic gaps, and open improvements. Claude Code can reference the same data as it implements content or metadata changes.
Set up
Connection happens inside Beamtrace: open Integrations in your dashboard, pick Claude Code and follow the steps there. The dashboard shows your connection details and the status of every connected client.
Requirements
- A Beamtrace workspace with at least one tracked website.
- A Claude Code setup that allows custom MCP / connector tools.
