Check reference
The labels your page carries everywhere else.
Five checks read the head of the homepage. None of them blocks indexing. They are medium or low severity and together carry 9 of the 90 points. They control how the page is labelled in search results, browser tabs and link previews.
Title is specific and scannable
MetadataMedium severity3 of 90 pointsid: title
Repair shown in the report: Write a 15 to 60 character title with the page topic near the front.
The rule. Reads the first <title> element, trims whitespace, decodes numeric character references such as — and six named entities (&, <, >, ", ' and ), then counts characters. Any other named entity is counted as written, so — adds seven characters, not one. 15 to 60 characters, inclusive, passes. The observed value shows the first 80 characters and the length.
Why it matters. Google asks for a descriptive, concise title on every page and distinct text for each one. It sets no length limit, but truncates title links as needed to fit the device width (Google, influencing title links). The 15 to 60 range is the audit's own rule.
How to fix it. Put the page subject first and the brand last, and give every page its own title rather than a shared template string.
Meta description explains the page
MetadataMedium severity3 of 90 pointsid: description
Repair shown in the report: Add a 50 to 160 character description that states the page outcome.
The rule. Reads the content of the meta tag named description, decodes the same numeric references and six named entities as the title check, and counts characters. Other named entities, such as ©, are counted as written. 50 to 160 characters, inclusive, passes.
Why it matters. Google sometimes uses the meta description for the search snippet when it describes the page more accurately than on-page text. There is no length limit, but snippets are truncated to fit the device, and Google asks for a unique description on each page (Google, how to write meta descriptions).
How to fix it. Write one or two sentences that say what the page offers and who it is for, and keep each page's description distinct.
Open Graph title and image are present
MetadataLow severity1 of 90 pointsid: open-graph
Repair shown in the report: Add Open Graph title and image metadata.
The rule. Passes when both og:title and og:image meta tags have content. Either the name or the property attribute is accepted.
Why it matters. The Open Graph protocol defines four required properties for every page: og:title, og:type, og:image and og:url (The Open Graph protocol). The protocol's stated aim is to let any web page become a rich object in a social graph.
How to fix it. Set all four, with og:url matching the canonical URL and og:image pointing at an absolute image URL.
X card metadata is present
MetadataLow severity1 of 90 pointsid: twitter-card
Repair shown in the report: Add twitter:card metadata for reliable X previews.
The rule. Passes when a meta tag named twitter:card has content. This site's own pages use summary_large_image.
How to fix it. Add the tag next to your Open Graph tags in the shared head template so every page carries it.
A favicon is declared
MetadataLow severity1 of 90 pointsid: favicon
Repair shown in the report: Declare a favicon for browser and result-page identity.
The rule. Passes when a link element's rel is icon or shortcut icon. An apple-touch-icon link on its own does not pass.
Why it matters. Google reads the favicon from a link tag in the head of your home page and supports icon, shortcut icon, apple-touch-icon and apple-touch-icon-precomposed. It shows one favicon per hostname, for domain-level and subdomain-level home pages (Google, favicon in search results).
How to fix it. Add <link rel="icon" href="/favicon.ico"> to the homepage head. Keep any apple-touch-icon link as well.
More check references
- Page access and indexing: Status code, HTTPS, noindex, canonical, viewport, language and HTML weight.
- Crawler access: How robots.txt is read for OAI-SearchBot, Claude-SearchBot, PerplexityBot and Googlebot.
- Discovery files: Whether robots.txt, sitemap.xml and llms.txt answer at the site root.
- Structured data and entity: Valid JSON-LD, a primary entity type, and sameAs identity links.
- Headings, content and links: One H1, two H2 sections, 300 words, three internal links and image alt attributes.
- Retrieval chunk size: Whether every heading section fits in one 375-word retrieval chunk.
Related Suede guides
- On-Page SEO and Metadata Services: titles, descriptions, headings and content aligned with each page purpose, with the published metadata verified.