Free tool · No sign-up
Launch Readiness Checker
Paste the page you are about to launch. In about ten seconds you will see what Google, link previews and AI crawlers see, with a score and a clear fix for anything that is broken.
Checking
Loading the page...
What the checker looks at
Launch day is the one day a lot of people see your page for the first time, mostly through a link: in a post, a newsletter, a Slack channel or a search result. The checker covers the four things that decide whether that first look works.
Crawling and indexing
Can search engines reach the page, and are they allowed to keep it?
- HTTPS and SSL certificate expiry
- HTTP status and redirect chains
- noindex in the HTML or the server headers
- robots.txt rules for Googlebot
- Canonical tag and XML sitemap
- Access for AI search crawlers
- Response time and compression
Search result
What your listing in Google will say, and the basics behind it.
- Title tag length and wording
- Meta description
- One clear H1
- Mobile viewport and language
- Favicon that actually loads
- Image alt text
- Text present in the HTML, not only in JavaScript
Social share preview
The card people see when your link is posted anywhere.
- og:title and og:description
- og:image downloaded and verified
- Image size, format, weight and shape
- twitter:card layout for X
- og:url pointing at the right page
Structured data
The markup that tells machines what your product is.
- JSON-LD that parses without errors
- SoftwareApplication or Product markup
- Price, category and operating system
- Organization and WebSite markup
How to use it
- Enter the page you plan to share. Usually your homepage, but check your pricing page and any landing page you will link to as well. You can leave out https://.
- Read the previews first. The Google result and the share card show you, at a glance, what strangers will see. If either looks wrong, the checks below explain why.
- Fix the red items, then the amber ones. Every failed or flagged check comes with the exact fix. Deploy, run the check again and watch the score move.
Why check before you launch
Most launch problems are invisible from the inside. Your page looks perfect in your own browser, because your browser runs every script, has every font cached and never gets blocked by your own firewall. The visitors that matter on launch day are different. Googlebot reads the robots.txt you forgot about. LinkedIn's preview bot asks for your og:image and gets a 403 from hotlink protection. Slack unfurls the link and finds a JavaScript app shell with no title. None of that shows up until someone shares the link and it looks broken.
The fixes are almost always small: one meta tag, one line in robots.txt, a re-exported image. The hard part is knowing they are needed before a few thousand people see the result. That is what this checker is for. It visits the page the way those bots do, from outside your network, without running JavaScript, and reports exactly what they would get.
How the score works
Each of the 28 checks has a weight based on how much damage the problem does. A pass earns the full weight, a warning earns half, and a failure earns nothing. Checks that do not apply, such as image size when there is no image, are left out of the total. Indexing, robots.txt and the page response carry the most weight, because a page search engines cannot reach will not rank however good its title is.
- 90 to 100, Ready to launch. Nothing serious left. Any remaining warnings are polish.
- 75 to 89, Almost there. A couple of things will make the launch look less sharp than it should.
- 50 to 74, Needs work. Several visible problems, usually in the share preview or search snippet.
- Below 50, Not ready yet. Fix the red items before you share the link anywhere.
One rule overrides the number: if the page returns an error, carries a noindex, is blocked in robots.txt or has a broken certificate, the result says Blocked, whatever the score. Those problems stop everything else from mattering.
The launch mistakes we see most often
A noindex tag left over from staging
Staging sites are hidden from search engines on purpose, often with a single checkbox or environment setting. When the site moves to production, the setting comes along. The page works, it just never appears in Google, and nobody notices for weeks. If the Indexing check fails, look for a robots meta tag in your template and an X-Robots-Tag header in your host or CDN settings.
A share image that apps refuse to show
An SVG logo as og:image, an image behind hotlink protection, a relative path, or a 4 MB PNG straight out of a design tool. Every one of these produces a text-only share card. Export a 1200 x 630 JPG or PNG, compress it under about 300 KB, and reference it with a full https address.
A JavaScript app shell with nothing in it
Single-page apps built with React, Vue or Svelte often send an almost empty HTML file and build the page in the browser. Google can render that eventually. Link-preview bots, most AI crawlers and many directories cannot, so they see no title, no description and no text. Pre-render your marketing pages, or at least render the head tags on the server.
A title that is only the product name
"Acme" tells a searcher nothing. "Acme: invoicing for freelancers that chases late payments" tells them whether to click. Lead with the name, follow with what it does and for whom, and keep it under about 60 characters.
AI crawlers blocked by accident
Some CDNs and security plugins now block AI bots by default, and plenty of robots.txt files copied from a template block them all at once. Blocking GPTBot keeps your content out of training data. Blocking OAI-SearchBot, Claude-SearchBot or PerplexityBot keeps your product out of AI search answers, which is rarely what a new product wants.
Copy-paste fixes
Replace the example values with your own. All of these go inside <head> unless noted.
The essential head tags
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Acme: invoicing for freelancers that chases late payments</title>
<meta name="description" content="Send invoices in a minute and let Acme follow up on late payments for you. Free for your first 10 clients.">
<link rel="canonical" href="https://acme.com/">
<link rel="icon" href="/favicon.png">
<meta property="og:type" content="website">
<meta property="og:url" content="https://acme.com/">
<meta property="og:title" content="Acme: invoicing that chases late payments">
<meta property="og:description" content="Send invoices in a minute and let Acme follow up for you.">
<meta property="og:image" content="https://acme.com/og-image.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta name="twitter:card" content="summary_large_image">SoftwareApplication and Organization markup
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "SoftwareApplication",
"name": "Acme",
"url": "https://acme.com/",
"description": "Invoicing for freelancers that chases late payments.",
"applicationCategory": "BusinessApplication",
"operatingSystem": "Web",
"offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" }
},
{
"@type": "Organization",
"name": "Acme",
"url": "https://acme.com/",
"logo": "https://acme.com/logo.png",
"sameAs": ["https://x.com/acme", "https://www.linkedin.com/company/acme"]
}
]
}
</script>A sensible robots.txt (at the root of your domain)
User-agent: *
Disallow: /admin/
Disallow: /app/
# Optional: stay out of AI training data, but stay in AI search answers
User-agent: GPTBot
Disallow: /
Sitemap: https://acme.com/sitemap.xmlWhat to check by hand
A crawler can only see what a crawler sees. Before you announce, spend ten minutes on the things that need a person:
- Sign up as a new user on a phone, from a private window, with an email address you have never used.
- Read the confirmation and welcome emails and check they did not land in spam.
- Make a real payment with a live card if you charge, then refund it.
- Open your 404 page by typing a nonsense address. It should help people find their way back.
- Check analytics is recording by visiting the site and watching the real-time view.
- Test every form, including contact and newsletter, and confirm the messages arrive.
- Load the site on a slow connection. Browser developer tools can throttle to 3G.
Frequently asked questions
What is a launch readiness check?
It is a quick technical inspection of a web page before you announce it. The checker loads the page the way search engines and link-preview bots do, then looks at whether it can be indexed, how it will look in Google, how it will look when someone shares the link, and whether it has structured data. You get a score, a preview of your search result and share card, and a plain-English fix for every problem.
Is the Launch Readiness Checker free?
Yes. There is no sign-up and no paid tier. To keep it fast for everyone, each visitor can run up to 10 checks every ten minutes and 60 a day.
Why does my share image not show up on LinkedIn, Slack or WhatsApp?
The usual causes are a missing og:image tag, an image in SVG or AVIF format, an image URL that returns an error or a login page to bots, a relative image address instead of a full https one, or a file that is too large. The checker downloads your og:image the way those apps do and tells you which of these applies.
Does this tool check pages that use JavaScript frameworks like React?
It reads the HTML your server sends, which is exactly what link-preview bots, most AI crawlers and many directories see, because they do not run JavaScript. If your page is an empty app shell that fills in with JavaScript, the checker flags it, since those visitors would see a blank page.
Why do you check AI crawlers like OAI-SearchBot and PerplexityBot?
ChatGPT search, Claude and Perplexity send these bots to read pages before citing them in answers. If robots.txt blocks them, your product cannot be recommended in those answers. Blocking training bots such as GPTBot is a separate choice and does not affect search answers, so the checker treats the two differently.
What score should I aim for before launching?
Aim for 90 or above with no failed checks. Some warnings are fine, for example multiple H1 tags or a missing og:url. Failed checks on indexing, robots.txt, HTTPS or the page response are blockers: fix those first, because nothing else matters if search engines cannot reach the page.
Can I check a page that is not live yet?
Only if it is reachable on the public internet. The checker cannot see localhost, private networks or pages behind a login. A staging URL works as long as it is public, but remember that staging sites often carry a noindex tag on purpose, so expect that check to fail there.
Do you store the pages I check?
No. The page is fetched, analysed and discarded. We do not keep a copy of your HTML or your report. The only thing recorded is a counter for the rate limit.
How is this different from Google Search Console or the Rich Results Test?
Those tools are excellent, but each covers one area and Search Console only works after you verify the site. This checker covers indexing, search snippet, share preview and structured data in one pass, works on any public URL, and is built for the moment just before you launch.
Check your page now
It takes about ten seconds and you do not need an account.
Run the checker