Chrome Not Respecting 'Do Not Track' for Specific Sites

1. Chrome's DNT Flag Is Disabled or Overridden for That Site

This is the most common reason Chrome ignores DNT on a specific website. Google hides the DNT flag behind a developer setting. It's not in the regular Settings menu. You need to flip a flag.

Step-by-step fix

1. Open a new tab in Chrome. Type chrome://flags into the address bar. Hit Enter.
2. In the search box at the top, type Do Not Track. You should see a flag called "Enable Do Not Track" or similar (exact wording changes slightly between Chrome versions).
3. Click the dropdown next to that flag. Set it to Enabled.
4. Chrome will ask you to relaunch. Click Relaunch Now.
5. After Chrome restarts, test the site again. Use a tool like dnt-test.appspot.com to verify the header is sent.

What you should see: After relaunch, the test page will show "Do Not Track: 1" in the request headers. If it still shows nothing or "0", move to the next cause.

2. A Privacy Extension Is Blocking or Overwriting the DNT Header

Here's a tricky one. Some ad blockers or privacy extensions (like uBlock Origin, Privacy Badger, Ghostery) can strip or modify the DNT header. They do this because they think they handle tracking better than Chrome does. But this leaves you without DNT on certain sites.

How to check and fix

1. Click the puzzle piece icon (Extensions) in Chrome's toolbar.
2. Click Manage Extensions.
3. Toggle off each privacy extension one at a time. Start with the one you suspect most (usually uBlock Origin or Privacy Badger).
4. After disabling each, reload the site that wasn't respecting DNT. Check if the header shows up now (use the same test site from step 1).
5. Once you find the culprit, you have two options:
   • Disable that extension entirely (if you don't need it).
   • Check the extension's settings for a "Do Not Track" option. Some have a toggle to stop interfering with DNT.

Real-world example: A user on Reddit found that uBlock Origin in medium mode was stripping DNT headers on YouTube. Disabling it fixed the issue immediately.

3. Per-Site Content Settings Override the Global DNT Request

Chrome lets you set site-specific permissions for cookies, JavaScript, and tracking. If you've previously told Chrome to allow tracking on a specific site (or blocked it in a way that confuses DNT), that per-site rule can trump the global DNT flag.

Fix: Reset site permissions

1. Go to the website where DNT isn't working.
2. Click the lock icon (or Info icon) left of the address bar.
3. Click Site settings.
4. Scroll down to Permissions. Look for anything related to cookies or tracking. Specifically:
   • Cookies: should be "Allow" (blocking cookies can break DNT).
   • JavaScript: should be "Allow" (disabling it breaks DNT headers).
   • If you see a line that says "Do Not Track" or "Tracking protection", set it to "Allow" or "Default".
5. If you're not sure, click Reset permissions at the bottom. This clears all custom settings for that site.
6. Reload the site and test again.

After resetting, Chrome should send the DNT header for that site. If it still doesn't, the site itself might be ignoring your request (some sites do this intentionally).

Quick-Reference Summary