Netvibes
Operated by Dassault Systemes (Netvibes)
Quick Facts
- User-Agent:
- Netvibes
- Category:
- SEO Tools
- Operator:
- Dassault Systemes (Netvibes)
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by Dassault Systemes (Netvibes)
Reported, not operator documented
Dassault Systemes (Netvibes) has not published a crawler page that names Netvibes. It is listed here on our own evidence. Verified by AI Crawler Check: 24 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for Netvibes, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Netvibes (Dassault Systemes) feed reader UA.
What that means for you: the Netvibes rule on this page is the best available spelling, but Dassault Systemes (Netvibes) has made no statement of purpose, crawl rate or robots.txt compliance. Treat a Netvibes request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.
What is Netvibes?
Netvibes is a monitoring and validation agent operated by Dassault Systemes (Netvibes). It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Netvibes is a monitoring and validation agent operated by Dassault Systemes (Netvibes). It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Netvibes uses the user-agent token Netvibes. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block Netvibes?
How to block Netvibes with robots.txt
<code>User-agent: Netvibes</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Netvibes safe to allow?
What does Netvibes do?
Understanding Netvibes's purpose helps you decide whether to allow or block it.
- Validates pages, ads, or policy compliance
- Performs automated quality and safety checks
- Does not collect training data
- No impact on search rankings
- Generally safe to allow
Netvibes in context
Netvibes is a utility crawler operated by Dassault Systemes (Netvibes). In plain terms, it checks pages for an SEO, uptime or analytics service. Our database files it under SEO tools and ranks it Tier 4, specialist crawlers that matter to particular sites or markets. 19 of the 19 SEO tools in our database share this tier.
Its safety rating is safe and its blocking impact is not documented. So the decision about Netvibes rests on what you want from Dassault Systemes (Netvibes), not on its behaviour. How we rate safety and impact.
How site owners treat Netvibes
In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 24 files (0.4%) name Netvibes in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.
Does it follow robots.txt?
Netvibes's operator does not clearly document how it treats robots.txt. Write the Netvibes rule anyway, then confirm in your logs that its requests stop.
Dassault Systemes (Netvibes) crawlers and close alternatives
Dassault Systemes (Netvibes) runs only this one crawler in our database, so a single User-agent: Netvibes group controls everything Dassault Systemes (Netvibes) fetches through it.
Other SEO tools that do the same job (checks pages for an SEO, uptime or analytics service) include AhrefsBot from Ahrefs, AhrefsSiteAudit from Ahrefs, AwarioBot from Awario, AwarioRssBot from Awario, AwarioSmartBot from Awario, Chrome-Lighthouse from Google. Deciding about Netvibes is usually a decision about the whole group, so check how your file treats these too.
We first recorded Netvibes on March 17, 2026. We could not find a page where Dassault Systemes (Netvibes) names it, so treat the token as reported rather than documented.
Which rule Netvibes actually follows
Netvibes reads exactly one group in robots.txt, the most specific one that names Netvibes, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: Netvibes
Disallow: /drafts/- Find the group. Netvibes looks for a group naming
Netvibes. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to Netvibes, because that rule lives in the*group it no longer reads. To keep it out of both, repeatDisallow: /private/inside its own group.
Test yourself: does a rule under User-agent: * apply to Netvibes if the file also has a User-agent: Netvibes group?
No. Once a group names it, Netvibes reads only that group. Put every rule you want it to follow inside its own group.
Test yourself: will blocking Netvibes remove your pages from AI answers?
Often, yes. Netvibes is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.
Test yourself: is User-agent: netvibes the same as User-agent: Netvibes?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow Netvibes? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Low stakes either way. It does not decide whether AI answers cite you. |
| You license content and want to stop AI training | Blocking it does not stop training, because Netvibes is a utility crawler. Block the operator's training crawler instead. |
| You run an online shop | Allow it unless your logs show it is costly. |
| Your server is under load from bots | Rate-limit before blocking. It is rated safe in our database. |
Check Netvibes on your own site
- Open
/robots.txton your domain and search forNetvibes. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group Netvibes follows and test your key URLs against them; the longest match wins, andAllowwins a tie. - Look beyond the file. A firewall or bot manager can refuse Netvibes even when robots.txt allows it, and that never shows in the file.
- Run our website crawlability test to see how Netvibes and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with Netvibes
The errors we see most often with Netvibes in the files and firewalls we test:
- Treating Netvibes as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when Netvibes is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Netvibes by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check Netvibes from outside after every change.
Spotting Netvibes in your logs
robots.txt says what Netvibes may do; your access logs show what it actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "Netvibes" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -cAnd this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "Netvibes" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20Check the requests are genuine
Anyone can send the Netvibes user-agent, so confirm the source before acting on a match:
Netvibes: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Netvibes request with caution.
Frequently Asked Questions
What user-agent string does Netvibes use?
Netvibes. Evidence that the spelling is in real use comes from our own robots.txt study: 24 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Dassault Systemes (Netvibes), which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.Is Netvibes safe?
Will blocking Netvibes hurt my SEO?
How do I block Netvibes in robots.txt?
/robots.txt file:User-agent: Netvibes Disallow: /
This instructs Netvibes not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Netvibes respect robots.txt?
Netvibes will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if Netvibes is crawling my site?
Netvibes (for example grep -i "Netvibes" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Dassault Systemes (Netvibes) sent it.