In short
Website markup means commenting on a page exactly where it's meant – by clicking the element itself instead of describing it in a separate email. A code snippet overlays a comment layer on the real page, and every note remembers the element, position and environment.
What does “marking up a website” actually mean?
Instead of describing a spot on a page, you click it. A small tool overlays a comment layer on the website so every note is tied to a real element, not an approximate position in a description.
How it works technically
A one-line code snippet is added to the website. It loads an overlay layer that intercepts clicks on elements and turns them into a note with an element reference – without altering the website itself.
The flow in four steps
A typical markup session looks like this:
- 1. Open the link to the page with the active snippet
- 2. Click the element that needs feedback
- 3. Type the comment; the environment is captured automatically
- 4. The note appears in the shared overview with a status
Why no account?
As soon as a login is required, usage by external viewers drops noticeably. nootiz allows commenting through a simple link because “create an account” is often the actual reason feedback never happens.
What gets captured automatically
For a note to stay traceable later, markup records more than the plain text:
- The exact position of the element on the page
- Browser, operating system and screen resolution
- URL and, where relevant, scroll position
- The time the note was created
Markup on responsive pages
Because layouts differ by device, a note on “the image at the top” is ambiguous on mobile. Markup tools bind the note to the element itself, so attribution stays independent of the device.
Difference from screenshot tools
A screenshot comment shows a frozen moment but loses the connection to the live page. Markup stays linked to the actual element, even if the surrounding content changes later.
Password-protected and internal pages
Markup also works on staging environments with access protection, as long as the snippet is embedded and viewers have access to the page itself.
From note to task
A good markup solution doesn't stop at the note. Handing it over to Asana, Trello, Jira or GitHub decides whether the feedback actually gets worked on or sits in a list.
Limits of website markup
Markup doesn't replace automated functional testing or code-level quality assurance. It's a tool for visual and content feedback from people who are looking at the page.
Conflicting markup notes on the same spot
When two people leave opposite notes on the same element, that's not a tool problem — it's a normal part of a review with several participants. Read both notes in context instead of handling them separately, and mark one as the leading direction once a responsible person has decided. Reply right at that spot so both people can see which direction is being implemented, instead of moving the clarification into a separate email.
Checklist before rolling out markup
Before introducing a markup tool on a project, it's worth checking:
- Is the snippet embedded on staging and/or the live site?
- Does everyone know that feedback only counts through this channel?
- Is it clear who resolves notes and who only reads them?
- Is there a rule for when a note counts as done?
Frequently asked questions
Does the markup snippet change my website?
No, it only overlays a comment layer and doesn't touch the page's code or design.
Does markup work on any website?
Yes, as long as the snippet can be embedded, regardless of the CMS or framework used.
Do viewers need an account to comment?
No, a link is enough, which is the key difference from classic project tools.
What happens to notes if the element later changes or disappears?
The note keeps its context (position, screenshot excerpt, timestamp) even if the element no longer exists.
Can markup be used offline or on PDFs?
Website markup applies to live web pages; PDFs need different annotation tools.
Is markup only useful for design feedback?
No, it works equally well for copy fixes, bug reports and functional notes.
How many people can mark up a page at once?
As many as needed, since every note is independent and doesn't require exclusive access to the page.