← Back to the glossary

Web design · Development · SEO

Third-Party Cookies

Third-party cookies explained: cookies in third-party contexts

Editorially reviewed ·

Clear definition

Third-party cookies are cookies associated with a different website or site while a user visits a page. They often arose through embedded advertising, analytics, video, or social media content and could connect activity across multiple websites. The precise technical classification depends on browser rules and site context, not merely the name of a service provider.

Browsers increasingly restrict or block third-party cookies, although behaviour and timelines vary by product. Businesses should therefore not base reliable measurement or advertising solely on them. First-party data, server-side processes, or contextual advertising are not automatically exempt from consent; transparency, data minimisation, security, and legal basis still require assessment.

At a glance

Third-party cookies come from a different site context. Visited website, Embedded third-party content.
Third-party cookies come from a different site context. Browsers may block or restrict them.Open infographic in full size

Third-Party Cookies in practice

Third-party cookies are set or read in another site’s context and are increasingly restricted by modern browsers. Tracking strategy should not be reduced to renaming or proxying the same data flows.

Web communication consists of individual requests and responses governed by headers, status codes, and security rules. Cookies are only one possible storage and transfer mechanism within that system. Purpose, lifetime, access protection, transmission, and consent need separate evaluation. A technically available mechanism is not automatically necessary or legally permitted.

Third-Party Cookies: relevance to SEO, paid search, and GEO

Protocol and cookie configuration can affect redirects, caching, security, and tracking. Mistakes lead to duplicate URLs, lost sessions, or incomplete conversions. SEO crawls, browser tests, and campaign measurement should therefore cover different consent and authentication states. Privacy notices do not replace a technical review of the requests that are actually sent.

For search and answer systems, coverage of Third-Party Cookies should distinguish its definition, scope, and evaluation criteria. The editorial reference is “Third-party cookies” by MDN Web Docs, making central claims traceable for readers and machine-based systems.

Sources and further reading

  1. Documentation Third-party cookies MDN Web Docs · Checked

Frequently asked questions

A third-party cookie belongs to a different site context from the website being visited and has often been used for cross-site measurement or advertising.

Depending on the goal, first-party data, contextual advertising, aggregated measurement, or browser APIs may help. No alternative is automatically privacy-compliant.