[Google Search API] Missing Keys for other_pages

[schaferyan]

A customer reported that for some searches, pagination.other_pages and serpapi_pagination.other_pages seem to be missing keys.

It's possible that these keys just don't show up in the Playground and Search Inspector. When I try them with the JS/TS library the keys are provided as expected. However they seem to be missing from the Playground in almost every search I tried.

Playground | Search Inspector | Intercom

[schaferyan]

The customer confirmed it seems to be working in their code - the problem they are seeing is in the Search Inspector.

[hartator]

Do you mean the structure of other_pages is odd on our pages?

It does look like an array and an object at the same time:

"other_pages":
{
"https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=10&sourceid=chrome&ie=UTF-8",
"https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=20&sourceid=chrome&ie=UTF-8",
"https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=30&sourceid=chrome&ie=UTF-8",
"https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=40&sourceid=chrome&ie=UTF-8"
}

Actual JSON has 2,3,4 as keys indeed:

    "other_pages": {
      "2": "https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=10&sourceid=chrome&ie=UTF-8",
      "3": "https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=20&sourceid=chrome&ie=UTF-8",
      "4": "https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=30&sourceid=chrome&ie=UTF-8",
      "5": "https://www.google.com/search?q=AAPL+financials+site%3Afinance.yahoo.com&oq=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=40&sourceid=chrome&ie=UTF-8"
    }
  },
  "serpapi_pagination": {
    "current": 1,
    "next_link": "https://serpapi.com/search.json?device=desktop&engine=google&google_domain=google.com&q=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=10",
    "next": "https://serpapi.com/search.json?device=desktop&engine=google&google_domain=google.com&q=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=10",
    "other_pages": {
      "2": "https://serpapi.com/search.json?device=desktop&engine=google&google_domain=google.com&q=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=10",
      "3": "https://serpapi.com/search.json?device=desktop&engine=google&google_domain=google.com&q=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=20",
      "4": "https://serpapi.com/search.json?device=desktop&engine=google&google_domain=google.com&q=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=30",
      "5": "https://serpapi.com/search.json?device=desktop&engine=google&google_domain=google.com&q=AAPL+financials+site%3Afinance.yahoo.com&safe=active&start=40"
    }
  }

[schaferyan]

Yes exactly, the actual JSON response is as intended, but we display it as an array-like object with no keys in the Search Inspector and Playground. The user had the impression we were returning invalid JSON.