Website
Project Settings
Project settings the owner controls. Indexing: a new project is not indexable (noindex, no sitemap.xml) until the owner says it may be. Read the state with get; make the website indexable with set-indexable only after the owner answered yes, passing their literal answer.
Endpoints (2)
Indexing state of this project: indexable (what search engines get now), force_noindex and why (new_project_default, owner_setting or default), who changed it and when, the owner confirmation on record, and whether the plan allows indexing. Read-only.
No input parameters required.
Make the website indexable (indexable true) or hide it from search engines again (indexable false). indexable true needs owner_confirmation: first ask the owner "Should the website be indexable now?" and pass their literal answer. Never call it with true without a clear yes from the owner in this conversation, and never write the answer yourself. indexable false needs no confirmation. On the Free plan pages stay noindex whatever this setting says.
| Field | Type | Required | Description |
|---|---|---|---|
indexable |
boolean | ✓ Yes | true = search engines may index the website; false = noindex. |
owner_confirmation |
string | No | Required when indexable is true: the literal answer of the owner, 2-500 characters. |
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| get | project-settings_get |
| set-indexable | project-settings_set_indexable |