Level 2: Fix Plan Add-on

Package ladder at a glance

Top fixes ranked

Ranked owner fixes: These are the top changes because they improve clarity before a visitor calls, books, enters location, or asks for help.

Do first: choose one primary action, explain location/request, and move one confidence detail near the mobile action. Do not add more widgets before simplifying the path.

Owner task

Copy/paste wording

Before

Layout instructions

confidence placement

Level 2 Fix Plan: Customer Voice handoff

Theme rows behind the handoff

Review sources used

Coverage boundary: Illustrative review themes only; no live review URLs are presented. Real customer reports use owner-approved review exports, official platform/API rows where available, or clean public snippets/screenshots with source dates. Deeper coverage should use owner-approved review exports, official platform APIs where available, or customer-provided screenshots/CSV rows.

Service-area/search wording

Search and local presence: Public page wording supports foundation repair, crawlspace support, settling/crack inspection, and local service-area context. City/service pages should use clearer foundation repair + service-area titles, descriptions, headings, and plain homeowner FAQ wording. No ranking, traffic, call, form, or revenue guarantee is made.

Google Business/local profile observations: The website has service/category and location signals that needs to align with Google Business listing categories, services, hours, booking link, phone, photos, and review response rhythm. Private Google Business listing insights were not accessed.

Easy-to-read and mobile-use checks

Acceptance checks

Fix Plan closeout

Search and local presence: Public page wording supports foundation repair, crawlspace support, settling/crack inspection, and local service-area context. City/service pages should use clearer foundation repair + service-area titles, descriptions, headings, and plain homeowner FAQ wording. No ranking, traffic, call, form, or revenue guarantee is made.

Google Business/local profile observations: The website has service/category and location signals that needs to align with Google Business listing categories, services, hours, booking link, phone, photos, and review response rhythm. Private Google Business listing insights were not accessed.

Owner interpretation guide

The charts show the pattern and the interpretation gives the owner and website person the next practical decision. For HarborPoint Foundation Repair, the repeated decision is not whether the site has trust or service information — it does. The repeated decision is how quickly a mobile or urgent foundation-repair visitor understands the next step before entering location, booking, calling, or choosing a service page.

Website-person handoff detail

The Fix Plan needs to be usable by a website helper without needing a meeting to decode it. The owner chooses the primary action and approves wording. The website person changes layout, helper copy, confidence placement, and mobile spacing. Both sides verify by recapturing the same desktop and phone screens.

The handoff intentionally avoids private website numbers, form submissions, calls, chats, live customer data, legal easy-to-use/readability claims, and revenue promises. If the owner later provides approved aggregate data, that belongs in a separate tracking layer, not in this public-evidence-only Fix Plan.

Fix Plan execution notes

This add-on needs to be concrete enough that a website person can make the first round of changes without guessing. The owner does not need to become a designer or Google/search specialist. The owner needs to approve the primary customer action, the helper wording, and the confidence line. The website person needs to place those items where the visitor actually decides: desktop hero, mobile first screen, location/request area, service page intro, and any sticky or floating action area.

The acceptance test is intentionally simple: if a first-time visitor cannot quickly tell what to click, why location is needed, what kind of foundation repair help is covered, and why the company is credible, the change is not done. If the screenshots show those items clearly, the fix can be marked complete and moved into the next monthly starting point.

Owner and website-person notes to prevent misread fixes

These notes are included because a visually strong report can still fail if the owner or website person misreads the action. The report is not asking the business to remove useful contact choices. It is asking the business to rank those choices. A foundation-repair visitor may prefer to call, book, or confirm local service by location. All three can remain available, but the first screen should make the safest recommended path obvious. Secondary actions should support the decision instead of competing with it.

The helper copy needs to be short and placed before the visitor has to act. For example, the Location/request explanation must not appear after the location box. It should sit beside or just under the location box so the visitor knows why the information is needed. The copy should avoid overpromising. It must not say that entering location guarantees availability, immediate dispatch, a specific arrival window, a discount, a booking, or a result. It should only explain the next step plainly.

Confidence details needs to be source-safe and close to the decision point. If a rating, review count, guarantee, or punctuality promise is used, it needs to be visible on the report date or approved by the owner. If the source changes, the wording needs to be checked again. The practical website goal is not to stuff more trust details onto the page. The goal is to put one believable reassurance line where it reduces hesitation before the visitor calls, books, or starts the request.

Search and local presence notes should stay owner-readable. The report includes title, heading, behind-the-scenes search basics, Google Business listing alignment, and tracked searches, but it should translate those terms into plain business decisions: does the page clearly say the service, does it clearly say the area, does the profile match the site, and can the same checks be repeated next month? This avoids turning the report into a technical Google/search dump while still covering the promised local-search work.

Competitor/reference comparisons needs to be used carefully. A competitor page may show a cleaner emergency message, simpler booking path, clearer service-area wording, or stronger first-screen reassurance. That is useful. It does not prove the competitor ranks higher, gets more calls, books more jobs, or has better customers. The safe use is to compare page patterns, choose what fits HarborPoint Foundation Repair, and reject anything that would add clutter, unsupported claims, or confusion.

Acceptance checks matter more than opinions. A fix is not complete because the page looks better to the website person. It is complete when the same desktop and mobile screenshots show the intended improvement: one action is visually primary, location/request is explained before data entry, the service/category is clear, one confidence detail is close to the decision point, and no new clutter hides the visitor path. If those screenshots do not prove the change, the issue stays open.

Final execution guardrails

The safest way to use this report is to make a small number of visible changes, then verify them with screenshots. The owner needs to not treat the report as a reason to rebuild the full website, add a new marketing stack, change pricing, promise faster service, or create new claims. The report is narrower and more useful than that. It identifies where a public visitor may hesitate before taking the next step, then turns that into a controlled set of website changes.

The website person needs to preserve what is already working: recognizable brand, foundation repair service fit, phone/contact findability, local service availability, and visible confidence details. The website person needs to improve what creates friction: unclear location/request purpose, competing first actions, mobile trust detail placement, and service-area wording that appears too late. Those changes are practical, reversible, and easy to verify.

The owner needs to approve wording before it goes live. Approved wording needs to be plain, short, and safe. It should explain the next step without guaranteeing availability, response time, dispatch, calls, bookings, rankings, sales, revenue, review improvement, or legal/easy-to-use/readability compliance. If the owner wants to use stronger claims, those claims need separate source evidence and approval outside this report.

The final check needs to be visual. Open the homepage and services page on desktop and phone. Confirm the main action is obvious, the location/request step is explained, the service fit is clear, confidence is near the action, and no sticky/floating element covers important copy. If those checks pass, the item can move into the next monthly starting point. If any check fails, keep the issue open and revise the page instead of calling the fix complete.

Final delivery scope

Work basis: public pages were checked from visible website evidence only. No forms were submitted, no phone call was made, no chat was opened, and no outreach was sent. This report does not guarantee calls, bookings, sales, revenue, rankings, legal disability-access compliance, review removal, rating improvement, or reputation repair. Findings are owner-facing plain-English notes based on what was visible at check time.

The report is intended to help the owner and website provider decide what to change first, how to verify it, and what to monitor next month. It is not a public ranking, customer behavior evidence, legal conclusion, or revenue forecast.