AI SEO Content for Your Nuxt Site, Loaded Server-Side
omnifamous researches winnable keywords and writes ranking-ready articles. Your Nuxt app pulls the published ones over a read-only API with @omnifamous/node inside useAsyncData. Keep your stack, your host, and your design.
Coming soonPull your published articles into Nuxt with @omnifamous/node. Target keyword: nuxt blog seo
A headless SEO blog for Nuxt, without leaving your stack
We do the work, not give you another dashboard. Here is what the engine does for your brand.
Pulls your published articles into Nuxt with the read-only @omnifamous/node SDK: listArticles for the index and getArticle for each slug, newest published first.
Fetches inside useAsyncData, which runs on the server for SSR and SSG, so the SDK token stays private and results are cached for the render.
Keeps your Nuxt app, your components, and your host. We are the content source, not another framework to adopt.
Tracks whether ChatGPT, Perplexity, and Google AI cite your Nuxt pages, then writes more of what earns the citation.
From keyword to a Nuxt page that ranks
Four steps. You stay the editor, the engine handles the rest.
Run the free AI visibility audit. We check your brand across the major AI engines and find the gaps worth filling.
We research winnable keywords and write each article ranking-ready, with headings, internal links, images, and an SEO block.
Install @omnifamous/node and build the client from server-only runtime config inside a composable, then call it from useAsyncData.
We keep writing and you keep rebuilding, so your rankings and AI citations grow month over month.
Questions, answered
Everything you need to know about how the engine does the work for you.
Install @omnifamous/node and wrap it in a composable that builds a client from server-only runtimeConfig. Call listArticles inside useAsyncData for your blog index and getArticle({ slug }) for each post. Because useAsyncData runs on the server, your token never reaches the browser. omnifamous does the research and writing; Nuxt just pulls the content.
Yes. Build the client from runtimeConfig (the private, server-only side) and call it inside useAsyncData, which executes on the server during SSR and SSG. The token is never serialized into the page payload.
Yes. useAsyncData runs on the server in both modes. With nuxt generate you get static pages built once per deploy; with SSR you fetch per request (delivery responses are cached around 60 seconds, so the origin is rarely hit).
Each article ships with an SEO block (meta title, description, JSON-LD, hreflang). Feed it into useHead or useSeoMeta on the article page, so every page is optimized for search engines and AI answer engines.
Yes. @omnifamous/node is read-only and pulls only published articles. It never publishes or mutates anything, and running it server-side inside useAsyncData keeps your key private.
Still have questions? Talk to us
One engine, every destination
Write once, publish to every CMS your audience reads, and optimize for AI search at the same time.
See where your brand stands in AI search
Run a free AI visibility audit. We check your brand across ChatGPT, Claude, Gemini, and more, then write and publish the content that gets you cited.
Run my free auditNo credit card required. Results in under 5 minutes.Join the Omnifamous waitlist
Tell us about your site and we'll let you in when your spot opens up.