NAP is name, address, and phone. It is the dullest part of local SEO and the one Philippine businesses break most often. The Google profile says one string, the website footer says another, Facebook has a third, and the Facebook ads use a mobile number that is not on any of them. Customers still find you. Google has a harder time deciding which record is the business.
We do not treat NAP as a superstition that “citations rank you.” We treat it as identity. If the public facts disagree, every later local task is noisier: verification, Google Business Profile and local pack work, directory cleanup, and even call tracking. One canonical version has to win, then everything else copies it.
What Has To Match, And What Does Not
The name should be how the business is known on the sign, the website, and to customers. Google’s representation guidelines say the profile name should reflect the real-world name and should not be stuffed with slogans, extra cities, hours, phone numbers, or service keywords. “Santos Dental Clinic Makati Braces Invisalign” is not a name. “Santos Dental Clinic” is.
The address should be the place customers visit, or the hidden base for a service-area business, written in a stable order. The phone should be a number a human can answer, in one published format.
What does not need to be identical is every marketing line. Taglines, service lists, and Facebook about text can vary. The identity fields should not. When a designer shortens “Avenue” on the site and a directory expands it, that is already two addresses. When ads run a Globe number and the profile shows a landline that rings out, that is two businesses as far as a caller is concerned.
Legal entity names and trading names need an explicit choice. If the SEC papers say “Santos Dental Inc.” and the sign says “Santos Dental Clinic,” pick the public trading name for NAP and keep the legal name on the documents. Do not bounce between them on different platforms because each vendor asked for a “registered name.”
Name Drift In Philippine Listings
The usual name errors are city stuffing, branch labels, and Facebook creativity. A single Quezon City shop becomes “Bright Auto Repair QC” on Maps, “Bright Auto Repair Cubao” on the site H1, and “Bright Auto” on Instagram. None of those is illegal. Together they look like three shops.
Branch names need a rule. If you have one location, do not put the city in the business name just to rank for it. If you have several staffed locations, each profile can use a real branch identifier the way customers already say it, without turning the name into a keyword sentence. Google’s own examples reject location stuffing that is not how the business is recognised.
Punctuation and legal suffixes cause fake mismatches. “Santos Dental Clinic,” “Santos Dental Clinic.”, and “Santos Dental Clinic Inc.” will be copied differently by directories. Unless the sign actually includes Inc. or LLC, leave it off the public name. Google’s name guidelines treat irrelevant legal terms as extra unless you can prove they are part of the real-world name.
We also see emoji, all caps, and “Official” tacked onto social names. Those can stay on social if you insist. They should not migrate into the Google profile or the website NAP block. The profile name and the site name in schema and footer should be the boring, matching string.
Address Strings That Fall Apart Locally
Philippine addresses are long because they are. Building, tower, unit, street, barangay, city, province, postcode. The mistake is using a different subset everywhere. The website shows building and street. Google shows street and city. Facebook shows village name. A directory in the United States parser wants a ZIP and invents one.
We lock an order and stick to it. A working pattern for a visit address is unit and floor, building, street number and street, barangay if you use it everywhere, city, postcode. If the business is in a village, decide whether the public address uses the village name, the street inside it, or both, then use that same decision on the site, the profile, and printed materials.
Do not put the unit in the business name because the address field felt small. Google provides address lines for that. Do not swap “EDSA” and “Epifanio de los Santos Avenue” at random. Pick the form that appears on the building and on Maps, then copy it.
Landmarks are useful in directions copy and useless as a substitute for the address. “Near SM North” is not an address. It can live in the description or on a contact section as help for drivers. It should not replace the street on the profile.
Service-area businesses still need an internal base address that is true. The public card may hide it. The website should not invent a fake shopfront in BGC to look premium. If you do not serve customers there, do not publish it as a visit address. That mismatch is how NAP cleanup turns into an eligibility problem.
Mall tenants should include the mall and the unit the mall itself uses. If the mall directory says Level 3, 335, the profile should not say 3F-35 because someone rounded. Security and Google both do better with the mall’s own identifier.
Phone Numbers, Country Codes, And Extra SIMs
Philippine numbers appear as 0917, 917, +63 917, and (02) landlines with or without the trunk zero. Directories abroad will rewrite them. Your job is to publish one primary number in one format everywhere you control, then let aggregators copy it.
We prefer a single primary that a person answers during stated hours. If you use a landline and a mobile, decide which is primary on Google. Secondary numbers can exist in other fields or on the site, but the NAP phone is one value. Call tracking numbers belong in tracking tools, not as a second public identity on Facebook and yellow pages.
Viber-only numbers and numbers that change when the SIM expires are toxic for NAP. If the sales manager’s personal Globe line is the “business number,” you will rebuild NAP every time that person leaves. Put the business on a number the business owns.
Do not list a number that dumps into an IVR if you still need SMS verification or if customers expect a human. Google has already said IVR will not receive verification codes. Customers are equally unimpressed.
Country code consistency matters for click-to-call on mobile. If the website uses +63 and the profile uses 0, many calls still connect, but some directories will treat them as different. We standardise on one written form for humans and make sure the tel link dials correctly.
Where Philippine Businesses Scatter NAP
The website footer, contact section, Google profile, Facebook page, Instagram bio, TikTok, Shopee or Lazada seller profile, job ads, email signatures, invoices, and old directories all copy the identity. One rebrand or office move that updates only the site leaves a trail of ghosts.
Facebook is the usual offender. Pages get created by a social intern with a nickname and a personal number. Years later the Google profile is correct and Facebook still converts, so nobody wants to touch it. Then ads amplify the wrong NAP. We update Facebook in the same round as Google, or we accept that we are running two identities.
Directories you never heard of still rank for brand searches. Some are useful. Many are scrapes of scrapes. We do not chase every site. We fix the sources you own, the Google profile, and the directories that actually send calls or that Google is likely to trust, then we suppress or mark closed the obvious duplicates.
Moved offices are a special case. The old address will outlive you on blogs and citations. The new address has to be correct on the properties you control first. Then we update or close the old Google listing rather than leaving two pins. Two pins with similar names and different addresses is the opposite of consistency.
How We Audit Without Guessing
We pull the live Google profile, the live website header and footer, and the main social profiles on the same day. We write down the three fields exactly, including punctuation and phone format. Anything that is not identical is a finding, not a style comment.
We then search the exact name and the exact phone. Extra listings, old villages, and staff names used as business names show up there. We do not bulk-submit to hundreds of directories as a first move. Submission on top of a dirty identity multiplies the dirt.
Schema on the site should repeat the same NAP, not a fourth version a plugin generated. If a page builder still has the old landline in a global widget, that widget is in the audit. PDF menus, Google Docs linked from the site, and Linktree pages count as public NAP.
For groups with several branches, each location gets its own NAP row. Shared numbers are recorded as a choice, not an accident. If two branches publish the same mobile, we ask whether that is how calls are routed. If not, we split them before building citations.
After The Canonical Version Exists
Once the business signs off on one name, one visit or hidden base address, and one primary phone, we update Google, the website, and the owned social profiles. Only then do we touch the directories worth touching. Review responses, posts, and print materials should start using the same block so we do not reintroduce drift.
NAP work does not replace categories, photos, or reviews. It stops those things from sitting on a confused entity. A clean identity with a weak site will still lose pack visibility. A strong site with three phone numbers will still leak calls and confuse local data.
We keep a short internal record of the canonical string so later designers and media buyers cannot “improve” it. If the business moves, we change the record once and roll it out again. That is the whole system.
If you want that audit done on the live properties, send the website and the Maps listing. We will line the public name, address, and phone up with local SEO services rather than spraying new citations on top of three versions of the same shop.
