Website that converts for Edmond, OK local services

1) The job of a local website

The job is not "looking cool". A cool site that does not get calls is not doing its job. The job of a local service website is to turn a stressed stranger into a calm caller.

That job can be broken into four simple goals:

• Make the offer clear.
• Show proof you are real.
• Use copy that reduces doubt.
• Make contact easy.

That is what turns visits into calls in Edmond, OK.

1.5) How people read service websites (they scan)

Most visitors do not read your whole page. They scan for a few things: "Do you do my job?", "Do you serve my area?", "Do you look real?", and "How do I contact you?"

If your page makes them work to find those answers, they leave. If your page gives those answers quickly, they feel safe and they call.

This is why structure and copy must work together. Structure controls what people see. Copy controls what people feel.

2) Above the fold (what must be there)

Above the fold means before scrolling. Your top section should give the visitor the basics in seconds, because many visitors will decide before they scroll much at all.

Your top section should include these items:

• Headline: job + city/state
• One sentence offer (what you do and who for)
• Primary CTA (call/text or booking)
• Proof hint (review line or photo)

Most owners hide the phone number. That is a conversion leak. If a visitor has to hunt for a number, many will leave and call the next company.

2.5) Above-the-fold template (copy/paste structure)

If you want a simple pattern you can follow on your homepage and service pages, use this:

• Headline: "{Job} in {City}, {State}"
• 1-sentence offer: what you do, who it is for, and what happens next.
• Primary CTA: call/text or booking.
• Secondary CTA: "Get a quote" or "See services" (optional).
• Proof hint: a short review line or "Rated 4.9 with 120 reviews" (if true).

Example (HVAC):

Headline: "AC repair in Edmond, OK"
Offer: "Fast diagnostics and clear options. Call or text for availability."
Proof hint: "Recent photos and real reviews."

2.6) Above-the-fold layout patterns (visual hierarchy)

Structure matters. The way you arrange above-the-fold content affects how fast visitors understand your offer. Below are three tested patterns.

Pattern 1: Center-stacked (safest for mobile)

This pattern centers everything, stacks elements vertically, and works well on all screen sizes.

• Headline (centered, large)
• One-sentence offer (centered, under headline)
• Primary CTA button (centered, large tap target)
• Secondary CTA or proof hint (centered, smaller)

Best for: service pages, contact pages, landing pages.

Pattern 2: Two-column hero (desktop + mobile friendly)

This pattern splits the hero into text on the left, visual on the right. On mobile, it stacks automatically.

• Left column: headline, offer, CTA buttons
• Right column: hero image or proof photo

Best for: homepages, high-trust service pages.

Pattern 3: CTA-bar sticky (for urgent services)

This pattern places a sticky bar at the top of mobile screens with a call/text button that never leaves view.

• Sticky bar: "Call (XXX) XXX-XXXX" or "Text for quote"
• Below: headline, offer, proof

Best for: emergency plumbing, HVAC, urgent repair services.

When choosing a layout, prioritize clarity over creativity. The visitor should know what to do in under 3 seconds.

2.7) The 3 checks visitors do (and how to pass)

Most visitors do three quick checks:

1. Fit: "Do they do my job?"
2. Safety: "Do they look real and trustworthy?"
3. Ease: "Is it easy to contact them right now?"

If any one of those fails, the visitor bounces. Your job is passing all three checks quickly.

3) Clarity beats clever

Most local websites try to sound professional. They end up sounding vague. Vague copy does not convert because it forces the customer to guess.

Clear copy converts. Clear copy looks like this:

• What you do (real job words)
• Where you do it (city/state)
• What to do next (call/text/book)

That is copy. That is the job. Everything else is extra.

3.5) Offer clarity (what to say in plain language)

Offer clarity is one of the fastest conversion wins. It means a stranger can understand you quickly, without reading five pages.

A clear offer answers three things:

• What job do you do?
• Where do you do it?
• What should I do next?

If any one of those is unclear, the visitor feels unsure. When people feel unsure, they leave and call someone else.

Checklist: local offer clarity checklist →

3.6) The right tone for trades (calm and human)

The best trade copy sounds like a calm professional, not a sales pitch. Most homeowners are already stressed. If your site sounds loud, they feel more stress.

A simple tone that works is: clear, calm, helpful, and specific. You can still be confident. You just do not need hype.

If you want a good test: would you say this out loud to a customer at their kitchen table?

3.7) Plain words (the #1 copy upgrade)

Local copy works best when it sounds like a calm person, not a brochure.

Use plain words:

• Say "leak repair", not "water intrusion solutions".
• Say "call or text", not "contact us for inquiries".
• Say "we show up on time", not "we pride ourselves on punctuality".

If a word feels like something you would never say out loud, remove it.

3.8) Use job words, not "marketing words"

Customers do not search for "solutions". They search for the job they need. Your copy should match the words in their head, not the words in a marketing book.

Examples of job words:

• AC repair
• water heater replacement
• leak repair
• house washing

If you use job words, you sound more real. You also match searches better, which helps local SEO.

4) "Who this is for" (filters bad leads)

Bad leads waste time. A short "who this is for" section helps.

Examples:

• "Serving homeowners in Edmond and nearby."
• "We specialize in repairs and replacements, not handyman work."
• "We offer clear steps and calm communication."

This is not about being rude. It is about being clear. Clear pages attract better leads and reduce angry conversations about price and expectations.

4.2) Filters that reduce tire-kickers

Many owners want more leads, but what they really need is better leads. Filters help.

Examples of simple filters:

• "Best for homeowners in Edmond and nearby."
• "We do repairs and replacements. We do not do handyman work."
• "We schedule appointments. No walk-ins."
• "We explain options before any big work."

Filters reduce conflict, improve reviews, and make follow-up easier.

4.5) Trust signals (what "real" looks like)

A visitor is thinking: "Is this company real?" Your site should answer that without being loud.

Trust signals that work:

• Real job photos (not stock).
• Real reviews (and calm replies).
• Clear service area.
• Clear process ("how it works").
• Clear contact paths (call, text, book).

Trust signals that often hurt:

• Walls of vague marketing text.
• Fake-looking badges and logos.
• Hidden phone number.

5) Start with the customer's fear

People do not hesitate because they need more info. They hesitate because they feel risk. They do not want to make a bad choice, especially when it is their home.

Common fears:

• "How much will this cost?"
• "Will they show up?"
• "Will they do bad work?"
• "Will they upsell me?"

Your copy should answer those fears with simple proof and clear steps. Proof is photos and reviews. Steps are "here is what happens when you call."

5.2) The message map (your copy in 10 minutes)

If you want copy that feels clear, start with a message map. A message map is just a few short answers. You can write these on your phone.

Fill this out:

• Job: What do you do? (use job words)
• Area: Where do you do it?
• Best fit: Who are you best for?
• Process: What happens after they call?
• Proof: What proof do you have? (photos, reviews)
• Next step: Call, text, or book?

Now you have the raw material for your homepage and service pages. Most owners try to "write a website" from scratch. That is why they get stuck.

5.5) The 3-sentence offer formula

Use this on your homepage, service pages, and Google profile.

1. Sentence 1: what you do. "We do AC repair and replacement."
2. Sentence 2: where you do it. "Serving Edmond, OK and nearby."
3. Sentence 3: next step. "Call or text for availability."

Checklist version: local offer clarity checklist →

6) Proof sections (what to include)

Proof lowers fear. Add proof early on the page.

• Job photos
• Review snippets
• Real details (years, service area, what you do)

Guides:

• before/after photo guide →
• job photo checklist →

If you are not sure what proof to add first, add job photos. Job photos are the fastest trust builder because they show real work.

6.2) Proof types (use the right proof for the right fear)

Different proof answers different fears.

• Photos: "They really do this work."
• Reviews: "Other people trusted them and it went well."
• Process: "They are organized and not chaotic."
• Policies: "If something goes wrong, they will handle it."

Use a mix. But if you are starting from zero, start with photos and review requests.

Photo deep dive: before/after photo guide →

6.5) Where proof should live (so people actually see it)

Proof does not help if it is hidden at the bottom of the page. Many visitors will never scroll that far.

A simple placement pattern is:

• Small proof near the top (a short review line or 1 photo).
• A dedicated proof section in the first half of the page.
• More proof near the end for readers who want extra reassurance.

Think of proof like a seatbelt. You do not show it after the crash. You show it early so the person feels safe.

6.6) Proof layout patterns (simple blocks that work)

If you are not sure how to place proof, use these patterns:

• Pattern A (fast): 1 photo + 1 review snippet near the top, then a proof grid mid-page.
• Pattern B (service page): "What you get" bullets, then photos, then "how it works", then FAQ.
• Pattern C (high-ticket): process steps + proof + case-style story + FAQ.

Proof blocks do not need to be fancy. They need to be real and easy to scan.

6.7) Visual proof patterns (trade-specific examples)

Different trades benefit from different proof structures. Below are concrete examples.

HVAC proof block

• Before/after photo: dirty filter vs clean filter
• Review snippet: "They explained everything and fixed it fast."
• Details: "AC tune-up in Edmond this week."

Plumbing proof block

• Before/after photo: leaking pipe vs repaired pipe
• Review snippet: "Showed up on time, clear pricing, clean work."
• Details: "Leak repair under kitchen sink, Edmond."

Exterior cleaning proof block

• Before/after photo: green siding vs clean siding (split-screen works well)
• Review snippet: "Looks brand new. No damage."
• Details: "House wash in Edmond, safe low-pressure."

Landscaping proof block

• Before/after photo: overgrown yard vs trimmed and mulched
• Review snippet: "Finished early, cleaned up perfectly."
• Details: "Yard cleanup + mulch, Edmond."

Use real photos. Do not use stock images. Stock images reduce trust.

6.8) Proof stories (one paragraph that sells without hype)

A proof story is a short paragraph that shows what happened. It is not bragging. It is clarity.

Template:

"This week in Edmond, we helped a homeowner with {problem}. They were worried about {fear}. We {simple steps}. The result was {outcome}. If you're dealing with something similar, call or text and we'll tell you what to do next."

You can write these in 60 seconds after a job. They become great website proof blocks and posts.

7) Headlines that work for trades

Headlines should be boring. Boring is clear.

Templates:

• "{Job} in {City}, {State}"
• "{Job} that gets done fast (without drama)"
• "{Job} for {City} homeowners"

Examples:

• "Water heater replacement in Edmond, OK"
• "House washing in Edmond, OK"
• "AC repair in Edmond, OK"

Headlines fail when they are about you instead of the job. "We are the best" is not a job. "AC repair in Edmond" is a job.

7.2) Headline fixes (fast improvements)

If your headline is weak, fix it first. Headlines are the front door.

Common weak headlines:

• "Home"
• "Welcome to our website"
• "Quality you can trust"
• "Professional services"

Better headlines:

• "Water heater replacement in Edmond, OK"
• "Leak repair for Edmond homeowners"
• "House washing in Edmond (safe and simple)"

Simple rule: job + area + calm confidence.

7.5) Paragraph rules (so it does not feel like a robot)

Most people are reading on a phone. Big walls of text feel heavy. One-sentence paragraphs feel childish. The goal is short, clear paragraphs that feel like a normal explanation.

A simple rule is: 2 to 4 sentences per paragraph for most sections. Use bullets when you want someone to scan quickly. Use paragraphs when you want someone to understand.

7.6) Bullet rules (make it scannable)

Bullets are for scanning. Use bullets when the visitor is asking: "What do they do?" or "What do I get?"

Good bullet lists:

• Short (3 to 7 bullets)
• Job words (real)
• Concrete (no fluff)

Bad bullet lists:

• 20 bullets
• All vague ("quality", "excellence", "professional")

8) Service pages (one job per page)

Each service page should match one intent.

Checklist: service page checklist →

If you want help building service pages that are clean and consistent, see: weekly website updates →

8.2) Service page template (the closer layout)

If you build one strong service page, you can repeat the structure for other services.

Service page template:

1. Above the fold: job + city/state + call/text CTA.
2. What you do: short bullets (no fluff).
3. Proof: photos and/or review snippets.
4. How it works: 3 to 5 steps.
5. Price signals: what changes cost, how you quote.
6. FAQ: answer fears.
7. Final CTA: call/text/book.

8.3) What every service page must include

A service page is where most local leads decide. It is not a place for vague marketing words. It is a place for clear answers and proof.

A strong service page usually includes:

• A clear headline (job + city/state)
• What you do (simple bullets)
• Proof (photos and reviews)
• How it works (simple steps)
• FAQ (pricing, timing, "what happens next")
• Clear next step (call/text/book)

If you do not know what to write, use the checklist: service page checklist →

8.4) Service page HTML structure (complete template)

Below is a full HTML structure for a service page. You can copy this and replace the bracketed placeholders with your own content.

<section class="hero">
  <h1>[Service] in [City], [State]</h1>
  <p>[One-sentence offer]</p>
  <a href="tel:[phone]" class="btn">Call [phone]</a>
  <a href="sms:[phone]" class="btn secondary">Text for quote</a>
</section>

<section class="what-you-get">
  <h2>What you get</h2>
  <ul>
    <li>[Bullet 1]</li>
    <li>[Bullet 2]</li>
    <li>[Bullet 3]</li>
  </ul>
</section>

<section class="proof">
  <h2>Recent work in [City]</h2>
  <div class="photo-grid">
    <img src="[photo1.jpg]" alt="[Service] before photo">
    <img src="[photo2.jpg]" alt="[Service] after photo">
  </div>
  <blockquote>
    <p>"[Review quote]"</p>
    <cite>— [Name], [City]</cite>
  </blockquote>
</section>

<section class="how-it-works">
  <h2>How it works</h2>
  <ol>
    <li>[Step 1]</li>
    <li>[Step 2]</li>
    <li>[Step 3]</li>
  </ol>
</section>

<section class="faq">
  <h2>Common questions</h2>
  <details>
    <summary>[Question 1]</summary>
    <p>[Answer 1]</p>
  </details>
  <details>
    <summary>[Question 2]</summary>
    <p>[Answer 2]</p>
  </details>
</section>

<section class="cta-final">
  <h2>Ready to schedule?</h2>
  <a href="tel:[phone]" class="btn">Call [phone]</a>
  <a href="sms:[phone]" class="btn secondary">Text for quote</a>
</section>

This structure works for most local service pages. Adjust sections based on your specific trade and customer questions.

8.5) Service page intro (a copy/paste formula)

Use this formula for the first paragraph of a service page:

"If you need {job}, you want a clear next step. We do {job} in Edmond, OK. Call or text and tell us what you're seeing, and we'll tell you what to do next."

This works because it is calm, it uses job words, and it tells the visitor what happens next.

8.6) Service page sections (what to write in each)

Here is what to write in each service page section:

• What we do: job bullets (3 to 7).
• Who it is for: good fit and not a fit.
• Proof: photos and a few review lines.
• How it works: steps (diagnose, options, schedule, done).
• Price signals: what changes cost, how you quote.
• FAQ: answer fears.

If you get stuck, write like you talk on a real call.

8.7) Complete service page examples (3 full pages)

These are full service page copy examples. You can adapt these to your business. Keep the structure. Change the job and the details.

8.8) "What you get" bullets (easy trust)

A simple "what you get" list reduces fear because it makes the job feel normal. It shows you have a process.

Examples you can adapt:

• Clear options before any big work
• Clean work area and respectful crew
• Photos of the problem when helpful
• Simple next steps after the job is done

Keep bullets real. Do not list things you do not actually do.

8.9) "Not a fit" copy (filters bad leads without sounding rude)

"Not a fit" copy reduces bad calls. It also makes you sound honest.

Examples:

• "We do repairs and replacements. We do not do handyman work."
• "We serve Edmond and nearby. If you are outside that area, we may not be the best fit."
• "Best for homeowners who want clear options, not rushed work."

Keep it calm. The goal is less conflict and better reviews.

8.10) Price signals on service pages (reduce bad leads)

You do not have to publish exact prices. But you should reduce surprises.

Add price signals like:

• "Pricing depends on access and parts."
• "We diagnose first, then we explain options."
• "We'll tell you the range before we start."

Price signals reduce angry conversations and improve your review quality.

9) Homepage template (simple and strong)

Your homepage is usually the "trust check" page. People click it when they want to see if you look real.

A strong homepage structure:

1. Headline + offer + CTA (call/text/book).
2. Services overview (1 line each).
3. Proof block (photos + reviews).
4. How it works (simple steps).
5. Service area (list a few real places).
6. FAQ (3 to 6 questions).
7. Final CTA.

Most owners try to "tell their story" first. Put the visitor first. Save your story for the about page.

9.2) Homepage HTML structure (complete template)

Below is a full HTML structure for a homepage. Replace bracketed placeholders with your content.

<section class="hero">
  <h1>[Business type] in [City], [State]</h1>
  <p>[One-sentence offer]</p>
  <a href="tel:[phone]" class="btn">Call [phone]</a>
  <a href="/services/" class="btn secondary">See services</a>
</section>

<section class="services-overview">
  <h2>What we do</h2>
  <ul>
    <li><a href="/services/[service1]/">[Service 1]</a> — [One-line description]</li>
    <li><a href="/services/[service2]/">[Service 2]</a> — [One-line description]</li>
    <li><a href="/services/[service3]/">[Service 3]</a> — [One-line description]</li>
  </ul>
</section>

<section class="proof">
  <h2>Recent work in [City]</h2>
  <div class="photo-grid">
    <img src="[photo1.jpg]" alt="[Description]">
    <img src="[photo2.jpg]" alt="[Description]">
    <img src="[photo3.jpg]" alt="[Description]">
  </div>
  <blockquote>
    <p>"[Review 1]"</p>
    <cite>— [Name], [City]</cite>
  </blockquote>
  <blockquote>
    <p>"[Review 2]"</p>
    <cite>— [Name], [City]</cite>
  </blockquote>
</section>

<section class="how-it-works">
  <h2>How it works</h2>
  <ol>
    <li>[Step 1]</li>
    <li>[Step 2]</li>
    <li>[Step 3]</li>
    <li>[Step 4]</li>
  </ol>
</section>

<section class="service-area">
  <h2>Serving [City] and nearby</h2>
  <p>We serve [City], [Nearby city 1], [Nearby city 2], and surrounding areas.</p>
</section>

<section class="faq">
  <h2>Common questions</h2>
  <details>
    <summary>[Question 1]</summary>
    <p>[Answer 1]</p>
  </details>
  <details>
    <summary>[Question 2]</summary>
    <p>[Answer 2]</p>
  </details>
  <details>
    <summary>[Question 3]</summary>
    <p>[Answer 3]</p>
  </details>
</section>

<section class="cta-final">
  <h2>Ready to get started?</h2>
  <a href="tel:[phone]" class="btn">Call [phone]</a>
  <a href="/contact/" class="btn secondary">Contact us</a>
</section>

This structure balances clarity, proof, and ease of contact. Adjust based on your trade and customer needs.

10) "How it works" copy (a simple 4-step)

This section answers a question people do not always ask out loud: "What happens after I call?" When you answer it, the lead feels calmer.

1. You call or text. We ask a few quick questions.
2. We schedule a time that fits.
3. We show up, diagnose, and explain options.
4. We do the work and make sure it is right.

If your business works differently, change the steps. The point is to show a simple process.

10.2) Process details that remove fear

Many fears come from uncertainty. Process copy removes uncertainty.

Helpful process details:

• Do you give options?
• Do you show up in a time window?
• Do you protect floors and clean up?
• Do you explain what you found?

Only promise what you actually do. Real promises build trust. Fake promises kill reviews.

10.5) Before/after copy examples (weak vs strong)

These side-by-side examples show how small copy changes make a big difference. The structure stays the same. The words change.

11) CTA placement

CTAs should be clear and repeated.

Two resources:

• CTA placement guide →
• call/text scripts →

11.2) CTA types (use the right one for the visitor)

Not every visitor is ready for the same next step.

Common CTA types:

• Call: best for urgent jobs.
• Text: best for shy leads and photo-based quotes.
• Book: best for non-urgent scheduling.
• Email list: best for "not ready yet" visitors.
• Freebie: best for educating and staying remembered.

The best sites offer one primary CTA, then one secondary path for people who are not ready.

11.5) CTA details that increase calls

Small CTA details can change results a lot because they remove friction. This is especially true on mobile.

Simple improvements:

• Make the main CTA a call or text button.
• Use button text that says what happens.
• Repeat the CTA after proof and at the end.
• Add a short response promise during business hours.

If you want ready-to-use replies, use: call/text scripts →

11.6) Response promises (a simple line that increases leads)

A response promise is a short line near the CTA that reduces fear.

Examples:

• "Call or text. We usually reply within 10 minutes during business hours."
• "Text a photo and your address for a quick quote."
• "Booking link is for non-urgent jobs. Urgent? Call."

Do not promise something you cannot deliver. If you promise 10 minutes and you reply in 3 hours, trust drops.

11.7) CTA mistakes that kill calls

Most CTA problems are simple. The button is hidden, the text is vague, or the visitor has to think too hard about what happens next.

• Phone number only in the footer
• Buttons that say "Submit" or "Get started"
• Too many choices (5 different buttons)
• No response promise (people do not know when you reply)

A simple improvement is adding a line like: "Call or text. We usually reply within X minutes during business hours."

11.8) Sticky CTA on mobile (simple rule)

Many visitors will never scroll back to the top. A simple sticky call/text button can increase calls on mobile.

Rules for sticky CTAs:

• Do not cover content.
• Keep it small and clear.
• Use click-to-call.
• Do not show 3 different buttons at once.

If you have one main CTA, make it easy to use on mobile.

12) FAQ that actually closes

FAQ is not filler. FAQ is where you answer fears.

Common fears to answer:

• Pricing and what changes it
• Timing and availability
• What happens if something breaks
• How to contact you fast

Browse: FAQ library →

12.2) FAQ structure that works (short + honest)

A strong FAQ answer has:

• A one-line quick answer.
• 1 to 3 short paragraphs with details.
• A next step ("Call/text if you're not sure").

FAQ works best when it answers real call questions, not "SEO questions".

12.5) The top objections (and copy blocks that answer them)

Objections are not "sales problems". They are fear problems. Here are common objections and simple ways to answer them in your copy.

Objection 1: "How much is this?"

Copy answer: "Most repairs are in the $200 to $600 range, depending on parts and access. We diagnose first, then we explain options before any big work."

Objection 2: "Will you upsell me?"

Copy answer: "We explain what is broken and what it will cost to fix. We give you options. You decide what makes sense. We do not pressure."

Objection 3: "Will you show up?"

Copy answer: "We give you a time window. We call or text when we are on the way. If something changes, we let you know right away."

Objection 4: "How long will this take?"

Copy answer: "Most repairs take 1 to 3 hours, depending on the problem. If it is a big job, we will tell you up front."

Objection 5: "Do you guarantee your work?"

Copy answer: "Yes. We warranty labor for 1 year. Parts are covered by the manufacturer warranty."

Objection 6: "Are you licensed and insured?"

Copy answer: "Yes. We are fully licensed and insured. We can send you proof if you want to see it before we start."

Objection 7: "What if I am not happy?"

Copy answer: "Call us. If something is not right, we will come back and fix it. No argument."

Objection 8: "Do I need to be home?"

Copy answer: "For most jobs, yes. We may need to ask questions or show you what we found. If you need us to work while you are gone, we can arrange that."

Objection 9: "Can you come today?"

Copy answer: "Sometimes. Call before noon and we will do our best to fit you in. If not today, we can usually come tomorrow."

Objection 10: "Do you clean up after?"

Copy answer: "Yes. We protect floors. We clean up debris. We leave the work area cleaner than we found it."

Objection 11: "What if you find more problems?"

Copy answer: "We will show you and explain your options. Nothing happens without your approval."

Objection 12: "Will this fix it for good?"

Copy answer: "We fix it right. If the part is old, we will let you know if it might fail again soon. No surprises."

12.6) Pricing copy (honest, without locking yourself in)

People want price info because they want to avoid surprises. If you refuse to talk about price at all, you feel less trustworthy.

You do not have to publish exact pricing. You can publish price signals and explain what changes the price.

Examples:

• "Most repairs are in the $X to $Y range, depending on parts and access."
• "We diagnose first, then we explain options before any big work."
• "If a trip fee applies, we say it up front."

13) Contact page template (make it easy)

Your contact page should remove friction. Many contact pages are a dead end.

A good contact page includes:

• Click-to-call phone number.
• Click-to-text option (if you want texts).
• A short form with 3 fields.
• Your service area (simple).
• A response promise ("We reply within X minutes during business hours").

Scripts for replying fast: call/text scripts →

13.2) Contact page HTML structure (complete template)

Below is a full HTML structure for a contact page.

<section class="contact-hero">
  <h1>Contact us</h1>
  <p>Call, text, or send a message. We usually reply within [X minutes] during business hours.</p>
</section>

<section class="contact-methods">
  <h2>Get in touch</h2>
  <a href="tel:[phone]" class="btn">Call [phone]</a>
  <a href="sms:[phone]" class="btn secondary">Text [phone]</a>
</section>

<section class="contact-form">
  <h2>Send a message</h2>
  <form action="/submit-contact.php" method="post">
    <label for="name">Name</label>
    <input type="text" id="name" name="name" required>

    <label for="phone">Phone</label>
    <input type="tel" id="phone" name="phone" required>

    <label for="message">What do you need help with?</label>
    <textarea id="message" name="message" rows="4" required></textarea>

    <button type="submit">Send message</button>
  </form>
</section>

<section class="service-area">
  <h2>Service area</h2>
  <p>We serve [City], [Nearby city 1], [Nearby city 2], and surrounding areas.</p>
</section>

Keep forms short. Long forms reduce submissions.

13.5) About page template (without being cringey)

Your about page should answer: who are you, how do you work, and what should I expect?

A simple about page structure:

• Who you are (one short paragraph)
• How you work (a few bullets)
• What you care about (clean work, clear communication)
• Proof (a review or a photo)
• Next step (call/text/book)

13.6) About page HTML structure (complete template)

Below is a full HTML structure for an about page.

<section class="about-hero">
  <h1>About [Business name]</h1>
  <p>[One or two sentences about who you are and what you do]</p>
</section>

<section class="about-story">
  <h2>How we work</h2>
  <p>[One paragraph about your approach]</p>
  <ul>
    <li>[Bullet 1: what you prioritize]</li>
    <li>[Bullet 2: how you communicate]</li>
    <li>[Bullet 3: how you leave the job]</li>
  </ul>
</section>

<section class="about-proof">
  <h2>What customers say</h2>
  <blockquote>
    <p>"[Review quote]"</p>
    <cite>— [Name], [City]</cite>
  </blockquote>
</section>

<section class="about-cta">
  <h2>Ready to get started?</h2>
  <a href="tel:[phone]" class="btn">Call [phone]</a>
  <a href="/contact/" class="btn secondary">Contact us</a>
</section>

Most about pages fail because they are vague. Be specific about how you work and what makes you different.

14) Forms that don't leak leads

Most local leads want speed.

Keep forms short. Ask for:

• Name
• Phone or email
• One short "what do you need" message

Then respond fast.

14.2) Form field rules (every extra field costs leads)

Each extra form field reduces submissions. If you want more leads, remove fields.

Good default fields:

• Name
• Phone (or email)
• Message

Optional fields (only if truly needed):

• Address (for quoting)
• Service type (dropdown)
• Photo upload (helpful for some trades)

14.3) Field-by-field form optimization (reduce abandonment)

Small changes to individual form fields can increase submissions significantly.

Name field

• Use "Name" or "Your name", not "Full legal name"
• Use a single field, not separate first/last name fields
• Placeholder: "John Smith"

Phone field

• Use type="tel" so mobile keyboards show number pad
• Do not require specific formatting (let them type freely)
• Placeholder: "(405) 555-1234" or "405-555-1234"

Email field

• Use type="email" for better mobile keyboard
• If you prefer phone, make email optional
• Placeholder: "yourname@example.com"

Message field

• Use a textarea, not a single-line input
• Label it clearly: "What do you need help with?"
• Keep rows="4" or rows="5" (not too tall)
• Placeholder: "Tell us what you need"

Submit button

• Use action text: "Send message" or "Get a quote"
• Avoid generic: "Submit" or "Send"
• Make it large and easy to tap on mobile

General rules

• Use labels above fields, not placeholders as labels
• Show required fields clearly (asterisk or "required")
• Use autofocus on the first field (but not on mobile)
• Add a response promise below the button: "We usually reply within 10 minutes."

14.4) Spam protection (without hurting real leads)

Forms attract spam. But aggressive spam blockers can also block real leads.

Simple spam protections that usually work:

• A hidden "honeypot" field (bots fill it, humans do not).
• Rate limiting on the server.
• Simple validation (required fields).

If your form is getting hammered, add protection, but keep the user experience simple.

Reference: MDN: Web forms

14.5) The follow-up promise (the easiest conversion lift)

Many visitors do not submit forms because they fear being ignored.

Add a clear promise like:

"Call or text. We usually reply within X minutes during business hours."

And then actually follow through. Speed is a trust signal.

15) Mobile-first rules

• Buttons must be easy to tap.
• Phone number must be clickable.
• Text must be easy to scan.
• Proof must be visible without digging.

15.2) Mobile details that matter (small changes, big effect)

Mobile visitors are often stressed and impatient. Make the next step easy.

• Use large tap targets (buttons and links).
• Keep paragraphs short.
• Put CTAs after proof blocks.
• Keep the phone number clickable and repeated.
• Do not hide the menu behind tiny icons only.

15.3) Tap target sizing (the 48px rule)

Small buttons are hard to tap on mobile. This leads to frustrated visitors and missed calls.

The 48px rule: all tappable elements (buttons, links, form fields) should be at least 48px tall.

Common mistakes:

• Phone numbers that are plain text (not clickable)
• Buttons that are too small or too close together
• Form fields that are narrow and hard to tap into
• Dropdown menus with tiny touch targets

Simple fixes:

• Make all buttons at least 48px tall and 120px wide
• Add padding around clickable elements (at least 8px)
• Use large, clear CTA buttons (not tiny text links)
• Test on your phone before publishing

Reference: Accessible tap targets (web.dev)

15.4) Mobile typography (readable text sizes)

Text that looks fine on desktop can be too small on mobile. Small text forces zooming, which reduces conversion.

Minimum mobile text sizes:

• Body text: 16px (browsers zoom if smaller)
• Headlines: 24–32px
• Small print (footer, captions): 14px minimum

Line height rules:

• Body text: 1.5 to 1.7 line height
• Headlines: 1.2 to 1.4 line height

Paragraph width:

• Keep paragraphs under 75 characters wide on desktop
• Full-width is fine on mobile (320–428px screens)

15.5) Mobile navigation patterns (simple and clear)

Complex navigation confuses mobile visitors. Keep it simple.

Pattern 1: Sticky header with call button

A thin sticky header with logo and call button. No menu clutter.

• Logo on left
• Call button on right
• Optional: small menu icon for secondary pages

Pattern 2: Bottom nav bar (app-style)

A sticky bar at the bottom with 3–4 main actions.

• Call
• Text
• Services
• Menu

Pattern 3: Hamburger menu (use sparingly)

A hamburger icon that opens a full-screen menu. Only use if you have many pages.

• Keep menu items under 7
• Put call/text at the top of the menu
• Use clear labels (not icons only)

Best practice: prioritize call/text buttons over complex navigation. Most visitors want to contact you, not browse 10 pages.

16) Speed basics (keep it light)

Speed is a trust signal too. Slow feels sloppy.

• Lazy-load images.
• Use compressed images.
• Keep scripts minimal.
• Keep CSS shared when possible.

Official reference: Core Web Vitals (web.dev)

Free tool: PageSpeed Insights (helps you spot big image and layout problems).

16.2) Image workflow (the #1 speed mistake)

Most slow local sites are slow because of images. Huge images hurt mobile speed.

Simple rules:

• Resize images before uploading.
• Use modern formats when possible (WebP).
• Lazy-load below-the-fold images.
• Use descriptive alt text (helps accessibility and SEO).

When images are handled well, your site feels fast and professional.

Accessibility reference: MDN: Image alt text

16.3) Step-by-step image optimization (practical workflow)

Below is a simple workflow for optimizing images before uploading them to your website.

Step 1: Resize images to display size

Do not upload 4000px-wide images if they display at 800px. Resize first.

• Hero images: 1920px wide (max)
• Content images: 1200px wide (max)
• Thumbnails: 400–600px wide

Step 2: Compress images

Use a free tool to compress without losing quality.

• Free tool: Squoosh.app
• Desktop tool: ImageOptim (Mac) or FileOptimizer (Windows)

Step 3: Convert to WebP (if possible)

WebP images are 25–35% smaller than JPEG with the same quality. Most platforms support WebP now.

• Use Squoosh to convert JPEG/PNG to WebP
• Keep a JPEG fallback for older browsers (or let your platform handle it)

Step 4: Add lazy loading

Lazy loading delays loading images until the visitor scrolls near them. This speeds up initial page load.

Add loading="lazy" to image tags:

<img src="photo.webp" alt="AC repair" loading="lazy">

Do not lazy-load above-the-fold images (it hurts performance).

Step 5: Add descriptive alt text

Alt text helps accessibility and SEO. Be specific.

• Bad: "image1"
• Good: "AC condenser unit repair in Oklahoma City"

16.4) Lazy loading (simple implementation)

Lazy loading is one of the easiest speed wins. It delays loading images and videos until they are needed.

For images

Add loading="lazy" to any image below the fold:

<img src="photo.webp" alt="Plumbing repair" loading="lazy">

For iframes (YouTube embeds, maps)

Add loading="lazy" to iframes:

<iframe src="https://www.youtube.com/embed/..." loading="lazy"></iframe>

What not to lazy-load

• Above-the-fold images (hero images, logos)
• Critical CSS background images

Lazy loading is supported in all modern browsers. No JavaScript library needed.

16.5) Script optimization (cut the bloat)

Every script you add slows your site. Be ruthless about removing unnecessary scripts.

Common script bloat sources

• 10+ tracking scripts (Google, Facebook, heatmaps, chatbots)
• Unused plugins (WordPress sites often have 20+ active plugins)
• Heavy page builders (some add 500KB+ of JavaScript)
• Social media embed scripts (Facebook, Twitter, Instagram)

How to audit scripts

1. Open PageSpeed Insights and run your site
2. Look for "Reduce unused JavaScript" warnings
3. Check which scripts are loading and how large they are
4. Remove or defer non-critical scripts

Defer non-critical scripts

Add defer or async to script tags:

<script src="analytics.js" defer></script>

Use defer for scripts that need to run in order. Use async for independent scripts.

Move scripts to the footer

Load scripts at the end of the page so they do not block rendering.

16.6) Browser caching (faster repeat visits)

Browser caching stores static files (images, CSS, JavaScript) on the visitor's device. This makes repeat visits much faster.

How to enable caching

Most platforms (WordPress, Wix, Squarespace) handle caching automatically. If you use custom hosting, add cache headers.

For Apache (.htaccess)

<IfModule mod_expires.c>
  ExpiresActive On
  ExpiresByType image/jpg "access plus 1 year"
  ExpiresByType image/jpeg "access plus 1 year"
  ExpiresByType image/png "access plus 1 year"
  ExpiresByType image/webp "access plus 1 year"
  ExpiresByType text/css "access plus 1 month"
  ExpiresByType application/javascript "access plus 1 month"
</IfModule>

For Nginx (nginx.conf)

location ~* \.(jpg|jpeg|png|webp|css|js)$ {
  expires 1y;
  add_header Cache-Control "public, immutable";
}

Caching reduces server load and improves repeat-visit speed significantly.

17) Choosing a website platform (WordPress vs Wix vs Squarespace vs custom)

Platform choice matters less than structure and proof. A simple site on any platform beats a fancy site with no proof.

WordPress (most flexible, needs maintenance)

Best for: owners who want control, need custom features, or plan to hire help.

• Pros: full control, thousands of plugins, strong SEO tools, can be inexpensive
• Cons: requires updates, security maintenance, hosting setup
• Cost: $5–50/month (hosting + domain), themes and plugins vary

Wix (easiest drag-and-drop, limited flexibility)

Best for: owners who want simple setup and do not need custom functionality.

• Pros: easy drag-and-drop, hosting included, no updates needed
• Cons: limited customization, slower load times, harder to migrate later
• Cost: $16–35/month

Squarespace (clean templates, good for portfolios)

Best for: owners who want a polished look without much customization.

• Pros: beautiful templates, clean interface, hosting included
• Cons: less flexible than WordPress, more expensive than DIY options
• Cost: $16–49/month

Custom PHP or static HTML (full control, technical)

Best for: owners with coding skills or who hire a developer.

• Pros: full control, fast load times, no third-party platform lock-in
• Cons: requires technical knowledge, harder to update without code skills
• Cost: $5–20/month (hosting + domain), developer time varies

Which should you choose?

If you are not technical and want simple: Wix or Squarespace.

If you want flexibility and plan to grow: WordPress.

If you have a developer or coding skills: custom or WordPress with custom theme.

Most important: pick one and focus on structure, proof, and CTAs. Platform matters less than content quality.

18) 15 website questions from contractors (with answers)

Below are common questions local service owners ask about their websites, with short answers.

1. Do I need a custom domain or can I use a free subdomain?

Use a custom domain. Free subdomains (like yourname.wixsite.com) look unprofessional and hurt trust.

2. How many service pages should I have?

One page per service. If you do AC repair and water heater replacement, those should be two separate pages.

3. Should I show pricing on my website?

You do not need exact pricing, but you should show price signals. Explain what changes cost and how you quote.

4. How often should I update my website?

Once a week is ideal. Add photos, update reviews, or add FAQ answers. Weekly updates compound trust.

5. Do I need a blog?

Only if you can maintain it. A dead blog with posts from 2019 hurts trust. Focus on service pages and proof first.

6. Should I use stock photos or my own photos?

Use your own photos. Stock photos reduce trust because visitors can tell they are fake.

7. How long should my homepage be?

Long enough to answer the visitor's main questions. Usually 800–1500 words with proof, process, and FAQ.

8. Should I have a chat widget?

Only if you reply fast. A chat widget that goes unanswered for hours hurts conversion more than having no chat at all.

9. Do I need an SSL certificate (HTTPS)?

Yes. HTTPS is a trust signal and affects search rankings. Most platforms include SSL for free.

10. Should I use a page builder or code my site?

Use whatever you can maintain. Page builders are fine. Code is fine. What matters is clarity, proof, and speed.

11. How do I get more reviews on my website?

Ask after every job. Use: review request script →

12. Should I include my address on my website?

If you have a storefront, yes. If you work from home and do not want walk-ins, list your city and service area instead.

13. How do I make my site mobile-friendly?

Use large tap targets, short paragraphs, and clickable phone numbers. Test on your phone before publishing.

14. Should I use video on my website?

Only if it is short, real, and adds value. A 30-second job walkthrough is good. A 5-minute intro is not.

15. How do I track if my website is working?

Track calls, texts, and form submissions. Set up Google Analytics and ask every caller: "How did you hear about us?"

19) Conversion analytics (tracking what works)

You cannot improve what you do not measure. Track calls, form submissions, and visitor behavior to understand what is working.

What to track

• Phone calls (use call tracking if possible)
• Form submissions
• Text messages
• Page views (which pages get the most traffic)
• Bounce rate (how many visitors leave immediately)

Simple tracking setup

Use Google Analytics (free) or Matomo (open-source, privacy-friendly).

1. Install tracking code on all pages
2. Set up goals for form submissions
3. Track button clicks (call, text, book)
4. Review weekly: which pages convert best?

Call tracking

Call tracking assigns unique phone numbers to different pages or campaigns so you know where calls come from.

• Tools: CallRail, CallTrackingMetrics, WhatConverts
• Cost: $30–100/month

If call tracking is too expensive, ask every caller: "How did you hear about us?" and track manually.

19.2) Heatmaps and session recordings (see what visitors do)

Heatmaps show where visitors click, scroll, and hover. Session recordings show exactly how visitors use your site.

What heatmaps reveal

• Do visitors see your CTA?
• Are they clicking on non-clickable elements?
• How far do they scroll before leaving?
• Which sections get ignored?

Tools

• Hotjar: Free plan includes basic heatmaps and recordings (up to 35 daily sessions)
• Microsoft Clarity: Free, unlimited sessions, includes heatmaps and recordings
• Crazy Egg: Paid, more features, A/B testing included

How to use session recordings

1. Watch 10–20 recordings per week
2. Look for patterns: where do visitors get stuck?
3. Fix friction points (hidden CTAs, confusing sections)
4. Retest and watch new recordings

Session recordings reveal problems analytics alone cannot show. You see real confusion in real time.

19.3) A/B testing (test one change at a time)

A/B testing shows which version of a page converts better. Test headlines, CTA placement, proof blocks, and forms.

What to test

• Headline wording
• CTA button text and placement
• Form length (3 fields vs 5 fields)
• Proof placement (top vs middle)
• Page structure (long vs short)

How to run a simple test

1. Pick one element to test (example: CTA button text)
2. Create two versions (A: "Call now" vs B: "Call (405) 555-1234")
3. Split traffic 50/50 using a tool
4. Run for 2–4 weeks (until you have at least 100 conversions)
5. Pick the winner and test something else

Tools

• Google Optimize (free, integrates with Google Analytics)
• Optimizely (paid, enterprise-level)
• VWO (paid, includes heatmaps and session recordings)

Only test one change at a time. If you test multiple changes at once, you will not know which one worked.

19.4) Conversion tracking checklist (make sure you are measuring)

Use this checklist to ensure you are tracking the right things.

• [ ] Google Analytics or Matomo installed on all pages
• [ ] Form submission goals configured
• [ ] Call button clicks tracked (use event tracking)
• [ ] Text button clicks tracked
• [ ] Heatmaps or session recordings enabled (Hotjar, Clarity)
• [ ] Weekly review habit (check what is working)
• [ ] Ask every caller: "How did you hear about us?"

20) Using AI to improve your website (safe use cases)

AI can help you draft content faster, but it can also make your site sound fake. Use it for editing, not inventing.

Good AI uses:

• Rewrite a paragraph to be shorter and clearer.
• Turn your rough notes into a FAQ answer.
• Generate headline options (then pick the clearest boring one).
• Create a checklist from your process steps.

Bad AI uses:

• Making up jobs you did not do.
• Making up warranties, pricing, or licenses.
• Copying competitor text.

Safe prompt pattern:

"Rewrite this at an 8th grade reading level. Keep it calm and specific. Do not add facts. Text: [paste]"

21) Weekly updates that compound trust

Weekly updates keep the site alive and accurate.

Ideas: weekly update ideas →

Service: weekly website updates →

21.2) What to update weekly (if you do not know what to change)

Weekly updates should improve trust, clarity, or proof. You do not need a redesign.

Safe weekly updates:

• Add 3 new job photos to a service page.
• Add a new FAQ answer from a real call question.
• Rewrite one headline to be clearer.
• Add a review snippet (if it is real).
• Add one "how it works" step block.

Idea list: weekly update ideas →

22) Common layout mistakes

• Vague headline.
• Hidden phone number.
• No proof.
• No clear next step.
• Walls of text.

22.2) More mistakes (that look small but cost jobs)

• No service area mentioned anywhere.
• Only one "services" page (no service pages).
• Only email contact (no call/text).
• No response promise.
• Photos that are old and not representative.
• Copy that sounds like a template instead of a real business.

23) 30-day plan (no full redesign needed)

23.5) 90-day plan (make your website a compounding asset)

30 days fixes leaks. 90 days builds momentum.

If you want the "system" view that includes channels and follow-up, use: advanced strategy →

23.6) Website toolbox (simple tools)

Tools should make you faster, not busier.

Useful tools (with open-source options where possible):

• Images: Squoosh (free, web-based), ImageOptim (Mac), FileOptimizer (Windows)
• Analytics: Matomo (open source, privacy-friendly) or Google Analytics (free)
• Heatmaps: Microsoft Clarity (free, unlimited) or Hotjar (free tier)
• Forms: native HTML forms (simple, fast) or FormSpree (free tier)
• Automation: n8n (open source) for lead routing and follow-up
• CRM: vTiger (open source) to track leads and follow-ups
• Speed testing: PageSpeed Insights (free, Google), GTmetrix (free)

The best "tool" is a weekly habit of proof + updates.

Want this done for you?

This is the service that keeps improving your site every week:

• Weekly website updates

Where to go next

New to local marketing? Start with marketing basics →

Ready to scale? See advanced strategy →

Need help? Book a quick call or see services →