What this prompt does
This prompt asks the model to act as a senior Nuxt engineer and build an SEO-ready marketing site that renders and passes a Lighthouse SEO check, returning working code rather than pseudocode. You set the [brand], the [pages], the [content_source], and the primary [keyword_theme], and it returns a project structure with @nuxt/content and @nuxt/image, the routes, per-page SEO meta, structured data, a sitemap and robots, responsive images, a dark-mode toggle, and a keyword-aware outline.
The structure works because the gap between a pretty site and one that ranks is all the unglamorous SEO plumbing. By driving per-page title/description, canonical, and Open Graph + Twitter meta through useSeoMeta, adding Organization and WebSite/Article JSON-LD, and auto-generating a sitemap, the prompt makes that plumbing concrete. [pages] defines the routes, [content_source] defines authoring, and [keyword_theme] shapes the content outline. Pairing @nuxt/content with @nuxt/image means writers work in markdown while images are emitted in optimised variants, so the site stays fast without a custom build pipeline.
When to use it
- You're building a marketing site or landing pages that actually need to rank.
- You want @nuxt/content for markdown pages and @nuxt/image for optimised assets.
- You need per-page SEO meta, canonical tags, and Open Graph driven by
useSeoMeta. - You want structured data plus an auto-generated sitemap and robots.
- You need responsive images with width/format variants and lazy loading.
- You want a keyword-aware content outline around a target theme.
- You want a persistent dark-mode toggle without wiring it from scratch.
Example output
Expect the file tree, the nuxt.config, one content page, and the SEO/meta composable. Around those, the build covers the [pages] routes authored via [content_source], per-page SEO meta through useSeoMeta, Organization and WebSite/Article JSON-LD, an auto-generated sitemap and robots, responsive images with format variants and lazy loading, a persistent dark-mode toggle, and a keyword-aware outline for the home and one inner page around [keyword_theme]. Together these give you a deployable starting point that already has the meta, structured data, and image handling a Lighthouse SEO check looks for.
Pro tips
- Validate your structured data before launch — one malformed JSON-LD block and the rich result silently never shows.
- Define
[pages]to match your real site map (e.g. home, features, pricing, blog) so routes and the sitemap are complete. - Set
[content_source]to how you'll actually author (e.g. local markdown in content/) so the @nuxt/content setup fits your workflow. - Make
[keyword_theme]specific; a vague theme produces a generic outline that won't target real search intent. - Use
[brand]consistently so the Organization JSON-LD and meta titles reflect the real product name. - Check the responsive images actually emit width/format variants, since image weight is a common Lighthouse drag.
