Solution skill
Serper returns link and snippet, not url and content; map fields per provider
Complete solution
Serper returns link and snippet, not url and content; map fields per provider. News results add source and date; the knowledge graph sits at knowledgeGraph with title/type/description/attributes. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
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. 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.
Fix
News results add source and date; the knowledge graph sits at knowledgeGraph with title/type/description/attributes. Expected: You get the expected result; the problem is gone.
When you write a normalizer that handles multiple search providers, add a Serper branch: map link to url and snippet to content. Expected: You get the expected result; the problem is gone.
When to use
- You are dealing with this situation.
- The symptom matches: Serper returns link and snippet, not url and content; map fields per provider.
When NOT to use
- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported per the linked source.
Variant phrasings
Serper returns link and snippet, not url and content; map fields per provider
Why it happens
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.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
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 2 · 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>