Where Brand SERPs Actually Stand Right Now
It is May 2026. I have been doing brand SERP work almost exclusively for eighteen months now, across eleven clients ranging from a 40-person B2B SaaS company to a regional hospital group and one very unhappy wealth management firm whose CEO decided to do a podcast interview in 2023 that aged badly. The work has changed more in that time than in the previous five years combined.
The phrase "brand SERP ownership" used to mean one thing: push down the bad stuff, pull up the good stuff. Simple suppression logic. And that still matters. But it misses most of what actually happens when someone searches your brand name in 2026.
There is a knowledge panel. Or there is not one, which is itself a problem. There is an AI Overview for roughly 34% of navigational brand queries I tracked through Q1 2026. There are suggested searches that either frame your brand in a question ("is [brand] legit?") or reveal exactly where public perception is fracturing. There are Reddit threads ranking in positions 4 through 7 with terrifying regularity. And there are Glassdoor and Indeed pages that are now being cited inside AI Overviews even when the review platforms themselves rank below the fold.
The job is no longer about ten blue links. It never really was, but now you cannot pretend otherwise.
What Changed Between 2024 and Today
Three shifts, none of them subtle.
First: AI Overviews 2.0 launched in November 2025 with dramatically expanded coverage of navigational and brand-adjacent queries. Where the original AI Overview largely sat out brand searches, the updated version now synthesizes third-party employer reviews, news coverage, G2/Trustpilot ratings, and Reddit sentiment into a zero-position summary that can appear before any organic result. I watched a client's AI Overview pull a two-star Glassdoor rating into the third sentence of the summary for a query that was just the company name. The Glassdoor page itself was ranking 14th. Ranking 14th did not matter.
Second: Google's entity graph has gotten materially smarter about separating person-entities from organization-entities, and this creates both opportunity and risk. Organizations now need clean, structured, verifiable entity data across a specific set of platforms Google actually trusts for entity resolution. Wikipedia is still on that list but is no longer dominant. Wikidata is more important than most practitioners acknowledge. The organization's own structured data, specifically its Organization and LocalBusiness schema, now feeds entity panel construction more directly than it did 24 months ago.
Third: The Reddit-Google content deal, plus Reddit's own improvements to structured content, mean Reddit threads rank with a consistency that was not possible before mid-2024. For brand searches, this is almost always negative. People do not make Reddit threads to say "this company is fine."
The PIPE Framework: My Working Model
I built this after the third client engagement where I realized I was running the same audit in a different order and calling it a different thing each time. Frameworks are not magic; they are checklists that do not get skipped under deadline pressure.
PIPE stands for:
- P — Panel. Does the entity panel exist? Is it verified? Is the data accurate and does it reflect current brand positioning? Is the knowledge panel pulling from the right primary source?
- I — Inventory. What does the brand SERP actually contain, today, for the 12–18 query variants that matter? Branded exact, branded plus review terms, branded plus location, branded plus competitor comparisons, branded plus "scam/legit/lawsuit."
- P — Prioritize. Of the problematic results, which are urgent (appearing in AI Overview), which are high-impact (positions 1–5 organic), and which can be addressed through platform response rather than displacement?
- E — Execute. Content creation, schema deployment, entity reinforcement, PR layer, structured review response. In that order, because that is roughly the order of leverage.
It is not clever. That is the point. When a client panics at 9 AM because their CEO found the company's Glassdoor summary in an AI Overview at 8:47 AM, clever frameworks do not help. Checklists do.
One nuance worth flagging: the Inventory phase almost always reveals that clients have been tracking the wrong query variants. The brand-exact query is rarely where the damage happens. "Brand name reviews" and "brand name vs competitor" are where suppression and entity problems manifest, and most teams are not watching those with any regularity.
I also track a metric I call the Entity Coherence Score, which is not an official Google metric and does not appear in any tool I am aware of. It is just a manual 0–10 assessment of whether the information Google surfaces in the entity panel, AI Overview, and People Also Ask section is consistent, accurate, and aligned with current brand positioning. Newer clients almost always score below 5 on first audit. After six months of systematic work, the average score in my book of business is 7.3. The ceiling seems to be around 8.5 for companies that do not have public legal issues or major press controversies in their past.
Claiming and Fortifying the Entity Panel
Let us be precise about what the knowledge panel is and is not. The panel is Google's rendering of entity data it has assembled from across the web. It is not a profile you fill out. The "claim this knowledge panel" workflow Google provides gives you the ability to flag errors, suggest edits, and verify that you are the official representative of the entity, but it does not give you direct editorial control. Practitioners who tell clients they can "manage their knowledge panel" are overpromising.
What you actually control: the data sources Google trusts.
This is why the structured data on your own site matters. This is why Wikidata matters. This is why having a consistent, accurate presence on platforms Google uses as entity corroboration (Crunchbase for funded companies, LinkedIn company pages, Google Business Profile where applicable, industry-specific databases for healthcare or financial entities) matters more than most people treat it.
I spent four weeks on one client whose knowledge panel was pulling a founding date that was wrong by three years, a CEO name that reflected a leadership transition from 2022, and a logo that predated their rebrand. The panel was not verified. The client had never gone through the claim process. After claiming the panel, flagging the errors, and more importantly correcting the underlying data in Wikidata and in the Organization schema on their site, every error resolved within 11 weeks. Not 6 weeks. Not overnight. Eleven weeks.
Organization Schema That Actually Works
Below is the Organization/Brand JSON-LD structure I now deploy as a baseline for all brand SERP clients. The key additions versus what most sites ship are the sameAs array (comprehensive, not lazy), the foundingDate and numberOfEmployees for entity corroboration, and the nested brand object for companies that operate multiple product brands under one corporate parent.
{
"@context": "https://schema.org",
"@type": ["Organization", "Brand"],
"@id": "https://example.com/#organization",
"name": "Example Corp",
"legalName": "Example Corporation Inc.",
"alternateName": ["ExampleCo", "Example"],
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/logo.png",
"width": 512,
"height": 512,
"contentUrl": "https://example.com/images/logo.png"
},
"image": "https://example.com/images/og-brand.jpg",
"description": "Example Corp provides enterprise workflow automation software to mid-market and enterprise clients across North America and Europe.",
"foundingDate": "2011",
"numberOfEmployees": {
"@type": "QuantitativeValue",
"value": 340
},
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street, Suite 400",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"contactPoint": [
{
"@type": "ContactPoint",
"contactType": "customer support",
"telephone": "+1-800-555-0100",
"email": "[email protected]",
"availableLanguage": ["English", "Spanish"]
}
],
"sameAs": [
"https://www.linkedin.com/company/example-corp",
"https://twitter.com/examplecorp",
"https://www.crunchbase.com/organization/example-corp",
"https://www.wikidata.org/wiki/Q12345678",
"https://en.wikipedia.org/wiki/Example_Corp",
"https://www.youtube.com/@examplecorp",
"https://github.com/example-corp",
"https://www.glassdoor.com/Overview/Working-at-Example-Corp-EI_IE123456.htm",
"https://g2.com/products/example-corp/reviews"
],
"brand": {
"@type": "Brand",
"name": "Example",
"logo": "https://example.com/images/brand-mark.png",
"slogan": "Work better, together."
},
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Example Corp Products"
},
"award": [
"G2 Leader Winter 2026",
"Inc. 5000 2024",
"Best Places to Work – Austin Business Journal 2025"
]
}Two things I always argue about with developers when deploying this. One: include Glassdoor in sameAs. I know it feels counterintuitive to link to the platform you are trying to suppress, but Google already knows the connection exists. Acknowledging it in structured data actually helps Google understand you are aware of and authoritative about your own entity profile. Refusing to include it does nothing for suppression. Two: award array matters because these strings surface in AI-generated entity summaries. "G2 Leader" in the award array is a positive signal the AI can cite when constructing the AI Overview for your brand query.
Wikidata, Wikibase, and the Unverified Claim Problem
Most brand SERP practitioners I talk to treat Wikipedia as the entity data source and Wikidata as an afterthought. This is backwards. Wikidata is the machine-readable layer that feeds entity resolution for Google, Bing, and every AI system using structured knowledge graph data. Wikipedia's prose matters for AI training and for AI Overview source selection, but Wikidata's structured properties are what drive the knowledge panel data fields.
For a client whose Wikipedia article was flagged for notability concerns and eventually deleted in early 2025, I ran a Wikidata-only entity reinforcement strategy. We created and maintained a comprehensive Wikidata item, ensured all property values were properly sourced with reliable references, and maintained consistency with the Organization schema on their site. The knowledge panel persisted through the Wikipedia deletion and continues to render today. Wikipedia is not required. Sourced, accurate Wikidata is.
The verification workflow I use for knowledge panel claiming is below. This is the process for the Google Search Console verification method, which is the fastest for companies that already have GSC access.
## Knowledge Panel Claim Verification — Step-by-Step
1. Search [brand name] on Google.com (logged into a Google account associated
with the organization's GSC property).
2. Locate the knowledge panel. Look for "Claim this knowledge panel" at
the bottom. If absent: the entity may not yet be in the graph, or your
account does not have sufficient association signals.
3. Click "Claim this knowledge panel" → Select "Official Website."
4. Google verifies ownership via Google Search Console. Your GSC property
URL must match the website listed in the knowledge panel. If it does not
match, add the property first.
5. Post-verification: access the "Suggest an edit" workflow for factual
corrections. Each correction requires a source URL. Use:
- Your own About page for description/founding date/employee count
- Press releases for leadership changes
- Wikidata item URL as corroborating source
- Crunchbase for funding/HQ data
6. Timeline expectations:
- Verification: immediate to 48 hours
- Edit approval: 3 to 11 weeks depending on data conflict severity
- Logo updates: typically 4–6 weeks
- Category/industry field updates: slowest, often 8–12 weeks
## Wikidata Corroboration Checklist
P856 → official website
P18 → image (logo or brand image)
P571 → inception date
P112 → founded by
P169 → CEO/executive director (current)
P452 → industry
P159 → headquarters location
P17 → country
P749 → parent organization (if applicable)
P1316 → replaced by (for rebrands)
P856 → official website
All properties must have at least one cited reference (ref URL)
from a reliable source. Uncited properties are marked as
"unverified claims" and carry less entity graph weight.How I Knocked Three Glassdoor Pages Off Page One
In August 2025, a client retained me with a specific problem: three distinct Glassdoor URLs were ranking on page one for their brand query. Not just one employer profile page. Three: the main employer overview page, a "salaries" subpage, and a "interviews" subpage. Together they occupied positions 4, 6, and 9. The AI Overview for the brand query was summarizing their 3.1-star average rating in the opening sentence.
Before I get to what worked, here is what I audited at baseline. The brand SERP contained: position 1, their homepage. Position 2, their LinkedIn company page. Position 3, a TechCrunch article from their Series B announcement. Positions 4, 6, and 9, Glassdoor. Position 5, their G2 profile. Position 7, a Crunchbase page with outdated headcount data. Position 8, an Indeed employer page. Position 10, a local business journal article about their office expansion.
Nine of ten page-one results were outside direct client control. This is not unusual. Most brand SERPs look like this.
The displacement strategy ran across four workstreams simultaneously.
Workstream one: owned content creation. We built seven new pages on the client's domain targeting query variants that adjacent search surfaces had claimed. An "Our Culture" hub with genuine employee story content (not PR pablum, actual named employees, actual specifics). A "Careers" section with role-specific pages. An "Awards and Recognition" page. A "Press" page that functioned as a proper news archive. A "Leadership" page with individual executive bios as separate URLs. A "Partners" directory. And a blog series called "Inside [Company Name]" with monthly posts.
Workstream two: third-party authority layer. We pitched three industry publications for feature coverage: one profile piece, one awards submission we won, and one podcast appearance by the CMO that resulted in a transcript page on the podcast's site. The podcast transcript ranked on page one for the CEO's name query within 11 weeks. We also claimed and completed profiles on G2, Trustpilot, and Capterra, soliciting legitimate reviews from existing customers through an email sequence. This pulled the G2 profile from position 5 to position 3 and increased its review count from 47 to 114 over six months.
Workstream three: internal link equity distribution. The client's existing site had a serious internal linking problem: their culture and careers content existed but received essentially no internal links from their high-authority product and homepage URLs. I ran a full internal link audit, identified 23 contextually appropriate places to add links to the new culture/careers hub from pages with strong organic rankings, and implemented them. This was the workstream most resistant to client buy-in. "Why does it matter if our careers page has internal links?" It matters because page authority flows through internal links and Googlebot discovers new pages through them.
Workstream four: structured response strategy on Glassdoor itself. Yes, this matters, not for ranking purposes but for AI Overview purposes. We drafted management responses to the 31 most-cited negative reviews, responses that acknowledged specific themes, noted policy changes, and added substantive positive context. The goal was to alter the text content of those Glassdoor pages so that an AI summarizing them would find more balanced signal.
By April 2026, nine months in: all three Glassdoor URLs had dropped off page one. The "interviews" subpage went to page two after five months. The "salaries" page went to page three after seven months. The main employer profile was the hardest, finally moving to position 12 after month nine. The AI Overview for the brand query no longer surfaced the star rating in its opening content.
Weird number worth noting: the total word count of management responses we wrote for Glassdoor was 14,700 words across those 31 reviews. That is more long-form content than some companies publish in a year. Nobody talks about this as a content strategy. It is.
Neutralizing a Damaging Reddit AMA
Different client, different problem. A former executive at a mid-size fintech company had done an AMA on r/personalfinance in March 2025 that started as a general Q&A about company culture and devolved, in the comment thread, into a fairly detailed account of product decisions the poster claimed were driven by revenue pressure over customer interest. The thread had 847 upvotes. It was ranking position 6 for the brand name query. The former executive had since left the company but the thread was not going anywhere.
The strategic options here are genuinely limited and I want to be honest about that. You cannot delete Reddit threads unless they violate Reddit policy, and "former employee says critical things about a company" does not violate Reddit policy. You cannot ask Reddit to de-index the page unless there is specific legal content (defamation, doxxing, etc.), and legal threats against Reddit community content are a terrible idea that will almost certainly generate more brand-negative coverage. You cannot pay Reddit or Google to suppress specific URLs.
What you can do: compete for the position with content that satisfies the same query intent better.
The query intent for "brand name Reddit" is: what do people who are not the company's marketing department actually think about this company? That intent is not satisfied by a press release or a corporate blog post. It is satisfied by authentic community discussion. So we built for authentic community discussion.
We identified three relevant subreddits where the company's product category was actively discussed. We had actual company team members, starting with the current CEO and two product managers, create accounts and begin genuinely participating in those communities: answering questions about the product category, sharing relevant expertise, occasionally mentioning the company when directly relevant and only with disclosure. This is not astroturfing. Astroturfing is fake accounts with fake identities. This is participation by real employees who disclose their affiliation.
Over four months, that participation generated three separate threads where the company was discussed positively by other community members, not by the employees themselves. Those three threads collectively accumulated around 1,100 upvotes. One of them now ranks position 5 for the brand name query, above the damaging AMA. The AMA dropped to position 8.
Not eliminated. But no longer the first Reddit result, and no longer surfacing in the AI Overview because fresher, higher-engagement threads about the brand now dominate the Reddit signal pool Google samples.
Timeline: four months to first observable shift, six months to the current state. Cost in time: meaningful. About twelve hours of genuine community participation per month from the employees involved, sustained over six months. There is no shortcut here that is not either dishonest or ineffective.
Defending the AI Overview Brand Mention
The AI Overview for a brand query is constructed from sources Google has determined are authoritative, up-to-date, and relevant to what a searcher is actually asking. For "what is [brand]" queries, it will typically draw from the company's own site, Wikipedia if an article exists, and one or two third-party sources like G2, Crunchbase, or major press coverage.
For "is [brand] legit" or "brand reviews" queries, the sourcing shifts dramatically toward review platforms, Reddit, and news coverage. This is where most brand SERP damage concentrates.
Defending against negative AI Overview content requires a two-part approach. First, you need to make the positive sources more authoritative and more AI-friendly than the negative ones. Second, you need schema markup that signals to Google what kind of entity you are and what your core positive attributes are, so that when the AI synthesizes a summary it has structured signals pulling in your direction.
I have seen three specific patterns where schema markup influenced AI Overview content for brand queries.
Pattern one: award strings in Organization schema appearing verbatim in AI Overviews. "G2 Leader" and "Best Places to Work" strings that were in the award array showed up in AI Overview summaries within 8 weeks of schema deployment.
Pattern two: description field language from Organization schema being partially echoed in AI Overview entity descriptions. Not copied verbatim, but the framing and key phrases appearing in the summary. This reinforces writing the description as a clean, factual, jargon-free summary of what the company does, not a marketing tagline.
Pattern three: aggregateRating from the company's own site (pulled from a legitimate review widget) competing with third-party ratings in AI Overview summaries. When the company's site carries structured rating data from multiple platforms (G2, Capterra, Trustpilot), Google sometimes surfaces the composite picture rather than leading with the single lowest-rated platform's number.
Schema Signals for AI Overview Brand Mention Defense
## AI Overview Brand Defense — Schema Priority Stack
Priority 1: Organization with comprehensive sameAs
(establishes entity identity, reduces ambiguity in graph resolution)
Priority 2: Organization.description — clean, factual, ≤250 characters
(feeds AI entity summaries; avoid superlatives and vague claims)
Priority 3: Organization.award array — specific, verifiable recognitions
(positive signal AI can cite when constructing brand summaries)
Priority 4: Organization.aggregateRating — site-level composite
Example:
{
"@type": "AggregateRating",
"ratingValue": "4.3",
"reviewCount": "312",
"bestRating": "5",
"worstRating": "1",
"description": "Composite rating from G2, Capterra, and Trustpilot"
}
Priority 5: Review schema on individual testimonial pages
(not fake or curated; must link to verifiable source platforms)
Priority 6: FAQPage schema on brand-adjacent content
(FAQPage schema can surface in AI Overview source citations for
informational brand queries; optimized Q&A framing gives you
narrative control over common brand questions)
Priority 7: Article schema on owned content covering brand story
(datePublished freshness signals influence which owned assets
appear in AI Overview source list for brand queries)
## Query Variants to Monitor for AI Overview Presence
- [brand name]
- [brand name] reviews
- [brand name] vs [competitor]
- [brand name] pricing
- [brand name] legit
- [brand name] [city] (for multi-location companies)
- [brand name] jobs
- is [brand name] worth it
- [brand name] problems / issues / complaints
## Monitoring Setup (Manual)
1. Create a Google account in incognito mode (to reduce personalization)
2. Check each query variant from this account weekly
3. Screenshot AI Overview content with timestamp
4. Track: presence/absence, source URLs cited, sentiment of summary,
specific data points surfaced (star ratings, founding dates, etc.)
5. Log changes week-over-week; correlate with schema deployments,
new third-party content, review volume changesThe monitoring setup above is manual because no tool I have tested tracks AI Overview content for brand queries reliably at weekly granularity. I have tried four different platforms in the past year. All of them have coverage gaps and none of them preserve the actual text of the AI Overview across time, which is what you need for attribution analysis.
You can get around this with a simple Google Sheet where a team member logs the AI Overview text weekly. Unglamorous. It works.
Two Things the Industry Gets Wrong
First contrarian take: Wikipedia is overrated for brand SERP defense, and chasing a Wikipedia article for companies that do not meet notability guidelines is a waste of time and sometimes actively harmful.
I know. This is not what most brand SERP practitioners will tell you. The conventional wisdom is that a Wikipedia article is the gold standard of entity legitimacy, that it feeds the knowledge panel, that it is page-one guaranteed real estate. All of this is true for companies that already have a Wikipedia article. For companies that do not, the calculation is different.
A Wikipedia article that gets nominated for deletion is worse for your brand than no Wikipedia article. The deletion nomination process creates a public discussion, indexed by Google, often containing the phrase "this company is not notable" or worse, factual disputes about the company's history or claims. I have seen clients end up with Wikipedia deletion discussions ranking on page two for their brand queries, which is an outcome precisely as bad as the Glassdoor problem they were trying to solve.
For companies under about 500 employees without significant press coverage, Wikidata is safer, more controllable, and provides most of the entity resolution value that Wikipedia provides. Stop chasing the Wikipedia article if the notability case is marginal.
Second contrarian take: brand SERP defense is not primarily a link-building problem, and treating it as one leads to wasted budget and misaligned timelines.
The dominant mental model in the industry is that negative results rank because they have more links, and the solution is to build links to positive content until those pages outrank the negative ones. This is partially true and mostly incomplete. Glassdoor pages rank for brand queries not primarily because of their link profile but because of their topical authority for employer-review content, their domain authority, and their content completeness for the specific query type. You rarely out-link Glassdoor for a Glassdoor-type query. You displace it by building content that better satisfies adjacent query intents until the brand SERP is crowded enough that Glassdoor falls to page two.
The lever is content surface area, not link count to specific pages. This is a slower strategy and a more honest one.
The Mistake I Made That Cost Six Weeks
Six weeks of lost momentum in a nine-month engagement is not catastrophic. But I want to document this because it is the kind of mistake that is easy to make and not often written about.
In the Glassdoor displacement engagement described above, I recommended deploying the Organization schema update and the new owned-content pages simultaneously. My reasoning was efficiency: fewer crawl events, consolidated technical signals, faster overall timeline. What actually happened was that Google's crawl of the new pages was delayed by a robots.txt configuration error that had existed on the client's site for months and that neither I nor the client's development team caught during QA. The new culture hub pages were disallowed in robots.txt for six weeks before anyone noticed.
The error was mine. Not because I should have reviewed the client's robots.txt (I did) but because I reviewed it before the new pages were deployed and did not re-verify after deployment. The development team had added a new URL pattern to robots.txt during a concurrent infrastructure change, and that pattern inadvertently matched the culture hub subdirectory path.
Six weeks of indexing delay on pages whose rankings were on the critical path for the engagement timeline.
My process now: any content deployment gets a robots.txt re-verification check 48 hours post-launch, using Google Search Console's robots.txt tester against the actual new URLs, not the pattern. And a Google Search Console URL inspection request for each key new page within 24 hours of launch, to confirm the page is accessible to Googlebot and requested for indexing.
Simple. Should have been in my process from the beginning. It is now.
Where Brand SERP Work Goes From Here
The trajectory is clear enough: AI systems are becoming the primary interface through which people form initial impressions of brands they have not encountered before. The question "what is [brand]?" is increasingly answered not by a SERP that users scroll through and evaluate but by an AI summary that synthesizes and presents a single narrative.
That narrative is built from the same underlying signals we have always worked with: what the brand says about itself, what third parties say about the brand, and how authoritative those third-party sources are. The difference is that in 2026, the synthesis happens before the user sees individual sources, and the user's ability to independently evaluate the sources is reduced when only one or two are cited.
This raises the stakes for every component of brand SERP work. Entity clarity matters more because ambiguous entity data produces inconsistent AI summaries. Third-party review management matters more because a 3.1-star rating in an AI Overview carries more weight than a 3.1-star result on page one that users might not click. Owned content quality matters more because AI systems preferentially cite structured, authoritative, specific content over vague brand-speak.
What I am watching closely: the development of brand-specific AI Overview feedback mechanisms. Google has expanded the "About this result" disclosure for AI Overviews, and there is a flagging workflow for factually incorrect AI summaries. I have used this flagging workflow twice, both times for incorrect founding dates pulled into AI Overviews. Both were corrected within three weeks. This is a legitimate channel that most practitioners are not using yet because most practitioners are still focused on ranking positions rather than AI Overview content.
The practitioners who thrive in this environment are the ones who understand that brand SERP ownership in 2026 is an entity management discipline first, a content strategy discipline second, and a link acquisition discipline third. The order of operations has genuinely changed. The underlying goal has not: own the first impression. Every channel, every format, every system that forms that impression is now in scope.
That is the job. Start with the entity panel. Work outward from there. And re-check your robots.txt after every deployment.
For further reading on related brand and entity topics covered in this series: the foundational brand SERP defense framework, knowledge graph optimization in depth, Organization schema beyond the basics, AI Overviews and CTR impact data, and generative engine optimization for brand queries.
External references: Schema.org Organization type specification and Wikidata WikiProject Companies guidelines for entity property standards.
