Publish to your code site via GitHub
If your site is built with Next.js, Astro, Hugo — or anything from Lovable, Replit, v0, Cursor, or Claude Code — Cite publishes by opening a pull request. You review and merge; your existing deploy ships it. Cite never pushes to your main branch.
Why a pull request?
Code sites have no CMS “publish” button — the content is a file in your repo. So Cite adds the article as a Markdown/MDX file on a new branch and opens a PR. The PR is the review step: you see exactly what lands, merge it, and your normal Vercel/Netlify build deploys it. Same approval gate as everywhere else in Cite.
Connect your repo (2 minutes)
- 1In Cite, go to Settings → Publishing → GitHub / code site and click Connect GitHub. Grant access to the repo you choose — with repo write permission, so Cite can open PRs.
- 2Pick the repository your website is built from.
- 3Confirm where articles go. Cite detects your framework and proposes a folder (e.g.
content/blog/). Change it if your blog lives elsewhere. - 4Enter your live site URL — used for the canonical tag.
- 5Save. Cite verifies it can reach the repo and the base branch.
Publishing an article
- Approve the article in the Editor, then in the Publish panel pick GitHub → Open PR.
- Cite opens a pull request adding the article file, with schema.org markup and a canonical tag included.
- Review the file, merge the PR. Your deploy ships it — and Cite marks the article live with its URL.
Requirement: your blog must be crawlable
To get cited by AI search, your article page must be server-rendered or statically generated — not a client-only single-page app. Most Next.js, Astro, and Hugo sites are static by default. If your site is a client-only SPA (e.g. plain Vite/CRA), AI crawlers can't read the article and it won't be cited. Cite warns you at connect time if it detects this.
Also make sure your robots.txt allows retrieval bots (OAI-SearchBot, PerplexityBot, Claude-SearchBot) even if you block AI training bots — they're separate, and blocking training does not block citation.
Supported setups
Next.js (App or Pages Router), Astro, Hugo, Jekyll, SvelteKit, Gatsby — and any repo built with Lovable, Replit, v0, Bolt, Cursor, or Claude Code. Cite detects the framework and proposes the right folder, filename, and frontmatter; you can edit any of it. Not on a code site? WordPress publishes in one click, and Markdown export works for everything else.