dotvitals

The page declares the same metadata more than once

LowConfirmedQuick winseo.meta.duplicate-tags

What this check looks for

This page carries more than one ‹field›, with different values. Which one is used is decided by the consumer, and different consumers decide differently.

Why it matters

When two tags disagree, you do not control which is shown. A search result, a social preview and a browser tab can each pick a different one, and the fix is invisible until you look at the raw markup.

When the check passes, your report says: “Each piece of page metadata is declared once”.

What it costs your score

When this check fails it removes 5 points from your SEO score, before the status, confidence and repeat multipliers are applied. SEO carries a weight of 5 in the overall score.

It shares the seo.meta family ceiling of 20 points: however many findings that family produces, together they cannot remove more than that from SEO. One underlying problem showing up in several places is still one problem.

Severity
low
Default confidence
confirmed
Status when triggered
warn
Deduction
5 points
Family cap
seo.meta · 20
Category
SEO
Module
Seo audit
Fix owned by
user
In the ruleset since
2026.09

How the whole score is calculated

How to fix it

Leave one component responsible for this metadata and remove the other.

Two conflicting values mean the consumer chooses, and different consumers choose differently.

  1. View the page source and find every tag declaring the field.

  2. Decide which component owns it — normally the application's own head management, not a plugin.

  3. Remove the tag from the other source rather than syncing the values.

How to confirm it worked

  • curl -sS ‹url› | grep -ci '‹grep›' — should be 1

A named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.

Technical detail

The values found were:

‹values›

HTML parsers take the first <title> and most consumers take the first <meta name="description">, but this is behaviour rather than a specification of what a page should contain, and it is not consistent across every consumer. The usual cause is two components writing the same metadata: a theme or layout template plus an SEO plugin, or a framework's head manager plus a hand-written tag in a partial.

Remove one source rather than making the two agree. Two sources that currently produce the same value will produce different ones the next time either changes, and the fault will be reintroduced without anyone touching the page.

Standards and references

Test this on your domain

Run the check that produces this finding, on its own, against any domain.

Open the seo audit checker

Other seo audit checks