Reviewing the AI draft

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"
    }
  }
}

Reviewing the AI draft

When Studio presents a draft, you are looking for two kinds of feedback: what is wrong, and what is missing. Both are normal parts of the process.

What to check on each pass

Structure first. Do the pages make sense? Is anything obvious missing? Is anything there that you do not need? Structural feedback is the most valuable early feedback, because everything else builds on it.

Then the copy. Read each page and ask:

• Is it accurate? Services, service areas, and business details must be right.
• Does it sound like you? If the tone is off, say so in your own words.
• Is anything overstated? If the draft claims something your business does not do, flag it.

Then the design. Does the feel match the brief? You do not need design vocabulary — "make it calmer" or "this feels too corporate" is enough.

Finally, the details. Contact information, links, and anything a customer would use to reach you.

You do not have to fix everything at once

It is fine to review in small passes. Point out the biggest thing first; Studio incorporates that feedback before the next revision. Several focused rounds usually beat one overwhelming list.

Accuracy is your job

Studio knows a lot about websites, but only you know your business. Dates, prices, service areas, licenses, and claims about your work should always be checked against reality before you publish.

Next steps

• Learn how to phrase feedback: Requesting changes.