Requesting changes

claude mcp add --transport http sitekick-docs https://docs.sitekick.ai/mcp

codex mcp add sitekick-docs --url https://docs.sitekick.ai/mcp

{
  "mcpServers": {
    "sitekick-docs": {
      "url": "https://docs.sitekick.ai/mcp",
      "type": "http"
    }
  }
}

Requesting changes

You shape a Studio site by asking. Requests can be as casual as a note to a colleague — Studio reads plain language and applies the change to the draft.

How to ask

Say what you want, where you want it. A few examples:

• "Make the headline on the homepage shorter."
• "The services page should mention that we travel within Greater Vancouver."
• "Remove the pricing table — we quote by project."
• "The whole thing feels too playful. Make it calmer and more premium."

You do not need to know the name of an element or the page's internal structure. Describe it the way you would to a person.

One change at a time works best

Small, specific requests produce precise revisions. If you list five unrelated changes in one message, you may get five imprecise ones back. Stack your requests in the order that matters most to you.

It is fine to iterate

If a revision misses, say what is still wrong — "closer, but the tone is still too formal" is useful feedback. Each pass narrows in on what you want. This loop is the product working as designed, not a failure.

When a request cannot be done

Some things fall outside what Studio can change — for example, features that belong to a plan you are not on. When that happens, Studio tells you rather than silently ignoring the request.

Next steps

• Happy with the draft? Continue to Publishing.