Chrome Visited Links Fix: Does It Stop Tracking?

No, the Chrome visited links fix does not stop websites from tracking you. It only changes how Chrome stores and displays the list of links you have clicked, preventing websites from using CSS to detect your browsing history; it does not block cookies, fingerprinting, or other tracking methods.

What the Visited Links Fix Actually Does

Chrome’s visited links feature has long been a privacy concern because of a technique called “CSS history sniffing.” A website can use JavaScript and CSS to check whether a link’s color matches the “visited” style. By testing many URLs, a site can build a list of pages you have visited. The fix, introduced in Chrome 51, changes the timing of when the visited style is applied, making it impossible for JavaScript to detect the difference between visited and unvisited links in real time. This closes that specific loophole but does nothing else.

How the Fix Works Technically

Before the fix, Chrome applied the visited style immediately when rendering a link. A script could read the computed style and know if the URL was in your history. Now, Chrome delays applying the visited style until after the page has finished loading, and it uses a separate internal list that is not exposed to JavaScript. The browser also limits the number of visited links it stores per page and clears the list after a short time. This means a site cannot query your history through CSS, but it also means the fix has no effect on other tracking vectors.

What Still Tracks You After the Fix

The fix only addresses one narrow method. Websites still track you through:

Cookies – both first-party and third-party, which remember your sessions and preferences.
Fingerprinting – collecting browser, screen, and device details to create a unique profile.
IP address – your general location and network identity.
Referrer headers – which page you came from.
Local storage and IndexedDB – persistent data that can be used to recognize you.
Tracking pixels – tiny images that signal when you open an email or visit a page.

None of these are affected by the visited links fix. So while the fix is a genuine privacy improvement, it is a narrow one.

How to Actually Reduce Tracking in Chrome

If you want to minimize tracking, you need to take additional steps:

Use Chrome’s built-in “Block third-party cookies” option in Settings > Privacy and security.
Enable “Send a ‘Do Not Track’ request with your browsing traffic” (though many sites ignore it).
Use an extension like uBlock Origin or Privacy Badger to block trackers.
Use Incognito mode for sensitive sessions, but know it does not stop all tracking.
Consider a privacy-focused browser like Firefox or Brave, which have stronger anti-tracking defaults.
Regularly clear your cookies and site data.

These actions address the actual tracking mechanisms, unlike the visited links fix.

Common Misconceptions About the Fix

Many users believe the fix means Chrome no longer stores your history. That is false – Chrome still keeps a full history file on your device, and it is still used for autocomplete and the history page. The fix only changes how the visited state is exposed to websites. Another misconception is that the fix blocks all forms of history sniffing. It blocks the CSS method, but there are theoretical side-channel attacks using cache timing or performance metrics that are not fully mitigated. These are harder to exploit and not used in practice, but they exist.

Comparing Chrome’s Fix to Other Browsers

Firefox and Safari have implemented similar protections. Firefox partitions the visited list per-site, meaning a site can only see if you have visited pages on that same site, not cross-site. Safari goes further by limiting the visited list entirely and using a separate process for history. Chrome’s fix is less strict than Firefox’s per-site partitioning, but it still closes the main attack. Edge, which is Chromium-based, inherits Chrome’s behavior. So the fix is not unique to Chrome, and its effectiveness is comparable across major browsers.

Does the Fix Affect Performance or Functionality?

No, the fix does not noticeably affect performance or break any normal functionality. The only visible change is that the visited link color may update slightly later when you navigate back to a page, but this is imperceptible in practice. Some very old websites that relied on JavaScript to detect visited links for features like “read/unread” might stop working, but such sites are rare and usually considered privacy-invasive anyway. The fix is enabled by default and cannot be turned off in current Chrome versions.

Frequently Asked Questions

Does the visited links fix delete my history?

No, it does not. Your browsing history is still stored locally in Chrome’s profile folder. The fix only prevents websites from reading that history via CSS. You can still view and clear your history manually.

Can websites still see my visited links through other methods?

In theory, yes, through side-channel attacks like cache timing, but these are not practical for most websites. The CSS method is the only widely used technique, and it is now blocked. Other methods require advanced knowledge and are not seen in the wild.

Will using Incognito mode stop visited link tracking?

Incognito mode does not store history on your device, so there is no visited list to sniff. However, it does not block cookies, fingerprinting, or IP tracking. The visited links fix is irrelevant in Incognito because there is no history.

Is the visited links fix the same as blocking all trackers?

No. The fix is a single, narrow protection against one specific technique. Blocking all trackers requires a combination of cookie blocking, fingerprinting protection, and tracker-blocking extensions. The fix is just one small part of a larger privacy strategy.

Does this fix work on mobile Chrome?

Yes, the fix is part of the Chromium engine, so it is active on Android and iOS versions of Chrome as well. The behavior is the same as on desktop.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →