How do you customize Logo Usage?

Override `logoRequirement` when your brand has a specific, visible rule you want held automatically. Good candidates are rules a reader could verify from a screenshot: which variant belongs on a dark background, that the mark must appear top-left rather than centred, that the wordmark must accompany the symbol, or that a sub-brand lockup must appear alongside the parent. Write it as an instruction to a careful reviewer, naming what you expect to see and where.

Stay on Standard when your question is "is the logo there and intact", which is what most audits actually need and what the default answers well. Keep the default when auditing sites you do not control the brand of — agency work in progress, partner pages, acquisitions mid-migration — because holding someone else's page to your lockup rules produces findings nobody can act on. If your rule depends on facts a capture cannot show, such as the source file format or the exact hex of an asset, a page audit is the wrong instrument.

The more specific the requirement, the more judgement each verdict carries, and the more likely a legitimate variant reads as a failure — a responsive header that switches to the symbol alone at narrow widths will fail a rule demanding the full lockup unless you say so. Very long requirements also blunt the finding: when one sentence names five rules, the failure tells you the sentence was not met rather than which part. Keep each requirement to the rules you would actually reject a page over.

The Standard requirement is written to be defensible for any brand without configuration, which is why it stops at present, visible and readable. A Custom requirement is a transcription of your brand book and should cite it — the value belongs to your brand team, with a named owner, not to whoever last ran an audit. When the brand book changes, this string is one of the things that has to change with it, so keep it somewhere that review touches.

A company with a dark-and-light lockup pair sets `logoRequirement` to state that the light-on-dark variant must appear in the header when the header background is dark, and the dark variant otherwise — a rule a capture can genuinely settle. A group brand requires that a sub-brand mark appear alongside the parent wordmark in the header, catching pages migrated from an acquisition before the lockup was applied. An agency auditing a client's live site before handover keeps the Standard requirement, because the useful finding at that stage is a broken or missing mark, not a guideline argument.