Frequently asked questions

Still stuck? Read the docs or create a free account.

How do non-technical clients report website changes?

Your client clicks the part of the page they want changed and describes it in their own words — no account, no screenshots, no jargon. An AI then interviews them like a senior developer would to fill in the missing detail.

What does SiteUpdate put in a developer ticket?

A written spec of the requested change, the exact element and page URL, a masked session replay, console logs and network errors, browser and device context, and reproduction steps — deduplicated against existing requests.

Will the capture widget slow down or break my site?

No. The widget is under 40KB gzipped and all capture code is error-isolated, so a failure inside it can never break the host site. It loads asynchronously and does nothing until a visitor starts a request.

What do you capture, and is it private?

Privacy is the default: session replay is masked, inputs are redacted, cookies and localStorage are allowlist-only, and Authorization and Cookie headers are never captured. You control what is recorded.

Which tools does SiteUpdate integrate with?

GitHub, Jira, Linear, and Slack two-way, plus Zapier, a Chrome extension, a REST API, and an MCP server so coding agents can pull fully-contexted tickets directly.

Does it work with WordPress, Webflow, and Shopify?

Yes. SiteUpdate is a small script tag that works on any website, including WordPress (there is also a dedicated plugin), Webflow, Shopify, and custom stacks. On WordPress, approved text fixes can also be applied directly through the plugin — see Autofix.

Can SiteUpdate fix the change itself?

For small plain-text edits, yes. When a client edits text in place, Autofix drafts the exact old-to-new change and shows you a diff to approve — free to preview on every plan. Approve it and it opens a GitHub pull request (never auto-merged) or applies the change directly on WordPress. It only ever touches a single exact text match, never markup or layout, respects the pages you protect, auto-reverts if a page breaks, and rolls back in one click. Shipping fixes is a Pro feature (25 a month); seeing the proposed fix is always free.

Is there a free plan?

Yes. The capture widget, API, MCP server, and console logs stay available on the Free plan. Paid plans add more sites, team seats, and higher AI intake volume.

How is this different from a normal bug tracker or feedback widget?

Feedback widgets dump raw complaints on your developers. SiteUpdate serves both ends: the requester stays simple while the AI turns a vague request into a dev-ready ticket — then tells the requester when the fix is live.