Can search engines read, understand and show every page.
Reported when: The page has no <title>.
Why it matters: Without a title, Google makes one up for search results and the browser tab shows the address.
Based on developers.google.com · seo_title_missing
Reported when: The title is longer than 60 characters, about what Google shows.
Why it matters: Google cuts titles longer than its results line, often losing the part that matters.
Based on developers.google.com · seo_title_long
Reported when: The title is shorter than 10 characters.
Why it matters: A one-word title tells searchers nothing about the page.
Based on developers.google.com · seo_title_short
Reported when: The page has no meta description.
Why it matters: Without a meta description, Google picks any text from the page for the snippet under the title.
Based on developers.google.com · seo_description_missing
Reported when: The meta description is longer than 160 characters.
Why it matters: Google cuts long descriptions, so the end of the sentence is lost.
Based on developers.google.com · seo_description_long
Reported when: The page has no <h1> after its scripts ran.
Why it matters: The main heading tells search engines and screen readers what the page is about.
Based on developer.mozilla.org · seo_h1_missing
Reported when: The page has more than one different <h1>. The same heading twice, one for phones and one for desktops, is fine.
Why it matters: Several different main headings make it unclear what the page is about.
Based on developer.mozilla.org · seo_h1_multiple
Reported when: A heading jumps more than one level down, for example from <h2> to <h4>.
Why it matters: A heading level is skipped (an H2 followed by an H4), so the outline of the page is broken for search engines and screen readers.
Based on developer.mozilla.org · seo_heading_skip
Reported when: The page has no <link rel="canonical">.
Why it matters: Without a canonical link, the same page under different addresses (with tracking parameters, a trailing slash) can be indexed as duplicates.
Based on developers.google.com · seo_canonical_missing
Reported when: The page names another address as canonical, so Google indexes that one instead.
Why it matters: The canonical link names another page, so Google shows that one in search results instead of this one.
Based on developers.google.com · seo_canonical_elsewhere
Reported when: The canonical address answers 4xx or 5xx.
Why it matters: The canonical link points to a page that returns an error, so Google may drop this page.
Based on developers.google.com · seo_canonical_broken
Reported when: A noindex robots meta tag or X-Robots-Tag header. Critical on the home page.
Why it matters: A noindex tag or header tells search engines not to show the page.
Based on developers.google.com · seo_noindex
Reported when: The <html> element has no lang attribute.
Why it matters: Without a language on the page, search engines guess it and screen readers may read it with the wrong voice.
Based on developer.mozilla.org · seo_lang_missing
Reported when: The page has no viewport meta tag, which Google’s mobile-first indexing expects.
Why it matters: Without a viewport tag, phones show the desktop page shrunk, and Google ranks the phone version.
Based on developer.mozilla.org · seo_viewport_missing
Reported when: og:title or og:image is missing, so shared links show no proper card.
Why it matters: Without Open Graph tags, a shared link shows as plain text or a random image on LinkedIn, Facebook, Slack and WhatsApp.
Based on ogp.me · seo_og_missing
Reported when: A JSON-LD block does not parse.
Why it matters: A JSON-LD block is not valid JSON, so Google ignores it and the rich results it was meant for.
Based on developers.google.com · seo_structured_data_invalid
Reported when: Images have no alt attribute. Tracking pixels and hidden images are left out.
Why it matters: Images without alt text say nothing to image search and screen readers.
Based on developers.google.com · seo_image_alt
Reported when: The HTML the server sends has less than a fifth of the text the page shows after its scripts run. A person checks it before you see it: a site that prerenders for crawlers can send Google the full page.
Why it matters: The HTML your server sends is nearly empty; the text appears only after scripts run, which search engines do later and less reliably, and AI assistants and link previews often not at all.
Based on developers.google.com · seo_js_only_content
Reported when: The title or description is only added by scripts, not in the HTML the server sends.
Why it matters: The title or description is only set by a script, so link previews and crawlers that run no scripts see none.
Based on developers.google.com · seo_js_only_head
Reported when: The page showed almost no text even after its scripts ran, so its content was not checked. Costs no points.
Why it matters: The page stayed blank in a fresh browser, even after its scripts ran. If a script fails to load or the app starts slowly for Google too, it indexes an empty page.
Based on developers.google.com · seo_not_rendered
Reported when: Two or more pages that are their own canonical have the same title.
Why it matters: Several pages share one title, so search engines cannot tell them apart and may show only one.
Based on developers.google.com · seo_duplicate_title
Reported when: Two or more pages have the same meta description. A person checks it before you see it.
Why it matters: Several pages share one description, so their snippets in search results look the same.
Based on developers.google.com · seo_duplicate_description
Reported when: Addresses in the sitemap answer 4xx or 5xx.
Why it matters: The sitemap lists pages that do not exist, so Google wastes visits on errors and trusts the sitemap less.
Based on developers.google.com · seo_sitemap_broken
Reported when: Addresses in the sitemap redirect somewhere else.
Why it matters: The sitemap lists addresses that redirect, instead of the final address of each page.
Based on developers.google.com · seo_sitemap_redirect
Reported when: Pages the site links to are not in its sitemap.
Why it matters: Pages the site links to are missing from the sitemap, so Google may find them later or not at all.
Based on developers.google.com · seo_sitemap_missing_pages
Reported when: robots.txt names no sitemap and /sitemap.xml and /sitemap_index.xml do not exist.
Why it matters: Without a sitemap, Google only finds pages by following links, and finds new ones later.
Based on developers.google.com · seo_sitemap_missing
Reported when: The sitemap has no <urlset> or <sitemapindex>, for example an HTML page served at /sitemap.xml.
Why it matters: The sitemap cannot be read as a sitemap, so Google ignores it.
Based on developers.google.com · seo_sitemap_invalid
Reported when: robots.txt disallows the whole site for all crawlers.
Why it matters: robots.txt tells every crawler to stay away from the whole site, so pages drop out of search results.
Based on developers.google.com · seo_robots_blocks_all
Reported when: A robots.txt group for Googlebot or Bingbot disallows the whole site, while other crawlers may crawl it.
Why it matters: robots.txt has a group of rules for this search engine that disallows the whole site, so it drops the pages from its results, and so do the AI answers built on its index: Copilot answers from Bing.
Based on developers.google.com · seo_robots_blocks_search
Reported when: A robots.txt group for OAI-SearchBot (ChatGPT), Claude-SearchBot (Claude) or PerplexityBot (Perplexity) disallows the whole site. Blocking training crawlers such as GPTBot, ClaudeBot or Google-Extended does not count: it does not hide a site from search.
Why it matters: robots.txt disallows the crawler an AI assistant uses to find pages for its answers, so the site is not shown or cited there. Training crawlers are different: GPTBot and ClaudeBot can stay blocked without this effect.
Based on developers.openai.com · seo_robots_blocks_ai_search
Reported when: robots.txt answers 5xx, which tells Google to crawl nothing.
Why it matters: robots.txt answers with a server error, and Google stops crawling the site while it does.
Based on developers.google.com · seo_robots_error
Reported when: The site has no robots.txt.
Why it matters: There is no robots.txt, so there is no line pointing crawlers to the sitemap.
Based on developers.google.com · seo_robots_missing
Reported when: No page read has JSON-LD structured data.
Why it matters: Structured data tells Google what the site is (an organization, a product, an article) and is what rich results are made of.
Based on developers.google.com · seo_structured_data_missing
Reported when: The http:// address answers without redirecting to https://.
Why it matters: The site also answers over plain http without redirecting, so there are two copies of every page and visitors on one see "Not secure".
Based on developers.google.com · seo_https_redirect
Reported when: The other spelling of the host (with or without www) answers without redirecting to the one the site uses.
Why it matters: Both www and the bare domain answer, so the site exists twice and links people share are split between them.
Based on developers.google.com · seo_host_redirect