What is Website Launch Audit?
Use this as a first pass before someone else visits your site. It checks a set of website signals and gives you findings to investigate. Follow up by opening the important pages on a phone and testing the contact or checkout journey yourself; an automated report cannot tell you whether that experience works.
How to use Website Launch Audit
- Enter your homepage URLPaste the public address into Public website URL; the free audit checks that one page.
- Run the auditThe GigaTools server fetches the page, its headers, robots.txt and sitemap.xml, and runs ten launch checks.
- Work through the warningsCopy the findings, fix the rows marked as warnings and run the audit again.
Common uses
- Do a final check the day before a new site goes live
- Catch a missing canonical tag or sitemap after a redesign
- Give a client a quick list of open launch items
Frequently asked questions
How do I use Website Launch Audit?
1. Enter your homepage URL: Paste the public address into Public website URL; the free audit checks that one page. 2. Run the audit: The GigaTools server fetches the page, its headers, robots.txt and sitemap.xml, and runs ten launch checks. 3. Work through the warnings: Copy the findings, fix the rows marked as warnings and run the audit again.
What do the ten checks cover?
Response, HTTPS, page title length, meta description length, a single H1, a canonical URL, robots.txt, an XML sitemap, four common security headers and the HTML size of the page. The score is the share of checks that passed.
What are the pass thresholds?
A title up to 65 characters, a meta description up to 170 characters, exactly one H1, at least three of the four security headers, and HTML of about 500 KB or less. These are practical guidelines, not rules from Google.
What does the audit not check?
It looks at the HTML of one page only. It does not crawl other pages, load images or scripts, measure speed in a browser, test forms or checkout, or judge content quality.
How is my site accessed?
The GigaTools server requests the page and the two root files from the public internet. Private and local addresses are refused, and the audit is protected by reCAPTCHA and a daily per-IP limit.