Deep competitor crawl and domain caching
Last updated 2026-06-14
Definition
A deep competitor crawl reads a rival’s pages in depth — not just the homepage — to learn how they sell. Quri caches each domain it crawls, so the next audit that touches the same competitor reuses the saved read instead of fetching it again. That keeps audits fast and cheap.
How to do this in Quri
- Start an audit at /app/audit and let Quri discover or accept competitors.
- Quri deep-crawls each rival’s key pages to map their offer and tactics.
- For a domain it already crawled, Quri serves the cached read instead of re-fetching.
- Open a competitor to see the crawled evidence behind every finding.
Frequently asked
- Why cache the crawl instead of refetching?
- Refetching the same public pages for every audit is slow and wasteful. Caching a domain’s read lets Quri reuse it, so your audit returns faster and costs less to run.
- How fresh is a cached crawl?
- Caches cover public pages that change slowly. When a domain’s read is stale, Quri recrawls it, so you are comparing against a current picture rather than an old one.