Contents
- Domma CMS User Manual
- 1. Using the CMS
- 2. Tutorials
- 3. Components
- 4. API Reference
- 5. Tools
- Tools
- Analytics Pro
- Backup Pro
- Blog
- Blog Pro
- Booking
- Booking Pro
- Calendar
- Campaigns Pro
- Cards
- Card credits
- Contacts Pro
- Crossword
- Daily Word
- Dashboard Pro
- Data Transfer
- Docs
- Docs Pro
- Email Pro
- Feedback
- Garage
- Invoices
- Job Board
- Mail Reader
- Messages
- MongoDB Adapter
- Onboard Pro
- Quiz
- Scraper
- Scraper Pro
- Security
- Security Pro
- SEO Pro
- Sheets
- Shopping Cart
- Shopping Cart Pro
- Social Media Pro
- Support
- Surveys
- Theme Roller
- Waypoint Pro
- Word Search
Scraper Pro
Updated by Darryl Waterhouse on 27 October 2026 · 1 min read
Scraper Pro adds two things to the Scraper.
Pages as a browser shows them
Some sites send an almost empty page and build their content with JavaScript once it loads. The Scraper reads pages as they are sent, so on those sites it finds nothing. With Scraper Pro, choose As a browser shows it (Pro) beside the address in the picker: the page is opened in a browser on the server, its scripts run, and the Scraper reads what they built. Recipes made this way run the same way.
- It is slower than reading a page as sent - a few seconds a page - so use it only for the sites that need it.
- The browser runs on the server that hosts your site, never in your own browser, and it can only reach public websites.
- If the picker says rendering is not set up on this server, ask your host.
Keeping rows in MongoDB
If your site has a MongoDB connection (System > Connections), a recipe's menu on the Scraper screen offers Where the rows are kept…: files on the site (the usual) or one of your connections. The rows already collected move with their ids, and later runs write to the new place. You can move them back the same way.