A website can look finished and still have one quiet problem that blocks a customer, breaks measurement, or keeps an important page out of search. This is a 15-minute red-flag pass, not a replacement for a full QA, accessibility, security or SEO audit.
Use it when a new site, redesign, migration or meaningful site change is close to going live.
How to run it: open the exact production URL on a phone and a computer, set a 15-minute timer, and mark each check Green, Amber, or Red. A Red finding on the core journey, payment/contact path, mobile usability, or indexability is a reason to fix the problem before deliberately sending traffic.
1. Open the exact production URL
Confirm the domain you will promote loads over HTTPS and that obvious alternate versions redirect where expected.
2. Complete the primary customer journey
Start at the homepage and do the main thing the site exists to enable: contact, book, sign up, start checkout, buy, download, or reach the key destination.
3. Test the real form / booking / checkout result
Do not stop at the success message. Confirm the submission, email, booking, payment state, or other expected result actually happens. Test one invalid input or failure state too.
4. Check the core flow on a real phone
Look for horizontal scrolling, clipped copy, overlapping controls, broken menus, unusable forms, hidden CTAs, and difficult tap targets.
5. Click the revenue- and trust-critical links
Check navigation, primary CTAs, pricing, contact/support, refund/policy links, and any page a buyer must use to decide or complete the action.
6. Run one clean-browser pass
Open the main journey in an incognito/private window or a second browser. This catches assumptions hidden by your normal cookies, cache, login state, or extensions.
7. Remove staging and placeholder residue
Search for lorem ipsum, TODO notes, test testimonials, temporary images, staging URLs, old prices, wrong contact details, or internal-only copy.
8. Verify visible offer and trust details
Compare pricing, plan/product names, limits, contact information, support/refund wording, and legal links across the pages where visitors will see them.
9. Check title, description and primary heading
Important public pages should have page-specific titles/descriptions and a clear H1 that matches the page’s purpose.
10. Check indexability and canonical signals
Make sure important live pages do not accidentally carry noindex, staging restrictions, or canonicals pointing to the wrong URL.
11. Open robots.txt and the XML sitemap
Confirm robots rules are intentional and the sitemap contains the canonical public pages you actually want search engines to discover.
12. If this is a redesign or URL change, test redirects
Open the most important old URLs and confirm they land on the intended new pages rather than 404s or irrelevant destinations.
13. Check for obvious production errors
On the key journey, watch for failed assets, broken requests, server errors, or recurring console errors. You do not need a perfect console; you do need to investigate failures that affect the visitor’s path.
14. Verify measurement before you need the data
Confirm the pageview or conversion measurement you rely on is actually firing in production, and avoid sending sensitive form content or unnecessary personal data into analytics.
15. Repeat a short smoke test after the final deployment
Recheck the homepage, primary conversion path, contact/support route, and any revenue-critical page after the production change is complete.
Decide what the result means
- Red: a critical journey, trust, revenue, mobile or indexability problem is broken. Fix it before promotion.
- Amber: not necessarily launch-blocking, but record the issue, owner and decision instead of forgetting it.
- Green: no obvious red flag was found in this 15-minute pass. It is not a guarantee that the site is defect-free, secure, accessible, compliant, or fully optimized.
Turn the check into evidence
For anything important, record the URL, check, result, screenshot or note, severity, owner, and retest status. A useful launch record is more than a row of checkmarks.
Want to see what an evidence-backed review looks like? See the Representative Website QA + SEO Action Audit Sample.
Want an independent second pair of eyes?
Website QA + SEO Action Audit — C$79 CAD
HCR reviews up to 10 publicly accessible pages and returns a concise evidence-backed report with screenshots, prioritized findings, and a practical fix list. Target delivery is within two business days after receiving the URL and priorities.
Prefer to run the fuller workflow yourself?
Website Launch QA + SEO Verification Kit — C$12.99 CAD
Use the reusable Excel workflow for a deeper launch checklist, issue log, page-level SEO checks, browser/device coverage, evidence, retests, and sign-off.
This red-flag check is an operational screening tool, not a guarantee of rankings, traffic, conversions, accessibility compliance, security, legal compliance, or a defect-free website.