An audit tells you where a listing stands today. The monitor keeps reading it — and the competitors you name — once a day on the server, charts the score you save against it over time, and tells you the moment something moves.
The monitor runs on the server, so it needs an account
An audit is a photograph. The monitor is the film: once a listing is on watch, this
server re-reads it once a day whether or not you have the page open, keeps a dated row of
what it found, and tells you what moved — on your listing and on the competitors you
name. That has to live somewhere other than your browser tab.
An email address and nothing else — no password
is asked for, stored or checked anywhere in this product.
01 — What moved
The alert feed
Every change the server has seen since it started watching. A price it cannot read is
reported as unread rather than guessed, and a rounding wobble is never called news.
02 — On watch
Your watched listings
Open a row for its score line, a then-and-now of every fact the server can read, and the
competitors watched alongside it.
How the watching actually works
A background
thread inside server.py re-reads every watched listing on a timer — once
a day by default, set by CHECK_EVERY in accounts.py. It compares
what it reads to the previous reading and records only material movement: a review gained,
a rating shift of a hundredth or more, a photo added or removed, a swapped cover image, a
rewritten title, an amenity list that changed length, a Superhost badge won or lost.
Airbnb stopped
printing the nightly price into the page for signed-out readers, so on most listings the
price row stays empty and says so. Review velocity — reviews gained per week,
measured across the readings — is the honest stand-in, and on a competitor it is a
better signal anyway: it is their booking pace, not their asking price.