in <head> (seo/title-missing)" description: "seo/title-missing: The title is the main input for the search result title link and for how agents label the page." canonical: https://void-design.vercel.app/rules/seo/title-missing lastModified: 2026-09-16 --- # No single non-empty <title> in <head> `seo/title-missing` · severity **error** · category SEO · detected by `void seo` and `void audit` ## Why it matters The title is the main input for the search result title link and for how agents label the page. Titles outside <head> (Next.js streamed metadata) are unreliable for crawlers. ## How to fix it Export metadata or generateMetadata with a title, and a root title template so every page gets exactly one <title> in <head>. ## Example ```ts // app/layout.tsx export const metadata: Metadata = { metadataBase: new URL(site.url), title: { default: 'Acme: fast widgets for teams', template: '%s | Acme' }, } // app/pricing/page.tsx export const metadata: Metadata = { title: 'Pricing' } // → "Pricing | Acme" ``` ## References - https://developers.google.com/search/docs/appearance/title-link - https://nextjs.org/docs/app/api-reference/functions/generate-metadata ## More seo rules `void seo` reports 60 rules in this category. What search engines need from the raw response: status codes, titles and descriptions in <head>, self-referencing canonicals, one h1, crawlable links, Open Graph, icons, robots.txt and a sitemap with real dates. - `origin-redirects` http:// or www/apex variant doesn't redirect to the canonical origin in one hop — [seo/origin-redirects](https://void-design.vercel.app/rules/seo/origin-redirects) - `html-lang` <html lang> missing or not a valid BCP 47 tag — [seo/html-lang](https://void-design.vercel.app/rules/seo/html-lang) - `viewport` Viewport meta missing, not device-width, or blocks zoom — [seo/viewport](https://void-design.vercel.app/rules/seo/viewport) - `charset` Character encoding not declared early — [seo/charset](https://void-design.vercel.app/rules/seo/charset) - `title-length` Title length outside 10–60 characters, or keyword-stuffed — [seo/title-length](https://void-design.vercel.app/rules/seo/title-length) - `meta-description-missing` No meta description in <head> — [seo/meta-description-missing](https://void-design.vercel.app/rules/seo/meta-description-missing) - `meta-description-length` Meta description length outside 50–160 characters — [seo/meta-description-length](https://void-design.vercel.app/rules/seo/meta-description-length) - `metadata-in-body` Crawler receives <title>/canonical/description inside <body> (Next.js streaming metadata) — [seo/metadata-in-body](https://void-design.vercel.app/rules/seo/metadata-in-body) Detected by `void seo` and `void audit`. Explain it in a terminal: `void rules seo/title-missing`

--- title: "No single non-empty in <head> (seo/title-missing)" description: "seo/title-missing: The title is the main input for the search result title link and for how agents label the page." canonical: https://void-design.vercel.app/rules/seo/title-missing lastModified: 2026-09-16 --- # No single non-empty <title> in <head> `seo/title-missing` · severity **error** · category SEO · detected by `void seo` and `void audit` ## Why it matters The title is the main input for the search result title link and for how agents label the page. Titles outside <head> (Next.js streamed metadata) are unreliable for crawlers. ## How to fix it Export metadata or generateMetadata with a title, and a root title template so every page gets exactly one <title> in <head>. ## Example ```ts // app/layout.tsx export const metadata: Metadata = { metadataBase: new URL(site.url), title: { default: 'Acme: fast widgets for teams', template: '%s | Acme' }, } // app/pricing/page.tsx export const metadata: Metadata = { title: 'Pricing' } // → "Pricing | Acme" ``` ## References - https://developers.google.com/search/docs/appearance/title-link - https://nextjs.org/docs/app/api-reference/functions/generate-metadata ## More seo rules `void seo` reports 60 rules in this category. What search engines need from the raw response: status codes, titles and descriptions in <head>, self-referencing canonicals, one h1, crawlable links, Open Graph, icons, robots.txt and a sitemap with real dates. - `origin-redirects` http:// or www/apex variant doesn't redirect to the canonical origin in one hop — [seo/origin-redirects](https://void-design.vercel.app/rules/seo/origin-redirects) - `html-lang` <html lang> missing or not a valid BCP 47 tag — [seo/html-lang](https://void-design.vercel.app/rules/seo/html-lang) - `viewport` Viewport meta missing, not device-width, or blocks zoom — [seo/viewport](https://void-design.vercel.app/rules/seo/viewport) - `charset` Character encoding not declared early — [seo/charset](https://void-design.vercel.app/rules/seo/charset) - `title-length` Title length outside 10–60 characters, or keyword-stuffed — [seo/title-length](https://void-design.vercel.app/rules/seo/title-length) - `meta-description-missing` No meta description in <head> — [seo/meta-description-missing](https://void-design.vercel.app/rules/seo/meta-description-missing) - `meta-description-length` Meta description length outside 50–160 characters — [seo/meta-description-length](https://void-design.vercel.app/rules/seo/meta-description-length) - `metadata-in-body` Crawler receives <title>/canonical/description inside <body> (Next.js streaming metadata) — [seo/metadata-in-body](https://void-design.vercel.app/rules/seo/metadata-in-body) Detected by `void seo` and `void audit`. Explain it in a terminal: `void rules seo/title-missing`