The LaunchGraded Standard, in full.

The headline is the first — and sometimes only — thing a visitor reads. If it's missing, buried below the fold, or too long to parse, they leave before understanding what you do.

A one-liner under the headline removes the ambiguity about who this is for and why it matters, right when attention is highest.

Visitors can't picture what they're getting from text alone. Without a screenshot or demo they're asked to trust a description of something they've never seen.

The <title> is what shows in the browser tab, in search results and in most link previews. A missing or generic one ("Home") wastes the most-seen line you have.

A page with almost no text gives visitors and search engines nothing to work with beyond a headline — there's no room to cover objections, use cases or how it works.

Copy that's either too dense (long sentences, jargon) or oddly simplistic reads as unpolished. A quick Flesch Reading Ease check over your body text flags the extremes — it's a formula, not a style opinion.

A missing or vague call to action leaves even a convinced visitor unsure what to do. Undecided visitors leave rather than hunt for the next step.

Hidden pricing with no path to a conversation makes visitors do extra work to find out whether they can afford or qualify for this. Many won't bother.

Most first visitors aren't ready to sign up or buy. Without a lighter option — updates, a waitlist, a newsletter — you lose everyone who was close but not convinced.

A first-time visitor has no reason to believe you yet. Without logos, testimonials, review counts or usage numbers, they have only your word that this works.

A site that asks for an email but links no privacy policy reads as unfinished, and some payment and ad platforms require both pages before they'll approve you.

A visible way to reach you is the cheapest trust signal there is. No contact link, email or social handle makes the product feel unattended.

A visible published or updated date lets readers judge whether content-style pages still reflect current information — undated or stale content reads as abandoned.

An unattributed article reads as anonymous, generic content. A named author with a bio gives readers someone to trust the claims came from.

Most first visits from a shared link are on a phone. A page with no responsive viewport renders as a shrunken desktop site and loses those visitors before they read a word.

Links and buttons that are too small or too close together cause mis-taps on a phone, and a mis-tapped call to action is a lost conversion.

Text under about 12 px forces phone visitors to pinch and zoom, and most simply leave instead.

Your page tells search engines to stay away. Every link, mention and launch post will point at a page Google won't list.

Without a meta description, search engines and link previews pick a random sentence from the page — usually not the one you'd choose.

A launch spreads by links. Without Open Graph title, description and image, your link shows up on social and in chat as a bare URL or a broken card.

Without a canonical tag, www/non-www, trailing slashes and tracking parameters can split your page into several URLs that compete with each other in search.

"Click here" and "Learn more" links tell neither visitors nor search engines what's behind them, and JavaScript-only anchors can't be crawled at all.

A sitemap tells search engines every URL you want indexed instead of relying on them to discover pages by crawling links, which is slower and can miss pages with no internal links pointing at them.

A sitemap listing dead or redirected URLs wastes the crawl budget search engines give your site and signals a stale or auto-generated file nobody checks.

robots.txt is the first file most crawlers check. A Sitemap: line there gets your sitemap discovered immediately instead of waiting on a manual submission or a lucky crawl.

Slow pages lose visitors before the content renders, and the drop-off compounds with every extra second on a phone connection.

Largest Contentful Paint is when the visitor sees your hero. Past 2.5 seconds on mobile, a noticeable share of them assume the page is broken. This is a live lab measurement, so it can read a few hundred ms differently between two scans of an unchanged page.

Layout shift is when a button moves as the visitor reaches for it. It reads as jank and causes mis-taps on the very elements you want tapped.

Accessibility failures shut out visitors using screen readers or keyboards, and the same issues — unlabelled controls, poor contrast — trip up everyone on a phone in sunlight.

Without alt text, screen-reader users hear "image" and search engines see nothing — your product screenshot becomes invisible to both.

An input with only a placeholder has no name once someone starts typing, and no name at all for a screen reader — the email capture you rely on is the field most often affected.

Without a lang attribute, screen readers guess the pronunciation rules and browsers may offer to translate a page that's already in the visitor's language.

Low-contrast text — light grey on white is the classic — is hard to read for everyone and unreadable for many, especially on a phone outdoors.

Browsers show a "Not secure" warning when a page is served over HTTP or mixes HTTPS and HTTP content. For a first-time visitor that reads as "don't type your email here".

Strict-Transport-Security, X-Content-Type-Options and a framing defence (Content-Security-Policy or X-Frame-Options) are cheap, standard headers that close off common browser-level attacks. Their absence is one of the first things a technical visitor checks.

An HTTPS page that loads even one image, script or stylesheet over http:// gets flagged as mixed content — browsers may block the resource outright or strip the page's "secure" padlock.

JavaScript errors on load usually mean something a visitor expects — a form, a menu, an embed — isn't working, and you won't hear about it from them.

A blank tab icon is a small thing that signals "unfinished" in every tab, bookmark and share card.

A site with no logo anywhere — not in the header, not in your Organization schema, not even a proper home-screen icon — reads as unfinished, and gives visitors nothing to recognize you by on a second visit or a share.

Most hosts redirect http:// to https:// automatically, but a server that answers on plain HTTP without redirecting serves an insecure, unencrypted copy of the page to anyone who types the bare domain or an old http:// link.

If both www.example.com and example.com load the same page with no redirect between them, search engines see two copies of every page, and links pointing at each host build up authority separately instead of together.

If a wrong URL returns 200 with a blank or homepage-lookalike page, search engines index junk URLs and visitors who mistype get no signal to correct it.

Exactly one <h1> and no skipped heading levels is how screen readers and search engines build an outline of the page — jumping from an <h1> straight to an <h3> (or having none, or several) breaks that outline.

A dead link on launch day is the fastest way to look unfinished. If it's in the nav or footer, it's on every page.

Structured data (JSON-LD) is how search engines and AI assistants understand what your page is about beyond the visible text — without it you're relying entirely on crawled prose.

Organization, Product, SoftwareApplication and WebSite are the schema types search engines and AI assistants rely on most to build knowledge panels and answer "what is this" queries — without one of them, structured data on the page has nothing to attach to.

A schema block missing its commonly-required fields — a Product with no offers, an Organization with no name — is often ignored by search engines even though it technically validates as JSON-LD.

Malformed JSON silently drops your structured data with no visible error, and two blocks of the same type that disagree (different names for what should be the same Organization) leave search engines unsure which one to trust.

BreadcrumbList markup can earn a breadcrumb trail in search results, and QAPage markup makes a genuine Q&A page eligible for a rich result — free visual real estate in the SERP. (Legacy FAQPage markup lost this eligibility in 2026.)

AI assistants (ChatGPT, Perplexity, Claude) can only cite or summarize pages their crawlers can reach. Blocking GPTBot, ClaudeBot and similar crawlers in robots.txt keeps your site out of those answers — sometimes a deliberate choice, but worth confirming it's intentional.

An llms.txt gives AI assistants a curated, plain-text summary of your site instead of making them parse rendered HTML. It's informational only — Google's own AI-optimization guidance says it doesn't affect Search visibility — but it's a cheap, emerging convention for the AI-crawler audience specifically.