Channel News Asia News Scraper

Fetches Channel News Asia's latest articles from its public Google News syndication feed. Unlike this NEWS family's other actors, this one returns the full article body, not just a short summary.

What you get

One SEARCH_SUMMARY row plus one ARTICLE row per article, most-recent-first:

• articleTitle, articleUrl, articlePublishedAt (clean ISO 8601)
• articleBodyHtml -- the full article body, upstream's own HTML (figures/images included)
• articleBodyText -- the same content with markup stripped, for a plain-text read
• articleLeadImageUrl -- the first image found in the body

Coverage: current feed, not a historical archive

This feed is a rolling snapshot of Channel News Asia's latest ~50 articles. Recon found no working page/offset parameter (?page=2 and ?offset=50 both answered with a byte length within noise of the unparameterized call -- i.e. ignored, not honored), so this actor does not offer one. Run it on a schedule if you want an accumulating archive; articleUrl is a stable id for de-duplicating downstream.

Filtering

keywords is applied client-side, after the fetch (case-insensitive substring match against title + body text, OR-combined). The feed has no server-side search, so this is this actor's own post-filter, documented here so it isn't mistaken for a real query parameter.

No WAF, no auth

The feed answered clean on every TLS profile tested (chrome124, firefox133, safari17_0, chrome99_android), cold, no warmup. robots.txt blanket-disallows /api/* but explicitly carves out Allow: /api/v1/google-news-feed -- this endpoint exists specifically for syndication and is meant to be fetched by exactly this kind of client. See CRAWLING_METHOD.md for the full robots.txt capture and why an earlier recon pass flagged (incorrectly, on a different endpoint) an Incapsula block here.

Known limits

• No per-article category/tag (this feed doesn't carry one; a separate rss-outbound-feed does, but with far less content per item -- see CRAWLING_METHOD.md for why it wasn't used instead).
• Upstream's own <updated> field is a broken, unparseable fragment on every entry (confirmed, not a parsing bug on this actor's side) and is therefore not included; articlePublishedAt uses the clean <published> field instead.