The first version of tourdash.io/waitlist looked finished and read
like a placeholder. This is the audit that was run on it, the score it got, and every line
that changed, with the old wording next to the new so any call can be reversed.
Traffic to a waiting list comes from the social profiles in the footer, so the reader knows the pain (a showing they can't make, or a slow week for a contractor) and may never have heard the name Tour Dash. Showing services are a crowded category, so a benefit alone gets discounted; the page has to show the mechanism.
| Question | Before | After |
|---|---|---|
| What is this? | Never answered. The page assumed the reader knew Tour Dash. | The lede says what gets posted, who applies, and who decides. |
| Is it for me? | Only in the role buttons, in vague terms. | Named in the lede and in both role options, each in the reader's own situation. |
| Does it work? | No proof of any kind. | Three product facts from the landing page. |
| What happens if I act? | "The invite goes to this list first." | Nothing to set up, nothing to pay, one email when it opens near you, and a success screen that says the same. |
Ranked by what each one loses, not by how easy it is to fix.
A visitor from a short video lands on "Be first in when Tour Dash opens near you" with no idea what is opening. That is the costliest gap a page can have, because the people it loses were ready to act.
Nothing on the page could be checked. The fix is not a testimonial the page doesn't have; it is the product's own facts, which are on the landing page already.
"Join the waiting list" describes the list. "Send me the invite" describes what they get. The line under it now answers effort and spam in one breath.
"Be first in" could sit on any waiting list. The replacement is the pain line the landing page already closes on, so someone who has seen both pages hears one voice.
Any of these can be put back. The reasons are there so the call is arguable.
| Where | Before | After | Why |
|---|---|---|---|
| Headline | Be first in when Tour Dash opens near you | Stop saying no to showings you can't make | Names the pain in the agent's words, and it is the same line the landing page closes on, so the two pages sound like one product. |
| Lede | Leave your name and email and tell us whether you post jobs or take them. When Tour Dash opens where you work, the invite goes to this list first. | Post the showing, inspection or errand, and licensed agents and local contractors near the address apply to take it. You pick who goes. Tour Dash isn't open everywhere yet, so leave your name and the invite for your area comes to you first. | The old lede never said what Tour Dash is. The new one gives the mechanism, names both readers, and states the offer. |
| Proof lines | None | Nine job types, from a buyer showing to a certificate of occupancy inspection. You read who applied, with their license, rating and reviews, before you say yes. Approve someone and it's a confirmed appointment on both calendars. | Three product facts from the landing page, each checkable in the app. They answer whether it works without a testimonial the page doesn't have. |
| Secondary link | None | None. A link to the app on sample data went in and was taken out again the same night. | The decision was to keep the page to one action. Nothing on it leads away from the form. |
| Role legend | You are a | You are | Reads as a sentence with either option. |
| Agent option | You post showings, inspections and errands for someone else to cover. | You post the showings, inspections and errands you can't get to, and choose who covers them. | Adds the part the buyer cares about: they choose. |
| Contractor option | You take jobs near you: photography, staging, cleaning, locksmith, moving and more. | Agents near you book you for photography, staging, cleaning, locksmith work, moving and more. | Says who does the booking, which is the contractor's actual question. |
| Button | Join the waiting list | Send me the invite | Names what the visitor gets rather than the list they join. The sending state reads "Saving your spot". |
| Line under the button | There's no account to create yet. We only use the address to tell you when Tour Dash opens near you. | There's nothing to set up and nothing to pay. You get one email when it opens near you, and nothing else. | Answers the two worries at the point of action: effort and spam. |
| Success heading | You're on the list | Your spot is saved | Confirms the thing they asked for. The repeat case still reads "You're already on the list". |
| Success body | We'll email you at (address) when your market opens, and not for anything else. | The invite for your area goes to (address) the day Tour Dash opens there. Until then, nothing else lands in your inbox from us. | Says what happens next and when, with one link back to the home page. |
| Name error | Add your name so we know who to write to. | Add your name so the invite has someone to go to. | Ties the field to the invite instead of to us. |
| Role error | Tell us whether you post jobs or take them. | Pick agent or contractor so the invite fits what you do. | Uses the two words on the buttons. |
| Save error | Something went wrong and your details weren't saved. Try again in a moment. | Something went wrong and your spot wasn't saved. Try again in a moment. | Same promise as the button. |
Both are stated on the page as fact. If either is wrong, the wording should change.
The lede says "Tour Dash isn't open everywhere yet" and the success screen promises the invite "the day Tour Dash opens there". That was already the premise of the first draft. If sign-ups are open everywhere and the list is for something else, say what, and those two sentences get rewritten.
The footer carries the three social links and nothing else. A reader who wants to ask a question before signing up has nowhere to write. A plain contact address in the footer would close that. None was invented here; it needs the real one.