Chet's Lock and Key Website

A locksmith's site rebuilt around the searches that actually bring in calls: a page per service, a page per part of the metro, and every old URL redirected.

Client
Chet's Lock and Key
Role
Design, development & SEO
Screenshot of Chet's Lock and Key Website

Chet's Lock and Key has served the Kansas City metro since 1984, residential and commercial. The rebuild replaced an ageing site with a fast ASP.NET Core MVC one on .NET 9, organised around the phone call: the number is in the header, the top bar and the hero, and a free on-site estimate form backs it up.

Local search rewards specificity, so the site is deliberately granular. Seven services each have their own page, URL and title, and eight parts of the metro have their own local page. The rule enforced throughout is that only one page leads with any given search phrase, because two pages competing for the same phrase split the result between them.

The service-area pages were the place to be careful. Pages that differ only by swapping a city name read as doorway pages and can pull down a whole site, so each one carries copy specific to that place rather than a template with the name changed.

The old site's URLs were kept alive. Legacy address patterns from the previous site permanently redirect to their closest new page, which preserves the value of years of existing links rather than handing visitors a 404.

Services, service areas and FAQs are each defined once in code, and everything else follows: navigation, the footer, the services hub, the related links on area pages, the sitemap and the structured data. Adding a service is one entry and one page of copy. Business facts that the client may change, such as the website discount, the parts and labour warranty, opening hours and whether automotive work is offered, are settings rather than text scattered across pages: an eighth service page is written and waiting behind one of those switches.

Highlights

A page per service

Seven service pages, each owning its own search phrase, title and URL.

Local landing pages

Eight parts of the metro with copy specific to each, not a template with the city swapped.

Legacy URL redirects

Address patterns from the old site permanently redirected so existing links keep their value.

One source of truth

Services, areas and FAQs defined once, then flowing into nav, footer, sitemap and structured data.

Structured data

Marked up as a locksmith with address, phone, founding year, service catalog and areas served.

Answer-ready FAQs

15 general and 32 service-specific questions, marked up for search engines.

Client-controlled facts

Discount, warranty, hours and service offerings are settings, not hard-coded copy.

Estimate form

Honest delivery failures, a honeypot and per-IP rate limiting, with the phone number always offered.