Session 1.3: Address Consistency

Course → Module 1: Identity Consistency: NAP and Beyond

Session 3 of 7

Address consistency is the most underestimated component of NAP. Business owners often think that because their address is "obviously" the same location, minor formatting differences do not matter. They are wrong. Google processes addresses as strings before geocoding them, and format variations can cause geocoding failures, entity splitting, or confidence reduction.

How Google Processes Addresses

When Google encounters an address string, it goes through a resolution chain. Understanding this chain explains why formatting matters.

graph LR A["Raw address string
'Jl. Sudirman No. 45'"] --> B["Parsing
Extract components"] B --> C["Normalization
Standardize format"] C --> D["Geocoding
Convert to coordinates"] D --> E["Entity matching
Link to known entity"] B -.->|"Parse fails"| F["Unresolved
Address ignored"] C -.->|"Non-standard format"| G["Low confidence
Weak entity signal"] style A fill:#2a2a28,stroke:#c8a882,color:#ede9e3 style B fill:#2a2a28,stroke:#6b8f71,color:#ede9e3 style C fill:#2a2a28,stroke:#6b8f71,color:#ede9e3 style D fill:#2a2a28,stroke:#6b8f71,color:#ede9e3 style E fill:#2a2a28,stroke:#6b8f71,color:#ede9e3 style F fill:#2a2a28,stroke:#c47a5a,color:#ede9e3 style G fill:#2a2a28,stroke:#c47a5a,color:#ede9e3

At each stage, format inconsistencies can cause problems. If parsing fails, the address is ignored as an entity signal. If normalization produces a different result than your other listings, the geocoded location may not match. If the geocoded location does not match what Google has on file for your entity, it weakens the entity signal rather than strengthening it.

Address Components

Every address is a set of components. Each component has formatting choices that must be consistent across all platforms.

Component	Common Variations	Rule
Street type	"Jalan" vs "Jl." vs "Jl"	Pick one abbreviation style and use it everywhere
Street number prefix	"No." vs "No" vs "#" vs nothing	Match the style used on your Google Business Profile
Unit / suite / floor	"Suite 200" vs "Ste 200" vs "Lt. 2"	Use one format. If GBP uses "Lt.", everything uses "Lt."
City name	"Jakarta Selatan" vs "South Jakarta" vs "Jaksel"	Use the official name. No abbreviations, no translations unless that is your market standard.
Province / state	"DKI Jakarta" vs "Jakarta" vs "JKT"	Use the version that matches postal authority standards
Postal code	"12190" vs "121 90" vs missing	Always include. No spaces unless the postal system requires them.
Country	"Indonesia" vs "ID" vs omitted	Include on international platforms. Omit only if the platform is country-specific.

Indonesian Address Formatting

Indonesia presents specific challenges because the addressing system is less standardized than countries like the US or UK. Here are the most common pitfalls.

RT/RW numbers. Some directories auto-import RT/RW (neighborhood/community) numbers. If your address on one platform includes "RT 005/RW 003" and another does not, these are different strings. Decide whether to include RT/RW and stick with that decision.

Kelurahan and Kecamatan. Full Indonesian addresses include kelurahan (village) and kecamatan (district). Some platforms include them, others do not. Again, consistency matters more than completeness.

Language mixing. "Jl." is the Indonesian abbreviation for "Jalan" (street). English-language directories might convert this to "St." or "Street." If possible, keep the original Indonesian format even on English platforms.

US Address Formatting (For Comparison)

If your entity operates in the US or targets a US audience, address formatting follows USPS conventions. Common pitfalls include:

Component	Correct (USPS Standard)	Common Mistake
Street type	123 Main St	123 Main Street
Direction	456 N Broadway	456 North Broadway
Unit	Ste 200	Suite 200 / #200
State	CA (two-letter code)	California / Calif.
ZIP	90210	90210-1234 (ZIP+4 is optional but must be consistent)

The USPS publishes formatting standards. Google's geocoding API uses these standards as a reference. Matching them improves parse accuracy.

The GBP Anchor Rule

Here is a practical rule that simplifies address consistency: your Google Business Profile address is the format reference for everything else.

Google Business Profile is Google's own product. The address you enter there is the one Google associates most directly with your entity. If your GBP says "Jl. Sudirman No. 45, Lt. 3, Setiabudi, Jakarta Selatan 12190," then every other platform should use that exact string.

This does not mean GBP is always right. If your GBP address has errors, fix GBP first, then propagate the corrected version everywhere else.

Your Google Business Profile is the address format authority. Every other platform copies from it, not the other way around.

Virtual Offices and Service-Area Businesses

Not every entity has a physical address. Service-area businesses and online-only businesses present a special case. If you do not have a physical location:

Do not invent a fake address. Google penalizes this.
Use a service-area business listing on GBP (no address shown publicly, but a service area defined).
On your website, use city and country without a street address.
Be consistent with whatever level of detail you choose. If you list "Jakarta, Indonesia" on one platform, use that exact string everywhere.

Assignment

Write your canonical address, formatted exactly as it appears on your Google Business Profile. If you do not have a GBP, format it according to your postal authority's standards.
Check your website (footer, contact page, about page). Does the address match your canonical format exactly? Include punctuation, abbreviations, and postal code.
Check three directory listings or social profiles. Record the exact address string on each. Note every difference from your canonical version.
If you are a service-area business or have no physical location, define what level of geographic information you will use (city only, city + country, etc.) and record it in your master NAP.

Address Consistency