BetaPage and PitchWall product cards: titles, URLs and descriptions

Collect product-discovery cards from public BetaPage/PitchWall pages. The saved example starts at https://betapage.co/, which currently redirects to https://pitchwall.co/. The Actor preserves both addresses so an export shows the requested source and the page that actually supplied the records.

Each row now uses the product heading as its title. The small “View” link supplies the product URL; its button label is not the product name. Description text comes from the same card, without the card's buttons, tags or relative-time labels.

BetaPage's redirect is part of the data

The September 11 source read followed BetaPage's ordinary redirect to PitchWall. The output input_url retains https://betapage.co/, while source_url becomes https://pitchwall.co/. Individual product links use PitchWall's /product/<slug> route.

The Gora Academy card in that read has the product title “Gora Academy” and its own language-learning description. An earlier parser returned “View” because that was the text of the product link. The corrected parser reads the nearby title within the same product card, then associates it with the directory link.

Cards can also contain outbound website links. The exported url remains the PitchWall directory record, not an automatically followed external company website. This distinction matters when your destination treats URLs as stable keys or wants an audit trail back to the discovery page.

What this export does not establish

A product's own description may contain performance, pricing or automation claims. The Actor reproduces the short public description; it does not verify those claims. Keep that text attributed to the listing and check the product's own documentation before using it in a comparison.

The export does not infer founding date, revenue, funding or founder identity. It does not convert a visible relative-time label into a verified launch timestamp. Product names may also resemble other company names, so a directory title is not a legal-entity match.

For a product-monitoring workflow, save each discovery snapshot and attach your own observation time. Review changes to title or description separately from changes to placement. A product moving off a limited homepage export is not evidence that it stopped operating.

The parser accepts product record paths on the expected BetaPage/PitchWall hosts. It skips category navigation and unrelated external links. It does not sign in, vote, follow products, submit listings or send messages.

Try the public example

Open the existing three-record Task. It contains the accepted source URL, selected input fields and the overview dataset view. Review the saved input and charge cap before starting a run. The Task is a convenient bounded example; publication does not establish the source's long-term reliability.

{
  "searchUrls": [
    "https://betapage.co/"
  ],
  "maxResults": 3
}

searchUrls is a list of public page URLs. maxResults caps output per input URL, not across the whole run. Two URLs with a limit of three can therefore save up to six records. The Actor deduplicates item URLs within a fetched page, but does not suppress duplicates across separate input pages or remember earlier runs.

Dated output example

This record comes from an ordinary public-page read on September 11, 2026. It illustrates the current parser output; the source can change its ordering or content after that observation.

{
  "source": "betapage-products-scraper",
  "kind": "startups",
  "index": 1,
  "title": "Gora Academy",
  "url": "https://pitchwall.co/product/gora-academy",
  "description": "Learn Russian, Serbian, Croatian, Montenegrin and Bosnian through structured lessons, native audio and clear grammar.",
  "input_url": "https://betapage.co/",
  "source_url": "https://pitchwall.co/"
}

title and url identify the displayed item. description contains that item's short source text when available. source names this Actor, and kind gives its broad record category. index is the one-based extraction order for that page. input_url and source_url preserve redirect provenance.

Structured source objects, when accepted, can additionally expose company and raw. Those optional fields are not guaranteed on every HTML card. The typed Output page documents field shapes; it does not promise that an upstream publisher fills every field.

Billing and export

The existing Free-tier price is $0.0025 per saved record, plus $0.00005 per start event. Paid-plan discounts remain listed in the Pricing tab. Start-event quantity depends on selected memory; use the small saved Task when evaluating a sample. At 512 MB, three result events and one start event equal $0.00755 in Actor fees. Check your account's applicable platform charges separately.

The result limit is a collection cap, not a dollar budget. Set an appropriate maximum total charge in the run options as well. A repeated run can bill for the same records again because this Actor does not maintain cross-run state. Owner verification usage is separate from customer revenue.

Download the default dataset as JSON, JSONL, CSV or Excel through Apify. JSON preserves nulls and optional nested objects more clearly than a flat spreadsheet. Retain the source URLs in either format so a reader can check an ambiguous record.

Failures and recurring use

An unavailable source page now fails the run visibly. If earlier pages produced valid records, those records remain in the dataset and the final error reports the failed-page count. Treat a failed multi-page run as partial data; do not replace a complete prior snapshot with it automatically.

A successfully fetched page with no supported item cards can still produce an empty result. That does not prove an empty directory: the site may have changed layout or delivered a different page. Inspect the log, final source URL and a small source sample before deciding what happened.

To automate collection, save your chosen URLs in an Apify Task, then use a Schedule or the existing Make, Zapier or n8n integration. Custom clients can start /v2/acts/benthepythondev~betapage-products-scraper/runs, wait for the returned run ID to finish and read its default dataset. Store the API token on the server, never in public page code.

Keep collection and notification decisions separate. Save the observation time in your destination and compare records by source URL before alerting. The Actor does not email anyone, create schedules or verify product claims on your behalf.

Compare the separate BetaList startup export when researching directory coverage. Preserve the source name and directory URL before deciding whether two products should be joined.

Use public data within the source's access and reuse rules. For support, include the run ID, a small redacted input and a link showing the expected field. Avoid posting tokens or private account data. If the result was useful, an honest Store review helps other users assess it.