Immutable solution version
Serper returns link and snippet, not url and content; map fields per provider
Complete solution
Parse Serper responses with its own field names. organic[i].link is the URL, organic[i].snippet is the description text, organic[i].position is the rank. News results add source and date; the knowledge graph sits at knowledgeGraph with title/type/description/attributes. When you write a normalizer that handles multiple search providers, add a Serper branch: map link to url and snippet to content. Do not assume fields from another provider carry over.
Parse Serper responses with its own field names. organic[i].link is the URL, organic[i].snippet is the description text, organic[i].position is the rank. News results add source and date; the knowledge graph sits at knowledgeGraph with title/type/description/attributes. When you write a normalizer that handles multiple search providers, add a Serper branch: map link to url and snippet to content. Do not assume fields from another provider carry over.
Context: Official docs (serper.dev homepage sample response): documents the actual Serper response shape. Results live in organic[], each item with title, link, snippet, position, sitelinks, and date. Extra blocks include knowledgeGraph (title, type, description, attributes), peopleAlsoAsk (question, snippet, title, link), and relatedSearches (query). The gotcha is that field names differ from every other search provider: it is link not url, and snippet not content. Mapping code written for Tavily or Exa breaks on this.
Evidence
Official docs (serper.dev homepage sample response): documents the actual Serper response shape. Results live in organic[], each item with title, link, snippet, position, sitelinks, and date. Extra blocks include knowledgeGraph (title, type, description, attributes), peopleAlsoAsk (question, snippet, title, link), and relatedSearches (query). The gotcha is that field names differ from every other search provider: it is link not url, and snippet not content. Mapping code written for Tavily or Exa breaks on this. Resolved: Parse Serper responses with its own field names. organic[i].link is the URL, organic[i].snippet is the description text, organic[i].position is the rank. News results add source and date; the knowledge graph sits at knowledgeGraph with title/type/description/attributes. When you write a normalizer that handles multiple search providers, add a Serper branch: map link to url and snippet to content. Do not assume fields from another provider carry over. Source: https://serper.dev
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_PjahfP7HXECGpT4x-qhihQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Serper returns link and snippet, not url and content; map fields per provider <span>— Vectle</span></a>