Website to Markdown Crawler for LLM & RAG (fast, no browser) avatar

Website to Markdown Crawler for LLM & RAG (fast, no browser)

Pricing

from $0.60 / 1,000 results

Go to Apify Store
Website to Markdown Crawler for LLM & RAG (fast, no browser)

Website to Markdown Crawler for LLM & RAG (fast, no browser)

Website to Markdown Crawler turns any site into clean Markdown per page for LLMs, RAG pipelines and vector DBs — no headless browser, $1 per 1,000 pages.

Pricing

from $0.60 / 1,000 results

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

18 hours ago

Last modified

Share

What is Website to Markdown Crawler?

Website to Markdown Crawler is an Apify Actor that turns any website into clean, LLM-ready Markdown — one row per page, with navigation, footers, sidebars and cookie banners stripped, headings and code blocks preserved, and every link made absolute. It runs on plain HTTP with Crawlee's CheerioCrawlerno headless browser — which is what makes it fast and roughly 10× cheaper than browser-based content crawlers. Feed it a start URL (or a whole /sitemap.xml) and it does a breadth-first crawl up to your page budget, ready to feed an LLM, a RAG pipeline, LangChain/LlamaIndex loader, or a vector DB (Pinecone, Qdrant, Weaviate, pgvector) in minutes.

Why use Website to Markdown Crawler?

  • Feed an LLM or RAG pipeline in minutes. Point it at your docs site, a competitor's help center, or your own product site and get clean Markdown ready for chunking and embedding — no HTML soup to clean up first.
  • 10× cheaper, no browser. apify/website-content-crawler and similar Actors spin up a browser per page. This Actor fetches raw HTML over HTTP, so it's faster and priced at $1 per 1,000 pages.
  • Predictable cost. maxPages is the billed unit and the crawl stops at exactly that count — no surprise runs.
  • Sitemap-aware BFS crawl. Optionally seeds from /sitemap.xml (including nested sitemap indexes) so you reach real content pages immediately instead of waiting for link discovery.

How to use Website to Markdown Crawler

  1. Paste one or more pages into Start URLs, e.g. https://docs.apify.com/platform or your own docs/blog root.
  2. Set Max pages — this is the billed unit ($1 per 1,000 pages) and the crawl stops exactly there.
  3. Optionally set Include path prefixes (e.g. /docs) to stay inside one section of a larger site.
  4. Choose Output format: Markdown, plain text, or both.
  5. Click Start, then download the dataset as JSON, CSV, Excel or HTML, or pull it straight into your RAG pipeline via the API.

Example input

{
"startUrls": [{ "url": "https://docs.apify.com/platform" }],
"maxPages": 50,
"maxDepth": 3,
"sameDomainOnly": true,
"useSitemap": true,
"outputFormat": "markdown"
}

Example output

{
"url": "https://crawlee.dev/docs",
"finalUrl": "https://crawlee.dev/js/docs/quick-start",
"statusCode": 200,
"title": "Quick Start | Crawlee for JavaScript",
"description": "Crawlee helps you build reliable scrapers. Fast.",
"lang": "en",
"canonical": "https://crawlee.dev/js/docs/quick-start",
"markdown": "# Quick Start\n\nWith this short tutorial you can start scraping with Crawlee in a minute or two...\n\n## Choose your crawler\n\n### CheerioCrawler\n\nThis is a plain HTTP crawler...",
"text": null,
"wordCount": 1484,
"headings": ["Quick Start", "Choose your crawler", "CheerioCrawler", "PuppeteerCrawler"],
"links": ["https://crawlee.dev/js/docs/introduction", "https://crawlee.dev/js/docs/guides"],
"depth": 0,
"contentHash": "3f9a1c2e...",
"crawledAt": "2026-09-12T18:21:07.000Z",
"error": null
}

What data does Website to Markdown Crawler extract?

One row per crawled page:

FieldTypeDescription
url / finalUrlstringRequested URL and URL after redirects
statusCodeintegerHTTP status code, null on a failed request
title / descriptionstringPage <title> (or first <h1>) and meta description
langstring<html lang> attribute
canonicalstring<link rel=canonical>, resolved to an absolute URL
markdownstringMain content as Markdown — headings, lists, code blocks, tables, absolute links/images
textstringMain content as plain text
wordCountintegerWord count of the extracted content
headingsarrayH1-H3 text, in order, up to 50
linksarraySame-domain absolute links found on the page, up to 200
depthintegerLink depth from the nearest start URL
contentHashstringSHA-1 of the plain text — diff two runs to detect changed pages
crawledAtstringISO timestamp
errorstringError message on a failed page, otherwise null

markdown/text are populated according to the Output format input (markdown, text, or both); the unused one is null.

Input parameters

ParameterTypeDefaultDescription
startUrlsarraydocs.apify.com/platformPage(s) to start crawling from
maxPagesinteger50Billed unit; the crawl stops at exactly this count (1-5000)
maxDepthinteger3Link depth from a start URL (0-10)
sameDomainOnlybooleantrueOnly follow links on the same domain (www. counts as the same)
includePathPrefixesarraynoneOnly crawl paths starting with one of these, e.g. /docs
excludePathPatternsarrayimages/PDF/CSS/JS, /login, /signup, ?replytocom=Regexes tested against the full URL; a match is skipped
useSitemapbooleantrueAlso seed from /sitemap.xml (follows one nested sitemap-index level)
outputFormatstringmarkdownmarkdown, text, or both
removeSelectorsarraynoneExtra CSS selectors to strip before extraction
maxConcurrencyinteger10Parallel requests (1-50)
respectRobotsbooleantrueSkip URLs disallowed by robots.txt
proxyConfigurationobjectnoneOptional Apify Proxy configuration

Pricing

Website to Markdown Crawler uses pay-per-event pricing: $1 per 1,000 pages ($0.001 per page), plus a negligible actor-start fee. There is no separate compute-unit or browser billing because no browser is used. Set Max pages (and, on the platform, Maximum cost per run) to cap spend — the Actor trims its own crawl to stay within budget and never bills more pages than it delivers.

Website to Markdown Crawler vs. browser-based content crawlers

Browser-based crawlers such as apify/website-content-crawler load every page in a real (often headless) browser before extracting content — that's necessary for JavaScript-rendered single-page apps, but it's slow and expensive for the huge majority of documentation sites, blogs and marketing pages that are plain server-rendered HTML. This Actor skips the browser entirely: a page that takes a browser-based crawler several seconds and a full render cycle is a sub-second HTTP fetch here, at a fraction of the price. The trade-off is explicit: sites that only render content client-side with JavaScript (pure SPAs) will come back with little or no text — see Limitations below.

Using Website to Markdown Crawler with AI agents, LangChain and LlamaIndex

Website to Markdown Crawler runs on pay-per-event pricing with limited permissions, so it's callable through the Apify MCP server directly from an AI agent — pass startUrls and maxPages and get back one Markdown row per page. The dataset also drops straight into a RAG pipeline: use Apify's LangChain or LlamaIndex ApifyDatasetLoader to turn the dataset into Document objects, then chunk and embed into Pinecone, Qdrant, Weaviate or pgvector. It also connects through n8n, Make and Zapier via Apify's standard integrations.

Limitations

  • JavaScript-rendered single-page apps are the main limitation. This Actor fetches raw HTML over HTTP and never executes page JavaScript, so a site that renders its content entirely client-side (no content in the initial HTML) will come back with an empty or near-empty row. It does follow <meta http-equiv="refresh"> redirect stubs (one hop) and ordinary HTTP redirects, which covers a common class of "empty landing page" issue, but not full client-side rendering. If you hit this, look for a browser-based crawler instead.
  • Interactive widgets that swap content via JavaScript (tabs, accordions with lazy content) are captured in whatever state they render in the raw HTML — usually just the first/default tab.
  • The main-content heuristic (no @mozilla/readability) is tuned for documentation and blog layouts (article, main, #content, .content); unusual layouts may need removeSelectors to clean up.

FAQ

Is this legal? The Actor reads only public HTML. You're responsible for crawling sites you're allowed to and respecting their terms of service.

Why is a row empty? Almost always a JavaScript-rendered page — see Limitations above. Check the statusCode and error fields; a 200 with an empty markdown usually means client-side rendering.

How do I stay inside one section of a site? Set includePathPrefixes, e.g. ["/docs"], and/or turn off useSitemap if the sitemap covers more than you want.

How do I control cost? Set maxPages; the Actor never crawls or bills past it. On the platform, also set Maximum cost per run.

Can I detect changed pages between runs? Yes — compare contentHash (SHA-1 of the extracted text) across runs to see which pages changed.

Does this work with n8n, Make or Zapier? Yes, through Apify's standard integrations, and through LangChain/LlamaIndex document loaders for RAG pipelines.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, runs without proxies or a headless browser, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Found a bug or want a feature? Open an issue on the Issues tab.