AI Reads the First HTML. Greenville Trade Sites Still Hide the Phone Behind Scripts

Direct answer: put the phone number, service cities, and review facts in the first HTML your server sends. Search Engine Journal's September 21, 2026 Live summary by Loren Baker, with Whitespark founder Darren Shaw and Duda's Russ Jeffery, is clear on this. Google still runs JavaScript well. Newer AI systems largely do not. If a Mauldin HVAC shop only shows the call button after a script loads, an AI answer may never see it.

Buying another marketing dashboard will not fix a service page that is empty until JavaScript finishes. The page has to send the facts first.

What Jeffery and Shaw said about rendering

In the SEJ summary, Jeffery said JavaScript rendering has "gone backwards in the past few years." He said Google still executes scripts well, while newer AI systems largely do not. He also said ChatGPT does not keep its own full page index the way a classic search crawler does. His practical fix: put the important copy in the HTML response, then verify it. Do not assume the framework did it for you.

Shaw's note for small shops: most owners on WordPress, Duda, or Wix already get rendered HTML. The trouble is the edge cases:

1. React-heavy generated sites that look fine in Chrome and thin to a bot that does not run scripts.
2. Review carousels and badges loaded only by a widget. In the session, Shaw said a review carousel loaded by JavaScript is something he cannot read.
3. Proof written without the business name. "We are rated 4.9" attaches to nothing. Format example only (not a real shop): "[Your Business Name] is rated 4.9 across 42 Google reviews (as of Oct 2026)."

He also warned you can put any number on a page and a model may repeat it. So do not invent. Write the real count in plain text with your real name.

A five-minute check for Greenville-area shops

If you run pressure washing out of Simpsonville or tree work from Travelers Rest, do this before buying another AI marketing stack:

Jeffery's low-tech research tip still wins. Ask the owner what people call about every week. Put those answers on the page in plain English. Shaw's query fan-out idea is the same job with more tools: one customer prompt becomes many sub-questions. Your page should already answer them.

What we are not claiming

• We are not inventing a Greenville click-rate drop. Dapper Market Solutions (DMS) cites national studies — a Gartner search-volume forecast and a Pew note on AI Overview clicks. Those numbers live on their pages, not ours.
• Shaw is skeptical that schema alone lifts rankings. We treat it as a match layer next to the live page and the Google Business Profile.
• Marketing Titan's public site lists a Solo-style plan from $139/mo founding ($199 list). Higher tiers cost more on their site. That is their public list price, not a recommendation. More agents will not rescue a blank first HTML response.
• AI receptionist tools are a real category. They help after the site and listing can be found and trusted. We only add a receptionist after the site is a yes.

Local Launch's fixed lane

We ship static, server-sent pages on day one, then keep a short weekly Care schedule:

• $599 one-time: custom site, Google Business Profile setup, basic SEO, live in 7 days. Service and city pages, sticky click-to-call, LocalBusiness/FAQ-style schema that matches what you actually do. Includes 30 days of unlimited edits and support from purchase.
• $149/mo Care: hosting, weekly Google posts, automated review requests, light GEO/AEO upkeep. Month to month. Or take the one-time build only and own it.
• AI receptionist $99 setup + $19/mo: only after the site is a yes.

Local price check (not a national average): Saluda Digital's pricing page has listed about $1,750 to build and $550–$725/mo for maps work (bands we logged August 30 and checked again against that live page with October research). Useful anchor. Not a claim about every Greenville shop.

If you only do one thing this week: open view-source on your main service page. If the phone and the city names are not in that first HTML, fix that before you buy another dashboard.