Website feedback for web designers

For web designers – Design feedback that is unambiguous: your client marks the element, you get an actionable change instead of a description.

In short

The client opens the page through a link, clicks the element and writes the change right on it – no account, no screenshot PDF. Every note keeps its location, author and status, so you close rounds instead of sorting them.

An open nootiz note with a comment thread right on the design element

Typical problems this removes

  • Contradictory change requests
  • Feedback with no reference to the page
  • Endless correction loops
  • Clients describe layout problems in words instead of showing them
  • Changes get lost between mockup, staging and live

How do you get design feedback you can act on directly?

You send the client a link to the staging site instead of a PDF export. The client clicks the element that's off – spacing, colour, image crop – and writes the requested change right on it. “The spacing at the top looks off” becomes a note with an exact coordinate you can act on without asking anything.

How do you resolve contradictory change requests from different stakeholders?

When management and marketing disagree about the same button, two notes on the same spot show it instantly, with author and timestamp. You don't have to reconstruct the contradiction from two email threads – you see it at a glance and can settle it before the next draft.

How do you tell layout bugs apart from pure taste preferences?

A wrapped line of text or a clipped button only shows up in the real layout, never in a mockup. Because notes are created on the live page, you see immediately whether a comment points to a technical bug or a stylistic preference, and can prioritise accordingly.

How do you keep feedback separate between draft, staging and live?

Every nootiz project is tied to a domain or staging system, so notes from the draft phase never mix with notes from production. When you push a new version, you can see clearly which notes belong to it and which are still open from an earlier round.

How do you cut the number of correction rounds?

Most extra rounds happen because a phrase like “the image top right” can mean more than one element. A note attached to the element itself removes that ambiguity entirely. That measurably lowers how often you need to ask before you can change anything.

How do you document a design approval for the client?

Every note carries a status from open to done. When the client accepts a change, either of you marks the note done. At the end of the project, the list shows what was requested and what was delivered, with no separate log to maintain.

How do you work with clients who don't know a design tool like Figma?

The client doesn't need to learn a tool. They open a link, see the real website, and click the spot that bothers them. That works regardless of whether the site was built with Webflow, WordPress, Shopify or a custom system, as long as the snippet is added.

Frequently asked questions

Does nootiz work on Webflow, WordPress or Shopify?

Yes. It is enough to add the snippet to the page.

Can a client mark an element without knowing its name?

Yes. They just click the spot on the page; nootiz captures location and context automatically.

How do I handle contradictory feedback from two stakeholders?

Both notes appear with author and timestamp on the same spot, so the contradiction is visible immediately.

Can I keep draft notes separate from notes on the live version?

Yes, every project is tied to its own domain or staging environment.

Can I see which changes the client has already accepted?

Yes, every note shows its status from open to done.

Do I need to give the client access to my design tool?

No. The client only works with the link to the page, not with Figma or any other tool.

Who nootiz is built for

Stop collecting feedback in email threads

Add the snippet, share the link, collect feedback right on the page – live in under 5 minutes.