[[FIG:kb-0527]]

Step 1: Apply distinct Person schema to each executive

On the corporate leadership page, mark up each executive individually using Person schema. The markup should include:

• Full legal name including any middle initial that distinguishes the two individuals
• Current job title (jobTitle)
• The organization they work for (worksFor)
• Biographical anchors: education, prior employers, date of birth where publicly available
• A sameAs array pointing to that individual’s own verified profiles, not shared pages, and not the same URLs used for the other executive

Person schema with verified sameAs links helps engines build an identity graph and pull biographical disambiguation anchors for each person separately. When the schema on the corporate site points to two distinct sets of authoritative profiles, engines have a structured signal that these are different people.

Step 2: Build separate authoritative bios

Each executive needs their own distinct presence across authoritative third-party sources:

• LinkedIn: A complete, fully filled-out LinkedIn profile for each person, with their specific role, tenure, and career history. LinkedIn profiles rank consistently well on Google name searches due to the domain’s authority, and LinkedIn profiles feed the entity layer through sameAs relationships.
• Association and industry directories: Separate listings in any professional directories or trade association member registries relevant to each individual’s role.
• Wikipedia where notability supports it: If either executive is independently notable, a standalone Wikipedia article is the strongest disambiguation signal available. Wikipedia disambiguation pages and Wikidata identifiers are among the primary mechanisms by which engines distinguish same-named entities.

Step 3: Establish unique sameAs links per individual

Apply sameAs links consistently for each executive: the same set of profile URLs appears in their Person schema, in their bio page links, and in their Wikidata entry. The sameAs property in schema links an entity to authoritative profiles such as Wikipedia, Wikidata, and LinkedIn as a resolution signal. These links must not overlap. If the same URL appears in the sameAs array for both executives, the signal fails and conflation continues. Each person’s Wikidata entry should carry that person’s own unique Q-ID and their own sitelinks.

Step 4: Produce role-specific content that differentiates each executive

Engines learn who is who from co-citation patterns: who is quoted on which topics, who is associated with which decisions, which journalist sources which executive on which story. To build distinct co-citation clusters for each person:

• Attribute press quotes to the full name (including middle initial where applicable) and explicit title
• Produce thought leadership content, blog posts, op-eds, conference talks, that ties each executive to their specific domain (CFO on financial topics, CTO on technical topics, etc.)
• Ensure bylines and speaker bios consistently use the distinguishing name form for each individual

Content that repeatedly ties a name to a specific role, decision, or subject area gives engines the context they need to resolve the name correctly in AI-generated answers.

Step 5: Monitor for conflation across AI engines

Conflation between same-surname executives often starts in one engine and spreads. AIQ™ monitors the eight major AI engines it currently tracks: ChatGPT, Copilot, Gemini, AI Overview, Perplexity, Grok, Claude, and Google AI Mode. It surfaces cases where an executive is described with the wrong role, wrong biographical facts, or attribution that belongs to a same-named colleague. Catching conflation early, before it settles into AI training data, is far easier than correcting it once the false association has spread across engines. Conflated or false-identity content tends to persist in AI training data even after live coverage is corrected.

The post How do you manage search results when multiple executives share similar names? appeared first on Five Blocks.

[[FIG:kb-0476]]

1. Publish factual customer-facing content

Publish factual content on owned properties that affected customers can act on, structured so search and AI engines can read it cleanly:

• A recall page stating what is recalled and why.
• A recall FAQ and clear contact mechanisms.
• Guidance on exactly what affected customers should do.
• Structured data on the page so engines surface the official version.

2. Coordinate regulatory-aware messaging with counsel

Draft public statements with legal counsel so they align with the formal regulatory record, keeping the customer-facing narrative consistent with what has been filed.

3. Monitor the AI narrative daily through AIQ

Monitor the recall-specific narrative threads daily in AIQ, so the team can see whether the engines are picking up the official version or amplifying speculation and respond at the source where they diverge.

4. Build authoritative coverage of the remediation

Coordinate press around the resolution: independent third-party verification, restored production, and settlement of any litigation, so authoritative coverage of the remediation outranks coverage of the initial recall over time. Structured timeline content on the corporate site often becomes the reference the engines link to.

The post How do you handle search results during a product recall? appeared first on Five Blocks.

[[FIG:kb-0500]]

What wire releases actually do

• They feed the entity layer. Releases on credentialed wires such as Business Wire, PR Newswire, and GlobeNewswire are crawled, indexed, picked up by aggregators, and increasingly cited by AI engines. That puts brand-controlled language into the data layer.
• They create durable, brand-controlled URLs. A wire release produces a permanent public record with your exact wording. It’s useful for routine corporate news, executive announcements, and formal disclosures.
• They rarely rank durably on their own. Google recognizes press releases as paid distribution and weights them accordingly, so they seldom hold durable positions for branded queries by themselves.

The right use vs. the wrong use

The right use is as supporting infrastructure: statements that need to exist as a public record. The wrong use is as a substitute for earned media. AI engines weight a wire release with no independent coverage lower than the same facts reported by a credible third-party outlet, so placing fifty wire releases won’t produce the SERP or AI effect that a few strong earned placements do. Use wires for what they’re good at and don’t over-invest in them.

The post What role do press releases play in modern reputation management? appeared first on Five Blocks.

[[FIG:kb-0435]]

Minimum involvement

• A named primary contact on the communications or executive side
• Biweekly or monthly strategy calls
• Client review of significant content before it is published or submitted
• Review of monthly reporting against program goals

Maximum involvement (active programs in sensitive sectors)

• Weekly check-ins
• Real-time crisis coordination
• Joint working sessions with the client’s PR firm or legal counsel

What the Five Blocks team handles

• Wikipedia edit requests
• Schema markup
• IMPACT™ and AIQ™ monitoring
• Content production
• Entity work

Most clients spend two to four hours per month on the engagement after onboarding completes.

The post How involved do we need to be? appeared first on Five Blocks.

[[FIG:kb-0456]]

1. Sustained authoritative counter-content from outlets Google considers comparable to the original source.
2. Source-level remediation where any factual errors in the original justify a correction request.
3. Patience to let Google’s authority signals on the new content accumulate over the months it takes.

Why the work has to be sustained

The reason displacement takes months rather than weeks is that a piece from an authoritative source does not fade on its own. Left unaddressed, a single Wall Street Journal, New York Times, or Reuters article can hold a top-page position for three, five, even seven years, because it keeps working in Google’s favor long after publication:

• It continues to accumulate inbound links over time.
• It gets cited in subsequent coverage, which reinforces its standing.
• It benefits from the source’s overall domain authority even as the article’s own freshness fades.

Because the article will not weaken on its own, the competing signals have to be built and maintained deliberately. Programs that promise to displace a major-outlet article in 60 days are not describing reality. Moving that top-page position takes a firm like Five Blocks working the authoritative-content and source-remediation levers steadily and tracking the SERP over time.

The post How long do negative articles stay visible in Google search results? appeared first on Five Blocks.

[[FIG:kb-0519]]

Step 1: Build strong Organization schema with distinctive anchors

Apply Organization schema markup to the corporate site and fill it with anchors no generic word can share: founding year, registered headquarters address, founder names, core products and services, and industry classification. These structured fields give engines unambiguous facts that tie the brand to a specific real-world entity rather than a dictionary definition.

Step 2: Add sameAs links from the schema to verified authoritative profiles

sameAs properties inside the Organization schema connect the corporate site to the brand’s entries on Wikidata, Wikipedia, LinkedIn, and other authoritative registries. Each link is a machine-readable statement that all of these pages refer to the same entity. Engines use this identity graph to separate the brand from its namesake word and from other entities with the same name.

Step 3: Develop (or strengthen) a Wikipedia article where notability applies

Wikipedia is the strongest single disambiguation signal the engines have. A dedicated, well-developed article puts the brand in a named entity category that no generic word occupies, creates a Wikipedia disambiguation page entry when one is needed, and feeds the Wikidata record that anchors the brand’s unique identifier across the Knowledge Graph.

Step 4: Build authoritative third-party coverage that names the brand as an entity

Coverage in mainstream outlets, trade press, and industry directories that consistently uses the brand name in the company sense, not the generic word sense, teaches engines to tie that string to the corporate entity. Co-citation across authoritative sources strengthens the entity signal beyond what owned properties can do alone.

Step 5: Monitor AI engine output for disambiguation failures

Common-word brands are unusually prone to conflation in AI responses: an engine can describe the brand as if it were the generic concept, or blend facts from an unrelated entity with the same name. Monitoring across the major AI engines catches these failures early, so you can correct the underlying entity infrastructure before the wrong description spreads.

The post How do you manage search results for a company that shares a name with a common word? appeared first on Five Blocks.

What an in-house team can own

• Social monitoring – tracking brand mentions across social platforms.
• Review responses – replying to reviews on Google, Glassdoor, and industry platforms.
• Corporate blog content – maintaining and publishing owned editorial.
• PR execution – pitching, placement, and executive visibility.

What typically needs a specialist

• Wikipedia editing under disclosed COI rules – paid and affiliated editors are strongly discouraged from editing articles directly and are expected to propose changes through the Talk-page edit-request process, which requires sustained editorial experience and standing with the editor community.
• AI engine source attribution – identifying which sources drive each engine’s answer requires a tool like AIQ and analyst pattern recognition; AIQ tracks how eight major AI models (ChatGPT, Gemini, Perplexity, Claude, Grok, Copilot, Google AI Mode, and AI Overview) describe a brand.
• Knowledge Graph and schema markup – deep technical fluency that few in-house teams carry full-time.
• Cross-account learning – knowing which sources move which engines, which tactics survive algorithm changes, and which placements waste budget compounds with a volume of accounts that no single company can generate.

[[FIG:kb-0418]]

The post Why can’t we manage our digital reputation in-house? appeared first on Five Blocks.

[[FIG:kb-0529]]

Step 1: Organization schema, the entity anchor

Organization schema in JSON-LD is the machine-readable foundation. It carries fields that search and AI engines read directly: name, legalName, url, logo, founder, foundingDate, address (headquarters), and contactPoint. The sub-element that matters most is the sameAs array: links to the company’s Wikidata entry, Wikipedia article, LinkedIn page, Crunchbase profile, and other authoritative directories. These sameAs links tell Google and AI engines which entity the page is about and connect it to the wider entity graph. Without them, the page is just prose.

Step 2: Narrative with descriptive headings

The body copy should say what the company does, for whom, and to what end, written to be extracted rather than merely read. Use descriptive <h2> and <h3> headings that work as extractable labels (for example, “What [Company] Does”, “Markets Served”, “How We Work”). Skip heading text that is decorative or meaningless on its own. AI engines build entity answers from owned web properties, and structured prose with clear headings is extracted more reliably than a wall of marketing copy.

Step 3: Leadership section with Person schema

Each named executive should appear with Person schema markup that specifies name, jobTitle, worksFor, image, url, and sameAs links to their LinkedIn profile and, where available, their Wikipedia article and Wikidata Q-ID. These sameAs links tie the individual to their machine-readable identity and stop engines from confusing them with same-named people. Each Person node should link out to a deeper bio page. That spreads entity signals across the site and gives engines a fuller identity graph for the leadership team.

Step 4: FAQPage schema for branded questions

Include a set of branded Q&A pairs covering the questions most likely to come up in a branded search session, “What does [Company] do?”, “Where is [Company] headquartered?”, “Who founded [Company]?”, and mark them up with FAQPage schema. FAQPage schema makes question-and-answer content explicitly machine-readable and extractable by AI engines and featured snippet algorithms. One caveat: as of May 2026, Google retired FAQ rich results, and FAQPage markup no longer generates an FAQ accordion in the organic SERP. The schema still helps with AI engine extraction and voice assistant answer selection, but it will not produce a visible SERP enhancement in Google Search.

Step 5: External citations section

Reference recent authoritative third-party coverage on the page itself: press mentions, awards, partner announcements, analyst inclusions. These citations do two things. They give engines live outbound signals to follow when confirming the entity’s authority and recency, and they cue engines to read the page as a credible, current entity document rather than evergreen marketing copy. AI engines treat authoritative sources, mainstream news, awards bodies, official partner networks, as trust signals when they build entity answers, so surfacing those citations on the About page connects the entity to that authority chain.

Step 6: Update cadence

Keep the page current. Retrieval-based AI engines can pick up content changes within weeks; training-based engines pick them up at the next training cycle. An outdated About page, stale leadership, an old headquarters, discontinued products, creates factual conflicts that make engines hedge or surface wrong information. A dependable maintenance cadence, quarterly at minimum, keeps the page matched to current reality and tells crawlers the content is actively maintained.

The post How do you optimize a company’s about page to rank on page one for branded searches? appeared first on Five Blocks.

[[FIG:kb-0552]]

Why a single global playbook fails

Press conventions

Editorial culture shapes what gets covered and which content format earns credibility. German business press tends to value precision, technical depth, and cited data; US press favors narrative accessibility and executive personality. Japanese press has traditionally prized formality, consensus language, and institutional framing. Pitching US-style content to a German outlet, or a German-style document to a US trade editor, produces friction and lower placement rates. (Note: these are practitioner-level observations; no quantified cross-market press preference study was available in the source library to corroborate them precisely, treat as informed framing rather than citable statistics.)

Authority signals

Third-party publications carry different weight depending on where the audience sits. A Forbes profile carries clear authority with US and some global institutional audiences, but its weight drops in markets that have their own dominant credentialing outlets or that see US business media as remote. Local trade press, regional business journals, and country-specific analyst coverage often carry more decision weight with local stakeholders than the equivalent tier of US outlet. (The source library confirms that Forbes and Bloomberg carry high domain authority globally, but does not provide market-by-market data on relative credibility weight, the specific Latin America vs. UK comparison in the original answer is directionally plausible but should be treated as unquantified editorial judgment.)

Acceptable content style

Tone that reads as confident and authoritative in a US context can read as boastful or aggressive in UK or Japanese contexts, where understatement and deference carry more credibility. Direct self-promotion in owned content, standard practice in the US, can generate skepticism or active distrust among some European or East Asian audiences. Content strategy has to be calibrated to local conventions, not translated from a US template.

Key channels

The platforms that hold stakeholder attention differ by market. WhatsApp groups act as a significant information channel in Brazil and Saudi Arabia in ways they do not in the US or UK, where email, LinkedIn, and broadcast outlets dominate professional communication. Regional social platforms, messaging apps, and local news aggregators each have their own reach, and a program designed around US-centric channels never sees them. (The source library contains WhatsApp’s terms of service but does not provide quantified data on WhatsApp’s share of professional communications in Brazil or Saudi Arabia, these channel observations are directionally supported by widely reported market-penetration patterns but were not independently verified through the source library.)

Search and AI engine behavior

Google resolves and describes entities differently across markets and languages. Country-code domains (.de, .fr, .jp) apply local ranking signals, and different Wikipedia language editions have their own editorial communities and standards that diverge from the English Wikipedia. A strong English-language entity presence does not automatically transfer to German, French, or Japanese search results. AI engines also apply language and locale context when forming responses, so per-market monitoring through tools like AIQ™, running prompts in the local language, is needed to understand what stakeholders in each priority market are actually seeing.

How to adapt to local markets

• Commission local expertise, not translations. The right model has local practitioners informing execution, whether in-house people with real market depth or partner agencies with established credibility in the target market. Translating a US playbook is not a substitute for local editorial judgment.
• Map the credentialing ecosystem per market. Identify which outlets, directories, association memberships, and third-party citations carry authority with local stakeholders before deciding where to invest earned media efforts.
• Audit channel assumptions. Confirm which communication and information channels actually reach decision-makers in each priority market; do not assume US-centric defaults transfer.
• Run per-market Wikipedia and entity work. Each language Wikipedia is a distinct editorial environment. Wikidata and schema work that supports English-language entity recognition has to be extended with language-appropriate Wikipedia articles and local directory citations to work across markets.
• Monitor in-language. SERP tracking and AI engine monitoring should run in the local language and from local geographic contexts, so the program sees what local stakeholders see rather than an approximation from a US vantage point.

The post How do cultural differences affect reputation management strategy? appeared first on Five Blocks.

[[FIG:kb-0468]]

What feeds a domain’s authority

The concept is generally understood to aggregate several inbound signals:

• Backlinks from credentialed, prominent sites
• Domain age and an established track record
• Content depth across the domain
• Citation patterns and how often the domain is referenced elsewhere

Google confirms that links from prominent websites are one factor it uses to assess quality, so higher-authority domains tend to make individual URLs easier to rank. This is why coverage on an established, widely-cited outlet often surfaces ahead of comparable content on a little-known site.

How reputation work treats it

Good programs treat domain authority two ways:

• As a long-term investment on owned domains: sustained quality content, careful link earning, and technical health, built up over months and years.
• As a placement criterion for earned work: prioritizing coverage on domains the engines already trust, rather than publishing on low-trust sites.

The failure mode: treating it as a number to game

The mistake is treating domain authority as a score to inflate through volume tactics, mass link building and similar manipulation. Google’s spam policies target this directly: the engine defines link spam as “creating links to or from a site primarily for the purpose of manipulating search rankings,” and it acts against that behavior. The short-term gains from such tactics rarely outweigh the penalty risk, which is why reputation work that lasts earns authority rather than manufacturing it.

The post What is the role of domain authority in reputation management? appeared first on Five Blocks.