Connect AdvisorSEO. Understand each step.

Before you connect

You need an AdvisorSEO account, a website you own or are authorized to manage, and a host account that allows custom remote MCP connections. Your Claude or ChatGPT plan and workspace administrator may limit that option. Check host availability before changing account settings.

The connector runs remotely; it is not an extension that reads your computer. Decide which workspace belongs to this site before you authorize it. Start with a read request and keep client sites separate.

Google Search Console, Analytics and Tag Manager connect per website through a Google link you open yourself; the directory guide covers them. Automated AI-answer tracking is planned, not live. A saved schedule is not proof that recurring execution is operating.

Connect in Claude or ChatGPT

https://mcp.advisorseo.ai/mcp

Claude

1. Open Settings, then Connectors, and choose Add custom connector if your account offers it.
2. Name the connection AdvisorSEO and enter the HTTPS address above. Follow the sign-in flow; do not paste a password or token into the conversation.
3. Read the consent screen, select the intended workspace, and approve only after checking that account and site access are correct.
4. Start a new conversation with the connector enabled. Ask it to list the websites in your workspace. Confirm the result before creating a record.

ChatGPT

1. Open your account's Plugins area and choose Add custom MCP server where available. Older interfaces may expose custom connections under Apps or Connectors and Developer mode. Workspace policies apply.
2. Enter the same connector address, configure the offered sign-in option, review the risk notice, and create the custom connection.
3. Complete AdvisorSEO consent and choose the correct workspace. Review the discovered capabilities.
4. Start a new conversation, select AdvisorSEO, and ask for your website list before requesting a change.

Host labels change. If the custom connection option is absent, ask your administrator or contact support; a different menu label does not establish that a directory listing has been approved.

The workspace selected by a person at consent is bound to the connection. An assistant message cannot choose a different customer's workspace. If the list looks wrong, stop and reconnect with the correct account.

In the Claude directory

A listing is not approved until it appears in the directory, and submitting does not establish approval.

The directory listing connects at the same address, https://mcp.advisorseo.ai/mcp, and signs in the same way. What it reads and changes in your workspace and in Google, with example prompts, is in the directory guide.

Inspect the capabilities actually offered by the edition you connect. Do not infer access from a capability family described elsewhere on this site. If the edition is unclear, send support its visible name and connection address, without tokens.

Set up your site and profile

1. Ask for the existing website list and select the exact site. Check hostname and workspace before adding a duplicate.
2. Ask to add your authorized site if it is absent. Read the creation preview and confirm the proposed record.
3. Supply verified business facts: services, service area, audience, contact route, editorial constraints and the person who reviews drafts.
4. Ask to preview the profile, correct uncertain details, then confirm saving it. Read it back after the change.

Show my selected site's business profile. Separate supplied facts from suggestions. Do not invent opening hours, qualifications, prices, customer stories or search volumes. Preview any change before saving it.

A profile helps the assistant work consistently. It is not evidence that every generated claim is true. Keep unverified fields empty or explicitly unknown.

Understand the six families

This is a scope reference, not an entitlement guarantee. See every capability registered in the server source, with its setup and approval limits. This is a source inventory, not a live availability guarantee.

Page-speed exception: a successful page-speed measurement is stored without a separate confirmation step. It requires configured access and returns unconfigured when access is missing. Missing measurements stay unknown.

The source crawl is same-origin, capped at 120 pages and depth 6, and reads static HTML. It does not execute page JavaScript or provide a whole-web backlink index. Tag detection is not analytics reporting. Heuristic readiness does not measure actual AI citations.

Read the evidence before acting

Ask for the source URL, observation date, excerpt, check scope and suggested action alongside each finding. Distinguish a page observation from the assistant's interpretation. A score without its formula version and denominator is not enough to compare two runs.

Not provided means the source did not supply a value. It does not mean zero. Keywords you save are not measured search volumes; captured leads are not verified revenue; a detected tag does not prove that events arrive.

Illustrative records explain a workflow. They are not customer results. Read the evidence status in each blog post before treating an example as a live run.

Draft, review, approve, publish

1. Ask the assistant to draft from verified facts and save the reviewed text. Confirm the saved draft's site and identifier.
2. Read the full text, links, title, factual claims and destination. Correct the draft and review the changed version again.
3. Request a preview that names the exact draft, destination and status: WordPress draft or live publication. A draft in WordPress is a separate state from a draft held in AdvisorSEO.
4. Give approval for that specific action only after checking the preview. If the text, target or status changes, request another review.
5. Check the returned record and inspect the destination. A chat acknowledgement alone is not proof of publication. If the action is unverified, keep it staged and contact support.

The WordPress path exists in source; successful customer publishing, permissions and rollback are not proven by this guide. Do not rely on an untested rollback. Keep an independent copy and review any takedown manually.

Revoking publishing access blocks future authenticated writes. It does not remove content already published on your website.

Publishing credentials

Publishing credentials are set up with support until self-service entry is live. Ask support to confirm the secure setup route. Do not send the application password to support or paste it into Claude, ChatGPT or email.

Once secure entry has been confirmed, use a WordPress Application Password for the intended user and site, rather than the login password. The credential is stored encrypted at rest under the published privacy policy. To revoke it, open WordPress, Users → Profile → Application Passwords, and remove the dedicated entry.

Install and check lead capture

1. Confirm that your existing form, consent notice and lawful basis cover the fields you intend to collect.
2. Ask for the lead-capture setup for the selected website. Inspect its site association. A capture key is site-specific and is not a publishing credential.
3. Install the site-specific snippet in the approved custom-code area on your own website, using the instructions supplied for that site. Avoid duplicate installation.
4. Submit a clearly labelled test through your actual form. Check that it appears in the intended workspace and that ordinary form delivery still works.
5. Remove the test record through your normal data process and document the installation location, so you can remove capture later.

The snippet sends the submitted form's own fields, a honeypot field and a spam-score signal. It reads no other page content, sets no advertising cookie and does not follow visitors around the web. A spam flag is a judgement to review, not proof that a person is genuine or fraudulent.

Not every form integration is proven. If your test is absent, check installation and the selected site's key before collecting more information. Never submit a real customer's sensitive details as a test.

Disconnect in five separate steps

1. Remove the assistant connection. Remove AdvisorSEO in the host's connection or plugin settings. This ends that connection's access; check any other connections separately.
2. Disconnect Google. Ask your assistant to disconnect Google for each website, which deletes the stored connection. Removing the assistant connection does not. To end the permission at Google too, remove AdvisorPPC on your Google account's third-party access page. Google lists AdvisorSEO under that name, and removing it also ends any AdvisorPPC connection made with that Google account.
3. Revoke publishing access. Revoke the dedicated WordPress Application Password in WordPress. Removing the assistant connection is not a substitute.
4. Stop lead capture. Remove the snippet or capture component from every place it was installed and confirm that no duplicate remains.
5. Request deletion. Email [email protected] from the account contact and identify the data request without sending credentials.

Disconnecting does not delete account records or remove content already published to WordPress. The privacy policy explains retention and deletion, including records the law requires us to keep.

Data and safety

The detail sits in the privacy policy and the terms. If something here is unclear or looks wrong, tell us, that is a bug in the writing and we would like to fix it.

Troubleshooting

Connector not listed

Check that your host account permits custom remote connections. Send support the host, visible account option and edition name. Do not assume a submitted directory edition is approved.

Consent keeps looping

Check the signed-in account and workspace on the consent screen. Stop repeated attempts and send the approximate time, timezone and redacted error text. Remove authorization codes and token-bearing URLs.

Publish refused

Check that the selected content version is approved for the intended site and that the dedicated WordPress credential has not been revoked. Send the content identifier, target status and safe error category. Never send the credential.

Snippet not firing

Check the selected site key and whether the snippet is installed once on the page containing the form. Send the public page URL, test time and non-sensitive error text. A screenshot of a filled customer form is not necessary.