Set Up Vixqo MCP — Step by Step

Step 1

Which agent do you use?

Pick one. Vixqo will only show the setup instructions for that agent.

Choose an agent to continue.

Step 2

Add Vixqo.

Use the settings below in your agent.

ConnectionAdd Vixqo to your agent

Step 3

Test the connection.

Open a new chat in your agent and send this. Do not make any site changes yet.

Use Vixqo. Tell me which site I’m connected to and the current monitoring status. Do not make any changes.

Success looks likeYour Vixqo site

The agent should identify the connected site and return Vixqo status without asking for a token or Search Console export.

Step 4

Give your agent one operating instruction.

This tells the agent that Vixqo owns prioritization, guardrails, and measurement.

Vixqo picks the action. Your agent validates it, makes only the scoped change, verifies production, reports back, and waits for measurement.

View full instructions

Use Vixqo to improve this site's SEO + GEO performance. Treat Vixqo as the source of truth for what to prioritize. Do not substitute your own SEO backlog or make unrelated improvements. 1. Ask Vixqo for the current site state and next recommended action. 2. Get the evidence supporting that action. 3. Validate the Vixqo action against the latest evidence before changing anything. 4. Get the full implementation plan, including target, exact proposed change, guardrails, and measurement rules. 5. Inspect the current repository and live page yourself. Confirm the target still exists and the change is supported by the actual content. 6. If the repository state, live page, active experiment, or evidence conflicts with Vixqo's plan, stop rather than guessing. 7. Implement only the smallest evidence-supported change. Do not broaden scope or perform adjacent SEO cleanup. 8. Do not invent claims, pricing, capabilities, statistics, citations, dates, ranges, or facts. 9. Do not change redirects, canonicals, noindex directives, legal copy, pricing, or other high-risk elements unless Vixqo explicitly authorizes them. 10. Use the existing development workflow: branch, make the scoped change, run applicable checks/builds, review the diff, and create a pull request. 11. After deployment, verify the exact intended change is live in production. 12. Report the implementation back to Vixqo with the action reference, status, commit, PR, deployment URL, and concise summary. 13. Ask Vixqo for the measurement state. Do not call the action a success merely because it shipped. 14. Leave the action in measurement until Vixqo has enough settled evidence to recommend Keep, Revise, or Revert. If Vixqo returns Observe or says an active experiment is measuring, make no production change. Complete one Vixqo action at a time.

Step 5

Turn on Vixqo monitoring.

This automates Vixqo’s side of the loop: refresh Search Console, re-score opportunities, block conflicts, then queue one action or Observe.

Checking monitoring…

Loading your workspace.

Checking

Last refresh—

Current queue—

Step 6

Do you want agent execution scheduled?

This is separate from Vixqo monitoring. Your agent needs its own recurring run to pick up queued actions. If your agent surface doesn’t support scheduled MCP runs, skip this for now.

Not scheduled

You can still use Vixqo manually whenever you want.

Not scheduled

Recurring run: ask Vixqo for the next action. If Vixqo says Observe, stop. Process at most one action, report it back, then stop.

View full recurring prompt

This is a recurring Vixqo execution run. 1. Ask Vixqo for the next action. 2. If Vixqo returns Observe, says an experiment is measuring, or says no action is queued, stop immediately and make no production change. 3. Process at most one Vixqo action in this run. 4. Validate the action against Vixqo's latest evidence and active experiments. 5. Get the full implementation plan. 6. Inspect the live page and repository before editing. 7. If anything conflicts with Vixqo's evidence or guardrails, stop and report the conflict. 8. Implement only the scoped change on a branch, run applicable checks, review the diff, and open a pull request. 9. After deployment, verify production and report the implementation back to Vixqo. 10. Ask Vixqo for measurement status, then stop. Do not start a second action. Never call deployment a win. Vixqo owns the Keep, Revise, or Revert decision after settled evidence.

✓

Setup complete

Vixqo is connected.

Your agent can now use Vixqo as the decision layer. Monitoring and agent scheduling remain separate so you always know what is automated.

Site—

Agent—

Vixqo monitoring—

Agent automation—

First safe testAsk Vixqo for the next non-conflicting action.

Have the agent show the evidence and full implementation plan. Do not execute until you’re comfortable with the output.

Open Vixqo dashboard →

If Vixqo says Observe, that is a valid result. It means there is no safe new action to take yet.