# Consent for Subdomains: One Banner or One Per Property? Source: https://cookierampart.com/blog/2026-10-15-consent-subdomains-one-banner-many-properties.html [Home](../index.md) / [Blog](index.md) / Consent for Subdomains: One Banner or One Per Property? Published 2026-10-15 A brands web presence is rarely one site. The shop sits on the main domain, help runs on a support subdomain, the blog lives somewhere else, and a web app has its own address entirely. Visitors drift across all of them in one session, which raises a practical question the law answers only in principle: does the choice made on one subdomain govern the others? Get it wrong one way and banners multiply until visitors are clicking accept on every page. Get it wrong the other way and a choice made for a blog is silently authorizing tracking in a checkout. This guide gives a decision framework based on purposes and tools rather than on domain names, plus the configuration and record keeping that make either answer defensible. ## The test is shared purposes, not shared branding Consent covers purposes and processing, not logos. If the subdomains are run by the same controller, present the same purposes and vendor list, and actually share the same tools, a single consent that names its scope, this choice applies across our sites, can legitimately cover them. The moment a subdomain runs materially different processing, an app with product analytics, a support tool with session replay, a shop with advertising pixels the blog never uses, the purposes diverge, and pretending one choice covers all of it stretches consent past what the visitor was told. ## How shared consent is implemented when it is justified Technically, a shared choice usually means storing the consent record on the parent domain so sibling subdomains can read it, with the banner on each property reading the same state and offering the same preference controls. The notice on every property must make the scope plain before the choice, not in a policy footnote afterward. Records should note which property collected the choice and that its scope covered the group, and preference changes made anywhere must propagate everywhere the shared consent applies, promptly and completely. ## When separate banners are the honest answer Distinct services with distinct value exchanges deserve distinct choices: a logged in app, a patient or client portal, a regional store under different law, or a subdomain operated by a genuinely different entity. Separate banners also protect the main relationship. A visitor furious at an aggressive banner on a marketing microsite should not have that experience contaminate checkout, and a refusal given to an advertising heavy property should not be misread as a refusal of essential analytics in the app. Separation feels like more work because it is more honest about what is actually separate. ## Keeping the estate audited as it grows Subdomains breed quietly. A campaign tool here, a documentation platform there, each with its own tags, and the consent estate drifts. Maintain an inventory mapping every public subdomain to its controller, its tools, and which consent scope governs it, and rescan on a schedule that includes the forgotten corners, staging and legacy properties included, since search engines and auditors find them even when internal teams do not. New subdomain launches should include a consent scope decision as a checklist item, made by a person, recorded in the inventory. ## Related reading These earlier guides cover connected questions in more depth: [Cookie Banner A/B Testing Without Skewing Consent Data](https://cookierampart.com/blog/2026-10-15-cookie-banner-ab-testing-consent-data.md), [Cookie Consent for Multi-Language Sites: Translating Choices Without Breaking Them](https://cookierampart.com/blog/2026-10-13-cookie-consent-multi-language-sites.md), and [Cookiebot Alternatives That Are Easier to Deploy](https://cookierampart.com/blog/2026-10-12-cookiebot-alternatives-easier-deploy.md). ## Frequently asked questions ### Does consent on a main site automatically apply to subdomains? No. It applies only if the notice said the choice covered those properties and the purposes and vendors are genuinely the same across them. Technically sharing a cookie across subdomains does not create legal coverage the notice never described. ### Can one banner cover a shop and a blog? Often yes, if both are run by the same company with the same purposes and tool stack, and the banner states its scope plainly. If the shop runs advertising and checkout tools the blog does not, the purposes differ enough that separate, scoped choices are safer. ### How are preference changes handled with shared consent? A change made on any covered property must update the shared record and take effect on all of them. If a visitor withdraws on the blog and the shop keeps tracking under the old choice, the shared system has failed at its most important job. ### Should staging or test subdomains have banners? They should not be publicly collecting data at all. Keep them access controlled and tag free where possible, and include them in scans, because publicly reachable test properties with live marketing tags are a recurring and embarrassing audit finding. ## Get a free consent audit of your website [Free consent audit](mailto:hello@cookierampart.com?subject=Free%20consent%20audit%20-%20cookierampart.com)