Skip to content

Metadata

How to remove a framework default title

A leftover scaffold title is the clearest possible signal to a visitor that the site is unfinished, and it appears in the search result, the browser tab and every shared link. It also means the page competes for the scaffold's words instead of your product's.

What 13x checks

This is rule metadata.title-default in the public registry: No framework default titles. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Metadata
Score weight
14 of the readiness score
Scope
Reported as skipped when the page renders only with JavaScript
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Replace the scaffolding title with one describing your product. Found: ``.

A usable title answers "what is this and who is it for" in under 60 characters:

Configuration
example.com — invoicing for freelance designers

Check every route, not just the homepage. Scaffolding titles usually survive in the pages nobody revisited.

Framework-specific versions

Where the change differs enough to be worth writing out separately.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More metadata checks