This quickstart walks you through the core workflow: adding a URL blocking rule, flipping the toggle to activate it, and confirming in Chrome DevTools that matching requests are being dropped. By the end you will have a working rule in place and a clear mental model of how Traffic Blocker operates.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/alexperezortuno/ce-blocker/llms.txt
Use this file to discover all available pages before exploring further.
Open the extension popup
Click the Traffic Blocker icon in the Chrome toolbar to open the popup. If you do not see the icon, click the puzzle-piece Extensions menu (⊞) to the right of the address bar, find Traffic Blocker in the list, and click the pin icon to keep it visible in the toolbar at all times.
Add a URL pattern
The Dashboard view shows two input fields at the top:
- Initiator domain (optional) — enter a domain such as
tracker.ads.comto restrict the rule so it only blocks requests that originate from that domain. Leave this field blank to block the URL pattern regardless of which page or origin triggers the request. - URL filter (required) — enter the pattern you want to block. Patterns follow Chrome’s
urlFiltersyntax:*matches any sequence of characters (protocol, subdomain, path segment, or query string).- Example:
*://*.doubleclick.net/*blocks all requests to any subdomain ofdoubleclick.netover HTTP or HTTPS.
*://*.doubleclick.net/* in the URL filter field, leave the initiator field blank, then click Add rule. The rule appears immediately in the rule list below.Traffic Blocker checks for duplicates as you type. If an identical
urlFilter already exists in the list, a warning is shown and the duplicate is not added.Enable blocking
Locate the toggle switch at the top of the Dashboard. Flip it to the ON position. The label turns green to confirm that all registered rules are now active. If the toggle is OFF, rules are stored but not enforced — no requests will be blocked.
Verify blocking
Confirm the rule is working in Chrome DevTools:
- Open a new tab and press
F12(orCtrl+Shift+I/Cmd+Option+I) to open DevTools. - Switch to the Network tab and make sure recording is enabled (the red circle button).
- Navigate to any page that loads resources from
doubleclick.net(a news site or e-commerce page typically will). - In the Network tab filter bar, type
doubleclickto narrow results.
(blocked:other) or will be absent from the waterfall entirely. This confirms that declarativeNetRequest is intercepting them at the network layer before they leave the browser.Example Rule JSON
When you export your rules (Settings → Export), the file contains a top-level object with arules array and the current isEnabled state. You can author this file by hand and import it back using either Replace or Merge mode:
urlFilter— the wildcard pattern to match against the full request URL.excludedInitiatorDomains— domains from which the rule should not fire. When you add a rule without specifying an initiator domain, Traffic Blocker automatically adds"localhost"here so local development traffic is never accidentally blocked.initiatorDomains— when present, the rule only fires for requests that originate from one of these domains. Set this to target a specific site’s outbound calls.priority— higher numbers take precedence when multiple rules match the same request.isEnabled— top-level flag indicating whether all rules are active. Matches the toggle state at the time of export.
What’s Next
Managing Rules
Search, reorder, edit, duplicate, and delete rules. Learn how priority order affects which rule wins when multiple patterns match.
Preset Blocklists
Load curated Advertising, Trackers, Social Media, or Malware blocklists with a single click from the Settings view.
Import & Export
Back up your rules to JSON, restore them on another machine, or subscribe to a remote blocklist URL.
Rule Schema
Full reference for every field in the Traffic Blocker rule object, including all supported
urlFilter syntax and condition options.