A field-by-field operating guide for locksmith owners who need the profile to match real locations, dispatch coverage, services, hours, and evidence.
A locksmith Google Business Profile should describe the business that can answer, dispatch, and complete the work—not the territory or schedule the owner hopes to cover. That distinction matters for a mobile operator taking midnight lockout calls, a shop cutting keys at a counter, and a commercial specialist scheduling master-key work.
Start outside the editor with evidence. Use the locksmith SEO guide for work beyond the profile.
Working rule: do not use profile fields to test a new service, city, location, or overnight promise. Establish operational truth first; publish it second; measure each response stage separately.
Classify the real locksmith business before opening the editor
A locksmith should first identify whether it is a staffed storefront, a mobile service-area business, a hybrid, or a genuinely separate location. A virtual office, lead-generation entity, or subcontractor-only footprint is not a substitute for real operations. Record unresolved eligibility evidence and stop editing until the business model is supportable.
Google's eligibility guidance requires eligible businesses to make in-person contact with customers during stated hours and excludes lead-generation agents and online-only businesses. Its service-area guidance permits businesses that travel to customers, subject to real-location, address-display, service-area, and profile-count rules.
| Model | Evidence required | Address treatment | Profile decision | Stop or resolve |
|---|---|---|---|---|
| Staffed storefront | Customer-facing premises, stated hours, signage where applicable, counter service such as key cutting | Show only if customers are served there | One profile for that operation | Resolve whether customers can actually visit during published hours |
| Mobile/service-area | Real operating base, dispatch roster, vans or technicians, supported lockout/rekey areas | Hide when customers are not served at the address | One profile for the operating base under Google's rules | Stop if the base or in-person service cannot be evidenced |
| Hybrid | Real shop plus documented mobile dispatch | Show if the shop receives customers during stated hours | One profile describing the combined operation | Resolve mismatched shop and dispatch hours |
| Separate staffed location | Distinct real operations, staff, customer contact, and location evidence | Apply the correct treatment per location | Separate profile only when each operation independently qualifies | One van or shared phone does not establish another branch |
| Virtual office | No substitute evidence | Do not use it to manufacture a location | Unsupported as a shortcut | Return to the real operating location |
| Lead generator | Entity routes enquiries but does not perform in-person work | Not applicable | Ineligible under Google's stated rule | Do not optimize around the eligibility conflict |
| Subcontractor-only footprint | Written operating control, customer contact, and location facts remain unresolved | Do not infer an address from contractor coverage | Needs case-specific review against official guidance | Stop until the represented business is clear |
Turn operating facts into a profile plan. Review the model, services, hours, and evidence before making consequential edits.
Build a proof packet from business truth
A proof packet is a controlled internal record connecting every important profile claim to current operational evidence. It should cover the real-world name, operating location, controlled contact channels, staffed hours, dispatch coverage, supported jobs, applicable credentials, and authorized owners. It prepares the team; it does not guarantee verification or reinstatement.
- Name: documents showing the name used in the real world, without adding “24 hour,” city names, or service keywords merely for search.
- Operating location: evidence of the actual base and an explicit decision on whether customers are served there.
- Contact control: who owns the phone number, domain, website login, call routing, and recovery access.
- Hours and dispatch: the intake roster, technician coverage, holiday plan, and after-hours queue.
- Service and area: which technicians handle residential rekeys, automotive keys, commercial hardware, safe work, or emergency entry, and where.
- Credentials: the current official jurisdictional source, identifier, expiry or review date, and reviewer. Do not generalize one state's requirements nationwide.
- Governance: primary owner, backup owner, approved editors, secure storage owner, and next evidence review.
Keep customer addresses, key codes, access details, identity documents, and security-sensitive job photographs out of a general marketing folder. Do not upload sensitive evidence anywhere except an official Google flow that specifically requests it. A filename list and access-controlled source register are often enough for routine internal review.
Proof-packet checklist
| Record | What to confirm | Owner and review |
|---|---|---|
| Real-world name | Consistent current use; no search modifiers added | Owner; after a legal or branding change |
| Location and signage | Real operation; customer-facing status; signage where applicable | Operations; after a move |
| Phone and website | Business control, live routing, correct destination | Intake/web owner; monthly |
| Roster and profile owners | Staffed hours, dispatch coverage, least necessary access | Dispatch/profile owner; on staffing changes |
| Service-area rule | Maximum drive rule and job-specific exceptions | Dispatcher; each seasonal capacity change |
| Credentials | Official link, jurisdiction, date checked, expiry/review date | Qualified reviewer; before expiry |
| Secure storage | Restricted access and retention rule | Named records owner; quarterly |
Map profile fields to the locksmith service register
Every editable field should trace to a service the locksmith can currently complete. Use the real-world name, a category reflecting the core operation, accurate services, a plain description, controlled contact details, and consented images. Split the register by job type because automotive, residential, commercial, emergency, and safe work have different gates.
Start with a register before writing the description. “Emergency lockout” needs an intake and dispatch window. Residential rekeying needs the tools and stocked cylinders the technician uses. Automotive key or ignition work needs vehicle coverage and equipment. Commercial access or door-hardware work needs the appropriate skill and scheduling. Safe work should remain unsupported unless the business actually performs it.
| Job type | Urgency / customer | Skill or equipment gate | Hours and area | Credential and job record | Capacity / owner / status |
|---|---|---|---|---|---|
| Vehicle lockout | Urgent; driver or fleet | Technician and vehicle-specific capability | Dispatchable hours; roadside radius | Jurisdiction source/date; ticket band from actual job records | Weather/event window; dispatcher; supported or not |
| Residential rekey or installation | Planned or urgent; homeowner/property manager | Hardware stock and trained technician | Appointment blocks; residential service area | Local source/date; internal ticket band | Move-in/turnover window; service owner; status |
| Automotive key or ignition | Urgent/planned; owner or fleet | Supported makes, programming/cutting equipment | Technician-specific coverage | Applicable source/date; actual ticket band | Equipment and technician capacity; automotive lead; status |
| Commercial access/door hardware | Usually planned; facility manager | Commercial hardware competence and authorization | Survey/install schedule; approved properties | Applicable source/date; quoted-job band | Project window; commercial lead; status |
| Safe work | Planned/urgent; verified owner | Safe-specific competence and ownership checks | Specialist availability and travel rule | Applicable source/date; protected job record | Specialist owner; supported only when evidenced |
Ticket bands belong in the internal register. They distinguish a long-distance vehicle dispatch from a planned commercial survey. Demand metrics are unavailable.
For generic interface details, see the broader guide to optimizing Google Business Profile fields.
Set service areas and locations from dispatch reality
A locksmith service area should follow the distance technicians can reliably travel for specific jobs, not every city that looks commercially attractive. One mobile base does not become several locations. Separate profiles require genuinely separate qualifying operations. Remove aspirational areas when staffing, travel time, credentials, or job economics fail the dispatch rule.
Write a maximum-drive rule that dispatchers can apply under pressure. It might use travel time rather than miles because bridge traffic, toll routes, winter weather, or a large metro boundary can change a locksmith's real coverage. Then add job exceptions: a nearby residential lockout may be supportable while a distant low-value key copy is not; a scheduled commercial hardware survey may justify a longer trip.
- Start at the real operating base, not a rented mailing address or target-city centroid.
- Map technician coverage by staffed shift and supported job type.
- Apply jurisdiction-specific credential checks using current official sources and a qualified reviewer.
- Compare the drive rule with actual dispatch records and job-record ticket bands; do not invent a universal profitable radius.
- Stop adding a city if no eligible technician can meet the area, timing, capacity, and credential rules.
Publish hours the intake and dispatch team can honor
Profile hours must reflect when the represented business can make the stated customer contact, while internal planning should separately track storefront access, answered phones, staffed dispatch, and technician coverage. Publish “24/7” only when the operation truly supports it. An overnight voicemail or next-morning callback is after-hours handling, not continuous locksmith availability.
| Time block | Storefront | Phone answered | Dispatcher | Technician coverage | Exceptions / handling | Evidence / owner |
|---|---|---|---|---|---|---|
| Weekday day | Actual counter hours | Named intake shift | Named dispatch shift | Job types and area by technician | Commercial surveys; key-counter cutoff | Roster; operations owner |
| Evening | Open or closed | Live answer or queue | Staffed or unstaffed | Lockout/rekey/automotive limits | Long-distance or specialist stop rule | On-call roster; dispatch owner |
| Overnight | Usually closed unless evidenced | Live answer, vendor, or voicemail | Actual coverage | Actual dispatchable jobs/area | Unsupported calls queued with stated follow-up | Call logs and roster; intake owner |
| Holiday/special | Special hours | Published handling | Holiday rota | Reduced or normal coverage | Parts/supplier constraints | Holiday plan; profile owner |
Choose categories with the fewest accurate labels
Choose the most specific current primary category that describes the locksmith's verified core business—normally “Locksmith” when that exact option is available in the profile—and add only a few categories that represent other real operations. Do not copy a competitor or select a category for perceived value. Category edits may require reverification.
Google's category guidance says the category should describe what the business is, not everything it sells, and advises using few categories. Check current in-product choices because labels can change.
Use a three-part checkpoint: the category exists now; the service register supports it; and evidence shows it represents the core or a meaningful additional operation. Review the detailed Google Business Profile categories guide before a consequential change. Save the old and proposed values in the edit log because adding or changing a category may trigger verification.
Use reviews, photos, and posts without inventing proof
Ask genuine locksmith customers for reviews without incentives, publish only privacy-safe job imagery with permission, and gate every post against current staffing and service truth. Posts may be updates, offers, or events, but each one needs accurate terms and a relevant destination. Do not stage work or expose addresses, vehicles, keys, or vulnerabilities.
Google permits requests for genuine reviews but prohibits incentives. Build the request into the completed-job workflow, after the customer has received the service, without prescribing a positive rating. The review management guide covers response operations; the locksmith-specific control is to keep replies free of access details, dispute-sensitive facts, and confirmation that a property is vulnerable.
For images, favor owned exterior or storefront context, consented technician-at-work photos that reveal no bypass method, and clear team or vehicle branding where identifiers are safe to show. Google's content policy applies to profile media and posts. Never upload a customer's address, key pattern, access-control layout, alarm position, vehicle plate, or staged “before and after” evidence.
Post truth gate
| Post control | Approval question | Stop condition |
|---|---|---|
| Type and service | Is this a current update, offer, or event for supported locksmith work? | Service is unsupported or wording overstates availability |
| Area and hours | Can the correct technician serve this area in the promoted window? | No staffed dispatch coverage |
| Capacity | Do roster and stock support automotive, rekey, or commercial demand now? | Specialist, blank, cylinder, or hardware capacity is unavailable |
| Image | Who owns it, who consented, and is security-sensitive detail removed? | Ownership, consent, or safety is unclear |
| Offer and URL | Are terms, dates, exclusions, and landing-page service accurate? | Terms conflict or destination promises unsupported work |
| Approver and expiry | Who approves, and when will the post be archived or rechecked? | No accountable approver or end review |
Google says posts can be live, pending, or not approved after review. A pending post is not proof of a restriction, and a post does not establish calls or ranking. Use the posting-frequency guide for cadence decisions or the GBP post generator for drafting, but run every draft through this truth gate.
Log edits and handle restrictions through official paths
Record every material profile edit with its old value, new value, supporting evidence, editor, timestamp, reason, and observed status. Treat live, pending, and not approved as distinct states. If Google restricts access or content, use the applicable official support or appeal path without promising that reversal or submission will restore the profile.
| Field | Old → new | Reason and evidence | Editor / timestamp | Status | Next review / escalation owner |
|---|---|---|---|---|---|
| Hours | Recorded exact values | New dispatch roster and holiday plan | Named editor; ISO timestamp | Submitted, pending, live, or not approved | Date; intake owner |
| Service area | Recorded city/area change | Drive rule, technician roster, credential check | Named editor; ISO timestamp | Observed separately | Date; dispatch owner |
| Category | Recorded label change | Core-business evidence and current option | Named editor; ISO timestamp | Include any verification request | Date; profile owner |
| Description/service | Recorded wording | Updated service register | Named editor; ISO timestamp | Observed separately | Date; service owner |
Avoid changing several foundational facts at once unless the real business changed and the records support the full correction. That practice preserves a readable audit trail; it is not a method for avoiding review. Google explains that profile access or content can be restricted and provides an appeal path for eligible restrictions. Follow that current official process.
The theStacc Local SEO module supports GBP posts, review replies, citation work, and Map Pack rank tracking. Those functions do not replace ownership evidence, Google's review process, or a locksmith's operational approvals.
Put a controlled workflow around GBP work. Align profile content, review handling, citations, and rank observations with named owners.
Measure the whole path without calling a click a job
Measure each stage of a locksmith enquiry separately: impression, website click, call click, answered call, form, unique enquiry, qualified enquiry, booked job, completed job, and repeat job. Give every stage a written rule, source system, owner, and exclusions. Segment results by job, urgency, area, staffing, and evidence window.
| Stage | Written rule | Source system | Owner | Key exclusions |
|---|---|---|---|---|
| Impression | Profile impression reported in declared window | GBP performance | Profile owner | Partial days where relevant |
| Website click | Website action from profile | GBP performance / tagged analytics | Web owner | Internal tests, identifiable duplicates |
| Call click | Call action on profile | GBP performance | Profile owner | Never infer connection |
| Answered call | Unique attributable call answered under written rule | Phone/call tracking | Intake owner | Spam, tests, duplicates, invalid attribution |
| Form | Valid submitted profile-attributed form | Form analytics | Web owner | Spam, tests, duplicate submissions |
| Unique enquiry | Deduplicated person/job request | CRM or intake log | Intake owner | Vendors, employment, duplicates |
| Qualified enquiry | Meets written job, area, timing, capacity, credential rules | CRM plus dispatch log | Intake owner | Unsupported jobs/areas and rule failures |
| Booked job | Qualified request with confirmed booking | CRM/dispatch | Dispatch owner | Quotes without confirmation; dedupe reschedules |
| Completed job | Booked job marked completed under written rule | Job-management system | Operations owner | Cancellations, no-shows, tests, duplicates |
| Repeat job | New completed job from a known prior customer | CRM/job system | Operations owner | Rework under original ticket, duplicates |
Five controlled formulas
Profile click-through rate = profile website clicks plus call clicks, reported separately and optionally summed only when both components are shown ÷ profile impressions. Use the same declared 28-day window, GBP performance data, and profile owner. Exclude direction requests when absent from the numerator, identifiable internal tests, and partial days.
Answered-call rate = unique attributable profile calls answered under the written rule ÷ all unique attributable profile calls received. Use one declared 28-day window segmented by staffed and unstaffed hours, the phone or call-tracking system, and intake owner. Exclude spam, internal tests, duplicates, and calls without valid attribution.
Qualified-enquiry rate = unique profile-attributed enquiries meeting written job-type, area, timing, capacity, and credential rules ÷ all unique attributable profile enquiries in the cohort. Use a declared 28-day intake cohort, call/form analytics plus CRM or dispatch log, and intake owner. Exclude spam, vendors, employment, duplicates, unsupported jobs/areas, and out-of-rule unstaffed contacts.
Booked-job rate = unique qualified enquiries with a confirmed booking ÷ all unique qualified enquiries created in the same cohort. Use a 28-day cohort plus declared booking lag, CRM/dispatch data, and dispatch owner. Count duplicate or rescheduled bookings once; exclude unconfirmed quotes. Canceled work remains booked, not completed.
Completed-job rate = unique booked jobs marked completed under the written rule ÷ all unique booked jobs from the same cohort. Use the declared booking cohort plus completion lag, job-management/dispatch data, and operations owner. Exclude cancellations, no-shows, duplicates, tests, and jobs outside the stated attribution scope.
GA4 supports separately defined events, but the locksmith must define what each stage means. Review by residential, automotive, commercial, or safe work; urgent versus planned; service area; staffed-hours status; and evidence window. That reveals whether a problem sits in profile response, phone coverage, qualification, dispatch capacity, or job completion without claiming causation.
Frequently asked questions about locksmith profiles
Mobile operations can qualify, but the address, hours, location count, categories, and services must follow the represented business. The answers below cover decisions that commonly arise after the evidence packet is assembled. They do not replace Google's current guidance, a jurisdiction-specific credential review, or the official support and appeal process.
Can a mobile locksmith have a Google Business Profile?
Yes. Google says a business that travels to customers can be eligible when it makes in-person contact during its stated hours and operates from a real location. A mobile locksmith should configure an accurate service area, follow the address-display rules, and avoid treating each covered city as a separate location.
Should a mobile locksmith show a home address on Google?
Not when customers are not served there. Google's service-area guidance says a business that does not serve customers at its address should remove the address from the public profile. The operating location must still be real. Record the address-display decision in the proof packet before changing the profile.
Can a locksmith use a virtual office for a Business Profile?
A virtual office is not a substitute for a real operating location. Google requires service-area businesses to operate from a real location and applies specific rules to offices in co-working spaces. Do not create a profile merely to gain a pin in another city; resolve eligibility from current official guidance first.
What hours should an emergency locksmith publish?
Publish only hours during which the stated customer contact can actually occur. If calls are answered overnight but no technician is dispatchable for automotive lockouts or residential entry, do not present that period as fully available emergency service. Use special hours for holidays and document the after-hours handling rule.
What evidence should a locksmith collect before editing a profile?
Collect evidence for the real-world name, operating location, address treatment, controlled phone and website, staffed hours, dispatch coverage, supported job types, service area, authorized owners, and applicable credential sources with review dates. Store it securely; upload sensitive material only through an official Google flow that requests it.
What should a locksmith post on a Google Business Profile?
Post an accurate update, offer, or event tied to a service the locksmith can staff in the promoted area and hours. A useful post might explain scheduled commercial rekey availability or publish genuine holiday hours. Confirm image permission, offer terms, destination URL, capacity, and expiry before publishing.
Can changing a Google Business Profile category trigger verification?
Yes. Google's category guidance says adding or editing a category may require the business to verify again. Choose the most specific available primary category that represents the verified core business, keep additional categories few and accurate, and prepare the supporting business evidence before making the change.
Does a call click count as a qualified locksmith enquiry or booked job?
No. A call click records an action on the profile, not whether the call connected, matched a supported locksmith job, or became a confirmed booking. Keep call click, answered call, unique enquiry, qualified enquiry, booked job, and completed job as separate stages with separate source systems and written rules.
Put the evidence-first workflow into operation
Optimize the profile only after the business model, proof packet, service register, dispatch areas, hours, categories, and content gates agree. Assign one profile owner and named operational owners, log each material change, and review funnel stages separately. When evidence is unresolved, hold the claim—not the supporting record or the customer.
- Classify: decide whether the locksmith is storefront, mobile, hybrid, or genuinely multi-location under current official rules.
- Evidence: assemble the proof packet and secure sensitive records.
- Register: mark each residential, automotive, commercial, emergency, and safe service supported or unsupported.
- Align: set areas, hours, categories, services, description, images, and posts from the registers.
- Govern: log edits and use official paths for restrictions.
- Measure: keep profile actions, enquiries, bookings, and completed jobs separate.
Build a locksmith profile around work your team can really deliver. Bring the evidence packet, service register, and open decisions to a practical review.
Sources & references
- Google — Business eligibility and ownership guidelines
- Google — Service-area business guidelines
- Google — Business Profile category guidance
- Google — Business Profile posts
- Google — Profile content policy
- Google — Requesting and managing reviews
- Google — Profile restriction appeals
- Google Analytics — Recommended events
Rank in the Map Pack, collect reviews, and keep every location active — on autopilot.