Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Google Search API] related_searches not returned on Mobile version #309

Closed
marm123 opened this issue Sep 7, 2022 · 7 comments
Closed
Assignees
Labels
status: urgent Urgent work

Comments

@marm123
Copy link

marm123 commented Sep 7, 2022

There is no related_searches key returned while scraping Google Search on mobile.

image

Playground | Inspect

@marm123 marm123 added the status: queued Ready to work on label Sep 7, 2022
@aciddjus aciddjus added the status: wip Work in progress label Sep 12, 2022
@tanys123 tanys123 self-assigned this Sep 19, 2022
@ilyazub
Copy link

ilyazub commented Oct 13, 2022

These Related searches are expected to be extracted into inline_people_also_search_for or related_search_boxes previously.

related_searches are ellipses with keywords at the bottom of the SERP.

image

Edit: Sorry. I've double-checked. Some pages contain both similarly-looking People Also Search For and Related Searches blocks. This is confusing. Search ID: 6347c4c0359e994965f10fbe.

People Also Search For Related Searches
image image

@dimitryzub dimitryzub removed the status: wip Work in progress label Nov 3, 2022
@marm123
Copy link
Author

marm123 commented Feb 10, 2023

Opening this thread as the issue back once again:

image

Playground | Inspect

@marm123 marm123 reopened this Feb 10, 2023
@marm123 marm123 added status: urgent Urgent work and removed status: queued Ready to work on labels Feb 10, 2023
@marm123
Copy link
Author

marm123 commented Feb 10, 2023

"People also search for" is also missing from the JSON response. It's a bit confusing with the naming, as Illia pointed out. I'm unsure if this is extracted in the same block, but if not, I can create a separate issue. LMK

image

Playground | Inspect

@aciddjus aciddjus self-assigned this Feb 10, 2023
@schaferyan
Copy link

schaferyan commented Feb 15, 2023

I'm reopening this thread as a customer just reported having this issue again. I was unable to replicate it in our Playground, however. Also it may be subtly different - feel free to move to a new thread if necessary. It's hard for me to see what's going on without being able to read Japanese, but in the example in the search_inspector it looks like we are only scraping query and link from "People also Ask" and not any of the other keys we usually parse..

image

search inspector

@schaferyan schaferyan reopened this Feb 15, 2023
@aciddjus aciddjus removed their assignment Feb 20, 2023
@aciddjus
Copy link

I'm reopening this thread as a customer just reported having this issue again. I was unable to replicate it in our Playground, however. Also it may be subtly different - feel free to move to a new thread if necessary. It's hard for me to see what's going on without being able to read Japanese, but in the example in the search_inspector it looks like we are only scraping query and link from "People also Ask" and not any of the other keys we usually parse..

image

search inspector

Not 100% sure I understand the problem. There is nothing here except query and link, and we are extracting it.

image

@marm123
Copy link
Author

marm123 commented Feb 20, 2023

@aciddjus I believe the confusion comes from language differences in API results. The issue customer has is that the "People also ask" is extracted together with related searches, while in fact, it's not "People also ask" but "People also search for". Below is the conversation with a customer about their issue:

Intercom conversation

I'm closing this one as the issue is more if we should extract "People also search for" together with "Related Searches" in the same related_searches block of the JSON response or not, and this thread is about something else.

@marm123 marm123 closed this as completed Feb 20, 2023
@aciddjus
Copy link

@marm123 Got it 👍

Yes it's super confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: urgent Urgent work
Projects
None yet
Development

No branches or pull requests

6 participants