Author: Onxeera Editorial Team | Last Updated: August 2026 | Reading Time: 10 min
TL;DR: This case study documents how a B2B management consulting firm specializing in supply chain transformation tripled its AI citation rate — from 14% to 43% — in 60 days through a focused schema audit and repair program. The firm had a mature content library (68 articles), solid thought leadership, and good domain authority, but schema implementation was riddled with errors: broken sameAs URLs, stale dateModified values on 54 articles, FAQPage schema on only 3 of 19 pages with FAQ sections, and missing Organization schema on the homepage. The schema audit identified 11 critical issues, 23 high-impact gaps, and 14 optimization opportunities. Fixing the top 20 issues over 8 weeks produced a 3x citation rate improvement. The full audit methodology, issue list, and fix sequence are documented here.
Table of Contents
- Firm Background
- Starting Citation Position
- Schema Audit Methodology
- Critical Schema Errors Found
- High-Impact Schema Gaps Found
- Fix Prioritization and Sequencing
- Week-by-Week Fix Implementation
- Results at 60 Days
- Per-Platform Citation Breakdown
- ROI Calculation
- Key Findings for B2B Professional Services
- The Schema Audit Checklist Used
- FAQs
- Related Articles
Firm Background
The firm in this case study — referred to as “ChainWise Consulting” — is a B2B management consulting firm of 85 consultants specializing in supply chain transformation, procurement optimization, and operations strategy for mid-to-large industrial and manufacturing clients. Founded in 2014, ChainWise had built a strong thought leadership content program over 4 years: 68 published articles, 4 white papers, 3 annual benchmark reports, and an active LinkedIn presence with 12,000 followers. The firm’s domain authority was 58 (Ahrefs DR), and it ranked on the first page of Google for 31 target keywords.
ChainWise first tested its AI search presence in January 2026 after noticing that several inbound leads mentioned “finding us through ChatGPT” in their initial inquiry emails. When the firm’s marketing director manually tested key queries in ChatGPT, Gemini, and Perplexity, the results were disappointing: ChainWise appeared in approximately 1 in 7 tested queries — a 14% citation rate that seemed low given the firm’s content volume and domain authority. The question was not whether to improve AI citation performance, but how — and the marketing director correctly identified the schema implementation as the logical first investigation area.
Related: GEO for Professional Services | GEO Schema Audit
Starting Citation Position
Baseline Measurement
A structured baseline measurement tested 42 target queries across ChatGPT Browse, Gemini, Perplexity, and Google AI Overviews — 168 query-platform combinations total. The 42 queries spanned five categories: brand identity (“what is ChainWise Consulting?”), expertise recognition (“leading supply chain consulting firms”), topic authority (“best practices for procurement transformation”), service-specific (“supply chain risk assessment consulting”), and thought leadership (“supply chain benchmark report 2025”). Baseline results: ChainWise cited in 24 of 168 combinations — a 14.3% citation rate. Citation quality was also uneven: brand identity citations were often incomplete or mixed with a different “ChainWise” entity (a software company with a similar name), and topic authority citations were present on Perplexity but absent on ChatGPT and Gemini for all but two queries.
The Entity Confusion Problem
An important secondary finding in the baseline audit: 6 of the 24 baseline citations described ChainWise incorrectly — attributing software products or technology features to the firm that actually belonged to a software company called “ChainWise Technologies.” This entity disambiguation problem was suppressing named citation rates and producing inaccurate brand descriptions in AI answers — a reputational risk in addition to a GEO performance problem. Resolving the disambiguation required both schema fixes (Organization schema with precise entity data) and Wikidata entity creation (to establish a machine-readable unique identifier that disambiguated the consulting firm from the software company).
Schema Audit Methodology
The schema audit followed a four-phase methodology across two weeks: site-wide schema crawl (Screaming Frog), individual page validation (Google Rich Results Test on all 68 articles and 12 service pages), Google Search Console Enhancements review, and sameAs URL integrity testing (manual testing of all 8 sameAs URLs in existing partial Organization schema). The audit produced a prioritized issue list in three tiers: critical errors (issues that actively harm citation performance), high-impact gaps (missing schema on pages with high citation potential), and optimization opportunities (completeness improvements on existing valid schema).
Critical Schema Errors Found
Critical Error 1: Broken sameAs URLs (5 of 8)
ChainWise had a partial Organization schema on the homepage (implemented 18 months earlier by a web agency) with 8 sameAs URLs. Testing each URL revealed 5 were broken: the LinkedIn URL used the old company handle (changed after a rebrand 14 months ago and now returning a 404), the Twitter/X URL pointed to a personal account rather than the company account, a Forbes contributor profile URL had been removed when the contributor left the firm, an industry directory URL had changed its URL structure (redirecting to the homepage, not the firm’s specific listing), and a speaking bureau profile URL returned a 403. The 5 broken sameAs URLs were actively harming entity recognition — AI systems that follow sameAs links and find broken destinations treat the entity’s cross-reference network as unreliable, reducing entity citation confidence.
Critical Error 2: JSON Syntax Error in Article Schema
A JSON syntax error — a missing closing bracket in the Article schema template used by the firm’s WordPress theme — was breaking Article schema on all 68 published articles. The error was introduced when the theme was updated 7 months prior and had gone undetected because the theme’s visual output was unaffected. The Google Rich Results Test confirmed the error: all 68 article schema blocks were invalid and returning a parse error. This single undetected error was eliminating structured article entity data for the entire content library — all 68 articles were effectively invisible to schema-dependent AI citation processes despite being fully indexed as HTML content.
Critical Error 3: datePublished Format Error
The firm’s CMS was outputting datePublished in a non-ISO format (“August 15, 2024” rather than “2024-08-15”) on 31 articles published before a CMS migration. AI systems parsing datePublished expect ISO 8601 format — non-standard date formats are either ignored or misread, which caused those 31 articles to appear to have no datePublished signal at all. This format error, combined with the Article schema JSON syntax error, meant that ChainWise’s entire pre-migration article library had effectively zero structured date signals for AI freshness evaluation.
High-Impact Schema Gaps Found
Gap 1: FAQPage Schema on 16 of 19 FAQ Pages Missing
ChainWise had FAQ sections on 19 articles and service pages — but only 3 had FAQPage schema implemented. The 16 pages without FAQPage schema were missing the primary structured citation signal for question-format queries. Given that supply chain and consulting buyers frequently ask question-format queries (“what does supply chain transformation involve?”, “how long does a procurement audit take?”, “what is the ROI of supply chain optimization?”), this gap was directly responsible for the near-zero citation rate on topic authority and service-specific query categories.
Gap 2: No Person Schema on Author Pages
ChainWise had 7 named consultants who authored articles on the firm’s blog — but no Person schema on any of the 7 author profile pages. Each author had a short bio and headshot, but no structured data linking their expertise to their credentials (MBA from Wharton, APICS CSCP certification, 18 years at a Big 4 consulting firm). Without Person schema, the authors’ credentialed expertise was invisible to AI E-E-A-T evaluation — potentially reducing citation confidence for the articles they authored, particularly for competitive expert-level queries where author authority matters.
Gap 3: Organization Schema Incomplete
The existing Organization schema (despite its broken sameAs URLs) was also missing: foundingDate, description (the existing description was one generic sentence — “ChainWise is a management consulting firm”), knowsAbout (entirely absent), numberOfEmployees, and areaServed. The incomplete Organization schema was contributing to the entity confusion problem — without specific, distinctive entity data, AI systems had difficulty distinguishing ChainWise Consulting from ChainWise Technologies.
Gap 4: No Schema on White Papers and Benchmark Reports
ChainWise’s 4 white papers and 3 annual benchmark reports — the firm’s highest-authority content — had no schema whatsoever. These were the pieces most likely to be cited for original data queries (“supply chain benchmark statistics,” “procurement transformation ROI data”) but were being treated by AI systems as unstructured HTML documents with no entity attribution. Article schema with author attribution and relevant keywords was absent on all 7 pieces.
Fix Prioritization and Sequencing
The 11 critical errors and 23 high-impact gaps were prioritized into a 8-week fix sequence based on three criteria: citation impact (how much citation improvement is this fix expected to produce?), implementation effort (how long will this fix take?), and dependency (does this fix need to be in place before another fix can be effective?). The sequence prioritized critical error fixes in Week 1 to 2 (these were blocking all other improvements), followed by high-impact gap fixes in Weeks 3 to 6, and optimization improvements in Weeks 7 to 8.
Week-by-Week Fix Implementation
Week 1: Critical Error Fixes
The JSON syntax error in Article schema was the first fix — a one-line correction in the WordPress theme’s schema template that immediately validated all 68 Article schema blocks. The fix was validated with the Google Rich Results Test on 10 representative articles, all of which passed immediately after the theme correction. All 68 articles were submitted to Google Search Console for indexing on the same day. The datePublished format error was corrected by updating the CMS’s date output format for articles published before the migration — a template change that applied retroactively to all 31 affected articles. Total Week 1 schema fix time: approximately 6 hours including validation.
Week 2: Organization Schema Rebuild
The existing Organization schema was replaced entirely with a comprehensive new implementation: canonical name (“ChainWise Consulting”), legalName (“ChainWise Consulting Group LLC”), foundingDate (“2014-02-10”), description (a specific 4-sentence description including the firm’s specialization in supply chain transformation and procurement optimization, target client profile — mid-to-large industrial and manufacturing companies — and geographic service area), knowsAbout (14 specific terms including “supply chain transformation,” “procurement optimization,” “supplier risk management,” “S&OP implementation,” “inventory optimization,” “logistics network design,” and “supply chain digital transformation”), areaServed (United States and Canada), numberOfEmployees ({“@type”: “QuantitativeValue”, “value”: 85}), and a corrected sameAs array with all 8 URLs replaced — 5 broken URLs removed and 5 correct current URLs added (LinkedIn with correct handle, company Twitter/X, Crunchbase, the correct industry directory listing URL, and a new consulting directory listing). A Wikidata entity was also created for ChainWise Consulting (Q-number obtained) and added to the Organization schema identifier property.
Weeks 3-4: FAQPage Schema Batch Implementation
FAQPage schema was implemented on all 16 pages with FAQ sections that lacked it. The implementation was batched by content type: 9 blog articles (Week 3, averaging 35 minutes each) and 7 service pages (Week 4, averaging 45 minutes each — service page FAQs tended to be longer with more complex answers requiring careful schema matching). All 16 pages were submitted to Google Search Console for indexing upon completion. The 3 pages that already had FAQPage schema were audited and updated — 2 had minor schema-content text mismatches that were corrected.
Weeks 5-6: Article Schema dateModified and Author Attribution
With the Article schema JSON error fixed, the focus shifted to dateModified currency and author attribution. All 68 articles were reviewed: 54 had dateModified values either absent or identical to datePublished (indicating they had never been updated in schema after publication despite many having received content updates). Each of the 54 articles received a substantive content update (updating one statistic, one case study reference, or one market data point to current figures) and a dateModified update to the update date. Person schema was implemented on all 7 author profile pages — each with the author’s full name, job title, educational credentials (alumniOf), professional certifications (hasCredential), employer (ChainWise Consulting as Organization entity), and knowsAbout (specific topic expertise areas for each author). Article schema on each article was updated to link the author property to the corresponding Person entity rather than using a plain text string.
Weeks 7-8: White Paper and Benchmark Report Schema
Article schema was implemented on all 4 white papers and 3 annual benchmark reports. Each schema block included: headline (exact document title), author (linked to the primary authoring consultant’s Person entity), publisher (ChainWise Consulting Organization entity), datePublished, dateModified (current, after a content review pass on each document), about (array of specific supply chain topics covered), keywords (specific supply chain terminology), citation (links to any third-party data sources referenced in the document), and isPartOf (linking benchmark reports to a series). The citation property on the benchmark reports was particularly important — it demonstrated that ChainWise’s original research was evidence-based and cross-referenced with authoritative third-party data sources.
Results at 60 Days
Overall Citation Rate
The 60-day measurement tested the same 42 queries across the same 4 platforms (168 combinations). Results: ChainWise cited in 72 of 168 combinations — a 42.9% citation rate, compared to the 14.3% baseline. Citation rate improvement: 3.0x (exactly tripled). All citation improvements were produced by schema fixes and entity optimization alone — no new content was published during the 8-week program, and no changes were made to content format, heading structure, or internal linking. The 3x improvement was entirely attributable to schema quality and entity signal improvements.
Citation Rate by Query Category
| Query Category | Baseline | Day 60 | Primary Fix Driver |
|---|---|---|---|
| Brand identity queries | 19% | 88% | Organization schema rebuild + Wikidata entity |
| Expertise recognition | 12% | 45% | knowsAbout schema + Person schema authors |
| Topic authority queries | 10% | 38% | FAQPage schema + Article dateModified fix |
| Service-specific queries | 14% | 40% | FAQPage schema on service pages |
| Thought leadership queries | 17% | 48% | Article schema on white papers + benchmark reports |
Entity Confusion Resolution
The entity disambiguation problem was fully resolved at Day 60: 0 of the 72 citations contained incorrect information attributable to ChainWise Technologies. The Wikidata entity, rebuilt Organization schema with specific consulting firm descriptors, and corrected sameAs network collectively eliminated the AI confusion between the two ChainWise entities. AI descriptions of ChainWise Consulting at Day 60 were consistently accurate — correctly identifying the firm as a management consulting firm specializing in supply chain transformation, with no technology product attributions.
Per-Platform Citation Breakdown
| Platform | Baseline | Day 60 | Key Fix Driver |
|---|---|---|---|
| Perplexity | 24% (10/42) | 60% (25/42) | dateModified freshness + FAQPage schema |
| ChatGPT Browse | 12% (5/42) | 43% (18/42) | Article schema fix + FAQPage schema |
| Gemini | 10% (4/42) | 36% (15/42) | Wikidata entity + Organization schema rebuild |
| Google AI Overviews | 12% (5/42) | 33% (14/42) | FAQPage schema + Article schema fix |
| Total | 14.3% (24/168) | 42.9% (72/168) | 3.0x improvement |
The most notable single-platform improvement was on Perplexity — from 24% to 60% — driven primarily by the dateModified freshness fix. Perplexity’s strong freshness weighting meant that fixing 54 stale dateModified values (after substantive content updates) produced an outsized improvement on this platform compared to others. Gemini showed the second-largest improvement (10% to 36%), driven primarily by the Wikidata entity and Organization schema rebuild — consistent with Gemini’s Knowledge Graph integration that makes Wikidata the highest-leverage entity investment for Gemini citations specifically.
ROI Calculation
Investment
Total implementation time: approximately 85 hours across 8 weeks — 60 hours from the marketing director (schema research, Organization schema writing, FAQPage schema implementation, author page Person schema), 15 hours from a web developer (Article schema JSON fix, CMS date format fix, theme schema template updates), and 10 hours of content review time from senior consultants (reviewing articles for substantive updates before dateModified refreshes). At blended internal rates, the total investment was estimated at approximately $8,500 in staff time.
Measurable Outcomes at 90 Days
Three measurable business outcomes were tracked at 90 days post-implementation: inbound leads that mentioned AI search in their first contact (email or inquiry form) increased from an average of 1.8 per month in the 6 months before the program to 6.3 per month in the 3 months following — an increase of 4.5 AI-attributed leads per month. Direct brand search volume (Google Search Console) increased 31% compared to the equivalent prior-year period. Two speaking invitations were received from conference organizers who “found ChainWise through AI research” — a qualitative indicator that ChainWise’s thought leadership content was now surfacing in AI-powered conference planning research.
At ChainWise’s average project value of $185,000 and a 15% close rate on qualified inbound leads, the 4.5 additional AI-attributed leads per month represented approximately $125,000 in additional expected monthly pipeline — a significant return on the $8,500 implementation investment within the first 90 days of measurable outcomes.
Key Findings for B2B Professional Services
- Finding 1: A single undetected JSON syntax error can silently invalidate an entire content library’s schema. ChainWise’s Article schema JSON error had been breaking all 68 articles’ structured data for 7 months without any visible impact on the website or traditional SEO performance. The only symptom was suppressed AI citation rates — and without citation tracking, the firm would not have identified the problem. Schema validation should be part of every website maintenance routine, not just initial deployment.
- Finding 2: Broken sameAs URLs are more damaging than missing sameAs URLs. A sameAs array with 5 broken links actively signals unreliable entity data — worse than having no sameAs at all. AI systems that attempt to verify an entity’s cross-references and find broken links treat the entity’s structured data as potentially stale or inaccurate. Audit sameAs URLs quarterly and remove any that no longer resolve correctly.
- Finding 3: Person schema on author pages with professional credentials significantly improves E-E-A-T citation signals for B2B professional services. ChainWise’s authors had impressive credentials (APICS certifications, Big 4 consulting experience, graduate degrees from recognized universities) that were invisible to AI systems before Person schema implementation. After implementing Person schema with hasCredential and knowsAbout, AI citation confidence for expert-level queries improved measurably — AI descriptions of ChainWise began consistently referencing the firm’s consultant credentials as a quality signal.
- Finding 4: Thought leadership content (white papers, benchmark reports) without Article schema is underperforming its citation potential. ChainWise’s benchmark reports — original data that other industry sources cited and referenced — had essentially no AI citation impact before Article schema implementation because AI systems had no structured way to attribute the research to ChainWise as the publishing entity. After schema implementation, the benchmark reports became the firm’s highest-performing citation assets — earning citations for data-specific queries that no amount of general content could earn.
- Finding 5: Entity disambiguation requires proactive investment — it does not resolve on its own. ChainWise’s entity confusion with ChainWise Technologies had persisted for at least 18 months before the GEO program addressed it. Without intervention, AI systems continued producing inaccurate brand descriptions and occasionally routing AI-attributed leads to the wrong company’s website. Entity disambiguation through Wikidata, Organization schema rebuild, and corrected sameAs required approximately 8 hours of investment and resolved the problem within 30 days — an investment that should have been made the moment the firm became aware of the competing entity.
The Schema Audit Checklist Used
The following checklist was used in ChainWise’s schema audit and can be applied to any B2B professional services firm:
Critical Error Checks (Fix Immediately)
- [ ] JSON-LD syntax valid on all schema blocks (use JSON-LD Playground validator)
- [ ] All sameAs URLs returning HTTP 200 (test each individually)
- [ ] datePublished in ISO 8601 format (YYYY-MM-DD) on all Article schema
- [ ] No schema-content price or factual mismatches
- [ ] No duplicate schema type implementations (two plugins generating the same schema type)
High-Impact Gap Checks (Fix Within 2 Weeks)
- [ ] FAQPage schema on all pages with FAQ sections
- [ ] Organization schema on homepage with complete knowsAbout and sameAs
- [ ] Person schema on all author profile pages with hasCredential
- [ ] Article schema on all white papers and research reports
- [ ] dateModified current on all articles updated in the past 12 months
Optimization Checks (Fix Within 1 Month)
- [ ] Article schema author linked to Person entity (not plain text string)
- [ ] Organization schema identifier with Wikidata Q-number
- [ ] Article schema about and keywords populated with specific topic terms
- [ ] BreadcrumbList schema on all pages
- [ ] citation property on research content linking to primary sources
FAQs
How was a 3x citation rate improvement achieved without publishing any new content?
ChainWise’s content library was already comprehensive and high-quality — the problem was not content quality but structured data quality. AI systems could not efficiently extract entity information, identify authorship and credentials, or recognize FAQ content for citation because the schema communicating this information was broken, missing, or stale. Fixing the schema allowed AI systems to correctly interpret content that was already there — unlocking citation potential that the content had always possessed but could not express without valid structured data. This is a common finding: strong content with poor schema significantly underperforms its citation potential.
Which schema fix produced the biggest citation improvement?
The Article schema JSON syntax fix produced the largest single citation improvement — it restored valid structured data to all 68 articles simultaneously. Before the fix, all 68 articles were being treated by AI systems as unstructured HTML with no entity attribution, no author data, and no date signals. After the fix, all 68 articles immediately became structured, attributed content with author entity links and date signals. The FAQPage schema implementation on 16 pages was the second-largest contributor, particularly for question-format query citations on Perplexity and ChatGPT.
How long did it take for schema fixes to show citation improvement?
The Article schema JSON fix showed citation improvement within 3 weeks — faster than typical schema changes because AI crawlers had to re-crawl content they already had indexed (just without valid schema), which happens faster than first-time indexing of new content. FAQPage schema improvements appeared on Perplexity within 4 weeks and on ChatGPT and Gemini within 5 to 6 weeks. The Organization schema and Wikidata entity improvements appeared most prominently on Gemini at 6 to 7 weeks — consistent with Gemini’s Knowledge Graph update cycle being slightly slower than Perplexity’s real-time crawl.
Is a schema audit worthwhile for a firm that already has some schema implemented?
ChainWise’s experience strongly suggests yes — the firm had schema implemented (partial Organization schema, Yoast-generated Article schema) but the implementation was broken and incomplete in ways that were invisible without a systematic audit. Partial or broken schema is not neutral — it can actively harm entity recognition and citation confidence by signaling that a domain’s structured data is unreliable. Any firm that implemented schema more than 12 months ago and has not validated it since should treat a schema audit as a maintenance necessity rather than an optional improvement.
Run Your Schema Audit
ChainWise’s experience demonstrates that schema quality is often the primary bottleneck separating strong content from strong AI citations — and that fixing schema issues produces faster, more predictable citation improvement than equivalent investment in new content creation. Start with the critical error checklist: a JSON syntax validation pass across your schema blocks and a sameAs URL integrity test takes under 2 hours and may reveal the same type of silent, high-impact errors that were suppressing ChainWise’s citation performance for 7 months.