AI SEO Content for Your Eleventy Site, Rendered at Build Time
omnifamous researches winnable keywords and writes ranking-ready articles. Your Eleventy site pulls the published ones from a _data file with @omnifamous/node. Keep your stack, your host, and your design.
Coming soonPull your published articles into Eleventy with @omnifamous/node. Target keyword: eleventy blog seo
A headless SEO blog for Eleventy, 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 Eleventy with the read-only @omnifamous/node SDK from a _data file that returns every article, newest published first.
Runs once per build, so any 11ty template can loop over the articles collection and pagination renders to static HTML.
Keeps your Eleventy project, your templates, and your host. We are the content source, not another framework to adopt.
Tracks whether ChatGPT, Perplexity, and Google AI cite your Eleventy pages, then writes more of what earns the citation.
From keyword to an Eleventy 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 return every published article from a _data/articles.js file, paginating the SDK until hasMore is false.
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 add a _data/articles.js file that creates a client and returns every published article by paginating listArticles. Any 11ty template can then loop over the articles collection and use pagination to build one page per post. omnifamous does the research and writing; 11ty just renders the pulled content.
Once per build. The _data file runs at build time, so the fetch happens when you build the site and everything renders to static HTML. Trigger a rebuild (or a scheduled build) when you want the newest articles live.
Use 11ty pagination over the articles data with size 1, and set the permalink from each article slug. Fetch the full body with getArticle inside the data file if you want the content available in the template.
Each article ships with an SEO block (meta title, description, JSON-LD, hreflang). Read those fields in your Nunjucks or Liquid layout and set the head tags, 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 because the _data file runs at build on your machine or CI, 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.