Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed wording of advanced blocking with wildcards #635

Merged
merged 2 commits into from
Dec 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/kagi/features/website-info-personalized-results.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ You can also apply Personalization in image search results by clicking the shiel

![Kagi Image search personalization](./media/block_domain.gif)

If you need advanced blocking features, such as specifying rules by match patterns (e.g., `*://*.example.com/*`) or by regular expressions (e.g., `/example\.(net|org)/`), the [uBlacklist](https://github.com/iorate/ublacklist?tab=readme-ov-file#ublacklist) browser extension includes support for Kagi Search.
Kagi Search allows you to block entire domains as part of its ranking tools, but it doesn’t currently support advanced blocking methods like path wildcards (e.g., `*://example.com/path/*`) or regular expressions (e.g., `/example\.(net|org)/`) – for these advanced options, the [uBlacklist](https://github.com/iorate/ublacklist?tab=readme-ov-file#ublacklist) browser extension offers these capabilities and integrates with Kagi.

## Domain Leaderboard

Expand Down