How to monitor a competitor website for changes without reading it yourself
Pick the three or four pages of a rival's site that carry real decisions, let an AI employee read them each morning, and hear only about prices, menus and branches that moved.
Part of the guide AI employees
To monitor a competitor website for changes, do not watch the whole site. Choose the few pages where the rival writes down its decisions (the price list, the menu or range, the list of branches, the careers page), have each one read on a timetable, and ask for a message only when the words on it differ from the last reading in a way you care about. An AI employee does exactly that: it reads the pages, compares them with what it remembered, and tells you in a sentence what moved.
This guide is for owners, pricing managers, category buyers and marketing leads who open a rival's site every so often and wonder whether anything is different. It covers which pages are worth the effort, how to word what matters, a worked example, what a page reader cannot see, and the blocks that make up the employee.
Which pages of a rival's site are worth watching
A home page changes weekly and says little. The pages below change rarely, and each change is a decision somebody at the other company took.
| Page | What a change tells you | How to watch it |
|---|---|---|
| Pricing or rate card | A price rise, a new tier, a dropped discount | Any change on the page |
| Menu, range or service list | A new product line, something withdrawn | Any change on the page |
| Store or branch list | A branch added or removed | New entries in a list |
| Careers page | Which teams and cities they are growing | New entries in a list |
| Delivery, returns or opening hours | A change in the promise to customers | Any change on the page |
The two ways of watching are settings of the Web page watch block.
The Web page watch block takes up to ten addresses and reads each once a run. Set to Any change on the page, it compares the page's text with its last look and passes on the lines added and removed. Set to New entries in a list, xMap AI reads the page as a list and passes on only entries it has not seen, each with the fields you ask for, such as the city of a new branch.
Say what matters, in your own words
A reader that reports every difference is switched off within a fortnight, because pages are full of small movements: the year in the footer, a banner that rotates, a counter of items in stock. Two settings deal with that. Say what changed has xMap AI write one or two plain sentences about each change, in English whatever language the page is in, and it leaves out changes that are only dates, counters, adverts or cookie notices. What matters is a line you write, and a change that is not about it is left out.
The wording of that line decides how useful the employee is. Compare these.
- Too wide: "anything interesting". Everything is interesting to a model with no brief.
- Too narrow: "the price of the 12-month plan". A new 24-month plan would be missed.
- About right: "prices, plan names, what each plan includes, and minimum contract length".
A worked example with made-up numbers
Take an invented case: a group of four climbing gyms in Denver with three rivals in the city. The marketing lead used to open the rivals' sites on the first of the month, which meant a price change could sit unnoticed for four weeks.
- A Schedule starts the flow every weekday at 06:45.
- A first Web page watch block holds the three membership pages and the three opening-hours pages, on Any change, with What matters set to "membership prices, day pass prices, joining fees, student rates and opening hours".
- A second Web page watch block holds each rival's locations page, on New entries in a list, with What the entries are set to "gym locations" and the city read for each.
- An xMap LLM block reads each change and adds one line: what the group might do about it.
- A Slack message goes to the marketing channel, and an Email to the owner.
In this made-up month, 21 of 22 mornings bring nothing. On one morning the message reads: one rival's day pass went from 24 to 27, and the student rate line was removed. The same rival's locations page gained an entry in a suburb where the group has a gym. Both arrive before the gyms open, with a link to each page.
What a page reader cannot see
It is better to know the limits before you depend on the silence.
- Pages built in the browser. Some sites send an almost empty page and fill it with scripts afterwards, which is common for store finders and live menus. Such a page shows little text to read, so there is nothing to compare, and the step says so. Look for a plainer page that holds the same facts, such as a printable price list or a simple list of branches.
- Pages behind a sign-in. Only public pages are read. A trade price list for account holders is out of reach.
- Pages that ask not to be read. The block obeys each site's robots.txt, the file where a site says which pages robots may read. A page it forbids is left out and named in the step. Watch only pages whose terms allow it.
- Prices inside pictures or PDFs. The block reads the words of the page. A menu posted as a photograph has no words to compare.
- The first reading. The first real run only remembers. Changes come from the second run on, and a test run never moves what was remembered.
- Renamed list entries. In list mode an entry is known by its title, so a branch the site renames comes through again as new.
The AI employee, block by block
In xMap Flows the whole job is one flow with a role, a timetable and a place to report, which is what the AI employees guide means by an employee. The quickest start is to describe it to Ask xMap in a sentence and paste the addresses; it builds the flow and tests it without sending anything.
- Schedule: every weekday morning. Rate cards rarely change more than once a day.
- Web page watch: the pages, the way of looking, and what matters.
- xMap LLM (optional): a line of advice, or a score for how much the change matters to you.
- Filter (optional): keep only changes scored as worth a person's time.
- Email, Slack or a row in Google Sheets: where the team will read it. A sheet gives you a dated history of every change.
For rivals whose sites cannot be read, the Browser block opens a page the way a person would and brings back the fields you name, and a ready template uses it to read the best-rated cafes' own sites every Monday. It reads; it does not compare with last time, so add a sheet if you want the history.
What lands in your inbox on a day with news is short: the page, one or two sentences on what changed, the lines added and removed, and a link. On other days, nothing at all.
Questions
How often should a competitor's pages be checked?
Once each working morning is enough for prices, menus and branch lists. Each page is read once a run, so a daily timetable is also the polite one for the site being read.
Can it watch a competitor's whole website?
No, and you would not want it to. One block reads up to ten addresses you choose, and the useful ones are the few pages where decisions are written down: prices, range, branches, hours and jobs.
Why did a page I added show no changes even though the site looks different?
The page may build its content in the browser, hold its prices in images, or be closed to robots by the site's robots.txt. The step says which. The first real run also only remembers, so changes show from the next one.
Does it work for sites in other languages?
Yes. The pages can be in any language, and the summary of what changed is written in English.
Is it allowed to read a rival's public pages?
The block reads only public pages, one request a page a run, and leaves out pages a site's robots.txt closes to robots. You are still responsible for checking that a site's terms allow it.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates