jprichardson / jprichardson/node-google
TLD not anymore used by Google, important consequences
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 456
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Google doesn't use anymore the TLD (Google.com, .fr, ...) in the ranking algorithm since last week.
Important consequences:
- Changing the var "google.lang" will still have an impact
- Changing the var google.tld won't have an impact
To get the Geographically AND Language based results:
- Google uses (IP from the client querying OR IF SET the parameters "Region Settings" in https://www.google.com/preferences ) AND language parameter set https://www.google.hr/preferences?#languages
If you want to get Google results like French with an IP based in Germany, 2 options:
- Having and IP address in Germany + set the language to German
- Changing the "Region Settings" AND the language
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating where google.lang and google.tld are handled, then compare that behavior with Google's regional and language settings; done means the module's Google result parameters reflect the reported TLD change and have coverage for the described combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100