To add comments to a web page you do not own, use a browser extension that draws a layer on top of the page: pick the note tool, click the element you want to talk about, and type. The comment stays anchored to that spot, and you share it as a screenshot. No CMS access, no account, no code change.
The page everyone can see and nobody can comment on
You are reviewing a staging build. The pricing block has the wrong currency, the second testimonial is a placeholder, and the footer link goes nowhere. Every tool you would normally comment in — the doc, the ticket, the design file — is somewhere else. So you write an email: "on the pricing section, third card, the price is wrong." Two replies later, nobody is sure which card is the third one.
Why the missing comment layer costs real time
A comment that lives away from what it describes forces every reader to re-find the thing. That lookup is small — ten, twenty seconds — but it happens once per comment, per person, per round of review.
- Ambiguity: "the button at the top" means three different buttons on a responsive page.
- Lost context: the page changes between the moment you write and the moment it is read.
- Round trips: one clarifying question per vague comment, and reviews stretch across days.
- Silent drops: comments that are hard to locate are the ones that quietly never get fixed.
What people use today, and where it breaks
The usual workarounds each solve a piece of the problem and drop another.
- Email and chat: fast to write, impossible to locate. The description has to reconstruct the page in words.
- Bare screenshots: they show the page, but the comment sits in the message body, detached from the pixel it points at.
- Design-tool comments: excellent — on the mockup. They cannot follow the design into the shipped page.
- Hosted feedback platforms: they do anchor comments to a URL, but they need an account for everyone involved and your page content goes through their servers.
- Browser DevTools notes or a text file: private, unstructured, and useless to share.
What a good page comment actually needs
Strip it back and the requirements are short. A comment on a web page should be anchored — attached to the element, not to a description of it. It should be readable in place, so the reviewer sees the remark and the problem in the same glance. It should cost nothing to create: if leaving a comment takes longer than describing it in Slack, nobody will use it. And it should be shareable in one artifact, because a comment nobody can send is a private note.
A good rule of thumb: if you have to write "the third one" or "just below the fold", the comment is in the wrong place. Move it onto the page.
How to comment on any live page in practice
With Highlite, a free extension, the flow takes a few seconds per comment:
- Open the page you want to review and activate the toolbar.
- Press N for a sticky note when the comment is a paragraph of feedback, or T for a text box when a few words on the page are enough.
- Click the element the comment is about, then type.
- Press H to highlight the exact words a comment refers to, so the remark and its target read together.
- Press ⌘⇧E to capture the page with all its comments and send it on.
The comments persist per page in your browser, so closing the tab and coming back to the same URL brings them back. They are stored locally and never uploaded, which matters when the page under review is an internal tool or a client staging site.
On that staging build, you pin a note to the pricing card ("EUR, not USD"), highlight the placeholder testimonial with a note saying "real quote pending from marketing", and drop a third note on the dead footer link. One capture, three unambiguous comments, zero follow-up questions.
Where this approach stops
Be clear about the trade-off. Comments held in your browser are yours alone: there is no shared thread, no @mention, no resolve button, and no sync to a second device. If your team needs a persistent comment database with assignment and status, that is a different category of product. For a review you write, capture, and hand off in the same sitting, the lack of setup is the entire point.
For the wider toolkit, see how to annotate any webpage, and for comments you want to leave as paper-style notes, how to add sticky notes to any website.
Frequently asked questions
Can I comment on a website I do not own?
Yes. A browser extension renders your comments in a layer above the page, so you are never editing the site itself. It works on public pages, internal dashboards, and staging builds alike — anything you can open in your browser.
What is the difference between a sticky note and a text annotation?
A sticky note is a small panel pinned to a spot on the page — best for a sentence or two of feedback. A text box writes directly onto the page, which suits short labels like "wrong size" placed right next to the element. Pairing either with a highlight makes it obvious which words the comment covers.
Do my comments stay on the page after I reload it?
Yes, per page and per browser. Annotations are stored locally and restored when you return to the same URL. They do not sync to other devices or to teammates — to share them, capture the annotated page.
Can other people see the comments I leave on a page?
Not automatically, and that is deliberate. Nothing is uploaded until you decide to share. When you want someone else to see the comments, you capture the annotated page and send that image.
Try it on this article: pin a note to this paragraph and see how the comment reads against the text it is about. Ten seconds, no account.