For product and pricing teams
Read a competitor's plan names and prices as numbers
Read a competitor's plan names and prices off the rendered page as values, and keep the history yourself.
The problem
A competitor drops a tier, renames another and raises its entry price. A text comparison of their pricing page says that something changed somewhere in a long block of copy; what the pricing team needs is the table: which plan, from what, to what.
How domscout handles it
Two extract fields read the plan names as a list and the prices with type number and all: true, which drops currency symbols and thousands separators before parsing. Run the request on your schedule and store each result, and comparing two rows of numbers tells you exactly what moved. Prices that appear only after JavaScript runs are there to read because the page is rendered, and a click action can flip a monthly and annual toggle first.
Where it shows up
- A weekly table of every competitor's plans and prices.
- An alert when an entry-level price moves.
- Price history for a pricing review.
The request
POST /scrape. extract starts at Pro and costs 2 credits a page. A monitor can watch the same page and alert on any change to its text, but monitors compare text, links and title rather than extracted values, so the price comparison stays in your code.
Go further
More in Monitoring and alerts: Website change monitoring · A feed for a site without RSS · Minimum advertised price checks · New job posting alerts · Vendor changelog watching · Tender, grant and notice alerts · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.