Draft a news carousel eligibility hardening: AMP/eligible markup retirement plan,…
- User
Draft a news carousel eligibility hardening: AMP/eligible markup retirement plan, live‑blog signals, timestamps rules, and latency SLOs.
Assistant
The user wants a "news carousel eligibility hardening" plan. The context appears to be related to web standards, SEO, and publishing platforms (specifically Google's News/Top Stories ecosystem, given the mention of AMP, eligible markup, live blogs, and SLOs).
Key elements requested:
- AMP/Eligible Markup Retirement Plan: How to move away from AMP or specific "eligible" markup requirements while maintaining carousel eligibility.
- Live-Blog Signals: Specific requirements for live coverage.
- Timestamps Rules: Accuracy and formatting of time data.
- Latency SLOs (Service Level Objectives): Performance thresholds required to stay eligible.
I need to draft this as a formal internal strategy or external announcement document (likely internal/technical strategy). I will structure it as a phased plan to "harden" the criteria for appearing in high-visibility news carousels.
Deconstruction & Brainstorming:
-
Context: Google has been moving away from mandating AMP for the Top Stories carousel (since the Page Experience Update). However, "eligibility hardening" implies tightening the requirements for non-AMP pages to ensure they perform just as well. This is about raising the bar for standard HTML to ensure high quality.
-
Section 1: AMP/Eligible Markup Retirement Plan
- Concept: We aren't "retiring AMP" completely necessarily, but rather retiring the preference or the exclusive eligibility tied to it, or perhaps the user means retiring the legacy AMP-specific markup in favor of standard schema.
- Correction: The prompt says "AMP/eligible markup retirement plan." This sounds like a plan to retire the dependency on AMP or specific complex markup to simplify the codebase while keeping eligibility.
- Strategy: Deprecate specific AMP cache reliance. Transition to Signed Exchanges (SXG) or just highly optimized Core Web Vitals (CWV).
- Action items: Audit current AMP pages, map features to standard HTML, implement SXG, monitor CWV.
-
Section 2: Live-Blog Signals
- Concept: Live blogs need to be treated differently than static articles. Search engines need to know "this is happening now."
- Requirements:
LiveBlogPostingSchema.org markup. Frequent updates. "Freshness" signals. - Hardening: Require specific update cadence (e.g., every X minutes). Require clear visual indicators (timestamps on blocks). Structured data validation must be 100% error-free.
-
Section 3: Timestamps Rules
- Concept: Time is critical for news. Misleading timestamps (e.g., recycling old news as new) is a penalty trigger.
- Rules: Must distinguish between
datePublishedanddateModified. - Hardening: Enforce ISO 8601 format. Strict logic:
dateModifiedcannot be beforedatePublished. Syndication handling (source attribution).
-
Section 4: Latency SLOs
- Concept: If we aren't using AMP (which is fast by default), our custom stack must meet strict speed goals.
- SLOs: Core Web Vitals (LCP, INP, CLS). Time to First Byte (TTFB).
- Thresholds: LCP < 2.5s. TTFB < 200ms (for the crawler). HTML payload size limits.
Drafting the Structure:
I will write this as a Strategic Planning Document titled "News Carousel Eligibility Hardening." I'll use a professional, engineering/PM tone.
- Title: Executive Summary.
- Phase 1: Markup & AMP Strategy: The transition from AMP/proprietary markup to standard web standards (CWV + Schema).
- Phase 2: Live-Blog Specifics: The schema and update frequency rules.
- Phase 3: Temporal Integrity: Timestamp logic.
- Phase 4: Performance Engineering: Latency SLOs.
- Timeline/Rollout: A brief schedule.
Refining the Content:
- AMP Retirement: Focus on "feature parity." If we remove AMP, does the carousel card look the same? (Images, headlines). We need to ensure structured data (
NewsArticle) is perfect. - Live Blogging: Emphasize the "End Time." If a live blog is over, mark it as finished immediately to stop wasting crawler resources.
- Timestamps: Mention "Server Time" vs "User Time." The Sitemap
<lastmod>must match the page header. - Latency: Define "Crawlability." The server must handle high QPS (Queries Per Second) during breaking news events without timing out.
Let's generate the response following this logic. I'll present it as a formal internal policy draft. Here is a drafted strategic plan for News Carousel Eligibility Hardening.
This document outlines the technical and policy requirements to transition from legacy formats (like AMP) to a high-performance Core Web Vitals (CWV) regime, enforce strict temporal accuracy, and ensure platform reliability.
Strategic Plan: News Carousel Eligibility Hardening
Objective: To redefine the quality bar for Top Stories and News Carousels by deprecating legacy AMP preferential treatment, enforcing strict structured data hygiene for live content, and establishing strict latency Service Level Objectives (SLOs).
Status: Draft Target Rollout: Q3 2024
1. AMP & Legacy Markup Retirement Plan
As the ecosystem moves toward Core Web Vitals as the primary ranking signal for performance, the reliance on AMP (Accelerated Mobile Pages) as a "fast-pass" into the Top Stories carousel is being deprecated in favor of page experience signals for standard HTML.
Key Actions
- AMP Preference Removal:
- AMP pages will no longer receive inherent ranking boosts for "swipeable" carousel visibility.
- Publishers utilizing canonical URLs with optimized Core Web Vitals (LCP < 2.5s, INP < 200ms, CLS < 0.1) will be granted equal eligibility.
- "Eligible" Markup Simplification:
- The distinct
eligiblestructured data property (often used to denote paywall or subscription status in legacy systems) is being unified. - Publishers must migrate to
isAccessibleForFree(Boolean) andhasPart(for paywalled content) withinNewsArticleschema. - Deprecation Warning: Legacy
<meta name="robots" content="snippet">logic for paywall control will be ignored; schema must drive access control signals.
- The distinct
Migration Path
- Phase 1 (Audit): Identify all domains still serving AMP versions exclusively for carousel traffic.
- Phase 2 (Parity): Canonical pages must match AMP performance. "Placeholder" canonicals that redirect to AMP are now flagged as soft 404s.
- Phase 3 (Retirement): AMP cache serving for News Carousel is discontinued. All traffic routes to the canonical origin.
2. Live-Blog Signals Hardening
To reduce clutter and ensure users see active coverage rather than abandoned posts, "Live" status will be strictly gated by active schema signals.
Schema Requirements
LiveBlogPostingEnforcement:- A page is only eligible for the "LIVE" badge if it utilizes the
LiveBlogPostingschema type. - Hard Requirement: The
coverageStartTimemust be defined.
- A page is only eligible for the "LIVE" badge if it utilizes the
- Update Frequency:
- To maintain the "LIVE" UI treatment, the
dateModifiedtimestamp (in the JSON-LD body) must update at least once every 20 minutes during the event. - Failure to update schema timestamps results in a fallback to standard
NewsArticletreatment (losing the live badge and real-time priority).
- To maintain the "LIVE" UI treatment, the
Lifecycle Management
- Automatic Expiration: The "Live" badge is automatically revoked 2 hours after
coverageEndTime. - Zombie Detection: Systems will crawl for new content blocks (
<article>or microdata updates). If the DOM content is static for >45 minutes despite schema claiming "live," the signal is disregarded.
3. Timestamp Rules & Temporal Integrity
Timestamp manipulation (backdating or future-dating articles to game recency rankings) is a primary target of this hardening effort.
The "Three-Timestamp" Rule
To be eligible for "Breaking" or "Latest News" slots, articles must expose three consistent time references:
- Structured Data:
datePublishedanddateModifiedin ISO 8601 format. - Visible UI: A human-readable date/time string visible above the fold.
- Sitemap:
<lastmod>in the XML News Sitemap.
Logic & Penalties
- Drift Detection: If
dateModified(Schema) differs fromlastmod(Sitemap) by more than 5 minutes, the recency signal is dampened (treated as "stale"). - Future-Dating: Any article timestamped more than 1 hour ahead of the crawler's server time is flagged as spam and de-indexed from the carousel.
- The "Repackaging" Rule: Changing the
dateModifiedvalue without a significant content change (measured by DOM shingle analysis) triggers a "artificial freshness" penalty.
4. Latency SLOs (Service Level Objectives)
Eligibility is no longer just about content quality; it is about infrastructure reliability. High latency during breaking news events results in user drop-off; therefore, slow origins are disqualified from the "Live" carousel.
Network & Rendering Thresholds
- Time to First Byte (TTFB): Origin servers must maintain a TTFB of < 200ms (p95).
- Hard Limit: Origins consistently exceeding 600ms TTFB will lose carousel eligibility.
- Core Web Vitals (CWV) Pass Rate:
- URLs must pass CWV assessments on 75% of field data (CrUX) loads.
- Real-Time Check: During the crawling phase for a Breaking News event, if the initial HTML response times out (>2s), the URL is skipped in favor of the next fastest source.
- Payload Budget:
- Critical path HTML should not exceed 50KB (gzipped).
- Ad script execution must not block main thread for >50ms (INP impact).
Summary of Impact
Metric Warning Zone Ineligible Threshold LCP (Largest Contentful Paint) > 2.0s > 4.0s TTFB (Server Response) > 400ms > 800ms CLS (Layout Shift) > 0.15 > 0.25 Update Latency (Live Blogs) > 20 min gap > 45 min gap
Implementation Checklist for Publishers
- Audit Schema: Ensure all live blogs use
LiveBlogPostingand update JSON-LD dynamically. - Sync Clocks: Verify server time synchronization (NTP) to prevent timestamp drift penalties.
- Edge Caching: Implement Edge Side Includes (ESI) or CDN caching for article headers to meet the 200ms TTFB SLO.
- Deprecate AMP: Ensure canonical pages are responsive and pass CWV thresholds before the switchover date.