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

Split Google crawlers into categories #107

Open
alaz opened this issue Sep 18, 2023 · 3 comments
Open

Split Google crawlers into categories #107

alaz opened this issue Sep 18, 2023 · 3 comments

Comments

@alaz
Copy link
Owner

alaz commented Sep 18, 2023

https://developers.google.com/search/docs/crawling-indexing/verifying-googlebot

@alaz alaz changed the title Split Google into categories Split Google crawlers into categories Sep 18, 2023
@aydinkazim
Copy link
Contributor

Hey, I think one possible fix for this could be adding Chrome-Lighthouse to the list of Google crawlers. Since it's commonly used for performance audits, it might make sense to group it with the other Google bots. Here's what the updated lib/legitbot/google.rb could look like:

rule Legitbot::Google, %w[
  APIs-Google
  AdsBot-Google-Mobile
  AdsBot-Google
  Googlebot
  Mediapartners-Google
  AdsBot-Google-Mobile-Apps
  FeedFetcher-Google
  Google-Read-Aloud
  DuplexWeb-Google
  googleweblight
  Storebot-Google
  Google-Site-Verification
  Google-InspectionTool
  Chrome-Lighthouse
]

@alaz
Copy link
Owner Author

alaz commented Oct 22, 2024

Hi, the idea of the card is a bit different, I was thinking of packaging Google crawler User-Agents into few lists just like Google presents them on this page.

I agree with your suggestion. Please feel free to create a PR.

@aydinkazim
Copy link
Contributor

Ah, now I understand 😮‍💨 I think you want to categorize it into three groups as mentioned in the document. Still, thank you for your kindness; I have created the PR. #160

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants