How to Block Trackers in Chrome with SBlock

The short answer: turn on Block tracker and reload

1. Install regular SBlock from its official Chrome Web Store listing.
2. Open the supported website you want to use in desktop Chrome.
3. Select the SBlock icon in the browser toolbar.
4. Make sure protection for the current website and page is on.
5. Find Block tracker and turn it on.
6. Reload the page so the tracker rules can apply from the beginning of the new page load.

Use the page normally after the reload. If an important feature stops working, do not switch off every privacy setting at once. Test one narrow change at a time so you can identify the cause and restore protection afterward.

What a web tracker can be

A tracker is not always a visible banner or a cookie. It can be a script, pixel, request, embedded widget, or another service that receives information when a page loads or when you interact with it. The information may be used for site analytics, advertising measurement, audience building, fraud prevention, customer support, or other purposes.

That range matters because not every third-party connection is automatically harmful, and not every necessary service is first-party. A payment form, map, video player, comments system, or support chat may come from another domain. The practical goal is to reduce known unwanted tracking while keeping the functions you intentionally use.

Different blockers classify and handle trackers differently. SBlock applies its own tracker rules on supported browser requests. It should not be treated as proof that no data ever leaves a page or that every third-party service has the same purpose.

What SBlock's Block tracker control does

The current SBlock product page describes Block Trackers as a control that reduces tracking before pages finish loading. The SBlock release notes document the Block Tracker option and updated ad and tracker rules. In the inspected SBlock 1.7.20 package, the popup's Block tracker switch controls a dedicated tracker ruleset.

That is different from hiding something after it appears. A network rule can stop a matching request, while a cosmetic rule changes what you see in the page. The recent guide to blocking specific page elements in Chrome explains that visual distinction in more detail.

Tracker lists and websites both change, so the outcome is not a permanent guarantee. SBlock 1.7.20 uses the current rules available in that release. Keep Chrome and SBlock updated, and report a repeatable miss or breakage instead of assuming that one result applies to every future page.

Install the right SBlock product

Regular SBlock and SBlock YouTube are separate extensions. Regular SBlock is the product for this tracker guide and for other supported websites. SBlock YouTube is built specifically for YouTube and YouTube Music.

The official regular SBlock listing currently shows version 1.7.20 and names tracker blocking among its features. Use that listing instead of a similarly named download from another website. After installation, Chrome's Extensions menu can pin the SBlock icon so its website, page, and tracker controls are easier to reach.

If the extension is disabled or Chrome reports that it needs repair, resolve that state before judging tracker protection. Google's extension-management guide explains how to turn extensions on, repair them, and review site access.

Check Chrome site access

An enabled extension may still have limited permission to read and change a site. Open Chrome's extension manager, select Details for SBlock, and review its site-access setting. Chrome can allow access when selected, on specific sites, or on all sites.

Choose the access level that permits SBlock to work on the pages you want protected while matching your privacy preference. If you allow access only when selected, you may need to activate SBlock for a new site. If you use a specific-site list, confirm that the current hostname is included.

Reload any tab that was already open when you installed SBlock or changed its permission. The old document may not receive the new access until it loads again.

Tracker blocking is not the same as blocking cookies

Cookies are small pieces of site data that can keep you signed in, remember preferences, or support personalization. Chrome distinguishes first-party cookies created by the site in the address bar from third-party cookies created by other sites embedded in the page.

Google's Chrome cookie guide explains how to block third-party cookies and warns that sites relying on them may not work as expected. Tracker filtering and cookie controls overlap, but neither is a complete substitute for the other. A tracker can use something other than a cookie, and a third-party cookie can support a feature you intentionally chose.

A cookie banner is different again. It is the visible consent interface, not the cookie itself and not every tracker behind the page. The guide to stopping cookie pop-ups without blocking every cookie explains how to handle that interruption without confusing presentation, storage, and network protection.

Do Not Track is a request, not a blocker

Chrome can send a Do Not Track request with your browsing traffic. That signal asks websites not to track you, but it does not force them to comply. Google's current Do Not Track guidance says many sites and services do not change their behavior when they receive the request.

SBlock's Block tracker control takes a different approach by applying filtering rules to supported requests. You can use the Chrome request and SBlock together, but they remain separate controls with different effects.

Neither setting makes you anonymous. Websites can still receive information needed to deliver a page, and your internet connection still has an IP address. Tracker blocking is one privacy layer, not a VPN, an identity shield, a malware scanner, or a replacement for safe browsing habits.

How to check that protection is active

Open the SBlock popup on the page you are testing. Confirm three things: regular SBlock is the installed product, protection for the current website and page is on, and Block tracker is enabled. Then reload the page.

Use the site rather than relying on a single counter or a dramatic test page. Open the feature you came for, follow a normal navigation path, and watch for any obvious change in behavior. A blocked-request count can be informative, but it does not prove that every tracker was found or that every blocked request would have tracked you.

If you use Chrome DevTools, the Network panel can show requests made during a fresh load, but interpreting every hostname correctly requires context. A request to another domain may be analytics, or it may be a necessary content delivery, sign-in, payment, or support service. Avoid declaring a site “tracker-free” based only on a short list.

Why a protected site can stop working

A website may depend on a third-party service for a feature you need. Sign-in buttons, checkout fields, embedded media, maps, comments, and live chat are common examples. If a tracker rule matches a request that the feature depends on, the control may fail, remain blank, or keep loading.

That does not mean you should permanently disable all protection. First reload once and confirm that the problem is repeatable. Then test the same action with only one SBlock setting changed. If the feature works immediately when protection is paused and fails again when it is restored, you have a useful reproduction.

Also check whether Chrome's third-party-cookie setting is involved. Google notes that blocking third-party cookies can affect sites that rely on them. Changing SBlock and Chrome cookie settings at the same time hides which control caused the behavior.

Use the narrowest recovery test

SBlock 1.7.20 can enable or disable protection for the current page or the current website. Start with the smallest scope that can answer your question.

1. Keep the failing tab open and note the exact action that fails.
2. Temporarily pause SBlock for the current page, reload, and repeat that action.
3. If the feature still fails, restore page protection before changing another setting.
4. If the issue occurs across several pages on the same hostname, test the website-level control once.
5. Turn protection back on after the comparison.

A page or website exception pauses more than tracker filtering for that scope, so it should be a diagnostic step rather than the automatic final answer. If a narrow exception is necessary, report the affected feature so the rules can be reviewed.

Test without extension conflicts

Two blockers can change the same request or page element in different ways. A privacy extension, antivirus browser add-on, script controller, cookie manager, or second ad blocker may act before SBlock sees the page. The result can resemble SBlock breakage even when another extension caused it.

For a clean comparison, temporarily stop other content-changing extensions from running on the test site, reload, and try the same action. Do not uninstall everything or erase all browser data. A reversible, one-change test preserves your settings and produces clearer evidence.

If general ad blocking is also failing, follow the broader Chrome ad-blocker troubleshooting checklist for extension status, permissions, updates, and conflicts.

What tracker blocking cannot promise

No browser extension can guarantee complete privacy, anonymity, or perfect classification. A first-party site can process information needed to provide its service. A tracker can change domains or techniques. A browser rule may not cover a native desktop or mobile application, another browser profile, or traffic outside Chrome.

Tracker blocking also does not make a dangerous website trustworthy. Keep Chrome's security protections enabled, install extensions only from official sources, review permissions, and avoid entering sensitive information on a site you do not trust.

Use accurate language when evaluating the result: SBlock helps reduce supported tracking requests. It does not prove that a company deleted previously collected data, that a site stores nothing, or that your identity is hidden from every service.

Report a missed tracker or broken feature safely

If the same issue survives the ordered checks, use the SBlock Issue Reporter. Include regular SBlock 1.7.20, your Chrome version, the public page URL, the feature you used, and the shortest repeatable sequence.

Say whether Block tracker was enabled, whether the current page and website controls were on, and whether another content-changing extension was active. For a broken feature, describe the expected and actual result. For a suspected missed tracker, identify the visible behavior or request hostname without claiming more than you observed.

Do not send passwords, cookies, session tokens, payment data, private account pages, or a full browser profile. Crop screenshots and exported network details carefully. Review the SBlock Privacy Policy for current product data practices.

Frequently asked questions

Does Block tracker remove cookie banners?

Not by itself. Tracker filtering, cookie storage, and the visible consent banner are separate layers. Use SBlock's cookie-popup control for supported banners and review the site's choices before consenting.

Should I block all third-party cookies too?

That is a separate Chrome decision. Blocking third-party cookies can reduce some cross-site activity, but Google warns that features relying on them may stop working. Use site exceptions only when needed and understand which setting you changed.

Why does a sign-in or checkout fail when protection is on?

The page may depend on a third-party request that was filtered, or a different extension or cookie setting may be responsible. Reload, test one narrow page-level change, restore protection, and report a repeatable result.

Should I use regular SBlock on YouTube?

Use the separate SBlock YouTube extension for YouTube and YouTube Music. Regular SBlock is the product for other supported websites and is the only product covered by this tracker guide.

Reduce tracking without losing control of the page

Start with the correct product, turn on Block tracker, confirm site access, and reload. Keep tracker filtering separate in your mind from cookie-banner hiding, third-party-cookie settings, and the voluntary Do Not Track signal.

If something breaks, compare one narrow page or website scope, restore protection after the test, and report the smallest repeatable case. Install regular SBlock from its official Chrome Web Store listing and use its controls as a privacy layer with realistic expectations.