On this page
- RNX-970.T001 · Local operating model
- RNX-970.T002 · Business Profile representation
- RNX-970.T003 · Primary category fit
- RNX-970.T004 · Regular hours accuracy
- RNX-970.T005 · Special hours accuracy
- RNX-970.T006 · Service area truth
- RNX-970.T007 · Location identity separation
- RNX-970.T008 · Review solicitation integrity
- RNX-970.T009 · Review response privacy
- RNX-970.T010 · Local profile verification evidence
- RNX-970.T011 · Bing Places import overwrite review
- RNX-970.T101 · Duplicate and department profile adjudication
- RNX-970.T102 · Profile address visibility
- RNX-970.T103 · Branch contact and landing-route accuracy
- RNX-970.T104 · Location page substantive accuracy
- RNX-970.T105 · Relocation and closure state propagation
- RNX-970.T106 · Secondary category accuracy
- RNX-970.T107 · Map position accuracy
RNX code library · 18 controls
RNX-970Local Profile Operations
Read what these checks mean, why they matter and which evidence they concern. Each ID below keeps its canonical place in the RNX hierarchy.
These are free learning summaries, not full technical tests or an industry certification. Specialized checks apply only to the relevant feature. Experimental labels are preserved from the canonical source.
RNX-970.T001
Local operating model
core readiness
Identify whether the business serves visitors, travels to customers, does both or works online only.
Why it matters. Listing choices depend on the real operating model.
Illustration — fictional. An online-only software business receives a failure solely for lacking a storefront map pin.
When it applies. Inspected target: location operating model. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T002
Business Profile representation
core readiness
Represent the real business in its profile.
Why it matters. Adding search phrases to its name can misstate its identity.
Illustration — fictional. The official profile name has extra service keywords absent from real-world branding.
When it applies. Inspected target: Business Profile name representation. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T003
Primary category fit
core readiness
Choose a primary category that describes the main business activity.
Why it matters. Customers should not be sent to a service you do not provide.
Illustration — fictional. The selected category describes a lucrative service the business does not provide.
When it applies. Inspected target: primary category selection. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T004
Regular hours accuracy
core readiness
Publish regular hours people can rely on.
Why it matters. Wrong hours can turn a discovery into a wasted trip.
Illustration — fictional. Published opening hours extend beyond the actual staffed operating hours.
When it applies. Inspected target: regular operating-hours schedule. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T005
Special hours accuracy
core readiness
Update known holiday hours and special closures.
Why it matters. Normal hours may be misleading on an unusual day.
Illustration — fictional. The profile advertises normal hours on a known full-day closure.
When it applies. Inspected target: special-date operating-hours schedule. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T006
Service area truth
core readiness
Advertise only areas the business really serves.
Why it matters. A claimed service area is a customer promise.
Illustration — fictional. A listing promotes emergency service in a region the team does not serve.
When it applies. Inspected target: declared service area. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T007
Location identity separation
core readiness
Keep different branches clearly identified.
Why it matters. Mixed locations can send a customer to the wrong team or address.
Illustration — fictional. Two branches share one profile with conflicting addresses and hours.
When it applies. Inspected target: branch identity record. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T008
Review solicitation integrity
core readiness
Ask for genuine reviews without filtering requests to favor happy customers.
Why it matters. Manufactured or selectively gated feedback gives a distorted picture.
Illustration — fictional. Only satisfied customers receive a review link, and positive ratings earn a gift.
When it applies. Inspected target: review solicitation workflow. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T009
Review response privacy
core readiness
Answer reviews without exposing private customer facts.
Why it matters. A public reply should solve a concern without breaking trust.
Illustration — fictional. A public dispute response exposes the customer's invoice and private account details.
When it applies. Inspected target: public review response. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T010
Local profile verification evidence
core readiness
Check listing verification in the provider account.
Why it matters. A visible public listing does not prove the owner has verified it.
Illustration — fictional. An agency calls a listing owner-verified solely because it appears publicly in Maps.
When it applies. Inspected target: profile verification-state record. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T011
Bing Places import overwrite review
Experimental — not an established ranking requirement
Review Bing Places details after an import.
Why it matters. Imported information can overwrite a branch's correct current facts.
Illustration — fictional. A corrected branch phone silently reverts after a profile import and nobody checks it.
When it applies. Inspected target: Bing Places import field comparison. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T101
Duplicate and department profile adjudication
core readiness
Distinguish duplicates from legitimately separate branches or departments.
Why it matters. Automatically merging every shared-address profile can erase a valid operation.
Illustration — fictional. Every shared-address profile is merged automatically.
When it applies. Inspected target: duplicate or department profile case. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T102
Profile address visibility
core readiness
Show an address only in a way that fits the business's operating model and provider rules.
Why it matters. A private home used for verification should not falsely appear to be a storefront.
Illustration — fictional. A service-area operator publishes a private residence as a customer storefront although customers are not served there.
When it applies. Inspected target: profile address visibility decision. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T103
Branch contact and landing-route accuracy
core readiness
Make profile links and contact routes lead to the right branch.
Why it matters. A correct name does not help if the booking page belongs to a closed location.
Illustration — fictional. The Dallas profile leads to a closed Austin branch page.
When it applies. Inspected target: branch contact route. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T104
Location page substantive accuracy
Experimental — not an established ranking requirement
Give location pages truthful, useful local details.
Why it matters. Many copied city pages must not invent offices or services.
Illustration — fictional. Fifty city pages claim staffed offices that do not exist.
When it applies. Inspected target: location landing page. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T105
Relocation and closure state propagation
core readiness
Carry moves and closures through affected pages, listings and booking routes.
Why it matters. Customers should not be invited to visit premises that have closed.
Illustration — fictional. The website announces closure but the booking route still accepts visits at the closed premises.
When it applies. Inspected target: location transition record. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T106
Secondary category accuracy
core readiness
Use secondary categories only for real permitted activities.
Why it matters. Nearby businesses do not become services your business offers.
Illustration — fictional. A hotel adds restaurant categories for nearby businesses it does not operate.
When it applies. Inspected target: secondary category set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-970.T107
Map position accuracy
core readiness
Place map pins and directions at the appropriate customer entrance.
Why it matters. A correct street address can still send visitors to a locked rear gate.
Illustration — fictional. The textual address is correct but the marker directs customers to the neighboring building.
When it applies. Inspected target: location map marker. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.