AI SEO Content for Your Jekyll Site, Written Into _posts at Build
omnifamous researches winnable keywords and writes ranking-ready articles. A small Node prebuild pulls the published ones with @omnifamous/node and writes them into your Jekyll _posts folder. Keep your stack, your host, and your design.
Coming soonSync your published articles into Jekyll _posts with a Node prebuild. Target keyword: jekyll blog seo
A headless SEO blog for Jekyll, 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 with the read-only @omnifamous/node SDK from a small Node prebuild script, newest published first.
Writes one YYYY-MM-DD-slug.md file per article into _posts before your Jekyll build, so the fetch happens once and Jekyll renders static HTML.
Keeps your Jekyll theme, your layouts, and your host (including GitHub Pages). We are the content source, not another framework to adopt.
Tracks whether ChatGPT, Perplexity, and Google AI cite your Jekyll pages, then writes more of what earns the citation.
From keyword to a Jekyll 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 run a prebuild that writes each article into _posts as dated markdown, then let Jekyll build.
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.
Jekyll builds from files and does not run JavaScript at build time, so add a small Node prebuild script that uses @omnifamous/node to fetch published articles and write each one into _posts as a YYYY-MM-DD-slug.md file with front matter. Run it before jekyll build. omnifamous does the research and writing; Jekyll renders the markdown.
Jekyll requires the YYYY-MM-DD-slug.md convention, so the prebuild derives the date from each article publishedAt and the slug from the article slug. The date and title also go into the post front matter.
Yes. Run the prebuild in a GitHub Actions workflow that fetches the articles, writes them into _posts, and then builds and deploys. Your token lives as a repository secret and never ships to the site. This is the same GitHub-backed pattern our connector uses.
Each article ships with an SEO block (meta title, description, JSON-LD, hreflang). The prebuild writes the title and description into front matter, and your layout renders 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 the token lives in your build environment, never in the generated site.
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.