GeoNames Username

The GeoNames Username is the account name RankGear sends to the GeoNames web service to authorize geographic lookups — resolving place names, coordinates, and administrative regions. It identifies your free GeoNames account so those requests are attributed to you rather than refused.

What it means in RankGear

You set this under Settings → APIs. GeoNames is a free geographic database whose web API requires each caller to register an account, enable web services, and then pass a username with every request. RankGear stores that username here so any feature that resolves locations — matching a query to a city or region, normalizing an inconsistent place name — can call GeoNames on your behalf. There is no separate secret key: the username itself is the credential, which is why the field holds a plain username rather than a token.

How to interpret it

Read the field as a reliability control, not a metric. When a geographic lookup fails, use the visible status, the diagnostics, and the credential test to separate a transient problem from a broken configuration. A test that passes alongside an occasional failure points to rate limiting or a slow response on the GeoNames side; a lookup that fails consistently with an authorization error points to the credential itself — a missing username, web services never enabled on the account, or the wrong account entirely.

Example

You enter your username and run a batch of location lookups. One request stalls and times out, so RankGear issues a single bounded longer retry before moving on — a momentary slowdown does not derail the run. On the next request GeoNames returns an authorization failure because web services were never switched on for the account; RankGear stops there instead of repeating the same failing call, and the diagnostics flag the credential rather than the network.

Important considerations

• The GeoNames free tier enforces hourly and daily request limits. A large volume of location work can exhaust the quota, after which lookups fail until it resets.
• Registering an account is not enough — web services must be explicitly enabled for the username before the API will answer.
• The username is a credential: keep it redacted in logs, diagnostics, and exports, and prefer read-only tests when checking that it works.
• Resolved geographic data is a reference for labeling and grouping, not a ranking signal. Getting a place name right helps RankGear organize what it measures; it does not make a page rank.

Related terms

• Language Override
• Credential Redaction

Part of the RankGear glossary · how RankGear measures · the 870 factors.