---
name: seomade
description: >-
  Use the SEOmade MCP server (https://seomade.app/api/mcp) to get a startup listed on launch and
  SaaS directories, audit a site for SEO, AI visibility and agent readiness, and run single SEO
  checks on a URL. Trigger when the user asks about directory submissions, launch lists, backlinks
  from directories, a site audit, llms.txt, indexability, redirects or their SEOmade projects.
version: 0.5.0
homepage: https://seomade.app/developers
metadata:
  site: https://seomade.app
  mcp: https://seomade.app/api/mcp
  install: https://seomade.app/mcp/llms-install.md
  pricing: https://seomade.app/pricing
---

# SEOmade MCP skill

SEOmade is a remote MCP server authenticated with an API key (`Authorization: Bearer sm_live_...`).
If the tools are not connected, follow https://seomade.app/mcp/llms-install.md.

## Tools

- **Catalog (read-only):** `search_directories`, `get_directory`, `catalog_meta`
- **Projects and profile:** `list_projects`, `get_product_profile`, `save_product_profile`
- **Submissions:** `next_submissions`, `get_submission_kit`, `set_submission_status`
- **Site audit:** `run_site_audit`, `get_site_audit`
- **SEO checks:** `list_seo_tools`, `run_seo_tool`

The server also offers three prompts that run these workflows for you: `submit_to_directories`,
`fix_my_seo` and `prepare_product_profile`.

## Workflow 1: get listed on directories

1. `list_projects` to find the `project_id`. If there is no project, ask the user to add their
   site at https://seomade.app/dashboard first.
2. `get_product_profile`. It returns the saved answers and a `missing` list. Ask the user for
   anything missing. Do not make up a tagline, description, category or contact email.
3. `save_product_profile` with what the user gave you. If it rejects a field, fix that field and
   send again. Nothing is saved on a rejected call.
4. `next_submissions` for a short, ranked list of directories not yet submitted.
5. For each one, `get_submission_kit`. It returns the submit URL, the value for each form field,
   and the rules. Fill the form with those values exactly.
6. Straight after each attempt, `set_submission_status`:
   - `submitted` when the site confirms it
   - `pending` when it needs an email confirmation or a review
   - `live` with `listing_url` when the listing is public
   - `rejected` with a short `note` when it was refused

## Rules for submitting

- Use the product's real name, URL and descriptions exactly as stored. No keyword stuffing, no invented claims.
- Ask the user before paying for anything, creating an account, or agreeing to terms for them.
- Never write, buy or trade reviews, votes or upvotes. Never post as anyone but the user.
- If a site shows a CAPTCHA, a login you do not have, or an email confirmation, stop and hand that step to the user.
- Pick the closest real category the form offers. If nothing fits, ask.
- Submit each directory once, then record the result.

## Workflow 2: audit and fix a site

1. `run_site_audit` with the `project_id`. It audits the project's own URL and takes a little while.
2. `get_site_audit` for the scores (SEO, AI visibility, agent readiness) and the issues, most
   valuable first. Each issue says what was measured and how to fix it.
3. Fix issues in the user's codebase in that order. Show the user the change before you ship it.
4. Confirm a single fix with `run_seo_tool` (for example `indexability-checker`, `redirects`,
   `llms-txt-checker`, `internal-link-checker`), then run the audit again.

## Workflow 3: one quick check

`list_seo_tools` returns every check with its slug and inputs. `run_seo_tool` runs one, for example
`{tool: "meta-analyzer", params: {url: "https://example.com"}}`. Private and internal addresses are refused.

## Limits

Audits and tool runs count against the plan quota for the key. `catalog_meta` shows what is left.
The quota is daily and resets at midnight UTC. On a `429`, tell the user and stop retrying.
