Loading...
14.x and later
Vaza automatically optimizes your Next.js site for search engines and AI answer engines. Works with App Router, Pages Router, and all rendering strategies (SSG, SSR, ISR). No configuration needed.
Auto-detects your routing strategy and adapts all SEO fixes accordingly. Metadata API for App Router, _document.tsx for Pages Router.
Fixes LCP, CLS, and INP issues specific to Next.js: next/image priority, font optimization with next/font, layout shift from hydration.
Automatically migrates raw <img> tags to next/image with proper sizing, lazy loading, and descriptive alt text for Google Images.
Generates metadata exports, OpenGraph tags, Twitter Cards, and JSON-LD schema using Next.js metadata conventions.
Understands ISR patterns and sets appropriate cache headers, lastmod dates, and revalidation signals for search engines.
Every SEO fix is verified with next build before pushing. If a fix breaks the build, the AI self-heals or reverts automatically.
// app/layout.tsx — auto-generated by Vaza
export const metadata: Metadata = {
metadataBase: new URL('https://yoursite.com'),
title: { template: '%s | Your Brand', default: 'Your Brand' },
robots: {
index: true, follow: true,
googleBot: { 'max-snippet': -1, 'max-image-preview': 'large' },
},
openGraph: { siteName: 'Your Brand', locale: 'en_US' },
twitter: { card: 'summary_large_image', site: '@yourbrand' },
}Yes. Vaza auto-detects whether you use App Router or Pages Router and adapts all SEO optimizations accordingly. It uses the Metadata API for App Router and _document.tsx patterns for Pages Router.
No. Every change is verified with next build before pushing to your repo. If a fix causes a build error, the AI attempts to self-heal. If that fails, the change is reverted automatically.
Yes. Vaza works with any hosting platform. It detects your deployment target and adapts headers, redirects, and caching rules accordingly.