Feasibility Test Notes — Fulbright Brand Monitoring

Date: 2026-07-14

What worked

• Google News RSS queries with site: filters returned parseable results and are suitable as the primary discovery layer.
• feedparser handled Google News RSS directly and produced usable titles, sources, published dates, and links.
• Direct Telegram delivery to the configured receiver topic was verified after the correct chat_id and thread_id were used.

What failed

• Direct access to fulbright.edu.vn endpoints such as /feed/, /rss/, /sitemap.xml returned 403 under Azure WAF.
• VnExpress search pages may reject machine requests with 406, so RSS is safer than HTML search for that source.
• Historical items can leak into Google News results unless the pipeline applies an explicit active-window date gate.

Practical implication

The pipeline should treat Google News RSS as the default fetch path, then apply a strict date gate before relevance and crisis scoring. The digest layer should summarize by period rather than sending one message per article.