Fetched page title matches a supported framework default
ShipReady found a title element whose complete value exactly matches one of its maintained scaffold-title defaults.
Why it matters
A default title can make a page difficult to distinguish in a tab or shared context. It is worth replacing with a title that accurately identifies the page.
How ShipReady detects it
What it inspects
ShipReady reads the fetched page title element and compares its trimmed text case-insensitively with a maintained set of framework and scaffold defaults.
What triggers a finding
The rule triggers only when the entire trimmed title exactly matches a supported default, such as Create Next App or Vite App.
What the evidence shows
The fetched page title exactly matched ShipReady's supported default-title list.
Limits of this check
ShipReady does not determine who created the page, assess other branding, inspect every route, or decide whether a title that merely contains a scaffold phrase is a problem. Custom titles containing a supported phrase do not trigger this check.
How to fix it
Set a deliberate page title
Replace the default title in the framework metadata or document head with a title that identifies the product and, where appropriate, the specific page.
How to verify the change
Inspect the deployed document title
Fetch or open the affected page after deployment and confirm its title is the intended custom value.
Expected: The page title no longer exactly matches a supported framework default.