Dave pours concrete, and Dave is a made-up name for a pattern, not a customer of ours. On a Tuesday evening he stood in a homeowner's driveway, tape measure still in hand, and said, "Just hit Schedule on my website."
The homeowner tapped it. The page flickered, and Dave's own homepage came back up. They tapped twice more, got the same flicker, shrugged, and said they'd think about it.
Dave knew what "I'll think about it" means. He just didn't know his own website had said it first.
TL;DR
- You can test every button on your site in four minutes with just your phone.
- There are five common causes of a looping button, and each one has its own fix.
- Harvard Business Review found that firms reaching a lead within an hour were nearly seven times more likely to qualify it than firms that waited longer.
- Most loops come down to one wrong link address, which often takes minutes to fix once you find it.
- While you fix it, the demo line at 605-315-3900 shows what an AI (artificial intelligence) receptionist can catch when the button fails.
The button that worked perfectly (for Dave)
That night, Dave sat in his truck and opened his site on his laptop. He clicked Schedule. The booking form loaded instantly.
He checked it twice, because he's the kind of guy who checks twice. It worked every time, and that was the problem.
**A looping button looks like it works, and that's the whole problem.** It also only misbehaves for strangers. Dave was logged in, on Wi-Fi, in a browser that already knew his site, and the homeowner was none of those.
**You test your site as the one person who already knows where everything is.** Customers aren't that person. A missing button gets noticed, but a looping one gets blamed on the customer's phone, and most people will not try a fourth time.
The four-minute phone test
So Dave grabbed his phone, which is what you should do too. Here's the exact test:
- Minute 1: Turn off Wi-Fi so you're on cell data. Open a private or incognito tab, which is a browser window that forgets your history, and type in your website.
- Minute 2: Tap every button that says Schedule, Book, Get a Quote, or Call. Do it in the menu, at the top of the page, and at the bottom.
- Minute 3: After each tap, look at the address bar. If you land on your homepage address when you expected a form, write down which button did it.
- Minute 4: Fill out the form for real, using a fake name and your own number. Then check that you actually got the message, by text, email, or both.
That last step matters more than people think. **A form that loads but never delivers is a loop with better manners.**
Dave's menu button passed. His top-of-page button passed. The big orange one in the middle of the homepage sent him straight back to the top of the homepage.
Here's where it gets interesting. One site, three Schedule buttons, and only one was broken. Which cause was it? Dave had to work down the list.
Cause 1: the link is a placeholder
Every link on a web page has a destination, called an **href**. MDN Web Docs describes the href as the part of a link that holds where it points.
When a site is being built, designers often put in a stand-in destination. A single `/` means "the front door of this site," which is your homepage. A single `#` means "the top of this same page."
If the real address never replaced the stand-in, the button goes nowhere new. **The fix:** open the button's settings in your site builder and paste in the full address of your booking page.
Dave opened the orange button's settings. The link field held a single `#`.
That was it. Someone had parked a placeholder there during the build and never came back. Dave pasted in the booking page address, saved, and ran the test again. Third button, working.
Dave got lucky. Yours may not be Cause 1, so here are the other four.
Cause 2: the page it points to moved
Sometimes the button is fine, but the page it points to is gone. Maybe someone renamed "Schedule" to "Book Online" and the old address stopped working.
Many sites handle this with a **redirect**, which is a rule that sends visitors from an old address to a new one. A sloppy redirect rule can send every old address to the homepage. The customer taps a button and lands at the front door, with no sign that anything went wrong.
**The fix:** tap the button, look at the address it lands on, and compare it to the address of your real booking page. If the two differ, change the button or fix the redirect rule so it points to the right page, not the homepage.
Cause 3: the booking tool changed its link
Many trade sites use a separate scheduling tool, and the button sends people there. Those tools sometimes change how their links work, or an account gets reset or expires.
When the old link stops working, some sites quietly fall back to the homepage. You'd never know unless you tested.
**The fix:** log into the booking tool, copy its current public link fresh, and paste it into your button. Then run the phone test again. Do this check every few months, because the tool's link can change without any notice to you.
Cause 4: the button has no link of its own
Here's a quieter one. In some page builders, a button is just a colored shape until you attach a link to it. If you never attached one, the shape may fall back on a link around it, often the logo or the whole header, and both of those lead home.
You can spot this because nothing shows up when you hover over the button on a computer. A working link usually shows its destination at the bottom of the browser when you point at it.
**The fix:** click the button in your builder and look for a field marked "link" or "address." If it's empty, add your booking page address there.
Cause 5: the button is built by a script
Some buttons aren't real links at all. A script, which is a small piece of code, creates the button and decides what happens when you tap it. If the script breaks or loads slowly, the button can fall back to a default, and the default is often the homepage.
Google Search Central says Google can follow links that are written as standard `<a>` tags with an href, which is how HTML (the code web pages are written in) normally makes a link. Buttons that depend on a script instead may not get followed by search engines. That's one more reason to prefer plain links.
**The fix:** ask whoever built your site to make the Schedule button a standard link with a real address. It's usually a small change, and it makes the button easier to test.
What Dave's loop cost him
Dave fixed the button in about the time it takes to reheat coffee. Then he did the math on the weeks it had been broken, and he didn't enjoy it.
You don't need exact numbers to see the damage. You need your own numbers, run through one short formula.
**Weekly phone taps on Schedule × share who would have booked × average job value × 4 weeks**
Here is how to fill each piece in:
- Weekly phone taps: check your site stats, or ask your site builder to pull the number of taps on that button.
- Share who would have booked: make an honest guess based on how many people who call actually book with you.
- Average job value: use your real number from your last few jobs.
- 4 weeks: that turns it into a rough monthly figure.
Run it once with a cautious guess and once with a hopeful one. The gap between those two answers is what a loop can cost you each month.
Speed makes it worse. Harvard Business Review reported that firms contacting a lead within an hour were nearly seven times more likely to qualify it than firms that waited even an hour longer. A looping button means the lead never arrives at all, so there's nobody to be fast for.
**Customers don't report broken buttons. They just stop calling.**
How we build to avoid this
LegacyForge AI is an AI-run web agency, and we build every site with the same AI systems we sell. The AI does the heavy lifting on layout and code. A human checks the taste, then taps every button on a real phone.
Our demo builds are free builds we make to show the craft. They are not paying clients, and we don't dress them up as anything else. You can see how we build and judge the buttons yourself.
Every Schedule button on a build gets the same test you just ran. That includes the last step, where we check that the form actually delivers a message to the owner. If the button or form fails, we fix it before the site goes live.
The part Dave didn't fix with a button
Back in the truck, Dave had one more thought. The orange button took him a minute to fix, but it had been broken for who knows how long, and nothing had warned him.
Buttons break again. A tool changes, a page moves, and a loop returns. **The backup for a broken button is a phone that gets answered.**
That's where our AI receptionist comes in. It picks up calls and chats around the clock, takes down the caller's name and the job, and passes it to you so you can follow up. When a Schedule button fails, a caller who taps your number still reaches someone, and a lead you would have lost becomes a message waiting for you.
You don't have to take our word for it. Call the demo line at 605-315-3900 and listen to how the receptionist handles a caller. That is the product, answering live.
What to do tonight
- First, run the four-minute test. Write down which buttons loop and where they land.
- Second, match each failure to one of the five causes above and make the fix. Most are a single field in your site builder, and a few need your web person.
- Third, set a reminder to run the test again in a few months.
If your Schedule button is sending customers in circles, visit legacyforgeai.com or call the demo line at 605-315-3900 and hear the receptionist yourself.
Questions people actually ask
How do I know if my booking button loops back to the homepage?
Open your site on your phone using cell data, tap every Schedule or Book button, and watch the address bar. If you end up on your homepage address instead of a booking form, the button is looping. The full test takes about four minutes.
How fast do I need to answer someone who asks for a booking online?
Harvard Business Review reported that firms that contacted a web lead within an hour were nearly seven times more likely to qualify that lead than firms that waited even one hour longer. A loop makes the wait infinite, because the request never reaches you.
Can a booking button work for me and still be broken for customers?
Yes. You are usually logged in, on Wi-Fi, and using a browser that remembers your site, and a customer is none of those. Test in a private tab on cell data, because that is the closest thing to a stranger's first visit.