SEO MCP Guides

Learn how to use SEO MCP responsibly, write verifiable prompts, audit content for search and AI answers, and choose MCP or an API.

These guides help you decide how to use SEO MCP across projects and tasks. Start with a workflow if you already know the outcome you need; return here when you need a reusable prompting, automation, or integration decision.

Choose a guide by decision

Decision	Guide	What you will learn
How should I ask for a checkable answer?	Prompt library	Add project scope, evidence, limits, and an output format to a real SEO question.
Which actions are safe to automate?	Responsible SEO automation	Separate read-only analysis, explicit writes, confirmation, and human review.
What can crawl evidence say about content and AI answers?	Content and AI search audits	Check technical foundations while keeping editorial quality and AI citations outside a crawl's claims.
Should I use MCP or the Screpy REST API?	MCP versus SEO API	Choose a conversational, tool-driven investigation or a deterministic application integration.

From a guide to a result

Use a guide to set the boundaries, then choose one workflow and test it against data your account can access. A useful result includes the source tool, project and dataset, exact finding, uncertainty, and a validation step. A copied prompt alone does not prove a finding.

If you are planning an automated report

Start with responsible automation to set read-only scope and reporting provenance. Then select the specific crawl comparison, ranking, or AI visibility procedure. These datasets have different dates and units; do not merge their observations into one unexplained score.

If you are reviewing a page for search

Use the content audit guide to separate crawlable technical signals from editorial quality. Inspect the actual page and relevant page records. For an AI-answer observation, open the underlying answer record before changing content. A citation or ranking is an observation, not proof of why it appeared.

If you are building a product integration

Read MCP versus REST API before designing the interface. Confirm that the exact operation exists in the current tool or API surface and decide which system owns authentication, retries, and stored results. The prompt library is useful for interactive analysis, but a copied prompt is not an application contract.

New guides should answer a distinct reader decision and link to the existing page that handles its prerequisites or execution. Closely related wording does not need a separate URL. The documentation overview remains the map for connection, tools, workflows, guides, and troubleshooting.