Launch mistakes
Broken links and missing files after launch
A broken internal link points at a page on the same site that answers with an error, usually 404 Not Found; a missing asset is an image, script or stylesheet the page references but the server does not deliver. After launch they show visitors dead ends, broken layouts and features that do not work. Crawl the live site once after go-live and fix every internal link and file that answers with a 4xx or 5xx status.
Last reviewed
How it happens
URL structures change during a rebuild. Pages are renamed, merged or dropped, and links in the content, menus and old posts still point at the previous paths. Redirects from the old site are planned late or not at all.
Files break in migration too: uploads that were not copied, paths that include the staging folder, file name case that the staging server ignored but the live server does not, and assets from a build that was not deployed.
How to spot it yourself
- Open the live homepage with the developer tools' Console and Network tabs open and reload. Look for failed requests with a 404 or 403 status.
- Click every item in the main menu and the footer.
- Visit a few URLs from the previous site or the client's printed material and check where they land.
- For a quick status check from a terminal, run curl -sI on a URL and read the first line.
How to fix it
- Update links to the live path, or add a permanent redirect from the old URL to its closest equivalent.
- Upload missing files, or correct the path in the template or the CMS.
- Restore pages that should exist, and remove links to pages that should not.
What Launch Ready checks
Each finding below shows the title, “Why it matters” and “How to fix” text the report uses. Severities are the defaults; a project rule override can change or silence a rule.
Rule broken_internal_links
What the scan looks at: Checks each <a href> on the crawled pages that points at the same site. A link is reported when the page it points at was fetched during the crawl and answered with HTTP 400 or above. A target that timed out, or that answered with a bot-protection challenge, is not counted as broken.
Default severity: Important.
Broken internal link
Why it matters: A link on this page points to a URL that errors. Visitors who click it will bounce.
How to fix: Update the href to a live page or unpublish the broken destination.
Rule missing_assets
What the scan looks at: Checks the images, scripts and stylesheets referenced on the crawled pages. After the crawl, up to 80 asset and outbound-link requests are made, and a file that answers HTTP 400 or above is reported. A file on another site that refuses crawlers (401, 403, 429 or 999) is not reported; its 404 is.
Default severity: Block Launch for a script or stylesheet on the homepage; Important otherwise.
An image
Image fails to load
Why it matters: An image failed to load. The page will look unfinished.
How to fix: Upload the file, fix the path, or remove the reference.
A script
Script fails to load
Why it matters: A script the page needs failed to load. Features that depend on it will break.
How to fix: Upload the file, fix the path, or remove the reference.
Rule http_4xx
What the scan looks at: Reports every crawled page on the site that answered with an HTML page and a status from 400 to 499.
Default severity: Block Launch for the homepage; Important for other pages.
Example: HTTP 404
Page not found or forbidden (HTTP 404)
Why it matters: An internal page is returning a client error. Linked pages like this look unfinished.
How to fix: Restore the page, fix the route, or remove links that point here.
What Launch Ready does not check here
- Links to pages the crawl did not reach within its page limit. A link is judged only when its target was fetched.
- Files beyond the per-scan request limit, fonts and images referenced from inside CSS files, and files requested by scripts.
- Old URLs from the previous site that nothing links to any more. Check those against your redirect map by hand.
- Links to other sites, which are a separate, sampled check.
- Launch Ready does not guarantee a bug-free website.
- It does not make the launch decision. People make it, with the report in hand.
How we scan describes what the crawler fetches, renders and stores.
Related checklist items
- No critical 4xx responses on required pages (Scan check)
- Internal links resolve without errors (Scan check)
- Required static assets are present (Scan check)
From the free 72-item website launch checklist, with each item's coverage label: Scan check, Partly checked or Manual.
Related launch mistakes
- Staging and localhost links left in: Links, canonical tags or redirects still send visitors to staging, a preview build or a developer's machine.
- Mixed content and SSL errors: An untrusted certificate, pages still served over HTTP, or files loaded over HTTP on secure pages.
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.