Your launch
fix guide.

Page response and redirects

Open the exact URL in a browser. A missing page needs the correct route or restored content; a server error needs investigation in your hosting logs. Update old links to their final destination to avoid unnecessary redirects.

HTTPS and mixed content

Enable a trusted certificate through your host and redirect HTTP visitors to HTTPS. Update embedded HTTP scripts, images and stylesheets to HTTPS versions. Check browser developer tools for blocked resources; our checker does not inspect JavaScript-generated assets.

Page title and description

Write a distinct title and a short description that tell a visitor what this page offers. If you use a site builder, look in that page’s settings for SEO, search preview or page description; edit the page itself, not just the site-wide default. If you edit HTML, put a tag like this inside the page’s <head>:

<meta name="description" content="Meet the author, explore the book, and find out where to buy it.">

Use your own accurate wording. Publish the change, view the page source to confirm the tag is in the final HTML, and rerun the check. A present tag does not guarantee search ranking or that a search engine will display your wording.

Mobile viewport

Add the viewport tag below in the page head, then test the actual layout on a phone. A tag alone does not make a layout responsive.

<meta name="viewport" content="width=device-width, initial-scale=1">

Main heading

Make the main page topic clear with a descriptive H1. Our one-H1 suggestion is a simple editorial convention, not a complete accessibility rule. Use headings to organize the remaining content.

Image descriptions

Describe meaningful images with alt text that conveys their purpose in context. Decorative images can use an empty alt attribute. Our check only detects a missing attribute; it cannot judge the quality of its text.

Canonical URL

If the same content is available at multiple URLs, set a canonical link to your preferred public URL. Confirm it is correct rather than copying another page’s canonical tag. We check presence only.

Search indexing directives

If a public page should appear in search, investigate any noindex or none directive in robots/googlebot meta tags or the X-Robots-Tag response header. Keep intentional exclusions for private or staging content. Absence of noindex does not guarantee indexing; robots.txt is outside this check.

Internal link sample

A sampled URL returning 404 or 410 to a HEAD request needs a browser check before you call it broken: some sites handle HEAD differently from GET. If the page also fails in a browser, restore it or update the link. Redirects, authentication requirements, blocks and network errors are unconfirmed. We sample at most three same-origin links, not a full crawl; verify important links manually.

Five-minute manual pass

The automated report cannot tell whether a link reaches the destination you intended. On your published site, click the primary action, every purchase or booking button, and each social icon. Confirm the destination belongs to the right account and works on a phone as well as a desktop. A link that returns to your own homepage may still technically load, but could be the wrong destination.

If there is a contact form, send a test message you can recognize and verify that the intended person receives it and can reply. Use the manual lead-path check to record each step. Do not enter real customer information for a test.

What this tool does not promise

Checks cover server-rendered HTML and public IPv4 targets on standard HTTP/HTTPS ports. Private addresses and our shared hosting server cannot be scanned. There is no JavaScript rendering, full link crawl, recurring monitoring, or complete security, accessibility, performance or SEO audit. Reports are not saved by the application. Download your report if you want to keep it.

Automated page checks cannot prove that a contact-form enquiry reaches the right person. Use the manual lead-path check to record submission, inbox receipt and reply.