logo
EN

Webpage to Markdown

Turn web pages into clean Markdown for AI and RAG: one row per URL with the main content, title, author, publish date and the page's links split into same-site and external; also works on pages that need JavaScript; pages that cannot be read say why and are not billed. Not affiliated with the websites read

Developer
Pricing
$0.0005 / Page read (main content returned)
Last updated
2026-11-13

Overview

Give it a list of web pages and get back one row per page: the main content as clean Markdown, plus the title, site name, author, publish date and the page's links, already split into same-site and external links.

The first step of almost every AI workflow that touches the web — summarizing an article, answering questions from a docs site, filling a RAG knowledge base — is turning a page into clean text. Raw pages are mostly navigation, ads, footers and cookie banners, which waste context and confuse the model. This app keeps only the main content and converts it to Markdown with headings, lists, tables, links and images intact, so people and models can both read it.

Every URL gets a row with a clear status: read, opened but empty, asked for a human check, refused, disallowed by the site, gone, or not a web page. You never send 10 URLs and get 7 rows back without knowing what happened to the other 3, and pages that could not be read are not charged.

Data notes

  • This app reads public pages at the addresses you give and converts their format; the content belongs to the original websites, so follow their copyright and terms of use. This is not an official product of any of these websites and is not affiliated with them. The fee covers fetching, rendering and conversion, not the content itself.
  • Only the pages you list are read; links on them are not followed, so the number of pages and the cost are known before a run. To go deeper, pick the next pages from "Same-site links" and read them in another run.
  • Pages whose content only appears after JavaScript runs are read too.
  • Sites are treated politely: their robots.txt is respected, and logins, paywalls, CAPTCHAs and interactive checks are never bypassed. Such pages come back with a status instead of content.
  • "Author" and "Published" are only filled when the page marks them explicitly; they are never guessed from the text. Dates are given as year-month-day.
  • Not covered: content behind a login, PDF and other files, and sites that block automated visitors outright (many social networks and large marketplaces). Main content longer than 100,000 characters is cut, and the status details say so.

What the results look like

Each row is one URL.

URLStatusTitlePublishedCharacters
https://www.anthropic.com/news/claude-opus-4-5okIntroducing Claude Opus 4.52025-11-2410342
https://www.allbirds.com/products/mens-tree-runnersokMen's Tree Runner - Jet Black (White Sole)4000
https://stackoverflow.com/questions/231767verification0

Each row also has the Markdown content, site name, author, language, description, same-site links, external links, images, status details and the time it was read.

Use cases

  • Feed an AI: hand "Content (Markdown)" to a model for summaries, Q&A or translation, without menus and ads in the way.
  • Build a knowledge base: store "Content (Markdown)" with "Title", "URL" and "Published" for each page, so answers can cite where they came from.
  • Read a docs site or blog section layer by layer: start with the entry page, choose the next URLs from "Same-site links" by link text or path (for example only addresses under /docs/), and read them in the next run. You decide how deep to go and how many pages each round reads.
  • Clean a URL list: filter on "Status" to find pages that are gone, refuse access or have no content, and fix or drop them; "External links" shows which outside sources each page cites.

Scope and boundaries

Up to 100 URLs per run; only the given pages are read, links on them are not followed. robots.txt is respected; logins, CAPTCHAs and interactive checks are never bypassed. Main content is capped at 100,000 characters per page. Billed per page whose main content was read; pages that could not be read also get a row but are not billed. The fee covers fetching, rendering and conversion, not the content itself

  • Good for
  • You have a list of page URLs and need their main content as clean Markdown for an LLM to read, summarize or answer from, or to load into a RAG knowledge base
  • You need the title, author and publish date of articles or blog posts together with their text
  • You want to read a documentation site or a blog section layer by layer: read the entry page, pick the next URLs from `internal_links` (skipping ones already read), and call again with them; you decide what each round reads, so its cost is known in advance
  • Do not use for
  • You have no URLs and want to find pages by keyword: use a web search app first, then read the URLs it returns here
  • The content is behind a login or a paywall, or the site shows an interactive CAPTCHA: these come back as blocked or verification
  • You need PDF, Word or other files: only web pages are read (they come back as not_html)
  • Social networks and marketplaces that refuse automated access (LinkedIn, Facebook, Reddit, Amazon and similar) usually come back as blocked

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1Every URL gets exactly one row. `status` says what happened: ok, empty_content, verification, blocked, robots_disallowed, not_found, not_html, timeout, dns_error, error; only ok is billed (`billed_pages` = 1)
  2. 2verification, blocked, timeout and error can be retried later
  3. 3robots_disallowed means the site's robots.txt asks crawlers not to fetch that page; it is not read
  4. 4empty_content means the page opened but has no readable main content (a list, login or app page); its title and links are still returned

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • URLsurlsRequiredarray<string>
    Web pages to read, 1–100. Each URL gets one row. Only these pages are read; links on them are not followed. A URL given twice is read once.
    Itemsup to 100 itemsExample["https://www.anthropic.com/news/claude-opus-4-5"]

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • URLinput_urlstring
    The URL as given in the input, to match rows to inputs
    Examplehttps://www.anthropic.com/news/claude-opus-4-5
  • Final URLfinal_urlstring
    The address actually read; differs from the input when the page redirected
    Examplehttps://www.anthropic.com/news/claude-opus-4-5
  • Statusstatusstring
    ok = main content read; empty_content = the page opened but has no readable main content; verification = the site asks for a human check; blocked = the site refused access; robots_disallowed = robots.txt does not allow this page; not_found = the page does not exist; not_html = not a web page (e.g. PDF); timeout = no response in time; dns_error = the domain does not exist; error = could not be opened. Only ok is billed
    Exampleok
  • Status detailsstatus_textstring
    Plain-English explanation of the status, with the reason when the page was not read; also notes when the content was cut at 100,000 characters
    ExampleMain content read

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "input_url": "https://www.anthropic.com/news/claude-opus-4-5",
  "final_url": "https://www.anthropic.com/news/claude-opus-4-5",
  "status": "ok",
  "status_text": "Main content read",
  "billed_pages": 1,
  "title": "Introducing Claude Opus 4.5",
  "site_name": "Anthropic",
  "author": "Anthropic",
  "published_at": "2025-11-24",
  "language": "en",
  "description": "Introducing Claude Opus 4.5",
  "markdown": "Our newest model, Claude Opus 4.5, is available today...",
  "char_count": 10785,
  "internal_links": "<internal_links>",
  "external_links": "<external_links>",
  "images": "<images>",
  "checked_at": "2026-11-12T10:00:00+00:00"
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=MagicData/webpage-to-markdown",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)

detail.access.mcp.composeHint

Pricing

Page read (main content returned)

Metered by summing the output field billed_pages. Failed runs are not charged.

$0.0005/ Page read (main content returned)

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
$0.0005 / Page read (main content returned)