Turn local SEO work into a documented pass-or-fail review for your massage practice

Use this guide when you need a documented local-search review for a solo massage therapist, a practice with several therapists, or a wellness business that offers massage. The goal is to verify public business information and website signals that you can inspect directly, not to predict a ranking outcome.

When this review is worth running

• Stale profile evidence. If no one can show when the practice last checked its Google Business Profile and the record may be 6+ months old, save a current screenshot and compare every business fact with the website and internal records. Pass/fail: pass when the public record matches current operations; fail when any client-facing fact is outdated. Severity: High for wrong contact, location, hours, or booking data. Owner: profile administrator. Corrective action: update only the inaccurate field. Validation: confirm the published profile after the change is live.
• Review-process gap. If the practice has fewer than 10 reviews, do not treat that number as a ranking threshold. Instead, inspect whether there is a consistent, policy-aware way to invite eligible clients to leave honest feedback. Pass/fail: pass when the same neutral request is available to eligible clients without gating or incentives; fail when requests are selective, coercive, or absent despite a stated business goal to collect feedback. Severity: Medium unless the process creates privacy or policy risk. Owner: practice manager. Corrective action: standardize the request and response workflow. Validation: review the live request language and a sample of public responses.
• Unverified directory presence. Gather the listings that actually represent the practice. Pass/fail: pass when relevant listings are claimed where appropriate and core business facts agree; fail when duplicate or conflicting records are visible. Severity: High for records that can misdirect a client. Owner: local SEO or operations owner. Corrective action: claim, correct, merge, or request removal as the platform allows. Validation: revisit each public listing.
• Recent business change. A move, phone change, new booking system, service-area change, ownership change, or website migration is a reason to run the checklist even if traffic appears stable. Pass/fail: pass when every public surface reflects the same current fact set; fail when old information remains discoverable. Severity: High. Owner: operations lead with technical support where needed. Corrective action: reconcile the affected records. Validation: search the practice name and inspect the main client pathways.

If the practice serves several genuine locations, document each real operating location separately and verify platform eligibility before creating or maintaining a profile or location page. A nominal market or service area does not automatically justify a dedicated page.

Organize the work into four evidence groups so a failure has a clear owner and validation method. The groups can reinforce one another, but none is a guaranteed ranking lever and none should substitute for accurate business information.

Area 1: Google Business Profile accuracy

Compare the live profile with authoritative practice records for identity, location or service area, contact details, hours, categories, services, and destinations. The earlier page referenced a 60-70% completion pattern without an external supporting source URL, so treat that figure as historical internal context that still requires source reconciliation, not as a current benchmark or Google scoring model.

Area 2: Citation and directory records

Use third-party listings to find conflicts in name, address where publicly appropriate, phone, website, and other client-facing facts. The purpose is consistency and usefulness, not accumulating listings. The related massage therapy SEO statistics resource can provide context, but every listing in this checklist still needs direct evidence.

Area 3: Review request and response controls

Inspect how eligible clients are invited to leave honest feedback and how staff respond in public. Review the linked website SEO audit guide when the problem extends beyond profile management into site content or technical implementation. Review volume, wording, and response activity should not be presented as guaranteed or official ranking factors unless documented by the platform.

Area 4: Structured data and local website basics

Validate machine-readable business facts against visible page content, then inspect mobile usability, HTTPS, crawlability, internal location information, and booking or contact paths. Structured data can reduce ambiguity for machines, but valid markup does not guarantee a search feature or map placement.

Open the live profile and the account used to manage it. Save screenshots or exports before editing so you can distinguish a verified correction from a guess.

1. Ownership and verification. Evidence required: the live profile, manager access, and the current verification prompt or status. Pass/fail: pass when the authorized business owner or delegate can manage an eligible profile; fail when ownership is unknown, duplicated, or inaccessible. Severity: High. Owner: business owner or authorized profile manager. Corrective action: use the platform's current ownership or verification workflow. The prior page used 5-10 days as a planning allowance; actual methods and timing can vary. Validation: confirm authorized access and the published profile after completion.
2. Core business facts. Evidence required: current business name, public phone, eligible address or service area, website, and client-facing hours from internal records. Pass/fail: pass when the profile reflects those facts accurately; fail when a field is stale, misleading, or unsupported. Severity: High. Owner: operations. Corrective action: correct the specific mismatch without adding promotional wording to identity fields. Validation: compare the published profile with the website contact information.
3. Categories. Evidence required: actual services offered and the category choices currently available in the interface. Pass/fail: pass when the primary category best describes the real business and secondary categories are genuinely applicable; fail when categories describe services the practice does not provide. Severity: Medium. Owner: profile manager. Corrective action: choose the closest accurate categories available. Validation: re-open the live profile and record the selected categories.
4. Business description. Evidence required: the current description, service menu, credential records that may lawfully be advertised, and applicable advertising guidance. Pass/fail: pass when the copy is factual, current, and avoids unsupported health outcomes; fail when it overstates services, qualifications, or results. Severity: High for potentially misleading claims. Owner: content owner with appropriate reviewer input. Corrective action: rewrite around verifiable services and practice facts. The earlier page cited 750 characters; confirm the current interface limit before relying on that value. Validation: review the published text against source records.
5. Images and video. Evidence required: the current media gallery and rights to use each asset. Pass/fail: pass when media accurately depicts the business and does not create privacy or consent issues; fail when assets are misleading, obsolete, unauthorized, or unrelated. Severity: Medium. Owner: practice manager or marketing owner. Corrective action: replace weak or inaccurate assets with real, authorized media. Use 10-15 as an audit inventory range from the prior page, not as a ranking quota. Validation: inspect the live gallery on desktop and mobile.
6. Regular and special hours. Evidence required: the booking calendar, staff schedule, holiday plan, and the hours shown publicly. Pass/fail: pass when clients can rely on the published hours; fail when the profile displays times the practice is not available under its stated business model. Severity: High. Owner: operations. Corrective action: update standard or special hours as appropriate. Validation: check the live profile after publishing.
7. Services. Evidence required: the current service menu and any relevant scope-of-practice or advertising constraints. Pass/fail: pass when listed services are actually offered and described without unsupported outcomes; fail when services are obsolete, unavailable, or overstated. Severity: High for misleading claims, otherwise Medium. Owner: service or clinical-content owner as appropriate. Corrective action: align the list with the current menu. Validation: compare the profile with the booking system and website.
8. Messaging or booking features. Evidence required: current profile features, staff capacity to monitor them, and the live destination or inbox. Pass/fail: pass when enabled features are supported operationally and route users correctly; fail when a feature creates an unanswered or broken client path. Severity: High for broken booking, Medium otherwise. Owner: front desk or operations. Corrective action: repair, reconfigure, or disable unsupported pathways. Validation: complete a non-sensitive test interaction.
9. Posts or updates. Evidence required: the current interface and any published updates. Pass/fail: pass when any post is accurate, current, and useful; fail when it contains expired offers, misleading claims, or broken destinations. Severity: Low to Medium. Owner: content manager. Corrective action: edit or remove stale material. The source's statement about 7 days should be treated as a historical product-detail reference until verified in the current interface, not as a posting cadence or ranking rule. Validation: inspect what users can currently see.

Directory listings are worth keeping when they accurately represent the practice on a platform that is relevant and allows the business to be listed. Do not assume a directory deserves priority merely because it is healthcare-related.

Priority 1: Review existing high-relevance records

• Healthgrades. Evidence required: an existing listing, the platform's eligibility criteria, and authoritative practice details. Pass/fail: pass when an eligible listing is accurate and controlled where possible; fail when it is wrong, duplicated, or inapplicable. Severity: High if clients can be misdirected. Owner: directory manager. Corrective action: claim or correct the record using the platform process. Validation: revisit the public listing after changes publish.
• Zocdoc. Evidence required: current platform eligibility, specialties actually offered, and any booking destination shown. Pass/fail: pass when the practice belongs on the platform and the public record is accurate; fail when availability, specialty, or booking information is misleading. Severity: High for broken booking information. Owner: operations. Corrective action: correct or discontinue an inapplicable listing. Validation: test the live user path.
• Yelp. Evidence required: the claimed or public business record, photos, contact information, and category. Pass/fail: pass when the listing accurately describes the practice; fail when identity, location, hours, or contact details conflict with authoritative records. Severity: Medium to High. Owner: local marketing owner. Corrective action: submit corrections through available controls. Validation: compare the published record with the website.
• Google Maps and Waze. Evidence required: the map pin, address or service-area representation permitted by the platform, and current business information. Pass/fail: pass when the map experience does not misdirect a client; fail when the location, phone, or hours are wrong. Severity: High. Owner: operations. Corrective action: use the relevant platform's correction process. Validation: check the live map result from a separate user view.
• State licensing directory, if one exists and applies. Evidence required: the official directory record and the therapist or business credential information permitted for public display. Pass/fail: pass when the official record is current; fail when it contains an error that can be corrected through the responsible authority. Severity: High for identity or credential inaccuracies. Owner: license holder or compliance contact. Corrective action: follow the authority's correction process. Validation: re-check the official record.

Priority 2: Select 5-8 relevant general listings for verification

Choose platforms because clients actually use them or because they serve a legitimate business-information purpose, not because a checklist says more citations are automatically better. For each selected record, evidence required is the live listing plus an authoritative business record; pass/fail is whether the core facts agree; severity is High when an error can misdirect a client and Medium for lesser inconsistencies; owner is the directory manager; corrective action is to claim, correct, merge, or remove a record as allowed; validation is a fresh public check.

Normalize meaningful facts, not typography

If one accurate record displays "123 Main Street" and another displays "123 Main St," do not claim that formatting alone creates separate businesses. Investigate substantive conflicts such as a wrong phone, incorrect suite, obsolete location, duplicate entity, or mismatched website. Evidence required: source-of-truth business records and all live listings. Pass/fail: pass when each listing points clients to the same real entity using materially correct information; fail when a listing represents a different or obsolete fact. Severity: High for client-routing errors. Owner: operations or local SEO owner. Corrective action: correct the underlying factual mismatch. Validation: revisit every affected listing after publication.

Review operations should protect client choice, avoid selective solicitation, and keep public replies free of information the practice should not disclose. HIPAA applicability depends on facts such as the entity's status and transactions, while other privacy, licensing, consumer-protection, and platform rules may also matter. This checklist cannot guarantee compliance; responsible legal, medical, or regulatory reviewers remain required where applicable.

1. Neutral review request. Evidence required: the exact email, text, card, QR destination, or in-person script used with eligible clients. Pass/fail: pass when the same process invites honest feedback without incentives, pressure, or filtering based on expected sentiment; fail when staff ask only selected happy clients or discourage criticism. Severity: High. Owner: practice manager. Corrective action: replace selective wording with a neutral request. Do not ask for a 5-star review. Validation: inspect every active request channel.
2. Privacy-safe request content. Evidence required: message templates and the fields collected before a reviewer reaches the public platform. Pass/fail: pass when the request does not prompt disclosure of diagnoses, symptoms, treatment outcomes, or other unnecessary sensitive details; fail when it solicits private health information for public posting. Severity: High. Owner: privacy or operations lead. Corrective action: remove health-outcome prompts and collect only what is necessary for the communication. Validation: send a test request to an internal account and inspect the full journey.
3. Public response workflow. Evidence required: recent responses, staff instructions, and escalation rules. Pass/fail: pass when responses stay general, professional, and do not reveal confidential session or client information; fail when staff argue facts publicly or expose sensitive details. Severity: High. Owner: designated responder. Corrective action: use a brief public acknowledgment and move sensitive resolution offline. The prior page suggested 3-5 days as an operating window; treat that as an internal service standard to evaluate, not an official ranking factor. Validation: review a sample of published responses for privacy and tone.
4. Negative-review handling. Evidence required: the review, platform policy, internal incident record when appropriate, and any draft response. Pass/fail: pass when the practice separates policy-reporting decisions from public communication and avoids retaliation or bargaining over removal; fail when compensation is conditioned on changing a review or when staff disclose private details to defend the practice. Severity: High. Owner: practice owner with specialist review when needed. Corrective action: document, assess, report only if policy grounds exist, and respond neutrally if a public reply is appropriate. Validation: confirm the final public record and retain internal documentation.
5. Measurement without invented targets. Evidence required: dated review counts, rating distribution, request logs if lawfully maintained, and source documentation for any benchmark used. Pass/fail: pass when trends are described as observations rather than ranking guarantees; fail when unsupported thresholds are presented as causes. Severity: Medium. Owner: marketing analyst or practice manager. Corrective action: label unsupported benchmarks clearly or remove them from decision rules. The source previously cited 50+ reviews and a 5-10 monthly pace without an exact supporting source URL; retain those figures only as historical statements requiring source reconciliation, not as targets. Validation: verify that reports distinguish observed review history from documented platform guidance.

Structured data should encode facts that users can also verify on the page. Treat validation as a technical quality check, not evidence that Google will award a local ranking position or special presentation.

1. Business entity markup. Evidence required: visible business identity, contact information, and the markup currently rendered. Pass/fail: pass when the selected Schema.org type and properties accurately describe the real business; fail when markup invents services, locations, credentials, or attributes not supported on the page. Severity: High for misleading data. Owner: developer or technical SEO owner. Corrective action: remove unsupported properties and align the entity representation with visible content. Validation: inspect rendered source and run an appropriate structured-data validator.
2. Organization information. Evidence required: public logo, business name, contact details, and official social profiles. Pass/fail: pass when markup points to the same organization users see; fail when it mixes personal and business entities or references obsolete profiles. Severity: Medium. Owner: developer with brand owner input. Corrective action: reconcile entity properties. Validation: compare parsed markup with visible content.
3. Address or service-area representation. Evidence required: the real operating model, public contact page, and platform eligibility rules. Pass/fail: pass when markup represents a genuine public location or appropriate business facts; fail when it fabricates locations or nominal markets. Severity: High. Owner: operations and developer. Corrective action: mark up only legitimate, useful location information. Validation: compare the page, profile, and rendered markup.
4. Opening hours. Evidence required: current client-facing schedule and rendered properties. Pass/fail: pass when machine-readable hours agree with visible hours and booking availability; fail when stale markup contradicts current operations. Severity: High. Owner: operations supplies the fact; developer implements it. Corrective action: update both visible and structured representations. Validation: check the live page and parsed data after deployment.
5. Practitioner information. Evidence required: approved public bios, credentials that may be displayed, photos with usage rights, and rendered markup. Pass/fail: pass when practitioner data is factual and appropriately public; fail when it overstates qualifications or exposes information that should not be published. Severity: High for credential misrepresentation. Owner: content or credential owner plus developer. Corrective action: remove unsupported properties and align the public bio. Validation: compare source records, visible copy, and markup.

Technical website check

Evidence required: current mobile performance data, HTTPS status, crawl/index diagnostics, and live contact or booking paths. Pass/fail: pass when the site is secure, usable on mobile, technically accessible, and its key user paths work; fail when technical faults block discovery or client actions. Severity: High for broken access or security issues, otherwise based on impact. Owner: developer. Corrective action: diagnose the specific bottleneck rather than chasing a single score. The earlier page used under 3 seconds as a speed target; treat it as a triage reference, not a guaranteed ranking threshold. Validation: retest the same pages and device conditions after remediation.

This schedule is a workload plan, not a forecast of ranking movement. Each stage has a different completion test: identity accuracy first, directory reconciliation second, implementation controls third, and recurring maintenance last.

Week 1-2: Establish the source of truth and profile accuracy (4-5 hours total)

• Profile ownership and core facts. Evidence required: authorized profile access and authoritative business records. Pass/fail: pass when identity, location or service area, phone, hours, website, and booking paths are accurate. Severity: High. Owner: operations. Corrective action: fix material mismatches first. Validation: inspect the published profile.
• Media inventory. Evidence required: current gallery and asset rights. Pass/fail: pass when media is real, current, and authorized. Severity: Medium. Owner: marketing. Corrective action: remove misleading media and fill genuine coverage gaps. Use 10-15 as the inherited audit inventory range, not a platform quota. Validation: review the live gallery on mobile.

Week 3-4: Reconcile directory records (3-4 hours)

• Listing inventory. Evidence required: search results and known directory accounts. Pass/fail: pass when relevant live listings have been identified and obvious duplicates are documented. Severity: High for conflicting location or contact data. Owner: local SEO owner. Corrective action: claim or correct eligible records. Validation: revisit each listing after publication.
• Business-fact consistency. Evidence required: the source-of-truth record and every material listing. Pass/fail: pass when users are directed to the same current practice information. Severity: High for misdirection. Owner: operations. Corrective action: resolve substantive conflicts. Validation: repeat the comparison after edits propagate.

Week 5-6: Implement structured data and review controls (3-4 hours)

• Structured-data deployment. Evidence required: visible page facts and rendered markup. Pass/fail: pass when markup validates technically and matches visible content. Severity: High for misleading data, Medium for non-critical errors. Owner: developer. Corrective action: repair invalid or unsupported properties. Validation: retest the deployed page.
• Review workflow. Evidence required: request copy, audience rules, and response guidance. Pass/fail: pass when eligible clients receive a neutral invitation without incentives or review gating and staff know how to respond without exposing sensitive details. Severity: High. Owner: practice manager. Corrective action: revise the process before scaling it. Validation: audit the live request and recent responses.

Ongoing: Reserve 1-2 hours monthly for change-driven maintenance

• Change log. Evidence required: business changes, profile edits, directory corrections, new reviews, and website releases. Pass/fail: pass when material changes trigger the relevant re-check. Severity: based on client impact. Owner: operations. Corrective action: reopen only the controls affected by the change. Validation: record a dated pass or failure with evidence.

The source previously described 4-8 weeks as an observed window for some practices to notice local visibility changes after substantial work. Because no exact supporting source URL appears in the source JSON, keep that range as historical internal context only. Measure your own impressions, profile interactions, organic visibility, calls, messages, and bookings where lawfully and reliably attributable, and do not treat the range as a promised outcome.

• Mistake 1: Treating profile completion as a numeric ranking score. The source contrasted 60% and 100% completion and paired the task with a 2-3 hours estimate, but no supporting source URL establishes those values as a Google ranking rule or guaranteed workload. Evidence required: the live profile and current business facts. Pass/fail: pass when every applicable field is accurate and useful; fail when material information is missing or wrong. Severity: High for client-routing errors. Owner: profile manager. Corrective action: correct relevant fields without chasing a completion percentage. Validation: inspect the published profile.
• Mistake 2: Confusing formatting differences with substantive citation conflicts. A record shown as "123 Main Street," another as "123 Main St," and another as "123 Main Street Suite 100" should trigger investigation, not an automatic claim that search engines see separate businesses. Evidence required: authoritative address records and the live listings. Pass/fail: pass when every listing materially identifies the same real location; fail when the suite, location, phone, entity, or website is genuinely wrong. Severity: High when a client can be misdirected. Owner: operations. Corrective action: fix the factual discrepancy. Validation: re-check the public listings.
• Mistake 3: Publishing unsupported health or outcome claims. Evidence required: profile copy, directory descriptions, website service language, credential records, and applicable advertising requirements. Pass/fail: pass when claims are accurate, supportable, within scope, and appropriately reviewed; fail when copy promises cures, guaranteed relief, or other unsupported outcomes. Severity: High. Owner: content owner with responsible professional review. Corrective action: replace unsupported claims with factual descriptions of services and qualifications. Validation: review the published copy on every affected surface.
• Mistake 4: Using public review replies to argue about private facts. Evidence required: recent review threads and staff guidance. Pass/fail: pass when replies stay general and move sensitive resolution offline; fail when they reveal or debate confidential details. Severity: High. Owner: designated responder. Corrective action: revise the response and retrain the workflow. Validation: sample future responses for adherence.
• Mistake 5: Steering review sentiment. Do not request a 5-star rating, offer benefits for favorable reviews, suppress negative feedback, or invite only people expected to praise the practice. Evidence required: every request template and staff script. Pass/fail: pass when eligible clients can give honest feedback without pressure or gating; fail when the process manipulates sentiment. Severity: High. Owner: practice manager. Corrective action: standardize neutral requests. Validation: inspect the live workflow and staff instructions.
• Mistake 6: Adding structured data without reconciling the page. The source attached a 1-2 hours setup estimate, which should be treated only as planning context because implementation complexity varies. Evidence required: visible business facts, rendered markup, and validation output. Pass/fail: pass when the markup is technically valid and factually aligned with the page; fail when it is invalid, stale, or unsupported. Severity: High for misleading entity data, otherwise Medium. Owner: developer. Corrective action: repair the page facts and markup together. Validation: re-run technical validation on the deployed page.