Open Graph module reports missing icon / lang even when provided via app.head #916

nicokempe · 2025-12-28T01:38:18Z

nicokempe
Dec 28, 2025

Hi,
I’ve been digging into the Open Graph module in Nuxt DevTools and wanted to start a discussion before going further or preparing a PR.

What I’m seeing

The Open Graph panel reports missing tags for:

icon
lang

…even though both are defined globally via app.head in nuxt.config.ts and are clearly present in the rendered <head> / <html> output.

Example (simplified):

app: {
  head: {
    htmlAttrs: { lang: 'en' },
    link: [
      { rel: 'icon', type: 'image/svg+xml', href: '/favicons/favicon.svg' },
      { rel: 'icon', type: 'image/png', sizes: '32x32', href: '/favicons/favicon-32x32.png' },
      { rel: 'icon', type: 'image/x-icon', href: '/favicons/favicon.ico' },
    ],
  },
}

Rendered HTML (confirmed via browser inspector):

<html lang="en">
  <link rel="icon" type="image/svg+xml" href="/favicons/favicon.svg">
  <link rel="icon" type="image/png" sizes="32x32" href="/favicons/favicon-32x32.png">
  <link rel="icon" type="image/x-icon" href="/favicons/favicon.ico">
</html>

Despite this, the Open Graph panel still shows icon and lang as missing.

What I’ve found so far

After tracing through the DevTools code, the behavior seems to come from how tags are normalized and matched, not from Nuxt / Unhead failing to provide them.

Relevant files:

packages/devtools/client/data/open-graph.ts
packages/devtools/client/pages/modules/open-graph.vue
packages/devtools/client/components/OpenGraphMissingTabs.vue

Normalization logic

In open-graph.vue, tags are normalized like this:

name: props.property ?? props.name ?? props.rel ?? tag.tag

and lang is only mapped if:

tag.tag === 'htmlAttrs' && props.lang

Later, missing tags are determined via strict equality:

ogTags.filter(define =>
  !props.tags?.some(tag => tag.name === define.name)
)

Question

Before going further, I wanted to ask:

Is this behavior expected?
- i.e. does the Open Graph module intentionally only consider route-level / useHead() / useSeoMeta() tags?
Or is this considered an edge case / bug in the normalization & matching logic?

If the latter, I’d be happy to:

further investigate how resolveTags() represents these cases
propose a PR that makes the detection more robust (e.g. normalizing rel, treating any icon link as fulfilling icon, broadening lang detection)

Just wanted to align on expectations first, thanks :)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Open Graph module reports missing icon / lang even when provided via app.head #916

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Open Graph module reports missing icon / lang even when provided via app.head #916

Uh oh!

nicokempe Dec 28, 2025

What I’m seeing

What I’ve found so far

Normalization logic

Question

Replies: 0 comments

nicokempe
Dec 28, 2025