Free pre-launch check
Test your survey before it reaches respondents
Send your invitation to a test address or paste the survey link. The report lists broken links, rendering problems, logic errors, accessibility barriers and unclear questions, most serious first.
- About a minute for a typical report
- No account needed
- Kept 24 h, longer with a free account
What the report checks
Invitation links
Every link and image in the email is requested and its redirects followed. The survey link is identified and opened.
Deliverability signals
SPF, DKIM and DMARC results, unsubscribe headers and unfilled merge fields in the message you actually sent.
Rendering
Screenshots at desktop and phone width, in dark mode and with images blocked, plus the checks Gmail clipping and Outlook tend to break.
Survey flow
A browser works through the survey with test answers and records dead ends, loops, skippable required questions and pages that overflow on phones.
Accessibility
Form labels, keyboard access, visible focus, contrast and error messages, tested with axe-core on every page reached.
Question wording
Double-barrelled, leading or vague questions, overlapping answer options and scales that change direction, with optional rewrites.
Every finding shows its evidence
Each item names the exact link, element or question, quotes what was found, explains the consequence and says how to fix it. You can mark findings as resolved or as an accepted risk, rerun the check and compare.
Findings are labelled by how they were found. Automated checks and browser observations decide the launch status; AI wording suggestions are capped at Medium and never block a launch on their own.
Survey link returns 404
“Start the survey” → response.questback.com/…/s/7Hx2
Why it matters
Respondents who click the invitation will see an error instead of the survey.
How to fix
Copy the respondent link again from the survey tool and make sure the survey is published and open.
How the launch status is decided
| Blocked | At least one critical issue, such as a survey that cannot be completed or a required question with no possible answer. |
|---|---|
| Needs fixes | High-severity issues remain, such as a broken invitation link, failing DKIM or a control keyboard users cannot reach. |
| Review recommended | Medium issues such as ambiguous wording, inconsistent scales or missing unsubscribe headers. |
| Ready to test | No open critical or high issues. It is a quality signal, not a guarantee of deliverability or data quality. |