Add and remove sites

How to add a site to SEOFix, what counts as one site, how many sites each plan includes, and what happens when you delete one.

Updated 8 October 2026View as Markdown

To add a site, go to Sites → Add site, enter the address (for example example.com) and choose Add site. Agents can do the same with create_site (MCP) or POST /v1/sites. The Free and Starter plans include 1 site, Growth includes up to 30.

Add a site

  1. Open Sites (or the Dashboard) and choose Add site.
  2. In Website, enter the address. You can type example.com: SEOFix assumes https:// when you leave out the scheme.
  3. Choose Add site. You land on the new site's page, where you can run an audit and verify ownership.

The audit starts from the site's home page. It crawls at 2 requests per second by default.

Agents and scripts:

curl -X POST https://api.seofix.ai/v1/sites \
  -H "Authorization: Bearer $SEOFIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'
{
  "id": 42,
  "url": "https://example.com/",
  "host": "example.com",
  "verified": false,
  "monitoring": "off",
  "max_pages": 500,
  "max_rps": 2,
  "alert_email": true,
  "verify_token": "…",
  "verify": {
    "url": "https://example.com/.well-known/seofix-verify.txt",
    "content": "seofix-verify=…",
    "content_type": "text/plain"
  }
}

MCP: create_site with url, and optionally max_pages, max_rps and alert_email. list_sites and get_site read them back (GET /v1/sites, GET /v1/sites/{id}).

Field Rule Default
url A public http or https address required
max_pages Pages per audit, 1 up to your plan's limit 10,000 or your plan's limit, whichever is lower
max_rps Requests per second, 0.5–10 (above 3 needs a verified site) 2
alert_email Email the team when an audit finds new errors true

You can also add sites in bulk from Google Search Console. See Connect Google Search Console.

What a site is

A site is one origin: a scheme, a host and, if it is not the default, a port. SEOFix drops any path you enter, so https://example.com/blog becomes https://example.com/.

  • One host per site. A team can have only one site per host. Adding the same host twice returns 409 site_exists.
  • www and the bare domain. During an audit, links between example.com and www.example.com count as internal, and the crawl follows a home page redirect from one to the other. Add the host your home page actually ends up on.
  • Subdomains are separate sites. blog.example.com is its own site and uses its own site slot. In an audit of example.com, links to blog.example.com are checked as external links, not crawled.
  • Ownership is per site. Each site has its own verification token. A DNS TXT record on example.com can verify any subdomain site, but each site needs its own record value. See Verify site ownership.

Site limits per plan

Plan Sites Pages per audit Scheduled monitoring
Free 1 500 No
Starter 1 10,000 to 500,000, by page tier Yes
Growth 30 250,000 to 500,000, by page tier Yes

When the team is at its limit, Add a site shows "Your plan includes N site(s)" and the form is disabled. The API answers 403 with error code plan_limit_sites:

{"error": {"code": "plan_limit_sites", "message": "Your plan's site limit has been reached."}}

Remove a site or upgrade to add another. Plans and prices are on the pricing page.

Some limits also depend on ownership, not only on the plan. Until a site is verified, audits are capped at 500 pages and 3 requests per second, and monitoring stays off. See Verify site ownership.

Change a site's audit settings

On the site page, the Audit settings panel sets the Page limit and Speed (req/s) used by manual runs and scheduled monitoring. Choose Save settings. Speed is "Capped at 3 until verified" and goes "Up to 10 when verified".

Agents: PATCH /v1/sites/{id} with max_pages, max_rps, alert_email or monitoring (off, weekly, daily), or the MCP tool set_monitoring.

Remove a site

  1. Open the site's page.
  2. Under Danger zone, choose Delete site.
  3. Confirm with Delete site.

Monitoring stops and the site leaves your sites list. Its past audit reports stay available under Audits. Removing a site frees its slot for another one.

If the site is connected to Cloudflare, SEOFix first deletes the firewall rule and the TXT record it created in your zone. If Cloudflare refuses, the delete is refused with 409 cloudflare_connected, so no skip rule is left in your zone without anyone managing it. Fix the token in Cloudflare or disconnect first, then try again. See Connect Cloudflare.

Agents: DELETE /v1/sites/{id} answers 204. There is no MCP tool for deleting a site.

More in Sites & firewalls

Still stuck? Email [email protected] with your site and what you expected to see.