The Brand Consistency Checker reads one page and compares the descriptions it ships: the meta description, og:description, twitter:description and the description in its Organization or WebSite schema. It also compares the page name across the title tag, og:title and schema. You get a side by side table, a note on which pair disagrees, and a pass, warning or fail for each check.
Updated
A page describes your brand in several places: the meta description, the social tags, and the schema. The checker puts those descriptions next to each other and flags the ones that say different things.
It checks four things: that a description exists, that schema states who you are, that the descriptions agree, and that the name is the same everywhere.
Agreement is measured by how many content words each pair of descriptions share. About half or more shared words passes. Fewer than that gets a warning, and a low overlap fails.
The schema check looks for an Organization, WebSite, LocalBusiness or similar node with a description. That is the description a model is most likely to read as a statement of fact about the company.
The usual cause is that each tag was written by a different person at a different time. The fix is to pick one sentence that says what you are and who you serve, and use it everywhere.
Your profiles on review sites and directories are the other half of the same problem, and that is where most of the drift happens. Check them by hand against the sentence you chose.
Inconsistent descriptions are one of the causes covered in Why AI Recommends Your Competitor.
Related study: How Much Do ChatGPT's Answers Change Between Runs?
Peak Answer runs checks like these every week, then writes the content and gets the placements.