← ClaudeAtlas

seo-news-discoverlisted

Use when auditing or planning publisher visibility for Google News, Discover, news search, or comparable freshness-sensitive surfaces across editorial policy, article pages, dates/bylines, corrections, large images, NewsArticle markup, news sitemaps, feeds, paywalls, and first-party reports; require current policy evidence and never promise inclusion, Top stories, Discover traffic, subscriptions, or revenue.
oegeyilmaz9/seo-aeo-geo-ultimate · ★ 2 · AI & Automation · score 66
Install: claude install-skill oegeyilmaz9/seo-aeo-geo-ultimate
# News and Discover SEO Audit the publisher system behind freshness-sensitive discovery: editorial transparency, article pages, dates and corrections, media, structured data, sitemaps/feeds, access state, and reporting. Read [news-discover-protocol.md](references/news-discover-protocol.md) before a formal audit. ## Procedure 1. Define publications, editions/locales, article types, paywall/access model, newsroom owners, publishing cadence, and target surfaces. 2. Capture representative article/listing pages, raw/rendered metadata, bylines, dates, corrections, publisher/contact/about evidence, images, structured data, sitemap/feed rows, canonicals, and access directives. 3. Reconcile visible headline, author, publication/modification dates, section, image, publisher, paywall state, and NewsArticle/Article data. Preserve correction history rather than silently rewriting time-sensitive facts. 4. Inspect news sitemap membership and freshness, article retirement/update rules, crawl/index state, large-image delivery, responsive page experience, internal discovery, and feed parity. 5. Apply current platform content and spam policies to sensational, misleading, scraped, scaled, synthetic, or thin publication patterns. AI-assisted content still requires accuracy, quality, relevance, and accountable editorial review. 6. Use first-party News/Discover/Search performance exports when supplied. Discover is not a stable keyword-ranking surface; keep its reporting separate from query-base