Workflow

How to keep notes attached to specific URLs.

If you have ever copied a link into a notes app just to explain what a page meant, you already know the problem. Browser notes become valuable when the note and the URL stay connected automatically.

Use exact URL notes when the page itself matters.

An exact URL note is ideal when the note belongs to one page and would be misleading anywhere else. That could be a competitor pricing page, a doc explaining one API behavior, a staging route with a reproducible bug, or a student source page with a specific quote.

Know the difference between exact URL and domain notes.

Exact URL notes

Use them for page-specific information. The note should show up only when you return to that exact location.

Domain notes

Use them when the thought applies across a whole site, such as “this dashboard hides export actions in the overflow menu” or “this CRM always requires manual follow-up after import.”

Global notes

Use them when the browser itself is the context rather than the site.

Keep the note attached to the relevant part of the page too.

URL persistence is the first layer. Source-linked context is the second. Highlighted text, clipped selections, and stable element anchors make it easier to jump back to the exact paragraph, button, card, or section that triggered the note.

Text anchors help with quotes, evidence, and source passages.
Element anchors help with dashboards, web apps, and complex interfaces.
Auto-placement near the source reduces reorientation time on revisit.

Use the dashboard when the URL note becomes part of a larger project.

Exact URL notes are strongest when paired with search, saved views, exports, and collections. That lets you keep page context without losing the ability to review a full research or QA project later.