Startpage — proxied Google results, no own crawler
Startpage is a privacy-focused search engine based in the Netherlands that returns results sourced from a partner index (historically Google) rather than operating its own large-scale web crawler. As a result, you generally do not see a Startpage indexing bot in your logs; your visibility there depends on the upstream index.
What this means
Startpage is a privacy-focused search engine that lets users search a major index (historically Google) without being tracked, acting largely as a privacy proxy in front of that index. Because it sources results from a partner rather than building its own large-scale index, it does not run a broad indexing crawler the way Google or Bing do.
The practical consequence for operators is that Startpage visibility follows the upstream index: if your pages are indexed by the partner search engine, they can appear in Startpage results, regardless of any Startpage-specific crawl.
Why you rarely see a Startpage bot
Since Startpage does not maintain its own web-scale index, there is generally no Startpage indexing crawler hitting your pages. You optimise for Startpage by optimising for its upstream partner index, not by catering to a separate Startpage bot.
This entry is marked partially verified because the exact partner arrangement and any limited Startpage-operated requests can change over time; confirm current details in Startpage's documentation before assuming behaviour.
- Startpage proxies results from a partner index (historically Google)
- No broad Startpage indexing crawler is expected in logs
- Visibility follows the upstream index, not a Startpage-specific bot
robots.txt considerations
Because Startpage relies on a partner index, controlling your appearance in Startpage means controlling your appearance in that upstream engine (for example via Googlebot rules), not a Startpage token. There is generally no Startpage crawler token to target.
If you ever see a Startpage-identified request, treat it as a bot event and verify against Startpage documentation. robots.txt is a request honoured by compliant clients, not an access-control mechanism.
How it appears in analytics and logs
Because Startpage proxies results from a partner index, an absence of a Startpage crawler in your logs is expected. Any Startpage-related fetch is more likely a proxied or feature request than a full indexing crawl, so it should not be treated as independent search indexing.
Diagnostic use case
Understand why a Startpage crawler rarely appears in logs, and recognise that Startpage visibility is governed by its upstream partner index rather than a Startpage-specific bot.
What WebmasterID can help detect
WebmasterID classifies any Startpage-identified request server-side as a search-related bot and surfaces it on the bot-intelligence surface, separate from human analytics, while making clear that Startpage relies on an upstream index rather than its own crawl.
Common mistakes
- Looking for a Startpage indexing crawler in logs when Startpage proxies a partner index.
- Assuming a robots.txt Startpage token controls Startpage visibility — the upstream index does.
- Confusing Startpage's privacy-proxy role with running an independent crawler.
Privacy and accuracy notes
Startpage positions itself on not tracking users; from an operator's view, any Startpage request is detected only by its user-agent and carries no human identity. WebmasterID records such a request as a bot event, separate from human analytics.
Related pages
- Qwant search crawler — Qwantify
Qwant is a privacy-focused search engine based in France that operates its own crawler to index the web for European search results. Its crawler self-identifies with a Qwant token (historically Qwantify). It is a genuine search-engine indexer, so allowing it can help your pages appear in Qwant results.
- Googlebot Desktop — Google's secondary crawler
Googlebot Desktop is the desktop user-agent variant of Googlebot. Under mobile-first indexing it is secondary to Googlebot Smartphone for most sites. It shares the Googlebot robots.txt token and is verified the same way: reverse DNS into googlebot.com or google.com, or matching Google's published crawler IP ranges.
- Regional search engines overview
In several markets a regional search engine leads instead of Google: Yandex in Russian-language search, Baidu in China, Naver in South Korea, Seznam in the Czech Republic, and Coc Coc in Vietnam. Recognising their crawlers matters because being indexed by them is how you reach those audiences.
- Web crawlers overview
How WebmasterID distinguishes proxy search engines from indexing crawlers.
Sources and verification notes
- Startpage — about / privacy searchStartpage returns results from a partner index rather than its own web-scale crawl; confirm current arrangement.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.