[Google Search API] `kgmid` is not extracted in `knowledge_graph`

[marm123]

It looks like the kgmid key is missing from the JSON response for most searches:

Playground search:

Google Search:

Page Source:

Playground | Inspect | Google Search with the kgmid parameter Playground | Inspect | Google Search with the kgmid parameter

[Toffee1878]

Looking forward to seeing this working again.

[ckosmic]

This issue seems to have popped up again. Playground 1 Playground 2

[Mrtierne]

Seeing the issue as well

[schaferyan]

Reopening this, since the comments above indicate it's become a problem again

[marm123]

Fixing this might help with getting the city_id for the Google Flights API. Reference: https://github.com/serpapi/public-roadmap/issues/1344#issuecomment-1886439184

[martin-serpapi]

Another customer reported this:

Intercom

[dmeltdown]

I just checked on this and it still appears to be broken.

[andypple83]

Thanks for reporting this issue. Google changed the encoding for their page source. I'll fix this issue soon.

[dmeltdown]

great! thank you.

its also here:

[andypple83]

Thanks @dmeltdown, we're scraping all these places to make sure it's available in our results.

[dmeltdown]

Hi @andypple83, Any updates on getting the KGMID results to show back up?

[redsparkautonetmedia]

For Vehicles it is usually in 4 different places in page source

data-maindata='[null,"/g/11sbdqtgc8","2023 Acura TLX",

,"/g/11sbdqtgc8","2023 Acura TLX",null,["CARS"],

https://www.google.com/search?kgmid\u003d/g/11sbdqtgc8\u0026hl\u003den-US

,"2023 Acura TLX",[277,"51+","/g/11sbdqtgc8",

Here is link: view-source: view-source:https://www.google.com/search?q=2023+acura+tlx&sca_esv=35124072aa3934e9&rlz=1C1CHBF_enUS920US920&ei=mCm7ZdTWAeGv5NoPrOW34AY&gs_ssp=eJzj4tVP1zc0LE5KKSxJT7YwYPTiMzIwMlZITC4tSlQoyakAAJEHCVM&oq=2023+acura+tlx&gs_lp=Egxnd3Mtd2l6LXNlcnAiDjIwMjMgYWN1cmEgdGx4KgIIADIREC4YgAQYigUYkQIYsQMYgwEyBRAuGIAEMgoQLhhDGIAEGIoFMgUQABiABDIFEAAYgAQyChAAGIAEGIoFGEMyBRAAGIAEMgUQABiABDIFEAAYgAQyBRAAGIAEMiAQLhiABBiKBRiRAhixAxiDARiXBRjcBBjeBBjgBNgBAUivGFAAWO4FcAB4AZABAJgBaaABgAKqAQMyLjG4AQHIAQD4AQHCAg4QLhiRAhixAxiABBiKBcICHRAuGJECGLEDGIAEGIoFGJcFGNwEGN4EGOAE2AEBwgIREC4YgwEYkQIYsQMYgAQYigXCAiAQLhiDARiRAhixAxiABBiKBRiXBRjcBBjeBBjgBNgBAeIDBBgAIEG6BgYIARABGBQ&sclient=gws-wiz-serp

[marm123]

Hi @dmeltdown and @redsparkautonetmedia. Thank you guys very much for following up on this thread. I wanted to let you know that we're currently working on this issue, and a pull request was created to resolve it. However, it requires some additional reviews before we can merge it.

Thank you so much for your patience!

[mertzdog]

I am having this same problem. An Idea when there will be a fix?

[marm123]

Hi @mertzdog, thank you for reaching out! While I can't share an ETA on when it'll be fixed, our Engineers are actively working on reviewing the pull request created to resolve the issue.

Feel free to reach out to us at contact@serpapi.com in case you have any questions or concerns. We'll be happy to help!

[andypple83]

Thanks everyone. The kgmid field should be available in our SerpApi results. Thanks

[martin-serpapi]

Reopening the issue as another hight volume customer reported that kgmid is not returned in the response for some searches. I was able to reproduce it in the Playground:

Playground | Inspect

Google Search

Intercom

[andypple83]

We've released a fix for this. The kgmid should be present in search results.