A well-built one-page site
that search engines cannot use

The number 434-942-8463 appears once, near the bottom of the home page, as plain text. There is no tel: link anywhere on the site, so on a phone it is not tappable. There is also no number in the header or the mobile menu, which means the first screen a visitor sees offers no way to reach you at all.

Septic work is an emergency category. The person searching has water where it should not be and is not going to scroll a page and retype a number.

Evidence: Rendered at a 390px viewport in a real browser: document.querySelectorAll('a[href^="tel:"]') returned 0 matches. Viewport screenshot confirms no number and no call button above the fold.

The sitemap lists 2 URLs. One is the home page. The other, /inquiry-services-page, is not linked from the menu or from anywhere in the home page markup, so a visitor can only reach it from a search result. Every item in the navigation (Our Story, Services Offered, FAQ) is an anchor that scrolls the same page.

Four services are named in a single block on the home page. None of them has a page of its own, so there is nothing for Google to rank against a search like septic inspection Bedford VA. A competitor with four service pages and three town pages has seven chances to appear where this site has one.

Evidence: pages-sitemap.xml holds 2 <loc> entries. In-browser, the home page carries 10 links total and only 4 distinct internal URLs: the home page itself plus 3 same-page anchors.

The two page titles are Home | Blue Ridge Septic and Inquiry Services Page | Blue Ridge Septic. Neither names a service, neither names a town, and the second one is the Wix page name showing through to the public.

Neither page carries a meta description, so Google writes the snippet itself from whatever sentence it finds first. That snippet is the advertisement for the click, and right now nobody is writing it.

Evidence: Parsed from the raw HTML of both pages: meta[name=description] count = 0. Titles read verbatim from <title>.

The only structured data on the site is a WebSite block holding a name and a URL. There is no LocalBusiness or Plumber markup, so the phone number, the service area, the hours and the services are invisible to the systems that build map results and AI answers.

The home page already has a Common Questions section written out in full, and it is not marked up as FAQPage. That is finished content earning nothing.

Evidence: 1 JSON-LD block found in the home page source, @type: WebSite, keys limited to @context, @type, name, url.

Measured against Google's own PageSpeed Insights API, mobile, median of three runs: a performance score of 65 and a Largest Contentful Paint of 6.8 seconds. Google's threshold for poor is 4.0 seconds.

The page pulls 194 requests and about 2.3 MB over the wire, which unpacks to 7.3 MB once decompressed, of which 148 scripts account for roughly 5,057 KB decompressed. That is the Wix template, not the photographs. The layout itself is stable and the images are already being served in modern formats, so this is a platform weight problem rather than a content problem.

The three samples came back 65, 68 and 48. A 20-point spread means any single PageSpeed screenshot of this site is meaningless on its own; we report the median.

Evidence: PageSpeed Insights API v5, mobile strategy, three runs: LCP 6,759 ms, FCP 3,164 ms, TBT 336 ms, CLS 0.0. Resource counts from performance.getEntriesByType('resource') in a real browser session.

The home page names Bedford, Lynchburg and Smith Mountain Lake, and then stops. The words Virginia and VA do not appear anywhere on the page. There is no address block, no service-area list, and no hours.

Bedford and Lynchburg both exist in several states. For a search engine trying to decide which map to place this business on, the page supplies a name, an email and an untagged phone number, and nothing that pins it to a place.

Evidence: Full rendered document.body.innerText tested against /\b(VA|Virginia)\b/: no match. No postal address string and no opening hours found in the rendered text.

The Our Story paragraph opens: At Blue Ride Septic & Grading, we're proud to be a locally owned company… The g is missing from Ridge. It is the second sentence on the page and it sits directly under a heading about honest work and quality.

Free to fix, and it is the kind of detail a homeowner comparing two quotes notices.

Evidence: Rendered body text, Our Story section: the literal string Blue Ride Septic & Grading.

Book Service and Schedule Now both leave the site for app.spectora.com/inspection-request/my-inspection-company-27eb08a6ec. The company name in that address is my-inspection-company, a placeholder rather than Blue Ridge Septic.

Two costs. The customer sees a third-party URL with a placeholder company name at the exact moment they are deciding whether to trust you, and every booking happens on a domain you do not own, so none of that activity ever counts toward brseptic.com.

Evidence: Both calls to action resolve to the same external host, read from the rendered DOM. Slug my-inspection-company-27eb08a6ec quoted verbatim. Whether that string is Spectora's default or a value typed in once is not something we can see from outside the account, so we report only what the URL says.

Of 9 images on the home page, 6 carry alt text like IMG_9875.jpeg and IMG_6302.jpeg. The hero photograph, the sunrise shot of the excavator, has an empty alt attribute.

These are real job-site photographs, which is exactly the asset most septic sites do not have. Described properly they are searchable and accessible; as camera filenames they are neither.

Evidence: Rendered img collection: 9 elements, 6 with IMG_*.jpeg alt values, 1 with an empty alt.

The server sends content-language: zh-CN on every response, while the page itself declares <html lang="en">. The two disagree.

This is a stale Wix setting rather than anything in the content. It is a one-field fix in the Wix language settings, and leaving contradictory language signals in place is an unforced error for a business that serves three Virginia towns.

Evidence: Response headers on https://www.brseptic.com/: content-language: zh-CN, against lang="en" in the document.

At a 390px viewport, 9 interactive elements measure under 44px on at least one side, which is under Apple's published 44pt minimum for a touch target.

Evidence: Measured with getBoundingClientRect() over every a and button at 390x844: 9 under 44px.

The home page runs a form asking for full name, email address and phone number. The site has two pages, and neither is a privacy policy or terms page.

Low severity because nothing is on fire, but it is a standard expectation once a form is live, and Wix will generate the page for you.

Evidence: Contact form present in the rendered DOM with required name, email and phone fields. The sitemap lists 2 URLs and neither is a policy page.

We searched for the exact phrase Blue Ridge Septic together with the word brseptic, which is the strongest possible branded query, the one a customer who already knows your name would type. Nine results came back. None of them was your website. Your Facebook page came back twice, your Better Business Bureau listing came back, and MapQuest came back. Your own domain did not appear once.

A separate site:brseptic.com query returned zero pages held in that index. We proved the check itself works by running the same query shape against a site that must return results, and it returned ten.

Two things follow. First, the site is new enough that it has not been picked up yet, which is normal at 21 days and is fixed by submitting it rather than waiting. Second, and more urgent: the top result for that branded search is Blue Ridge Septic Solutions, a different company with a similar name. Right now that name collision is being resolved in their favor because they have a website in the index and you do not.

Evidence: DuckDuckGo HTML endpoint, read in a real browser, 2026-09-19. Query "Blue Ridge Septic" brseptic: 9 results, 0 pointing at brseptic.com. Query site:brseptic.com: 0 results. Positive control site:wikipedia.org on the same endpoint minutes apart: 10 results, which proves the probe fires. This index is Bing-derived and is not Google; Google index coverage needs Search Console access, which is free and yours to grant.

Worth saying plainly, because it means the problems above are content and setup problems rather than repairs. The apex redirects to www with a single 301 and no chain. HTTPS is enforced with HSTS. robots.txt allows crawling and points at the sitemap. The sitemap is valid. A missing URL returns a real 404. Layout shift measured 0.000 across all three runs. Wix even publishes an llms.txt for AI crawlers automatically.

Nothing here needs a rebuild. The platform is fine; the site is simply unfinished.

Evidence: brseptic.com 301 to www; strict-transport-security: max-age=31556952; robots.txt 200 with Allow: / plus a Sitemap line; /llms.txt 200; a nonsense URL returns 404; CLS 0.000 from PSI.