Site rules
Overview · Actions · Site rules · Export & import · Permissions · FAQ
Every shortcut carries its own site scope. There are three modes.
| Mode | Behaviour |
|---|---|
| All sites | The default. The shortcut works everywhere. |
| Only these sites | An allow list. The shortcut works on the listed hosts and nowhere else. |
| Except these sites | A deny list. The shortcut works everywhere but the listed hosts. |
How a pattern matches
Patterns are matched against the page's hostname. One pattern per line.
| Pattern | Matches | Does not match |
|---|---|---|
example.com |
example.com, www.example.com, a.b.example.com |
notexample.com |
*.example.com |
Identical to the line above — the bare domain and its subdomains | notexample.com |
A plain domain already includes its subdomains, so
example.com and *.example.com behave the same way.
The *. form exists because people expect to be able to write it;
it is not a different rule. There is no pattern that matches a domain
without its subdomains.
Paths, query strings and ports are not part of the match. A rule for
github.com applies to every page on GitHub.
Write the bare hostname, in lower case. Version 1.0.0 does not
validate what you type, so a malformed pattern shows up as "the shortcut does nothing"
rather than as an error. GitHub.com, https://github.com,
github.com/user and *github.com all silently fail to match.
Worked examples
- Mute only where you watch video. Bind Alt+M
to Mute / unmute tab, mode Only these sites, patterns
youtube.comandtwitch.tv. Both cover their subdomains automatically. - Keep a shortcut away from an app that already uses it. Bind
Alt+J to Next tab, mode Except these sites,
pattern
docs.google.com. It works everywhere else. - Two different actions on the same keys. Nothing stops you binding the same combination twice with non-overlapping site scopes — the first matching rule in list order wins. ⚠️ In version 1.0.0 the list order is the order you created them in, and there is no way to reorder in the interface. If you need a narrower rule to win, create it first, or delete and re-add the broader one so it lands after.
What happens on pages the extension cannot reach
Chrome does not allow extensions to run on its own internal pages
(chrome:// addresses, the Web Store, and the new tab page in some
configurations). Page-level shortcuts do not fire there. This is a browser rule,
not a setting.