RRepoGEO

REPOGEO REPORT · LITE

openvenues/libpostal

Default branch master · commit 25099c50 · scanned 5/23/2026, 8:36:58 AM

GitHub: 4,804 stars · 469 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
69 /100
Needs work
Category recall
1 / 2
Avg rank #1.0 when recommended
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface openvenues/libpostal, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Strengthen README's opening to highlight data quality and record linkage applications

    Why:

    CURRENT
    libpostal is a C library for parsing/normalizing street addresses around the world using statistical NLP and open data. The goal of this project is to understand location-based strings in every language, everywhere.
    COPY-PASTE FIX
    libpostal is a C library for parsing and normalizing street addresses worldwide using statistical NLP and open data. It's designed to standardize location-based strings across languages, making it ideal for data cleaning, record linkage, and deduplication tasks.
  • mediumhomepage#2
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    https://openvenues.github.io/libpostal/
  • lowreadme#3
    Consider adding a 'Why libpostal?' or 'Comparison' section to README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, perhaps titled 'Why libpostal?' or 'Comparison', with an introductory sentence like: 'Unlike generic C libraries or commercial geocoding services, libpostal offers an open-source, offline, and highly specialized solution for international address parsing and normalization.'

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
1 / 2
50% of queries surface openvenues/libpostal
Avg rank
#1.0
Lower is better. #1 = top recommendation.
Share of voice
6%
Of all named tools, what % are you?
Top rival
Loqate
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Loqate · recommended 2×
  2. Google Maps Geocoding API · recommended 1×
  3. libcurl · recommended 1×
  4. Jansson · recommended 1×
  5. cJSON · recommended 1×
  • CATEGORY QUERY
    How to accurately parse and normalize international street addresses using a C library?
    you: #1
    AI recommended (in order):
    1. libpostal ← you
    2. Google Maps Geocoding API
    3. libcurl
    4. Jansson
    5. cJSON
    6. OpenCage Geocoding API
    7. Loqate
    8. AddressDoctor
    9. PCRE2
    Show full AI answer
  • CATEGORY QUERY
    Need a tool to standardize global address strings for record linkage and deduplication.
    you: not recommended
    AI recommended (in order):
    1. Loqate
    2. Melissa Clean Suite
    3. Experian Pandora
    4. Google Maps Platform (Geocoding API)
    5. SmartyStreets
    6. Postcode Anywhere
    7. OpenCage Geocoder

    AI recommended 7 alternatives but never named openvenues/libpostal. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of openvenues/libpostal?
    pass
    AI named openvenues/libpostal explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts openvenues/libpostal in production, what risks or prerequisites should they evaluate first?
    pass
    AI named openvenues/libpostal explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo openvenues/libpostal solve, and who is the primary audience?
    pass
    AI named openvenues/libpostal explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of openvenues/libpostal. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/openvenues/libpostal.svg)](https://repogeo.com/en/r/openvenues/libpostal)
HTML
<a href="https://repogeo.com/en/r/openvenues/libpostal"><img src="https://repogeo.com/badge/openvenues/libpostal.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

openvenues/libpostal — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite