Image Alt Text for SEO in Vue · Nuxt SEO

-
-
-
-

[1.4K](https://github.com/harlan-zw/nuxt-seo)

[Nuxt SEO on GitHub](https://github.com/harlan-zw/nuxt-seo)

Learn SEO

Master search optimization

Nuxt

 Vue

-
-
-
-
-
-
-

-
-
-
-
-
-
-

-
-
-

-
-
-
-
-
-
-
-
-
-
-

-
-
-

-
-
-
-
-
-
-
-
-

1.
2.
3.
4.
5.

# Image Alt Text for SEO in Vue

How to write effective image alt text in Vue for accessibility, Google Images ranking, and AI model understanding.

[![Harlan Wilton](https://avatars.githubusercontent.com/u/5326365?v=4)Harlan Wilton](https://x.com/harlan-zw)8 mins read Published Mar 23, 2026

What you'll learn

- Alt text is the [#1 accessibility failure](https://webaim.org/projects/million/) on the web, with 55.1% of homepage images missing it entirely
- Google Images accounts for [22.6% of all internet searches](https://sparktoro.com/blog/google-marketing-live-2019-recap/). Alt text is the primary ranking signal for image results
- Standard `<img>` tags in Vue give you full control over alt text. Write it for every informative image
- Google's John Mueller has stated alt text is [not primarily an SEO decision](https://www.searchenginejournal.com/john-mueller-alt-text-is-not-primarily-an-seo-decision/537035/), it is an accessibility one that also helps search

Alt text describes images for screen readers and search engines. Google cannot see your images the way humans do. It reads the `alt` attribute to understand what an image depicts, how it relates to the page, and whether it should appear in [image search results](https://developers.google.com/search/docs/appearance/google-images).

Missing alt text means missing ranking signals and accessibility failures. Every informative image on your site needs a descriptive `alt` attribute.

```
<img src="/dashboard-screenshot.webp" alt="Vue dashboard showing Core Web Vitals scores for mobile and desktop">
```

## [Why Alt Text Matters](#why-alt-text-matters)

Google Images handles [22.6% of all internet searches](https://sparktoro.com/blog/google-marketing-live-2019-recap/). Of every 1,000 Google searches, only [374 clicks go to the open web](https://sparktoro.com/blog/for-every-1000-google-searches-only-374-clicks-go-to-the-open-web/). Image search is one of the few channels where visual content can still drive organic traffic directly.

1. **Image search rankings**: Google's [image SEO documentation](https://developers.google.com/search/docs/appearance/google-images) explicitly lists alt text as a key ranking factor for image results.
2. **AI Overviews and citations**: SEMrush's [AI Overview study](https://www.semrush.com/blog/google-sge-study/) found that visual content with proper metadata is more likely to be cited in AI-generated snippets. Descriptive alt text helps AI crawlers understand what your images depict.
3. **Accessibility compliance**: Missing alt text is the [#1 accessibility error](https://webaim.org/projects/million/) across the web. WCAG 2.1 [requires text alternatives](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) for all informative images. The [European Accessibility Act](https://ec.europa.eu/social/main.jsp?catId=1202) became enforceable in June 2025, and the [ADA's web accessibility guidance](https://www.ada.gov/resources/web-guidance/) received updates in 2024. Legal risk is real.
4. **Core Web Vitals**: Images are often the [Largest Contentful Paint (LCP)](https://web.dev/articles/lcp) element. Alt text provides meaningful content to users while the image loads, and screen readers announce it immediately.

## [The State of Alt Text on the Web](#the-state-of-alt-text-on-the-web)

The [WebAIM Million report](https://webaim.org/projects/million/) audits the top 1,000,000 homepages annually. The results are not encouraging.

_Alt text quality across the top 1,000,000 homepages. Source: [WebAIM Million 2025](https://webaim.org/projects/million/)_

Over half of all homepage images have no alt text at all. Another 15% use generic strings like "image", "photo", or a raw filename. Fewer than 1 in 4 images have properly descriptive alt text.

### [Impact Comparison](#impact-comparison)

| Scenario | Search Result | Accessibility | AI Understanding |
| --- | --- | --- | --- |
| **Good alt text**: `alt="Bar chart comparing Vue vs React build times"` | Image ranks for relevant queries | Screen reader conveys meaning | AI understands the data being presented |
| **Missing alt text**: `alt=""` or no attribute | Image ignored in search | Screen reader skips image | AI has no image context |
| **Keyword-stuffed**: `alt="vue seo best vue framework vue optimize"` | Potential spam penalty | Confusing, unhelpful for users | AI may flag content as low quality |

## [Writing Effective Alt Text](#writing-effective-alt-text)

Good alt text is specific, concise, and describes what the image shows. The W3C provides an [alt text decision tree](https://www.w3.org/WAI/tutorials/images/decision-tree/) for determining the right approach per image type.

**Guidelines:**

- Be specific about what the image depicts, not what you want to rank for
- Include relevant keywords naturally where they fit the description
- Keep under 125 characters. Screen readers may truncate longer text
- Skip "image of" or "photo of" prefixes. Screen readers already announce the element as an image

For deeper technical guidance, see the [WebAIM Alternative Text guide](https://webaim.org/techniques/alttext/).

✅ Correct

❌ Wrong

```
<img src="/hero.webp" alt="Vue dashboard showing Core Web Vitals scores">

<img src="/team.webp" alt="Three developers collaborating at a whiteboard with system architecture diagrams">

<img src="/chart.webp" alt="Line graph showing 40% increase in organic traffic after implementing structured data">
```

```
<!-- Too vague -->
<img src="/hero.webp" alt="image">
<img src="/hero.webp" alt="screenshot">

<!-- Keyword stuffed -->
<img src="/hero.webp" alt="vue seo best vue seo tool vue optimization vue framework">

<!-- Empty alt on informative image -->
<img src="/chart.webp" alt="">
```

## [Vue Implementation](#vue-implementation)

### [Static Images](#static-images)

In Vue, standard `<img>` tags work exactly as in HTML. You don't need a special component:

pages/index.vue

```
<template>
  <img
    src="/hero.webp"
    alt="Vue SEO configuration panel with sitemap and robots settings"
    width="1200"
    height="600"
    loading="lazy"
  >
</template>
```

If you're using a library like [vite-imagetools](https://github.com/JonasKruckenberg/imagetools) or [unplugin-imagemin](https://github.com/unplugin/unplugin-imagemin) for image optimization, the `alt` attribute is still written on the same `<img>` element.

### [Dynamic Alt Text from API Data](#dynamic-alt-text-from-api-data)

When images come from a CMS or API, bind the alt text dynamically using Vue's `:alt` binding:

src/pages/products/[slug].vue

```
<script setup lang="ts">
import { onMounted, ref } from 'vue'
import { useRoute } from 'vue-router'

const route = useRoute()
const product = ref(null)

onMounted(() => {
  fetch(\`/api/products/${route.params.slug}\`).then(r => r.json()).then(d => product.value = d)
})
</script>

<template>
  <img
    v-if="product"
    :src="product.image"
    :alt="product.imageAlt"
    width="600"
    height="400"
  >
</template>
```

Always store alt text alongside the image URL in your CMS. Generating alt text after the fact is error prone and usually produces vague descriptions.

### [Content Images in Markdown](#content-images-in-markdown)

If your Vue app renders markdown content (via [markdown-it](https://github.com/markdown-it/markdown-it), [remark](https://github.com/remarkjs/remark), [mdream](https://mdream.dev), or similar), standard markdown image syntax maps to the `alt` attribute:

content/blog/my-post.md

```
![Comparison table of SSR vs CSR rendering times in Vue](/images/rendering-comparison.png)
```

The text inside the brackets becomes the `alt` attribute in the rendered HTML. Make sure your markdown renderer doesn't strip or ignore it.

## [Decorative vs Informative Images](#decorative-vs-informative-images)

Not every image needs alt text. The rule: if removing the image would lose information, it needs descriptive alt text. If the image is purely visual decoration, use an empty `alt=""` attribute. The W3C [decision tree](https://www.w3.org/WAI/tutorials/images/decision-tree/) walks through this logic step by step.

### [When to Use Empty `alt=""`](#when-to-use-empty-alt)

✅ Correct

❌ Wrong

```
<!-- Decorative background pattern -->
<img src="/bg-pattern.svg" alt="">

<!-- Icon next to a text label (label provides context) -->
<span>
  <img src="/icons/check.svg" alt="">
  Task complete
</span>

<!-- Spacer or decorative divider -->
<img src="/divider.svg" alt="">
```

```
<!-- Product photo with no alt -->
<img src="/product-shot.webp" alt="">

<!-- Chart that conveys data -->
<img src="/revenue-chart.png" alt="">

<!-- Screenshot showing a specific UI state -->
<img src="/error-modal.png" alt="">
```

### [CSS Background Images](#css-background-images)

Images applied through CSS don't have alt attributes and aren't indexed by Google Images. Use CSS backgrounds for purely decorative visuals:

components/HeroBanner.vue

```
<template>
  <div class="bg-cover bg-center h-96" style="background-image: url('/hero-bg.webp')">
    <h1>Welcome to Vue SEO</h1>
  </div>
</template>
```

If a CSS background image conveys information, consider switching to an `<img>` tag with proper alt text instead.

## [OG Image Alt Text](#og-image-alt-text)

When sharing links on social platforms, the `og:image:alt` meta tag describes the preview image for screen readers and assistive technology. Use `useSeoMeta()` from `@unhead/vue` to set it:

src/pages/blog/[slug].vue

```
<script setup lang="ts">
import { useSeoMeta } from '@unhead/vue'
import { onMounted, ref } from 'vue'
import { useRoute } from 'vue-router'

const route = useRoute()
const post = ref(null)

onMounted(() => {
  fetch(\`/api/posts/${route.params.slug}\`).then(r => r.json()).then(d => post.value = d)
})

useSeoMeta({
  ogImage: () => post.value?.ogImage,
  ogImageAlt: () => post.value?.title,
  twitterImage: () => post.value?.ogImage,
  twitterImageAlt: () => post.value?.title,
})
</script>
```

Note that social crawlers (Slack, Twitter, Facebook) fetch OG tags server-side. For social sharing meta tags to work correctly, your Vue app needs SSR via a framework like [Nuxt](https://nuxt.com), [Quasar](https://quasar.dev), or a custom [Vite SSR](https://vite.dev/guide/ssr) setup. Client-rendered SPAs will not surface OG tags to social crawlers. For more on social sharing meta tags, see the

 guide.

## [Automated Auditing](#automated-auditing)

Manually checking every image for alt text doesn't scale. Automate it with linting and testing tools.

### [ESLint for Vue Templates](#eslint-for-vue-templates)

The `eslint-plugin-vuejs-accessibility` plugin catches missing alt attributes at development time:

```
pnpm add -D eslint-plugin-vuejs-accessibility
```

eslint.config.ts

```
import pluginVueA11y from 'eslint-plugin-vuejs-accessibility'

export default [
  ...pluginVueA11y.configs['flat/recommended'],
]
```

This reports errors when `<img>` elements are missing alt attributes in your Vue templates.

### [Lighthouse Accessibility Audit](#lighthouse-accessibility-audit)

Chrome DevTools Lighthouse checks for missing alt text as part of its accessibility score. Run it against every page to catch issues that linting might miss (dynamic images, CMS content, third party embeds).

### [Runtime Testing with axe-core](#runtime-testing-with-axe-core)

For complete accessibility testing in CI, `axe-core` scans rendered pages:

tests/a11y.test.ts

```
import AxeBuilder from '@axe-core/playwright'
import { expect, test } from '@playwright/test'

test('homepage has no accessibility violations', async ({ page }) => {
  await page.goto('/')
  const results = await new AxeBuilder({ page }).analyze()
  expect(results.violations).toEqual([])
})
```

This catches missing alt text on dynamically rendered images that static linting cannot detect.

## [Common Mistakes](#common-mistakes)

**Prefixing with "image of" or "photo of"**: Screen readers already announce "image" before reading the alt text. Writing `alt="Image of a sunset"` results in "image, Image of a sunset" being read aloud. Write `alt="Sunset over the Pacific Ocean"`.

**Keyword stuffing**: Cramming keywords into alt text can trigger Google's spam filters and provides a terrible screen reader experience. Write for humans first. Google's John Mueller has [explicitly stated](https://www.searchenginejournal.com/john-mueller-alt-text-is-not-primarily-an-seo-decision/537035/) that alt text is primarily an accessibility decision, not an SEO one.

**Empty alt on informative images**: An image that conveys meaning (charts, product photos, screenshots) should never have `alt=""`. Empty alt tells screen readers to skip the image entirely.

**Same alt text on every image**: Using identical alt text across a product gallery (e.g., `alt="Product photo"` on 10 images) provides no useful information. Describe what makes each image unique: the angle, the color variant, the specific feature shown.

**Skipping alt on dynamic images**: When you render images from API data, it's easy to bind `:src` and forget `:alt`. Always pair them. A missing `alt` attribute (not the same as `alt=""`) causes screen readers to read the image filename aloud instead.

---

On this page

- [Why Alt Text Matters](#why-alt-text-matters)
- [The State of Alt Text on the Web](#the-state-of-alt-text-on-the-web)
- [Writing Effective Alt Text](#writing-effective-alt-text)
- [Vue Implementation](#vue-implementation)
- [Decorative vs Informative Images](#decorative-vs-informative-images)
- [OG Image Alt Text](#og-image-alt-text)
- [Automated Auditing](#automated-auditing)
- [Common Mistakes](#common-mistakes)

[GitHub](https://github.com/harlan-zw/nuxt-seo) [ Discord](https://discord.com/invite/275MBUBvgP)

###

-
-

Modules

-
-
-
-
-
-
-
-
-

###

-
-
-

###

Nuxt

-
-
-
-
-

Vue

-
-
-
-
-
-
-
-

###

-
-
-
-
-
-
-
-
-
-

Copyright © 2023-2026 Harlan Wilton - [MIT License](https://github.com/harlan-zw/nuxt-seo/blob/main/license) · [mdream](https://mdream.dev)