Turn public web pages into clean text, article text, or Markdown for LLM prompts, RAG inputs, content review, and exports. Add URLs, choose the text shape, and get page text with metadata, headings, links, counts, redirects, and timestamps.
No reviews yetBe the first to leave a review for Webpage Text Extractor
Maker
📌
Hi Product Hunt,
I built Webpage Text Extractor as part of my Apify actor portfolio.
It takes public HTML pages and returns clean text, article text, or Markdown, plus useful page details like title, metadata, headings, links, word counts, final URL, and scrape time.
It is useful for LLM prompts, RAG inputs, content review, and simple spreadsheet exports when you do not want to copy page text by hand.
If you try it, please let me know what you think 🫡
Report
How does the extractor handle pages behind paywalls or ones that require JS rendering to show the actual content?
Report
How does it handle pages that are heavily JavaScript-rendered or gated behind a login, and is there an API I can hit so I can pipe results straight into my own scripts?
Report
How does it handle pages that block scraping or require login, and does it respect robots.txt under the hood?
Report
how does it handle pages that block scrapers or require login, is there a way to pass cookies or proxy through when a site throws a 403?
Report
Tried it on a couple of long reads and the Markdown output came back really clean, links and headings preserved nicely. The redirect flag was a nice touch, saved me from chasing broken sources.
Report
Pasted in a few long articles and the Markdown output kept headings and links intact, which saved me a bunch of cleanup before feeding it into a prompt. The redirect and timestamp metadata was a nice touch I didn't expect.
How does the extractor handle pages behind paywalls or ones that require JS rendering to show the actual content?
How does it handle pages that are heavily JavaScript-rendered or gated behind a login, and is there an API I can hit so I can pipe results straight into my own scripts?
How does it handle pages that block scraping or require login, and does it respect robots.txt under the hood?
how does it handle pages that block scrapers or require login, is there a way to pass cookies or proxy through when a site throws a 403?
Tried it on a couple of long reads and the Markdown output came back really clean, links and headings preserved nicely. The redirect flag was a nice touch, saved me from chasing broken sources.
Pasted in a few long articles and the Markdown output kept headings and links intact, which saved me a bunch of cleanup before feeding it into a prompt. The redirect and timestamp metadata was a nice touch I didn't expect.