Pages that refuse AISA's reader are now read through Linkup

A page that ended Failed because your site answered AISA's reader with a 403, a 429, a bot-check page or an empty page may now be read.

When AISA's own request is refused that way, it asks Linkup to fetch the same page, in its standard mode first and then once in its pro mode. AISA reads the HTML Linkup returns with the same code as a direct read, so the type, text and content come out the same. It happens only after a refusal, never first, and never for a 404, a redirect to another site, a timeout or a page that is too large. JavaScript is not run.

Only the public address of the page is sent to Linkup. No page text, no conversation, nothing about your account. The address is checked first: it must be on your site, use https and not point to a private network.

This is on for every site and you do not switch it on. The request to your server comes from Linkup, so it does not use AISA's own User-Agent and an allow rule on that User-Agent does not cover it. A sitemap import has no such fallback.

Linkup was already a sub-processor for web search and page fetch during a conversation, which you enable per agent. The sub-processor list now names this second use. We have signed no data processing agreement with Linkup, and no processing region is pinned.