Behavior
The default engine radio is "Google + Bing 对比" which fires two engine.submit calls — one engine=google, one engine=bing. Each is a full SerpAPI search, so one Submit costs 2 credits against the shared monthly quota.
Why it's designed this way
Side-by-side comparison is the headline feature of the compare mode; either engine alone only tells half the story. Making it implicit (1 Submit = 1 SerpAPI call) would break the comparison.
If you are credit-constrained
- Switch the engine radio to
Google for single-engine submits (1 credit each).
- Check the quota progress bar at the top of the page before each submit.
- Tick
忽略缓存 only when you genuinely need fresh data — cached 24h hits cost 0 credits.
References
app.py:571-580 — compare-mode dispatch fires two submits.seoserper/config.py — SERP_CACHE_TTL_SECONDS = 86400.
Behavior
The default engine radio is "Google + Bing 对比" which fires two
engine.submitcalls — oneengine=google, oneengine=bing. Each is a full SerpAPI search, so one Submit costs 2 credits against the shared monthly quota.Why it's designed this way
Side-by-side comparison is the headline feature of the compare mode; either engine alone only tells half the story. Making it implicit (1 Submit = 1 SerpAPI call) would break the comparison.
If you are credit-constrained
Googlefor single-engine submits (1 credit each).忽略缓存only when you genuinely need fresh data — cached 24h hits cost 0 credits.References
app.py:571-580— compare-mode dispatch fires two submits.seoserper/config.py—SERP_CACHE_TTL_SECONDS = 86400.