Set the lang attribute on <html> — v0

Missing lang attribute means screen readers use the wrong pronunciation and Google may serve your page to the wrong language market.

rocket_launch

Fixing this in v0

Vercel AI component and app generator

v0 scaffolds Next.js App Router code — most fixes live in metadata objects and Server Components. Paste the prompt below into your v0 chat and the fix rolls out across the project in one pass.

Using a different tool? Pick your stack:

Lovable Cursor Bolt v0 Replit Windsurf Claude Code Base44

The prompt for v0

Copy and paste this into your v0 chat exactly as-is.

Regenerate my v0 component / page with these fixes applied:

Add lang attribute to HTML

1. Add lang="en" (or the correct language) to the <html> tag.

Why this matters

The lang attribute tells browsers, screen readers, and search engines which language the page is in. Without it, screen readers use the OS default (often wrong), and Google may misidentify the target market.

For multilingual sites, set lang correctly on each locale and use hreflang tags for alternates. This is how Google decides which version to serve for German-speaking users vs. English-speaking.

How to use this prompt in v0

1. Open your v0 project.
2. Copy the prompt above with the copy button.
3. Paste into the v0 chat and send.
4. Review the diff, accept the changes, redeploy.
5. Verify the fix using the checklist below.

Common mistakes to avoid

error_outlineLeaving the default `lang="en"` on a German site — Google serves English users.
error_outlineForgetting to update lang when adding i18n support.
error_outlineUsing `lang="en-US"` for a global English site — en-US is fine, but `en` is enough.

How to verify the fix worked

check_circleView source — `<html lang="...">` matches your content language.
check_circleLighthouse Accessibility → "HTML has a lang attribute" passes.
check_circleGoogle Search Console → International Targeting report — matches your intent.

Frequently asked questions

Should I use en or en-US?expand_more

Either works. en-US for US-specific English; en for general. Both pass accessibility.

How do I handle multilingual pages?expand_more

One `lang` per page matching the content. Use hreflang tags in the head to link between language versions.

Want all 34 prompts tailored to your v0 site?

Pantra scans your site in 10 seconds, detects the stack, and generates the exact prompts that apply — only the ones you actually need.

Scan my site

Related v0 prompts

Technical