Website Design in Indianapolis: What a Lead Site Needs

Before anyone picks a layout, pull your last 30 inquiries out of the phone log, the inbox and the text thread. Write down the service each person asked for, the town they called from, and the question they led with. A Greenwood homeowner with water coming through a ceiling at 9pm and a Carmel office manager collecting quotes on a Tuesday morning want different things from the same website, and your page list should show that difference.

That log also settles arguments about copy. If eleven of those thirty callers asked whether you handle the insurance paperwork, the answer belongs near the top of the service page in plain language. Keep the log, because you'll use it again after launch to check whether the finished site answers what buyers actually ask.

Most Indianapolis service businesses land between eight and fifteen pages. Each one has a job:

• Home. What you do, where you do it and how to reach you, all readable on a phone before the first scroll.
• One page per service. Separate buying decisions get separate pages, so a roof replacement page can explain and price itself without competing with gutter work.
• Town pages for the places you genuinely drive to, with specifics about each one. Fishers, Avon, Greenwood and Noblesville deserve their own facts, including crew coverage and typical drive time.
• Proof. Projects, photos and reviews carrying enough detail that a stranger can check them.
• About. Real names, real faces, license numbers and how long you've worked in Marion and Hamilton counties.
• Contact. Phone, form, hours, service area and a sentence about what happens after someone hits submit.
• A confirmation page that loads after a submit, which is also how you count form fills later.

How to check it: open the sitemap at yourdomain.com/sitemap.xml and count the service pages against the services you sell. A site with one bundled Services page and four revenue lines has three pages missing, and a site with 40 town pages for towns you've never worked in has padding you're paying to maintain.

The page a buyer reads before calling has to survive one test: can someone outside your trade say roughly what this costs, what's included and what happens first. That means the scope in writing, the way you price the job, the usual range of timelines and the step that follows a call. A companion post on scope and pricing on a service page walks through how much to publish when every job is custom.

Write it so a person skimming on a phone gets the shape of the deal in the first screen and the detail underneath. If you'd rather sanity check the budget side before you brief anyone, the breakdown of what a small business website costs in Indiana covers the ranges you'll see in local quotes.

How to check it: hand the page to someone who has never bought your service and ask two questions. What does this cost, and what happens if I call today. If they guess wrong or shrug, the page has a gap.

Proof is the part most local sites fake and the part buyers read hardest. Project entries should name the neighborhood, the problem, the work done and the season it happened in. Photos should be yours. Review quotes should carry a first name, a town and a date, and the rating on your site should match the rating on your Business Profile.

The Federal Trade Commission's endorsement guidance is worth reading before you publish testimonials. The FTC says that “if there's a connection between an endorser and the marketer that a significant minority of consumers wouldn't expect and it would affect how they evaluate the endorsement, that connection should be disclosed clearly and conspicuously” (FTC endorsement guides). The same page warns that “delaying the posting only of negative reviews, even just by a few days, could create a biased picture of a product at any given time, which makes this practice problematic.” If you feature one standout job, the FTC says an ad using that endorser “must make clear to the audience what the generally expected results of following that same regimen are.” The practical version lives in adding proof without inflating claims.

How to check it: pick three claims on the site and ask your marketing person which document backs each one. A permit, an invoice, a dated review screenshot or a signed release all count.

A lead site gives people at least two ways to reach you and makes both work on a phone. The header phone number should be a tap to dial link. The form should ask for the smallest set of fields you can act on, then route to a phone that somebody carries, since a form sitting in an unwatched inbox produces the same revenue as a form nobody submitted. The service inquiry design playbook covers field order, routing and follow up timing.

Keep the number consistent everywhere. Google's guidance for Business Profiles says to “provide a phone number that connects to your individual business location, or provide a website that represents your individual business location” (Google Business Profile guidelines). The same page says service area businesses “can't list a 'virtual' office unless that office is staffed during business hours,” which matters if your quote includes a fake Indianapolis address to look local.

How to check it: submit your own form from a phone on cellular data, then time how long the reply takes and check whether the confirmation email lands in spam. Tap the header number and confirm it dials the line somebody answers.

Google publishes numbers here, so you can hold a designer to something concrete. On Core Web Vitals, Google says to “strive to have LCP occur within the first 2.5 seconds of the page starting to load,” to “strive to have an INP of less than 200 milliseconds,” and to “strive to have a CLS score of less than 0.1” (Google Search Central). Google frames the payoff carefully, saying this “along with other page experience aspects, aligns with what our core ranking systems seek to reward.” That's a reason to build fast pages and a reason to be suspicious of anyone promising a ranking jump from speed alone.

Mobile comes first in the literal sense. Google says it “uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking,” and tells owners, “Make sure that your mobile site contains the same content as your desktop site” (Google Search Central). Hidden accordions and trimmed mobile copy still count against you.

How to check it: run three pages through PageSpeed Insights on the mobile tab, then open the Core Web Vitals report in Search Console after launch for real visitor data. Read your own home page on a phone with one bar of service in a truck.

Google's technical requirements are short. Google “only indexes pages on the web that are accessible to the public and which don't block our crawler, Googlebot, from crawling them,” and it “only indexes pages that are served with an HTTP 200 (success) status code” (Google Search technical requirements). The same page says indexing “isn't guaranteed” even when you meet the bar, so treat this as the floor you have to clear.

Page titles carry more weight than most owners realize. Google advises that it's “important to have distinct text that describes the content of the page in the title element for each page on your site” and to “avoid vague descriptors like ‘Home’ for your home page” (Google Search Central). Local business markup is the other piece. Google says “local business structured data can help pages appear in a unique Google Search result,” with name and address required and telephone, url, geo and opening hours recommended, while also stating that “Google does not guarantee that features that consume structured data will show up in search results” (Google Search Central). Get the facts right before the syntax, as the guide to structured data quality checks explains.

How to check it: search site:yourdomain.com in Google and count indexed pages against your sitemap. Read the browser tab title on three pages. Paste a service page URL into the Rich Results Test and confirm the business name, phone and hours match what your Indianapolis SEO and AEO work already publishes elsewhere.

Run the nine checks on the site you own today and write the failures down in one column. That list becomes the scope of a redesign, or the punch list for the build you're about to approve, and it keeps the conversation on outcomes both sides can measure. If you want a second read before you commit, our website design team runs the same nine checks when we scope a lead site for a local business.