Fixing with AI

Loomaly never edits your site. Your AI assistant (or a developer) makes the change; Loomaly ranks what to fix and re-checks the live page.

Through your assistant (recommended)Copy Anchor Link

1. Connect Claude Code, Cursor or Codex — see MCP.
2. status, then todo. The top open item already carries fixPrompt, evidence, url, and verify. Call problem only when you need more detail.
3. Apply fixPrompt in the repo on a branch (or send_to_dev) and open a PR.
4. Immediately check with target: fix and ref set to the PR URL.
5. Loomaly waits briefly; if the page is unchanged it awaits deploy and re-checks on its own. The next status announces the result.

Ops and product roles can call send_to_dev instead of editing the repo — paste the task to a developer. See Roles.

Paste-ready starter:

Use Loomaly to see what to fix first. Fix the top issue in this repository on a new branch, open a PR, then check with target fix and the PR URL as ref.

What todo / problem returnCopy Anchor Link

The top todo item includes the rule, the affected URL, scan evidence, and fixPrompt — an instruction written for your site's framework (Next.js, Nuxt, Astro, SvelteKit, WordPress, Shopify, and a general fallback). problem expands the same for one findingId when you need more. When the same rule is open on other pages of the same template, the result says how many; one layout change often clears them all.

After it is liveCopy Anchor Link

check with target: fix and the PR URL as ref starts the re-check. If the live page has not changed yet, the attempt sits in awaiting deploy (under your plan's cap); Loomaly re-checks automatically at no charge. When the problem is gone, the issue closes. If it is still there, the finding stays open with fresh evidence.

Page-judgment issues (for example two pages competing for the same search) need a later full-site pass (check target: site or the weekly rescan), not a single-page re-check. See Issues.

Not a developer?Copy Anchor Link

In Claude web, ChatGPT or a similar chat client, ask Loomaly to explain the top problem in plain language. Use send_to_dev (ops role) for a paste-ready brief, or follow CMS-oriented steps the assistant drafts from the evidence. Account and billing stay at /account.