SerpGoblin

Tutorials

Practical Walkthroughs

Use these workflows to move from first connection to a measured SEO fix, either in the app or through a connected AI coding agent.

Run The First Analysis

  1. Sign in and connect Google Search Console from onboarding or Integrations.
  2. Create a project for the site you want to improve.
  3. Select the Search Console property that matches the project.
  4. Start an analysis from the project board.
  5. Open the highest priority Ready card and review the evidence.

Turn An Issue Into A Brief

Pick a Ready issue with clear evidence, then prepare a brief. SerpGoblin moves the issue through Brief Builder and places the generated output in Review when it is ready.

Agent prompt

List my SerpGoblin projects, open the highest priority Ready issue, prepare the brief, and summarize the implementation work.

Use Codex For A Fix

  1. Connect Codex using the setup on the MCP page.
  2. Ask Codex to call list_projects and choose the right project.
  3. Ask for get_project_board, then inspect one Ready issue.
  4. Let Codex implement the fix in your repository and run the relevant tests.
  5. After the change ships, ask Codex to call mark_issue_resolved with a short note.

Use Claude Code For A Fix

  1. Add the remote HTTP server with claude mcp add --transport http.
  2. Run /mcp, authenticate, and confirm the server is connected.
  3. Ask Claude Code to inspect the board and explain the selected issue.
  4. Have it patch the site, run tests, and report the files changed.
  5. Mark the issue resolved in SerpGoblin so it enters Tracking.

Close The Measurement Loop

Tracking is not a final archive. It is the waiting room for fresh search data. After Google has enough new data, run another analysis and compare observed movement against the expectation saved on the resolved issue.

Good Result

Keep the issue tracked as evidence and repeat the pattern elsewhere.

Flat Result

Reopen the work, inspect the query/page evidence, and adjust the fix.

Bad Result

Rollback or revise quickly, then leave a note for future audits.

Troubleshooting

The agent gets a 401.

Run the client OAuth flow again. The MCP endpoint requires bearer auth on every request.

The board is empty.

Confirm the project has a selected Search Console property and at least one completed analysis.

The wrong project appears.

Ask the agent to call list_projects and pass the intended project ID explicitly.

The OAuth browser callback fails.

Retry from the client, and make sure your SerpGoblin host is reachable from the browser.