Everything below was checked directly against your live website on July 20, 2026 — we visited it the same way Google's software does and looked at exactly what it sees. Each problem includes a small "proof" section your web person can verify, but you don't need to open those to follow along.
01
Google sees a blank page, not your business
Costing you customers
When a person opens your site, their browser downloads a large computer program that then draws the page. But when Google first looks at your site, it receives a page with no words on it at all — no "boat docks," no "Smith Lake," no photos, nothing. Google eventually runs the program and finds the content, but it does so later, less often, and less reliably.
Think of it like a billboard with a tarp over it. Drivers who stop and lift the tarp can read it — but most just drive past. That's how Google treats your site today.
Proof for your web person
$ curl https://kingboatdocks.com/
<body>
<script id="manus-runtime">…</script> ← no text, no headings, no images
</body>
JavaScript required to render: ~1 MB
The new site is built so every word and photo is right there the moment Google (or anyone) arrives — nothing to run, nothing to wait for. See the new site.
02
Your six pages all look like one page to Google
Costing you customers
You have pages for Docks, Accessories, Service, About, and Contact — but Google receives the exact same page no matter which one it asks for. Same headline, same description, identical in every way. So the Service page can never show up when someone searches "dock repair Smith Lake," and the Docks page can never show up for "triple decker boat dock." Google thinks you have one page, repeated six times.
Each page of your site should be its own fishing line in the water — one for dock building, one for repairs, one for lifts. Right now all six lines have the same hook and the same bait.
Proof for your web person
$ curl https://kingboatdocks.com/about | md5
bf376f0c2843ce3b745b0e37f3577ff4
$ curl https://kingboatdocks.com/docks | md5
bf376f0c2843ce3b745b0e37f3577ff4 ← identical response for every page
Every page of the new site has its own title and description written for what people actually search — for example, the service page is titled "Dock Service, Repair & Maintenance on Smith Lake."
03
Your site tells Google to ignore everything but the homepage
Costing you customers
Websites carry a small behind-the-scenes label that tells Google "this is the official address of this page." On your site, that label on every single page says the official address is the homepage. In plain terms, your own website is instructing Google: "Don't bother listing my Docks, Service, or About pages — they're just copies of the front page." Google obliges.
Proof for your web person
<link rel="canonical" href="https://kingboatdocks.com/" />
← this tag is served on ALL six pages
On the new site, each page correctly identifies itself, so Google is free to list all six.
04
Google has no map of your site
Costing you customers
There are two standard files every website is expected to have: one that gives search engines the rules of the road, and one that lists every page you want found — like handing Google a table of contents. Your site has neither. Worse, when Google asks for them, your site answers "found it!" and hands back a regular web page instead, which confuses the software on the other end.
Proof for your web person
$ curl -I https://kingboatdocks.com/robots.txt
HTTP 200 Content-Type: text/html (a web page, not a robots file)
$ curl -I https://kingboatdocks.com/sitemap.xml
HTTP 200 Content-Type: text/html (same — no sitemap exists)
The new site includes both files, done properly — Google gets a complete list of all six pages the moment it visits.
05
Google doesn't know you're a local business
Important
There's a standard way for a website to introduce itself to Google: "I'm a local business named King Boat Docks, here's my phone number, I serve Lewis Smith Lake, here's my Facebook page." Your site never makes that introduction. That introduction is what helps Google connect your website to your business listing, show your phone number right in search results, and surface you for "near me"-style searches around the lake.
Proof for your web person
$ curl -s https://kingboatdocks.com/ | grep -c 'application/ld+json'
0 ← no LocalBusiness structured data anywhere
Every page of the new site carries that business card for Google — your name, phone, email, service area, and Facebook page, in the exact format Google asks for.
06
Your photos are slowing the site down — and invisible in image search
Important
Your dock photos are beautiful, but they're being sent at full camera size — some close to a full megabyte each. On a phone at the lake with a weak signal, that's the difference between a page that pops up and one that makes people give up. And the files still have camera names like IMG_2008.jpg, which tells Google nothing. A photo named "triple decker boat dock smith lake" can show up when someone searches for exactly that; a photo named IMG_2008 cannot.
Proof for your web person
IMG_2115_bc63dd18.jpg 849 KB
IMG_2697_4cad3edc.jpg 762 KB
IMG_2008_2825f105.jpg 692 KB — full-size JPEGs, generic names
The new site uses the same photos, compressed to load 3–10× faster with no visible quality loss, named after what's in them (like triple-decker-boat-dock-smith-lake), and sized appropriately for phones vs. computers.
07
Dead ends on your site pretend to be real pages
Important
Type any nonsense address on your site — say, kingboatdocks.com/banana — and instead of saying "that page doesn't exist," your site says "here's a page!" Google calls these fake yeses "soft 404s." They waste the limited attention Google gives a small site and can clutter your search listings with junk addresses.
Proof for your web person
$ curl -o /dev/null -w "%{http_code}" https://kingboatdocks.com/any-fake-page
200 (should be 404)
The new site answers honestly — missing pages say so, with a friendly page that points visitors back to your docks.
08
Sharing your site on Facebook shows a borrowed, breakable preview
Important
When someone shares your website on Facebook — your main way of reaching the lake community — the preview picture doesn't come from your website. It's a screenshot stored on the servers of the company whose tool built your site. If they ever clean house, your Facebook previews go blank. The backup image your site points to is broken already: asking for it returns a web page instead of a picture.
Proof for your web person
og:image → https://files.manuscdn.com/webdev_screenshots/… (third-party CDN)
$ curl -I https://kingboatdocks.com/og-image.jpg
HTTP 200 Content-Type: text/html (not an image)
The new site hosts its own share image — your Triple Decker against the blue sky — so every Facebook share shows your best dock, forever under your control.
09
Visitors can't zoom in on their phones
Worth fixing
Your site is set up to block pinch-to-zoom on phones. Plenty of your customers are going to squint at a dock photo or a phone number and try to spread two fingers to zoom — and nothing will happen. Google specifically checks for this and counts it against a site's mobile-friendliness.
Proof for your web person
<meta name="viewport" content="… maximum-scale=1" /> ← disables pinch-zoom
Zoom works normally everywhere on the new site.
10
Small polish that adds up: no tab icon, heavy first load
Worth fixing
Your site never tells browsers what little icon to show in the tab or in Google's mobile results, so you get a generic blank instead of a King Boat Docks mark — a small trust signal, lost. And between the large program from problem #1 and three full font families loading before anything appears, the first visit feels slower than it should, especially on lake-house Wi-Fi.
Proof for your web person
$ curl -s https://kingboatdocks.com/ | grep 'rel="icon"'
(no output — no icon declared)
Fonts: 3 families × 4 weights, render-blocking, atop ~1 MB JS
The new site has a gold-on-navy "K" icon, loads only the font weights it uses, and needs almost no code at all — it appears essentially instantly.