Decide whether you need advice or execution

Write down the unresolved organic-search purchase. Do you need someone to investigate indexing problems, maintain approved service pages, implement technical changes or coordinate several outside suppliers? A document recommending improvements is different from an agreement to make those improvements.

For a therapy group, separate practice-wide work from location and service-page work. Record who verifies real addresses, service availability and public clinician credentials. An SEO supplier should not invent a location or infer that every clinician provides every advertised service.

Our SEO workflow for therapists explains the underlying operating tasks. Use that framework as background, then compare the actual people and execution responsibilities offered by each proposal. Do not purchase a second general strategy document when the unresolved need is authorized implementation.

Compare the working arrangement, not the label

An agency proposal should identify the person responsible for the engagement and which work other people or subcontractors perform. Ask who communicates with the practice, who edits content and who handles technical questions. The word agency does not establish a particular team size, backup arrangement or clinical-review capability.

A freelancer proposal should be equally explicit about availability, work performed personally and tasks referred elsewhere. A single accountable contact can be useful, but it does not mean the individual supplies development, writing, design and specialist advice within one fee.

Compare named responsibilities on the same task list. If one proposal includes implementation and the other ends with recommendations, they are not equivalent alternatives merely because both mention SEO. Mark missing dependencies before comparing price.

Test the group-practice approval queue

A group practice may need several approvals before a page can change. Someone verifies services and scheduling information; a designated clinical reviewer approves clinical descriptions; someone with publishing authority approves release. Define those roles without sending patient examples to the supplier.

Ask each candidate how it would handle a service-page correction when the practice has not yet approved the wording. A useful answer identifies the pending decision and the person responsible. It does not promise to bypass review to keep a production calendar full.

Then compare how questions are collected. A freelancer may work well with one organized practice contact. An agency may also require that same consolidation rather than separately managing every clinician. Include the practice's coordination time in either model instead of assuming the supplier absorbs it.

Establish who can actually change the website

The SEO provider may not control the site's code, hosting or publishing system. Identify whether changes require an existing developer, website vendor or practice employee. Specify who requests work, who estimates separate charges and who verifies the deployed result.

Do not interpret access to an SEO report as authority to edit the site. Conversely, granting a website permission does not authorize every proposed rewrite, tracking installation or redirect. The agreement should identify the allowed work and approval boundary.

Use the existing website-change release checklist for technical acceptance questions rather than duplicating a second release process inside the SEO proposal. Ask the candidate which checks it performs and which remain with the website supplier. Unassigned implementation is a real purchasing gap.

Evaluate evidence without accepting ranking guarantees

Google's guidance on hiring an SEO discusses hiring a company or person and evaluating proposed work. It advises against a provider that guarantees first place in search results. That supports scrutiny of both organizational models, not a recommendation that one model always wins.

Ask candidates to explain a relevant public example, their actual contribution and what the example cannot prove. Do not require confidential client accounts, private practice records or patient stories. A supplier can explain its reasoning without exposing another organization's information.

For a group practice, test whether the candidate distinguishes a real second location from a telehealth service area, and a public service-page correction from a clinical claim. Evaluate the explanation rather than treating a badge, impressive screenshot or unrelated traffic increase as proof of suitability.

Normalize the fee around the work retained

Compare the same service period, tasks and dependencies. Separate investigation, implementation, recurring maintenance and separately engaged development. Confirm how revisions, additional locations, new service pages and unexpected technical work affect the proposal.

Do not assume a freelancer's quoted rate is the whole engagement cost or that an agency retainer includes unlimited work. An apparently smaller fee may leave the practice buying implementation elsewhere. An apparently broader agreement may include work the practice does not currently need.

Build a decision sheet with each responsibility, its provider, its applicable fee and any unresolved exclusion. Include internal approval and coordination effort without assigning it an invented standard dollar value. This gives the practice a meaningful comparison without borrowing a generic industry price range that may describe a different purchase.

Keep clinical information outside the procurement process

The supplier needs approved public facts and an agreed website scope, not patient histories or access to clinical records. Use synthetic examples when evaluating a proposed content or reporting process. Do not upload patient lists, inquiry narratives, appointment exports or clinical-system records into proposal tools.

Ask what analytics and website information the supplier expects to examine. Any later access requires an explicit, limited authorization and appropriate privacy review. A vendor's general security statement does not settle whether a particular tracking configuration or information transfer is appropriate.

If the proposal includes reporting, agree on useful business-level measures and their limitations. The practice can retain identity-level records internally and supply approved aggregates where appropriate. Neither an agency contract nor a freelance arrangement changes those boundaries.

Examine continuity before it becomes an exit problem

Ask how work status, approved page copy and outstanding issues are recorded. Determine what the practice will receive if the engagement ends and which records depend on another supplier's account. Verify ownership and access against the actual agreement rather than assuming a website change belongs to the practice in every contractual sense.

An agency may or may not offer cover when a particular contact is unavailable. A freelancer may or may not have an approved continuity arrangement. Ask for the real process instead of inferring either answer from the business model.

For a group, include the person who maintains location and service information in the handoff plan. Supplier continuity is less useful if nobody inside the practice owns the facts that keep public pages accurate.

Use a bounded proposal test

Give each candidate the same fictional business brief: a therapy group has an approved service-page correction, an unresolved indexing question and a website vendor that must implement code changes. Ask the candidate to distinguish investigation, practice approval, implementation and verification. Do not include patient details or grant access for this comparison.

Compare the resulting responsibility map, not presentation length. Which dependencies are accepted? Which require a separate agreement? What happens if the practice cannot approve a page or the website vendor cannot implement a recommendation?

Choose the arrangement whose actual work and retained responsibilities fit the group. An agency may be appropriate for a defined coordinated scope; a freelancer may fit a narrower assignment with strong internal coordination. Neither conclusion follows from the label alone.

Compare a project with a maintenance commitment

An agency retainer and a freelancer's fixed project can differ more because of the assignment than because of the supplier model. Ask both candidates to price the same bounded starting work before deciding whether recurring support is necessary. Separate an investigation of existing pages from continuing responsibility for approved updates.

For a group practice, list the changes that actually recur: approved service changes, clinician departures, real location information and corrections to request instructions. Then identify which of those the SEO supplier will maintain, which the practice will supply and which belong to the website vendor. Do not assume every public-content change requires an SEO retainer.

Discuss how unfinished work is handled if approvals or development are delayed. Will the remaining assignment be deferred, narrowed or separately quoted under the actual agreement? Do not invent a universal rollover policy for either model. A comparison is stronger when it identifies what the practice can realistically approve and release, rather than buying a promised volume of output it cannot review.

Finally, distinguish maintenance evidence from a ranking promise. A record of completed, approved work can support acceptance of an engagement without pretending that search positions are controlled deliverables.

Keep the advertising decision separate

If the unresolved need is an existing Google or Meta advertising account rather than organic-search delivery, review HMP's actual advertising scope and published management plans. Advertising management and client-paid media are separate costs; these plans are not SEO agency or freelancer prices.

For that existing-account question, request a free ad-account audit using business details only. Review scope and authorized permissions are agreed separately. The request does not authorize campaign changes, create a paid engagement or purchase SEO implementation. Keep patient information, passwords and access codes out of the inquiry.