Skip to main content
Illustrative broadcast camera and editing desk with a world map and video timeline
All use cases

NEWS MONITORING / SOURCE-LED RESEARCH

CNN news
data.

Follow the story.
Not just the headline.

Story links, video metadata and observed changes, structured for a clearer view of the coverage that matters to you.

FROM THE NEWS PAGE TO YOUR WORKFLOW

Track your topics.
Keep the evidence.

Build a defined view of CNN coverage around your companies, markets or research questions. Keep every observation connected to its source.

Monitor relevant coverage

Bring selected story links and source context into your research or alerting system, with a refresh schedule agreed for the project.

Compare coverage formats

Understand how a topic appears across written stories, video and live coverage without treating them as identical records.

Follow observed changes

Track headline and metadata changes against the same story. Keep edits, new observations and collection failures distinct.

A DATA MODEL THAT KEEPS THE CONTEXT

Stories, video
and what changed.

Different records answer different questions. Define the fields you need before collecting more pages or adding analysis.

The story, with its source.

Connect a headline to its own URL, content type and discovery page. Enrich only the fields your research actually needs.

url / headline / source_kind
Article identity and the publisher's content type.
source_section / source_page
Where the story belongs and where it was discovered.
published_at / updated_at / observed_at
Three different clocks. Missing source dates stay null.
text_scope / media_reference
State what was collected; keep media attached to the right story.
story.json

Illustrative schema / not a collected CNN result

{
  "example_only": true,
  "record_type": "story",
  "source": "CNN",
  "url": null,
  "headline": "Regional rail network announces autumn service changes",
  "source_kind": "article",
  "source_section": "travel",
  "source_page": null,
  "published_at": null,
  "updated_at": null,
  "observed_at": null,
  "text_scope": "listing_metadata",
  "full_text_included": false,
  "media_reference": {
    "url": null,
    "credit": null
  }
}

Fictional records and values. No live data request.

Fictional headline and values. A listing is not the full article; author, dates and article text require separately validated sources.

Illustrative delivery schemas, not collected CNN records or a built-in API response. Field availability, source access and intended use are confirmed during scoping.

NEWS DATA HAS MORE THAN ONE CLOCK

Published. Updated.
Observed.

A fresh collection timestamp does not make an old story new. Keep source dates and your collection timeline separate.

01 / PUBLISHED

When the source says it began

Use an explicit source timestamp when available. A date in the URL is not an exact publication time.

02 / UPDATED

When the source reports an edit

Preserve the publisher's update time separately. If it is missing, leave it unknown.

03 / OBSERVED

When the collection saw it

Record the snapshot time and source page. This is your evidence window, not the article's age.

COLLECT THE SIGNAL, NOT EVERY PAGE

Discover once.
Enrich what matters.

A useful news pipeline starts with source selection and freshness checks. Browser rendering and AI are not automatic requirements.

  1. 01 / DISCOVER

    Choose a defined source set

    Agree editions, sections, content types and collection cadence. A homepage is a changing selection, not a full archive.

  2. 02 / EXTRACT

    Parse and match records

    Read available listing metadata, deduplicate URLs and keep each image reference with its own story. Enrich approved missing fields separately.

  3. 03 / MAINTAIN

    Watch freshness and changes

    Validate source dates, preserve snapshot history and flag collection gaps. Do not turn a failed request into a false deletion or a quiet news day.

PUBLIC LISTING METADATA

Start with the HTML

When permitted, parse existing page markup before adding a browser or AI. Homepage metadata does not establish access to the full article, and legacy feeds need a freshness check.

Raw HTML collection reference
FULL CONTENT & REUSE

Review publisher access

Full-text, archive and republication requirements need their own access and rights review. CNN documents content licensing and a Newsource syndication service.

CNN content licensing

The collection route is validated for your scope, not assumed from a sample. Public visibility does not grant reuse rights. No login, subscription or paywall bypass is included.

ONE REQUEST OR A MAINTAINED NEWS DATASET?

Choose who runs
the collection workflow.

Use the API for your own page requests. Choose managed delivery when you need source selection, matching, refresh monitoring and a maintained schema.

YOU CONTROL THE PAGE REQUESTS

Scraping API

Collect accessible public pages across permitted sources, with optional analysis or classification.

  • Content-only mode without AI processing
  • Your URLs, parsing and result handling
  • No CAPTCHA, login or paywall bypass
Explore the API
WE SCOPE AND MAINTAIN DELIVERY

Managed CNN data

A news metadata workflow built around your topics, refresh needs and permitted downstream use.

  • Source coverage and sample validation
  • Deduplication and observed change history
  • Scheduled JSON, CSV or agreed API delivery
Discuss your news dataset

BEFORE YOU BUILD ON THE DATA

Coverage, freshness
and content rights.

Does a homepage result include the full article?

No. Headlines, links, section labels and selected media references can be listing metadata only. Bylines, publication times, article text and live-blog entries require separately validated sources. We do not infer an exact publication timestamp from a URL, or describe a headline-only collection as full-text analysis.

Can you monitor breaking news in real time?

We agree a collection cadence and coverage window, not an unsupported instant-delivery promise. Homepage selections change and may vary by edition. Monitor successful observations, source freshness and failures separately. A response with HTTP status 200 can still contain stale data, and one page cannot establish complete CNN coverage.

How do you handle duplicates, edits and corrections?

Match records using validated source identifiers or normalized URLs, retaining the original URL and discovery context. Preserve observed changes when version tracking is in scope. An edited headline is not automatically a publisher correction, and an item leaving the homepage is not evidence of deletion.

Are videos and live blogs collected as normal articles?

No. Written stories, video pages and live coverage keep separate types. A live-blog link does not contain every update, and a live video channel may not have a fixed runtime. Video downloads, transcripts and individual live-blog entries need a separately agreed access and field scope.

Do we need a browser or an AI call for every story?

Not when the required metadata is already in permitted HTML or a suitable structured source. Parse the listing first, deduplicate it and enrich only missing fields. Rendering and optional AI are separate steps. A single successful HTML test is not a guarantee for every page, region or future request.

Can we republish the text, images or video?

Data collection does not grant republication rights. Public links, media references and access to a page are not a licence for downstream use. CNN offers content licensing and syndication routes. We review the requested fields and intended use before proposing delivery; no login, subscription or paywall bypass is included.

Can you add topic labels or sentiment analysis?

Where the intended processing is permitted, analysis can be added separately with source references and a defined input scope. Publisher sections, publisher labels and derived AI labels remain distinct. A headline-only classification is not an analysis of the full story, and an analysis article is not automatically an AI-generated result.

START WITH YOUR NEWS RESEARCH BRIEF

Which coverage
matters to you?

Share the topics, sections and fields your workflow needs. We will review access, freshness and a sample scope before proposing delivery.

  • Topics, sections and example URLs
  • Fields, date range and refresh schedule
  • Delivery format and intended use
Discuss your project

Up to 5,000 characters.

Projects are accepted individually, subject to feasibility and available capacity. An enquiry does not reserve a solution or confirm delivery. Pricing and terms are agreed directly with our team.

We review your brief first. This form does not run a scrape or create a paid task.

ScrapingBuddy is not affiliated with CNN. The news-production image and dataset examples are illustrative, not CNN premises, footage or actual news records. Collection, analysis and delivery depend on appropriate access and agreed usage rights.