Client Education · Google Business Profile

Suite Numbers on Your Google Business Profile: When to Use Them

November 18, 2026By Chaz Edward

A suite number helps customers find your door. It doesn't decide where you rank.

Google places your business by its street address, so "101 Baltimore St" and "101 Baltimore Street, Ste 4090" point to the same building. That makes the suite number a decision about your customers, not a NAP-consistency risk. We include it when visitors need it. In a few situations we leave it off your Google Business Profile and still use it on your website and other listings.

One address, five listings

  • Your Google profile 101 Baltimore Street, Ste 4090 Same buildingRight door
  • Your website 101 Baltimore St, Suite 4090 Same buildingRight door
  • Directory listing 101 Baltimore St #4090 Same buildingRight door
  • Another directory 101 Baltimore St (no suite) Same buildingBuilding only
  • An old listing 101 Baltimore St, Ste 4009 Same buildingWrong door
Where Google places you 101 Baltimore St

5 of 5 listings point to this building

Lobby directory at 101 Baltimore St
  • Suite 1010Dental office
  • Suite 2040Law office
  • Suite 4009Insurance agencyThe old listing sends visitors here
  • Suite 4090Your office
Google

Every listing points to the same building. Google ties your business to the street address, treats "Suite," "Ste" and "#" as the same thing, and can place you even when the suite is missing.

Visitor

Inside the building, the suite number is what gets someone to your door. A missing suite leaves them looking, and a wrong one sends them to another office.

Illustrative example built on the address used in this guide. The other tenants and suite numbers are made up.

How Google reads a suite number

Google ties your business to the street address

The suite number is a detail for visitors.

Google's own setup keeps them apart

Its guidelines put the street address in Address Line 1 and the suite in Address Line 2. They also say a suite number "may" be included.

Google's Business Profile guidelines

Formatting differences don't matter

Google and Bing understand abbreviations and small variations, such as "Suite" vs. "Ste," so these don't break NAP consistency.

Whitespark

A missing suite doesn't confuse Google

Joy Hawkins of Sterling Sky, quoting listings expert Nyagoslav Zhekov, says Google can work out the address without the suite if the rest of the listing is accurate. Her advice: unless you're in a huge building where it matters, don't stress about it.

Local Search Forum

Different suite formats across directories aren't a ranking problem

Moz's Miriam Ellis notes they're not considered a big deal for SEO, though they can confuse customers.

Moz Q&A

Where accuracy still matters is customers. A directory that shows the wrong suite sends people to the wrong door, so keep it right on the listings people actually use.

When to include it, and when to leave it off

Does a customer need the suite number to reach you?

That's the deciding question. Find your situation below.

Your situation On your Google Business Profile On your website, schema markup and other listings
Customers walk in and need the suite to find you (shared retail, medical or professional building) Include itin Address Line 2 Include it
You have the whole building, or the suite tells visitors nothing Optionala judgement call Include it if it's part of your mailing address
Your own staffed office inside a coworking or executive-suite center Often left offVisitors check in at reception, and the center's suite number is often shared with its mail-only clients Include it wherever mail and visitors need it
Service-area business with the address hidden Not shown publiclyEnter the full address so Google can verify it Include it if you publish the address
Mail-only or virtual office address Not eligiblefor a profile at all. Suite numbers can help Google identify ineligible virtual office locations. Use it as a mailing address only

Under Google Business Profile Help, automated spam and verification systems actively scrutinize and restrict addresses tied to virtual offices, private mailboxes (such as The UPS Store), and co-working spaces.

A classic sign of a virtual office is multiple businesses sharing the same suite number, and such cases trigger automatic scrutiny by Google's spam and verification systems.

What a suite number can't do

Three things a suite number won't do

A suite number won't separate you from a competitor, can't be invented, and won't make an ineligible address eligible.

It won't get you around the local filter

When two businesses in the same category share an address, Google often shows only the stronger one for a search. A suite number doesn't make your location a separate address (BrightLocal). Practitioners have also found that separate suites don't help same-category businesses in one building escape that filter (Moz Q&A).

Never invent one

Don't create a "Suite 100-A" and "Suite 100-B" to split businesses at one address. Google's guidelines require your actual, real-world location, with nothing in the address lines that isn't part of it (Google).

It won't make a virtual office eligible

A rented mailing address you don't operate from can't have a Business Profile. An office in a coworking space qualifies only if it has clear signage, receives customers during business hours, and is staffed by your own employees during those hours (Google).

Common questions

Questions clients ask about suite numbers

An SEO tool says my listings are inconsistent because some show a suite and some don't. Should we fix them all?

Not for rankings. Google places you by the building, so a missing suite isn't a ranking problem. Fix any listing that shows the wrong suite, because that sends customers to the wrong door.

Does it matter whether it says "Suite," "Ste" or "#"?

No. Google and Bing treat common abbreviations as the same address.

Doesn't Google tell you to include suite numbers?

Google's address help page says to include building, suite and floor details, while its main guidelines say they may be included. We include the suite whenever it helps customers. When we leave it off, the street address on your profile is still complete and accurate.

Should my website match my Google profile exactly?

Your website and schema markup should show your full mailing address, including the suite. Google can work out your address with or without the suite, so the difference doesn't create a conflict.

What should we keep in place at our address?

Keep permanent signage with your business name. Google's guidelines expect it at any address you show on your profile. Keep your lease or a utility bill handy too, in case Google asks you to verify the location.

Not sure which situation fits your office?

Tell us how your location is set up. We'll tell you what belongs on your Google Business Profile, your website and your other listings before anything changes.

Ask About Your Address
Technical deep dive

What Google's internal documentation reveals about addresses and locations

November 19, 2026A technical companion to the suite-number guide

Google's internal map database gives a business's position, building and floor their own structures, and none of them is a suite number.

In Geostore, a business is placed by its geometry, a point or storefront shape, and by links to the floor, building and entrances around it. Its address is a separate postal attribute built from parsed parts like the street number and street, and the documented address model has no dedicated suite field.

None of the 72 ranking signals recovered from a 2026 Geostore binary is tied to an address. The leak doesn't reveal how much any field weighs. What it does show is consistent with the guide's main point: a suite number helps people find the door, but it isn't how Google locates or ranks the business.

Google places a business by geometry and links, not by its suite number

Simplified from Geostore classes in the 2024 Content Warehouse leak

Business feature

TYPE_ESTABLISHMENT_POI

point + storefront shape = map position

geometry_precision_meters (accuracy)

The business has an address

Address: a postal attribute
Parsed components

street number, checked against ranges

street name, linked to one street feature

city, state and postal code

addressLines

unparsed, most specific text

where a suite would sit (our reading)

A suite number lands here as text
Business name

kept out of the address entirely

The business is linked to

Location: geometry and links
Floor (TYPE_LEVEL)

business links to it via RELATION_ON_LEVEL

its own address is always empty

Building (TYPE_COMPOUND_BUILDING)

lists its levels and floor count

Entrances and access points

routing endpoints, e.g. the road segment for the 100–200 block of Main Street

If Google keeps a suite number, it sits in the address text. What puts a business on the map is its own geometry and its links to the floor, building and entrances.

A suite number, if Google keeps one, is unparsed text in addressLines. The documented model gives it no link to a map feature, a floor or a building.

The map position comes from the business's own point and storefront geometry. Its floor, building and entrances are separate features joined to it by relationships.

About the sources

Two sources, and what they can prove

Two bodies of material describe Geostore, Google's map database. Both show how it is structured, not how much any field counts.

The 2024 Content Warehouse leak

Internal API documentation for Google's systems, now mirrored on HexDocs. Its Geostore* classes describe how map features, addresses and the relationships between features are stored. Most references below link to these pages.

Resoneo's Geostore analysis, August 2026

"Google Map Dissected" cross-checks that leak against a more recent binary with a non-public Geostore scope, Maps protocols and network traffic. It catalogs 1,623 protobuf descriptors, 4,013 messages and 10,936 Geostore declarations.

What a schema can and can't prove. A schema shows which fields exist and how they connect. It doesn't show how much each one weighs in ranking: Resoneo notes the coefficients are missing. Some fields were also stripped from the binary, including 25 slots of the main feature record and 4 fields of its trust data.

The docs show

The structure is written in the documentation.

Suggests

Our own reading of it. These notes sit in dashed boxes below.

How Geostore stores an address

Parsed parts plus free text, never the business name

An address is a postal attribute attached to a business: parsed parts plus a block of free text, never including the business's own name.

101

TYPE_STREET_NUMBER

Checked against the street's known number ranges.

Baltimore Street

Street component

Linked to one street feature, so "St" and "Street" land on the same street.

Ste 4090

Suggests

Unparsed text in addressLines, with no link to a map feature.

The guide's example address, read the way the documented model stores it. The suite placement is our reading; the docs never name suites.

A postal label, kept apart from the name

GeostoreAddressProto is "attached to features to identify their address(es)." Addresses never include the feature's name; the docs' example is a pizza shop whose address is just "123 Main Street." On the main feature record, addresses follow the postal hierarchy, not the political one.

Parsed parts, smallest to largest

The component list holds parsed parts such as the street and city, ordered from the street number and street outward. Index 0 is the most specific component (GeostoreAddressComponentProto).

Free text for the most specific part

addressLines holds the unparsed portion of the address. It is separate from the parsed parts and must be the most specific portion of the address.

SuggestsA suite that isn't parsed as its own component sits here, as text. The docs never name suites, so treat this as our reading.

No suite type is documented

The component type field names TYPE_FEATURE and TYPE_STREET_NUMBER. Most components map to map-feature types like country, locality or route, and a few have none, such as PO boxes. The full list lives in source code that wasn't leaked. Neither the address pages nor the main feature record define a suite, unit or sub-premise type.

Street names resolve to one map feature

A street component can be linked to the actual street feature through feature_id, and formatting follows that link to pick the name. Google also keeps an AreAddressComponentsEquivalent() check for comparing components. That's why "101 Baltimore St" and "101 Baltimore Street" land on the same street.

Street numbers are checked against known ranges

Road segments carry address-number ranges (GeostoreAddressRangeProto). Resoneo found that autocomplete grades a street number as IN_RANGE, IN_GAP, OUTSIDE_MINMAX or OUTSIDE_SEARCH_RANGE. The street number is the part of the address Google validates against the map; nothing comparable is documented for suites.

Where a business sits: geometry, buildings and floors

Position is stored apart from the address

A business's position is stored as geometry and as links to other map features, separately from its address.

Geometry places it on the map

On the main feature record, point "defines the geometry of the feature," and center is the conceptual center used for routing. Only business features (TYPE_ESTABLISHMENT_POI) get a storefront geometry (GeostoreFeatureProto). A geometry_precision_meters value says the true location lies within a circle of that radius (v0.4.0).

Buildings are their own features

TYPE_COMPOUND_BUILDING features carry building data such as the number of floors and the list of their levels (GeostoreBuildingProto).

Floors are their own features, linked by a relationship

A level feature represents a logical level such as a floor. Anything on that floor points to it with RELATION_ON_LEVEL, and the level records which building it belongs to. Its number gives height in floors: 0 is ground, 1 is the first floor, -3 is three levels down. A level's own address field "should always be empty" (GeostoreLevelProto). For indoor features, Google prefers RELATION_ON_LEVEL to other ways of ordering things vertically (GeostoreVerticalOrderingProto).

Relationships tie the pieces together

A relation records a geographic or logical relationship between one feature and another (GeostoreRelationProto). Google's public Vector Tile API gives the example of a building occupied by a given business (Relation).

Entrances and access points route people to the door

An access point links a business or building to another feature. The docs' example: the access point for a building at 123 Main Street would likely be the road segment for the 100–200 block of Main Street. Indoor access points record the level they're on (GeostoreAccessPointProto). Entrances are features too, referenced by the places they serve (GeostoreEntranceReferenceProto).

SuggestsWhen Google knows which floor or entrance a business uses, it models that with these links, not by reading "Ste 4090." For most small businesses in buildings without indoor mapping, the point and the building are what Google has.

How Google decides which value wins

Every value has a source, a trust level and a bar to clear

Every value has a recorded source and trust level, and a new value has to clear a bar before it replaces the old one. All figures here come from Resoneo's analysis unless linked otherwise.

Provenance is kept per field

Each field records its field_path, provider and dataset, and the provider catalog holds 793 sources. One business can draw on several sources at once, with a different origin for each field. Addresses and relationships carry field-level metadata too (GeostoreAddressProto, GeostoreRelationProto).

Sources are ranked by trust

Directory data sits in the middle of the scale:

  • SUPER_TRUSTED64Highest tier
  • TRUSTED48A reliable source
  • YP_FEEDS40Yellow-pages feeds: data bought or ingested from business directories
  • NOT_TRUSTED32
  • BLOCKED16
  • UNKNOWN0Lowest tier

The default merge doesn't take a vote

Geostore exposes three merge methods: CONFLATION_PICK_FIRST_VALUE (the default), CONFLATION_UNION_CSV and CONFLATION_SUM. The default takes the first admissible value in priority order rather than letting sources vote. Resoneo cautions that this is the machinery Geostore holds, not proof that every Maps attribute is merged this way.

An edit has to clear a barrier

Each attribute also has an edit barrier: the level a future edit must reach to replace it. The formula wasn't recovered. In practice, changing a value in Business Profile doesn't necessarily replace the old value right away.

Identity events are tracked

Existence states include closed, removed, moved, rebranded, duplicate, replaced and spam, each confirmation stored with its origin and timestamp.

SuggestsA directory feed that formats a suite differently doesn't outvote a more trusted value by default. And if you remove a suite from a profile, Google may keep showing the old one for a while.

What the ranking data shows, and what it doesn't

No address-specific signal, and no known weights

None of the ranking signals recovered from the binary is tied to an address, and their weights aren't known. All points here are from Resoneo's analysis.

72

Ranking signals recovered from the binary

0

Described as address-specific

None

Signal weights recovered

72 signals, none address-specific

None of the 72 RankSignalProto.Signal values is described as address-specific. The closest are APPROACHABILITY, TOTAL_ROAD_SEGMENT_USAGE and LANDMARK, which are named but whose formulas aren't given.

No weights

The coefficients are missing, so the weight of any signal is unknown. That cuts both ways: the leak can't prove a suite number carries zero weight, and nothing in it gives a suite one.

Search radius isn't tied to the address

It adapts to how dense the area is and to the query.

NAP isn't a leak term

The article doesn't use the words NAP or citations. Its advice that name, address, phone, category, URL and brand should "tell the same story" is the author's interpretation, not a field in the data. Its sharpest practical line: "An identity error is worse than a poorly optimised field."

Open questions. The article doesn't name the fields Google uses to detect duplicates, and it doesn't cover how businesses sharing a building are filtered.

What this means for suite numbers

The documentation backs the guide

The internal documentation backs the guide's position: a suite number is a detail for visitors, not how Google places or ranks a business.

  1. Position comes from geometry and links, not the suite

    A business is placed by its point and storefront geometry and by its links to floors, buildings and entrances. The address is a separate postal attribute.

  2. The address model has no suite field

    The documented parts are the street number, street, city and other postal parts. The most specific free text goes in addressLines, kept as plain text with no link to a map feature.

  3. Formatting differences resolve to the same street

    Street names link to one street feature, and Google keeps an equivalence check for address parts. "St" vs. "Street" or "Suite" vs. "Ste" is not a meaningful difference.

  4. No ranking signal is tied to an address

    None of the 72 recovered signals is address-specific. The weights are missing, so this is strong consistency with practitioners' findings, not proof of zero effect.

  5. What the leak does flag is identity

    Moves, duplicates, rebrands and spam are tracked states. A wrong street number, an old address or a duplicate listing is a real problem. A missing or reformatted suite isn't.

  6. Changes don't overwrite instantly

    Trust levels and the edit barrier mean directory feeds rank below trusted sources, and a profile edit may take time to replace the stored value.

Sources

Read the documentation

Analysis

Leaked Geostore documentation (2024 Content Warehouse leak, HexDocs mirror)

Public Google documentation

Local SEO Audit & Strategy Call

After you complete this form you’ll be prompted to schedule a Complimentary Zoom Strategy Session with Chaz