AI SEO Content for Your Astro Site, Generated at Build Time
omnifamous researches winnable keywords and writes ranking-ready articles. Your Astro site pulls the published ones over a read-only API with @omnifamous/node. Keep your stack, your host, and your design.
Coming soonPull your published articles into Astro with @omnifamous/node. Target keyword: astro seo content
A headless SEO blog for Astro, 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 Astro with the read-only @omnifamous/node SDK: listArticles in your index frontmatter and getArticle for each page, newest published first.
Generates one static page per article with getStaticPaths, so everything renders at build time and readers hit static HTML, not a live API.
Keeps your Astro project, your components, and your host. We are the content source, not another framework to adopt.
Tracks whether ChatGPT, Perplexity, and Google AI cite your Astro pages, then writes more of what earns the citation.
From keyword to an Astro 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 pull articles in your index frontmatter, then use getStaticPaths to build a page per slug.
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, create a client with your delivery token and workspace id in the component frontmatter, then call listArticles for your blog index. Use getStaticPaths plus getArticle({ slug }) to statically generate one page per published article. omnifamous does the keyword research and writing; Astro just pulls the finished content.
Yes. Astro runs your frontmatter and getStaticPaths at build, so articles are fetched once and rendered to static HTML. Delivery responses are also server-side cached for around 60 seconds. Trigger a rebuild (or a scheduled build) when you want the newest articles live.
Yes. The delivery API returns trusted, rendered HTML for the body, which you drop in with set:html. You can also request the markdown export if you would rather run it through your own Astro markdown pipeline.
Each article ships with an SEO block (meta title, description, JSON-LD, hreflang). You read it in frontmatter and set your <title> and <meta> tags in the Astro layout, 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. Because frontmatter runs at build on the server, your token stays out of the shipped output.
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.