How Hugsa Vakt works
Hugsa Vakt checks one source at a time, stores a baseline and tells you when something genuinely changes.
- Choose a source Enter an address or choose a verified source. You can choose a section, keywords and an interval.
- We check The first check becomes the baseline. Later checks read the source at your interval, with ETag/Last-Modified, size and time limits, and respect for robots.txt.
- You get a notification When content changes, the change is stored with evidence and you are notified according to your settings.
Content changes
The page is read, text blocks are normalized and compared with the previous baseline. You see what appeared and what disappeared.
Good for: Deadlines, notices, conditions and other information that changes rarely but matters.
Limit: We do not check JavaScript-rendered content or pages whose main content is hidden behind a login.
New items
RSS/Atom feeds and listings are read for stable items. Items are deduplicated by URL or provider identifier.
Good for: Notice lists, procurement pages and feeds where you only want to know about new items.
Limit: No crawling of the linked pages. We open only the source you chose.
Keyword match
You choose one or more text terms. We tell you when they first appear or disappear.
Good for: Following specific names, phrases or terms on a large page.
Limit: Matching is simple text matching, not natural language understanding. You can use several terms and exclude others.
The first check does not alert
When you create a watch, Hugsa Vakt captures a baseline. That baseline is the starting point, not a change. Without this rule, a new watch would alert about everything that was already there.
If you later change the address, mode, selector or keywords, a new baseline is captured. That is also honest: the basis for comparison has changed.
Limitations
We prefer to state the limit rather than promise too much.
- We check selected public sources only – not the whole web.
- We do not take content from behind a login, paywall or CAPTCHA.
- We do not check pages that are built with JavaScript and have no static content.
- A source can stop, move or change its structure. Hugsa Vakt shows that instead of inventing a change.
- Notifications can be delayed. Always check a deadline at the original source.
The states you see
The status reports what the last check found – not what we think.
- No changes The last check succeeded and found no change.
- Change detected The last check found a genuine change.
- Source temporarily unavailable The source did not answer, returned an error or asked us to wait. We retry later.
- Check error The content could not be read or looked implausible. We keep the previous baseline.
- Not supported The source is blocked by robots.txt, source policy or because the address is unsafe.
- Paused You paused the watch. No checks are running.
Questions and answers
Can Hugsa Vakt follow the whole web?
No. You choose one source at a time. Hugsa Vakt does not follow links on the page or check other pages without your consent.
Why did I get no alert from the first check?
The first check is a baseline. It does not alert because all of the content is already new to you. The next genuine change will be reported.
How soon is a source checked?
On the interval you choose, with a minimum of 3 hours. Sources can require a longer interval, and a daily check limit applies to everything.
Do you store whole pages?
No. We store a normalized, size-limited baseline of the extracted text and short evidence for changes. We do not store raw HTML bodies.
What if a source changes its layout?
We normalize text and compare content, not rendering. A layout change should not produce an alert. If a source becomes unstable, Hugsa Vakt stops email alerts and shows it.
Can I get alerts without email?
Yes. In-app notifications are always available. Email requires a verified address and an SMTP connection configured by the operator.
Start with one source
You can pause, edit or delete the watch at any time.