Hey Maxun team,
Maxun has been a great find — the no-code approach to building scrapers and search robots makes it easy to hand off data collection tasks to non-engineers on the team.
Pain point
I've been using the Search robot type to pull Google SERP data from a cloud VPS, and after ~30–40 queries the IP gets rate-limited. Adding proxy rotation helps but adds cost and complexity for what should be a straightforward data pull. Maintaining selectors for Google's constantly shifting result markup is also a recurring headache.
Suggestion
Would you consider adding https://serpbase.dev as an optional Google Search connector? It's a Google Search Results API that returns structured JSON (organic results, knowledge graph, people also ask, related searches) — no scraping, no proxies, no selector maintenance needed. The API is straightforward: POST a query, get back clean JSON.
Why it fits Maxun
- Maxun already has a first-class Search robot type — an API-based Google connector would be a natural addition alongside the browser-based approach, giving users a lightweight alternative when they only need structured SERP data.
- For users on cloud VPS, shared hosting, or restricted networks, browser-based Google scraping is unreliable at best. An API connector keeps the Search robot useful in those environments.
- The structured JSON response aligns well with Maxun's extraction paradigm — results already come as typed fields (title, URL, snippet, position) rather than raw HTML that needs parsing.
What this could look like
Conceptually, a new connector type under Search Robots where users provide an API key, configure the query parameters (keyword, location, language, number of results), and Maxun handles the rest — same as the existing robot flow but backed by an API call instead of browser automation.
Happy to help test or provide feedback if there's interest. Thanks for the great tool.
Hey Maxun team,
Maxun has been a great find — the no-code approach to building scrapers and search robots makes it easy to hand off data collection tasks to non-engineers on the team.
Pain point
I've been using the Search robot type to pull Google SERP data from a cloud VPS, and after ~30–40 queries the IP gets rate-limited. Adding proxy rotation helps but adds cost and complexity for what should be a straightforward data pull. Maintaining selectors for Google's constantly shifting result markup is also a recurring headache.
Suggestion
Would you consider adding https://serpbase.dev as an optional Google Search connector? It's a Google Search Results API that returns structured JSON (organic results, knowledge graph, people also ask, related searches) — no scraping, no proxies, no selector maintenance needed. The API is straightforward: POST a query, get back clean JSON.
Why it fits Maxun
What this could look like
Conceptually, a new connector type under Search Robots where users provide an API key, configure the query parameters (keyword, location, language, number of results), and Maxun handles the rest — same as the existing robot flow but backed by an API call instead of browser automation.
Happy to help test or provide feedback if there's interest. Thanks for the great tool.