SEO and AI search content for AI-built websites

The site's built, the content isn't

Lovable, Bolt, v0, Replit, Framer or Webflow got the site live. Rankbox finds the questions your buyers ask AI engines, writes long, sourced articles in your brand voice, scores each one for search and AI answers, and hands them to your site through its API. Its research tools work inside your builder's chat, too.

Start with your URL

7-day free trial · Card required · Cancel anytime

sourced, long-form articles per site
30/mo
AI tools that can call its research over MCP
49 tools
HTML and Markdown, for any stack
REST API
scores on every article before it ships
SEO + GEO
Sample. The same page, twice: as people see it in the builder's preview, and as a crawler that doesn't run JavaScript receives it. Tallyfold is a sample app.

What is Rankbox for sites built with AI?

Rankbox is an AI search growth engine for websites made with an AI app builder such as Lovable, Bolt, v0 or Replit, or with Framer or Webflow. It finds the questions buyers ask ChatGPT, Perplexity, Gemini and Google AI Overviews about the site's topic, writes source-backed articles of about 2,000 to 3,500 words in the site's brand voice, scores each one for SEO and GEO, and delivers them through a REST API. Its research tools also run inside those builders over MCP. It does not audit or fix how a site renders, so a page that only builds in the browser can still look empty to crawlers.

Check this first

Your article only counts if it's in the HTML

Rankbox writes the article. Whether a crawler can read it depends on how your builder renders the page, and that differs by builder, by stack and by when the project was made.

  • Built in the browser

    Often empty

    The server sends an almost empty HTML file and JavaScript fills the page in. A crawler that doesn't run JavaScript gets the empty file.

    Andrea Saez, Feb 13, 2026 · Vercel and MERJ, Dec 17, 2024

  • Pre-rendered for crawlers

    Usually readable

    A rendered copy of the page is served to bots when they ask for it. Lovable does this for its older React and Vite apps, for verified crawlers only.

    Lovable docs, checked Nov 10, 2026

  • Rendered on the server

    Readable

    Every request returns the full HTML. Lovable apps created from May 13, 2026 work this way, and Framer pre-renders every page to HTML before serving it.

    Lovable docs · Framer Help, updated Sep 15, 2026

Rankbox doesn't check or change any of this. The free AI Search Readiness Check fetches your page without JavaScript and counts the words a crawler can read.

Run the free readiness check
After launch

What the builder didn't build

Lovable says 100,000 new projects start on it every day (its own figure, November 2025). A builder is quick at the app. It doesn't know what your buyers ask, and one prompt per blog post doesn't add up to a library.

  1. 01

    The site is a landing page, a pricing page and a sign-up form. Nothing on it answers a question a buyer would ask.

    Rankbox reads your URL and lists the questions buyers ask AI engines about your topic, grouped by intent, for you to approve.

  2. 02

    Asking the builder for a blog post gets a short, generic page with no sources behind it.

    Each article is researched and source-backed, about 2,000 to 3,500 words, in the brand voice you set for the site.

  3. 03

    There's no way to tell whether a page is any good for AI answers before it goes live.

    Every article gets an SEO score and a GEO score before it ships, and the editor lets you fix what's weak.

  4. 04

    You work in the builder's chat. Another dashboard is one more tab you won't open.

    Add Rankbox's MCP server to Lovable, Bolt, v0, Replit or Cursor and ask for questions, briefs and meta descriptions from the chat.

Inside your tools

Research in the chat, articles by API

You already build by asking. Rankbox's research answers in the same chat, and finished articles reach your site through an API your builder can wire up.

MCP server, in the builder

Add https://rankbox.xyz/mcp as a custom MCP server and your builder can call three Rankbox tools: questions people ask AI about a topic, a content brief for a keyword, and meta descriptions for a page.

  • Use Rankbox to find what people ask AI about invoicing for freelancers.
  • Get a Rankbox brief for “late invoice reminder” and build the post from it.
  • Write meta descriptions for every page with Rankbox.

Works in the builder's chat, not inside your published app. It researches; it doesn't publish.

REST API, in your code

Fetch finished articles as HTML and Markdown, with slugs, meta descriptions and tags, then report each live URL back.

// Server code or a build step, never the browserconst key = process.env.RANKBOX_API_KEY;const res = await fetch(  "https://rankbox.xyz/api/public/v1/articles?limit=100",  { headers: { Authorization: `Bearer ${key}` } },);const { articles } = await res.json();

Keep the key on the server. In a Vite app, any variable that starts with VITE_ ships to the browser, where anyone can read it.

REST APIRead the API recipes
How it fits

Two places, four steps

Rankbox does the research and the writing. Your builder builds the page that shows it.

  1. 1

    In Rankbox

    Paste your URL

    Rankbox reads the site, you set its brand voice (tone, audience, product details), and it lists the questions your buyers ask AI. Approve the ones worth writing.

  2. 2

    In your builder

    Add the MCP server

    Paste https://rankbox.xyz/mcp into your builder's MCP settings, then ask for questions, briefs or meta descriptions while you build pages.

  3. 3

    In your builder

    Build the blog route

    Ask the builder for a blog that fetches from the Rankbox REST API in server code or at build time, so each article is in the HTML crawlers get.

  4. 4

    In Rankbox

    Articles go out

    Rankbox writes on the schedule you set, up to 30 a month. Your site picks up each finished article on its next pull and can report the live URL back.

Who does what

Rankbox writes it. Your build renders it.

Rankbox runs this

  • The question list

    What buyers ask AI engines about your topic, found from your URL.

  • Long-form drafts

    Sourced articles of about 2,000 to 3,500 words, in your brand voice.

  • A score before it ships

    An SEO score and a GEO score on every article, so you see what's weak.

  • Delivery by API

    Finished articles as HTML and Markdown, on the schedule you set.

Your build keeps this

  • How the page renders

    Server-rendered or pre-rendered HTML is your stack's job. Rankbox doesn't check it.

  • The blog route

    The page and layout that show an article, built in your builder.

  • The API key

    Kept in server code or a build step, never in code the browser downloads.

  • What's true about the product

    Features, prices and promises. Read and edit every draft before it goes out.

Features

The four parts that matter here

The builder made the app. These are the parts of Rankbox that make the content.

What it replaces

What you'd otherwise wire up

The usual ways a builder-made site gets content, each one another thing to connect and keep fed.

  • A prompt per blog postShort pages, no research, no sources
  • A headless CMSAnother account and schema, and still nobody writing
  • A keyword toolSearch volumes, not the questions people put to AI
  • A freelance writerA brief for every post and an edit on every draft
  • Writing it yourselfBetween shipping features, so rarely

One plan is $49.50 a month per site, with 30 articles, the REST API and the MCP server included. Built more than one app? Studio adds each extra site for $49.50 a month on the same invoice.

Business · One site, one plan

$49.50a month per site

  • 30 sourced, long-form articles a month
  • SEO and GEO scores on every article
  • The REST API and the MCP server
  • Backlink-exchange and Reddit-draft allowances, rolling out

More than one app? Studio adds each extra site for $49.50 a month, with a full plan of its own.

Start free trial

7-day free trial · Card required · Cancel anytime

See pricing

FAQ

Questions builders ask

Read the docs

My site was built with Lovable. Can crawlers read it?

It depends on when and how it was built, and Rankbox can't tell you. Lovable's docs say apps created from May 13, 2026 (June 22 on Enterprise plans) render on the server, and older React and Vite apps are pre-rendered for verified crawlers. A single-page app that builds itself in the browser sends crawlers an almost empty HTML file, and a Vercel and MERJ study (December 2024) found that the major AI crawlers it measured, apart from Google's and Apple's, didn't run JavaScript. The free AI Search Readiness Check counts the words a page shows without JavaScript.

Does Rankbox fix rendering or audit my site?

No. Rankbox doesn't audit sites, change your code or fix how pages render, and it has no rank tracker or link index. It researches, writes and scores articles and delivers them through its API. Making sure each article is in the HTML your server sends is your build's job.

How do articles get onto a site built with Lovable, Bolt, v0 or Replit?

Today articles reach your site through the Rankbox publishing API, which a developer sets up once, and plugins for Shopify, WordPress, Webflow, Square, and Framer are in development. On a builder-made app, ask the builder to add a blog that fetches from the REST API in server code or at build time. Keep the API key out of browser code: in a Vite app, any variable that starts with VITE_ is copied into the code visitors download.

What can my builder do with the MCP server?

Three things: find the questions people ask AI engines about a topic, build a content brief for a keyword, and write meta descriptions for a page. Add https://rankbox.xyz/mcp as a custom MCP server in Lovable, Bolt, v0, Replit, Cursor or any of the 49 tools Rankbox lists. It works in the builder's chat, not inside your published app, and it doesn't publish anything.

I built on Framer or Webflow. Does this work?

Yes. Framer's help docs say every Framer page is pre-rendered to HTML on its servers, so crawlers that skip JavaScript still get the text. Check a Webflow page the same way with the free readiness check. On the Rankbox side, the Framer plugin isn't live yet, and the Webflow app is built and waiting on Webflow's Marketplace approval, so for now articles come through the REST API, which a developer connects to your CMS.

Will this get my site quoted by ChatGPT or Google AI Overviews?

Nobody can promise that, and Rankbox doesn't track citations or rankings, so it can't tell you whether you're quoted. What Rankbox controls is the article: researched questions, sourced claims, and a GEO score for how ready the page is to be quoted. To see what happens after it's live, use Google Search Console and your analytics.

Do I need to be a developer?

Not for the research and the writing: you paste a URL, approve topics and edit drafts in Rankbox. Putting articles on a custom-built app means wiring the REST API once, which you can ask your builder or coding agent to do, then checking the live page with the free readiness check.

What does it cost?

$49.50 a month per site, with 30 articles, the REST API and the MCP server included. Each extra site on Studio is $49.50 a month on the same invoice. Start with a 7-day free trial. A card is required, and you're charged $49.50/month 7 days after you start, unless you cancel first.

Where this page's facts come from

Checked on November 10, 2026. Builders change fast, so check your own site too.

  • Lovable · Nov 18, 2025

    One year of Lovable

    100,000 new projects a day, in Lovable's own words.

  • Lovable docs · Checked Nov 10, 2026

    SEO and AI search

    Server rendering for apps created from May 13, 2026; pre-rendering for older ones.

  • Vercel and MERJ · Dec 17, 2024

    The rise of the AI crawler

    The major AI crawlers measured, apart from Google's and Apple's, didn't run JavaScript.

  • Andrea Saez · Feb 13, 2026

    The Lovable SEO problem

    A client-rendered Lovable site served crawlers an empty root element.

  • Framer Help · Updated Sep 15, 2026

    Make your site readable by AI agents

    Every Framer page is pre-rendered to HTML before it's served.

Other situations

Keep exploring

Serve every crawler a page it can read

Key terms

Give the site something to say

Paste your URL and see the questions your buyers already ask AI about what you built.

Start free trial

7-day free trial · Card required · Cancel anytime