Website Pre-Launch Audit Checklist

Format

Text Parameterized

Inputs

website_url (text) · Required

Outputs

pre_launch_audit (text)

Replace the ${…} placeholders with your values before using this prompt. See parameters and defaults below.

Audit this website before launch: ${website-url}

Review the 20 checks below. For each one, report a status (Pass, Needs attention, or Unable to verify), the evidence you found, and a specific recommended fix. Do not assume a check passes when you cannot verify it; say what additional access or manual testing is needed.

1. **Mobile display:** Check the site on a phone, from the homepage through the main action. Look for covered menus, small buttons, overflowing text, and other usability problems.
2. **Clear page purpose:** Identify the primary goal of each page, such as buying, signing up, reading, or contacting. Flag pages with unclear or competing goals.
3. **Specific calls to action:** Flag vague button labels such as “Get Started” or “Learn More.” Recommend labels that explain what happens next, such as “Buy Now,” “View Pricing,” or “Chat on WhatsApp,” where appropriate.
4. **Easy contact:** Check whether visitors can readily find the relevant contact method, such as WhatsApp, email, or a contact form. Look in the header, footer, and near primary actions.
5. **Working, relevant navigation and links:** Check menus and links for broken destinations, empty pages, or links that lead somewhere unrelated.
6. **Helpful 404 page:** Check whether a missing-page error offers a useful route back, such as a homepage link or search.
7. **Distinct page titles:** Check that each page has a descriptive, unique browser title, preferably with the page name before the brand name.
8. **Meta descriptions:** Check for a clear, human-readable summary of each important page, not a pile of keywords.
9. **Social sharing previews:** Check whether important pages have an appropriate share image, title, and preview when shared in messaging apps or social platforms.
10. **Favicon:** Check that the site has a recognizable browser-tab icon, such as the brand logo or symbol.
11. **Useful image alt text:** Check that important product, portfolio, or explanatory images have alt text describing their meaning or function rather than filenames.
12. **Readable contrast:** Look for low-contrast text and buttons, including pale text on light backgrounds. Flag any elements that may be difficult to read.
13. **Authentic proof:** Check for verifiable evidence supporting trust claims, such as genuine reviews, work samples, product photos, figures, or case studies. Do not treat unsupported claims like “trusted” or “best” as proof.
14. **Easy-to-use forms:** Check whether forms request only necessary information, clearly identify required fields, and explain errors in text rather than relying only on red color.
15. **Form-submission confirmation:** Check whether users see confirmation that their form was received, what response time to expect, and what happens next.
16. **Privacy policy:** If the site collects information through forms, analytics, or a newsletter, check whether it explains what data is collected and how it is used.
17. **robots.txt and noindex rules:** Check whether robots.txt or noindex directives accidentally block important pages from search engines. Identify any uncertainty if these files or settings are inaccessible.
18. **Sitemap:** Check whether an appropriate sitemap exists and whether it includes pages intended to appear in search. Recommend submitting it to Google Search Console if that has not been done.
19. **Analytics readiness:** Check whether analytics is installed and configured to measure useful activity, such as traffic sources, page exits, and important button clicks. Do not claim tracking works unless you can verify it.
20. **Testing across devices and browsers:** Check or identify the need to test on phones, laptops, and other browsers, including Safari and older phones. Do not claim to have performed tests you could not actually run.

Finish with a concise launch-readiness summary, the highest-priority fixes to complete before publishing, and the checks that require manual testing or access you do not have.