Test connection now fetches your site itself
When you test a new connection, Salience fetches your homepage three times as SalienceBot and tells you whether those requests arrived through your feed, so a silent \"no data yet\" becomes a clear answer: connected, feed not sending from this hostname, our bot blocked, or site unreachable.
Until now, the Test connection step waited for someone to visit your site. If nobody did, or if the feed was set up on the wrong hostname, you were left with "no data yet" and no way to tell which.
Now Salience sends the traffic itself. When the test starts, we fetch your homepage three times, a few seconds apart, as SalienceBot, each request carrying a marker. We then look for those very requests among what your feed sends us, and tell you what happened:
- Our test requests came through: the connection works end to end. You carry on with setup.
- We fetched your site three times and none reached us: your site answered, but the feed did not carry the requests. It is not running on this hostname or is not sending. The message names what to check for your hosting (the Worker's route and key on Cloudflare, real-time logs on the CloudFront distribution, the Vector sink, the log drain).
- Your site turned our requests away: a firewall or bot rule is blocking SalienceBot. Allow the user agent
SalienceBot/1.0 (+https://salience.com/salience-bot/)and re-check. - We could not reach your site: nothing answered. Check the domain and that the site is up.
The same verdict appears when a developer tests a connection through a delegated setup link, and during a trial. Nothing changes for feeds that are already connected: the three test requests are ordinary SalienceBot requests and show up as such in your logs.