# How to Monitor Brand Consistency Across Websites > Use a brand kit to check colours, fonts and spacing across websites, distinguish design drift from approved variation and give each issue a clear owner. To monitor brand consistency across websites, define an approved brand kit, check live pages against its colours, fonts and spacing rules, and assign unexpected differences to someone who can resolve them. Combine scheduled checks with reviews after releases. The reference should be your agreed standards, not simply how each page looked yesterday. That distinction matters across regional sites, campaign microsites and agency-managed portfolios. A page can remain unchanged while using an obsolete font. Another can change substantially while staying entirely on-brand. Your monitoring needs to distinguish a design change from design drift: a departure from the standards that apply to that page. ## Turn the brand kit into rules you can check A presentation showing the logo and a few attractive layouts is not enough for repeatable checks. Translate the guidelines into explicit values and usage rules. A developer, designer and monitoring reviewer should reach broadly the same conclusion when they inspect a button or heading. - Colours: record approved values and their roles, including text, backgrounds, links, primary actions and error states. An approved colour can still be wrong in a particular role. - Typography: specify font families, permitted weights and styles, heading hierarchy and approved fallbacks. Include alternatives needed for languages the main typeface does not support. - Spacing: define the scale used for padding, margins and gaps, plus responsive rules. For example, a suggested scale might use 4, 8, 16, 24 and 32 pixels, with documented exceptions. - Exceptions: identify approved campaign palettes, regional variations, third-party components and legacy pages awaiting migration. Give temporary exceptions an owner and review date. Keep separate kits for genuinely different brands. For one brand with regional variations, document the shared rules and local exceptions rather than merging every variation into one unrestricted palette. Record the kit version and approver so a later rebrand does not leave teams debating which standard applies. ## Choose pages that expose different failure points Build a register of domains, page types and responsible teams before scheduling checks. Include regional domains, subdomains and active campaign sites. Record which brand kit governs each property and who controls its templates. A domain list without ownership leaves you with findings but nobody clearly responsible for fixing them. For an initial sample, choose a homepage, service or product page, editorial page, form and campaign landing page on each relevant site. Include shared navigation and footers, but also inspect locally editable components. A consistent header tells you little about a promotional block built independently by a regional team. Review desktop and mobile layouts at consistent viewport sizes. Record language, consent state and any other conditions that materially change the page. Sampling helps establish coverage, but does not prove every URL is consistent. Expand checks to unique templates, high-exposure pages and areas where editors can override styling. ## Check rendered styles, then inspect their use The live browser view matters because a stylesheet can contain the right values while another rule overrides them. Browser developer tools let you inspect an element's computed styles: the values calculated after the applicable style rules have been resolved. Use these alongside visual inspection, not as a replacement for it. ### Colours: check roles as well as palette matches Compare text, backgrounds, borders and interaction states with the approved palette. Inspect hover, focus, error and disabled states where relevant. A primary button using an approved secondary colour may pass a simple palette check while still breaking your component rules. Keep colour contrast assessment separate: a palette match alone does not establish readable contrast. ### Fonts: distinguish declared families from loaded typefaces Check families and weights on headings, body copy, buttons and form fields. A computed font-family declaration can list the correct brand font even when its file failed to load and the browser used a fallback. If the page looks wrong despite a matching declaration, inspect font loading and the typeface actually rendered using the browser's font inspection tools. ### Spacing: compare equivalent components at equivalent sizes Inspect padding inside components, margins between sections and gaps within grids. Compare like with like: mobile cards may deliberately use different spacing from desktop cards. Fluid layouts can also produce values between fixed scale steps. Agree which measurements must follow a strict scale and which follow responsive formulas before treating differences as defects. ## Set tolerances without approving the mistakes Start with a designer-approved page, not whichever page happens to be available. If you extract a palette or spacing pattern from a live site, review it before adopting it as the standard. Otherwise, an existing mistake becomes an approved rule and spreads unnoticed to other properties. Allow variation for a reason. A spacing tolerance can accommodate fractional values from responsive calculations. A colour tolerance needs care: a near-match may be an accidental shade rather than acceptable rendering variation. Do not widen the entire palette tolerance to silence one troublesome component. Investigate the component and record a narrow exception if justified. Treat an overall consistency score as a way to prioritise review, not a design sign-off. A page-level summary can hide a prominent wrong logo or primary action among many correct elements. Review the affected component and its visibility to visitors before deciding urgency. For example, suppose a campaign template introduces the wrong heading font across several regional sites. Fixing each page individually may hide the symptom temporarily. Group the findings by template, inspect the shared styling and correct the source. Then recheck every affected site, including any with local overrides. ## Give every finding a decision and an owner Use a short, repeatable review process. The person receiving an alert should be able to establish what failed, which rule applies and whether the difference was approved without rebuilding the investigation from scratch. - Confirm the finding: record the URL, component, viewport, detected value, expected rule and screenshot. Recheck under the same conditions to rule out a temporary loading problem. - Classify the result: defect, approved variation, outdated brand kit or unsuitable check. A difference is not automatically an unauthorised edit. - Assign the correction: route shared styling faults to the template owner and local content overrides to the publishing team. Give prominent customer-facing errors priority over minor spacing discrepancies. - Verify closure: rerun the check after the fix, retain the result and inspect related pages. Do not close the issue solely because a deployment completed. As a starting routine, consider daily checks for active campaign pages and weekly checks for quieter sites, with additional checks after template releases. Adjust that schedule to publishing activity and review capacity. Assign a backup reviewer so an absent designer does not leave findings unattended. ## Choose automation that makes findings explainable Before selecting a tool, test whether it exposes the mismatched values, supports relevant tolerances and separates brands correctly. Establish which pages and page states it actually checks. Ask how scheduling affects usage allowances. A dashboard score is less useful if your team cannot trace it to a specific rule and component. TLDTrack's [brand consistency monitoring](https://www.tldtrack.com/features/brand-consistency-monitoring) compares page styles with an approved brand kit. Its font, colour and spacing checks use computed styles, with configurable weighting and tolerances for colours and spacing. Checks can run daily, weekly, monthly or manually, with an alert threshold you set. The [brand kit setup guidance](https://www.tldtrack.com/help/audits/brand-consistency) explains the rules behind these checks. Begin with one approved kit and a representative group of pages. Resolve ambiguities before extending coverage. The useful outcome is not identical websites: it is knowing which differences are intentional, which need correcting and who will make that correction. --- Published: 2026-11-04 Web version: https://www.tldtrack.com/blog/monitor-brand-consistency-across-websites