Fast Glass, Inc.

Google decides who appears in the local map results using a business’s name, address and phone number. Until now the site published none of that in a form Google can read — it was on the page for people, and invisible to the machine.

Every one of your nine locations now publishes its own entry: the shop name, the town and state, the phone number for that shop, and the list of communities it covers. Reno/Sparks and Fallon also publish their street address.

This is the single change most likely to move you in the local results, because it is the thing you were missing that your competitors have.

Paste any page into Facebook, a text message or an email and it arrives as a card: the page title, a one-line description and a photo, in your own colours. Before this, all 21 pages shared as a naked web address.

For a local trade where work comes through recommendations, that is the difference between a link someone taps and one they scroll past.

Each of the 21 pages now states its own real address, its title and its summary, so Google never has to guess and never treats two versions of a page as duplicates.

The site map is generated from the pages themselves rather than kept by hand, so it can no longer fall out of date when a page is added. The instructions for search engines are in place and block nothing.

Every location page and every service page carries three or four real questions with real answers — repair or replace, what glass goes where, which towns a shop covers.

They are published in the format Google uses to show an answer directly in the results, which is how a search for “can a chipped windshield be repaired” can land on you.

We deliberately did not publish your Yelp rating as review markup. Google’s rules do not allow a business to publish ratings about itself on its own site, and doing it anyway risks the listing rather than helping it.

The stars people see in the local results come from your Google Business Profile. Send us the link to it and we will connect the site to it properly.

They used to average 69 words and differ only in the town name and the phone number. Google treats a set of near-identical pages like that as filler, which is a large part of why they were sitting at seventh to ninth place.

Each one now runs 300 to 480 words about that town specifically: the county, the highways that actually run through it, the communities the shop covers, and three questions answered for that location. Winnemucca talks about I-80 and mine-road traffic; Las Vegas talks about what summer heat does to a chip.

None of it invents anything about your business. Where a question would need a promise we cannot make for you — how fast, how much, how far you travel — the answer says to call the shop.

Residential glass is the one area where you sell four real product lines and do not appear in search at all. The page meant to lead that section was 129 words — shorter than the four pages beneath it.

It is now a proper guide: what the four jobs actually involve, the difference between tempered, laminated and ordinary glass, where safety glass is required in a house, and what to have ready before asking for a quote.

Your current site has a page at /windshield-safety-camera-recalibration — recalibrating the cameras behind a windshield after it is replaced. The rebuild did not carry it over, and the crawl we ran captured the address but not the words on it.

That is worth fixing before anything else on this list. Almost no local competitor covers recalibration, every vehicle built since roughly 2018 with lane-keep or automatic braking needs it, and it is expensive work that people search for by name. The old address now redirects to the auto glass page so nobody hits a dead end — but a redirect is not a page.

Send us the copy from the old page and it comes back as a real one.

Your warranty and whether you offer financing appear nowhere on the site. Both are questions people ask immediately before they commit.

We left them out rather than write something plausible. Tell us what is true and they go in.

The auto glass page — the one that matters for the town searches you already rank for — had two links in its text, both to the contact form, and pointed at none of your nine locations.

Every service page now lists all nine towns by name, and every town page links back to the services, to the other shops in that state, to the reviews and to the about page. Links inside the writing more than doubled, from 109 to 265.

Search engines largely ignore menu links and pay attention to links inside the text. That is the layer that was missing.

Every internal link on the site was followed and resolves. No page is unreachable, and no page is a dead end. The deepest page is two clicks from the homepage.

The reviews page in particular used to lead nowhere — the strongest thing you have for convincing a customer, and it had no way onward. It now routes to the work it describes.

The “Company” menu — Reviews, About, Contact — only opened when a mouse hovered over it. Tablets held sideways get the desktop menu and have no mouse, so on those devices tapping it did nothing and those three pages could not be reached from the menu at all.

It now opens on a tap, closes with the Escape key, and tells screen readers whether it is open.

On a phone, the call button was 40 pixels square, under the 44 recommended for something you tap with a thumb. It is the main thing a customer with a cracked windshield does on your site.

Both it and the menu button are now 44 by 44. Nothing moved on screen — only the area that responds to a tap grew.

Every combination of text and background on the site was measured against the accessibility standard. All twelve pass, and nine of them pass the stricter level.

Forms are fully labelled, the result of sending one is announced out loud to screen readers, and the whole site can be used with a keyboard alone — with a visible outline showing where you are.

Everything above was measured directly and verified in a real browser. What has not happened is a full pass with an actual screen reader or a formal accessibility tool.

Nothing found so far suggests a problem, but that is a different claim from a clean audit, and it is worth saying which one this is.

The homepage was printing the words REPLACE_WITH_3D_ASSET — 1600×900 as visible text in the top banner, on the first screen a customer sees. It also told screen-reader users there was a photo of a technician replacing a windshield, which there was not.

And the quote form used to say “we’ve received your request and will be in touch shortly” while sending nothing at all — every enquiry quietly discarded and the customer told the opposite. That is worse than having no form.

It now tells visitors up front that online requests are not live yet and points them at the phone numbers, instead of pretending to work. Nothing is being lost, but nothing is being collected either.

Decide where you want quote requests to land — an email inbox, a form service, your own system — and it goes live with a single change.

The commercial page uses a stock photo of a building with foreign-language signage, half hidden behind bare branches. We re-cropped it to the best part of the frame, but the subject is wrong.

Real photographs of your own crews and finished jobs would do more for this page than any amount of cropping. The same is true of the top banner on the homepage, which is currently a plain colour panel where a hero image was planned.

Six photos weighed 1.4 MB between them. Two of them were tall portrait shots being squeezed into a wide slot, so most of what was downloaded was cropped away and never seen — those two alone were two thirds of the total.

They were re-cropped to the shape they are actually shown in, chosen by subject rather than by the middle of the frame, and are now delivered in a modern format at three sizes so a phone downloads a phone-sized photo. All six together now come to 293 KB.

Every page used to pause and ask Google for the fonts before it could finish drawing. That is a separate company’s server on the path between your customer and your homepage.

The two typefaces are now served from your own site and requested in advance, so the text appears without that detour.

The site is built on a framework, and that framework is about 89 KB before a single line of your own site exists — roughly 85% of what a visitor downloads.

We split the rest so each page only carries its own share, which helped by 7 to 13%. Going meaningfully below that floor would mean changing the framework, not tuning it. Worth knowing before anyone spends money trying.

Everything above was measured from the finished files. What has not been measured is how the site performs for a real visitor on a phone over a mobile network, because that needs the site to be live on its own address first.

File size predicts speed well, but it is not the same as having measured it. Run that check once the site is live.