Domain ranking: block, lower, raise, pin
Domain ranking reshapes which results you see and in what order, permanently, across every search. There are four actions:
- Block — remove a site's results entirely.
- Lower — push a site down.
- Raise — pull a site up.
- Pin — force a site to the top.
Ranking runs after results are fetched, as a re-rank over the normal order, so it is instant and never costs an extra search. Rules are yours to set from two surfaces: the per-result Adjust control, and Settings → Search Control.
The Adjust control
Every result on the page carries an Adjust chip. Open it to block, lower, raise, or pin the result's site — or reset it to normal — in one click. The chip shows the site's current state, and a change takes effect on your next search. For finer control (strength, match type, scope, query conditions), use Settings → Search Control.
Match types
A rule can match a site or URL in several ways:
| Match type | Matches | Example pattern |
|---|---|---|
| Domain | Exactly this host (and www.) |
example.com |
| Domain suffix | This host and its subdomains | example.com (also blog.example.com) |
| Host wildcard | A host glob with * |
*.ru, news.*.com |
| URL path | URLs that start with host + path | example.com/blog/ |
| URL regex | A regular expression over the full URL | ^https?://m\.example\.com/ |
| Title keyword | The result title contains text | sponsored |
| URL keyword | The result URL contains text | /amp/ |
| Any keyword | Title or URL contains text | utm_ |
The Adjust chip uses domain suffix, so a rule covers the whole site, subdomains included; example.com and
www.example.com are always treated as the same host.
Strength (weight)
Lower and raise carry a strength that nudges a result down or up; the Adjust chip uses a moderate ±60. In Settings you can set any strength: lower is −1 to −100, raise is +1 to +100. Pin carries a priority (0–100) that orders multiple pins. Block has no strength — it removes the result outright.
How overlapping rules are resolved
When more than one rule matches a result, Suede resolves them deterministically:
- Block wins over everything (a blocked result is removed).
- Then pin (highest pin priority first).
- Then raise / lower combine: the strongest matching adjustment leads, with weaker matches contributing a fraction; the total is clamped to ±100.
- A more specific match beats a broader one (a URL/path/regex rule outranks a domain rule, which outranks a suffix rule, which outranks a keyword rule).
- Layering: your personal rules beat an active view's rules. A personal normal can neutralize a lower-priority rule from a view or list.
Summoning pinned sites
If you pin a site, Suede summons it: it fetches that site's results for your query and ranks all of them ahead of everything else — a pin's results can span page after page, with everything else following after. This happens even when the site already ranks on its own, and the summon runs alongside the normal fetch rather than after it, so it costs no time. The digging is demand-driven: it starts a page deep and keeps going as you page, so a pin with plenty to give keeps leading until it genuinely runs out (admins set how many pins are summoned per search and a per-pin depth ceiling). It applies to site pins (domain / domain-suffix / path) and keyword pins, and works across every result source Suede is drawing from. Wildcard and regex pins — and anything beyond the ceiling — still pin whatever surfaces in the ordinary results, on the page where it appears.
Transparency
Suede always tells you what it changed. The results page shows a summary bar — "N blocked · N raised · N lowered ·
N pinned by your rules" — and each adjusted result carries a small why tag (raised / lowered / pinned). Expand
the summary to see exactly which sites were blocked, and unblock any of them with one click. To see the page
exactly as it came from the index, follow the raw results link (or append ?pz=0 to the URL).