Lovable

The Lovable integration lets RankYak publish articles to a site you built with Lovable. A Lovable site has no CMS for RankYak to log in to, so Lovable creates the receiving end instead: RankYak provides a setup prompt, Lovable adds a blog and a webhook to your project, and from then on every new article is delivered to your site, live or as a draft for your review.

Connecting

The connection takes three steps: one in RankYak, one in Lovable, and one back in RankYak.

1. Go to Settings, then Integrations, click Connect next to Lovable, and click Continue. RankYak creates the connection with a secret and opens the connection settings, which show the setup prompt.
2. Click Copy prompt and paste the prompt into the chat of your Lovable project. The prompt makes Lovable create an articles table, a webhook that checks the secret and stores each article, and the pages /blog and /blog/:slug. Depending on how your project runs its backend, the webhook is a Supabase edge function named rankyak-webhook or a route on the project's own server. The prompt carries the secret; if Lovable asks you to enter it in a secrets form instead, click Copy secret in RankYak and paste it there. When Lovable finishes, it prints the URL of the webhook.
3. Back in RankYak, paste that URL into Webhook URL and click Save. RankYak sends a test request to the URL, and when your site answers, the connection shows as connected. Publishing starts with the next scheduled article.

You should publish your Lovable project after the setup, so the blog pages are live when the first article arrives. The prompt asks Lovable to build article links from the published domain of your site; if the links RankYak shows point at the preview domain instead, ask Lovable to use the published domain, or fill in Blog URL in the connection settings. Of course, you may reopen the setup prompt and the secret at any time by clicking Edit settings next to the connection.

If the test request fails, RankYak keeps the URL and tells you why under the field. Typically, a rejected secret means the secret was not stored in your project, or the edge function still requires a Supabase sign-in, which the prompt asks Lovable to turn off. Ask Lovable to correct it, then click Save again.

What your site receives

Each article arrives at your webhook as JSON: the title, the body as HTML and as Markdown, the excerpt, the meta title and description, the URL slug, the header image URL, and the relevant dates. The body holds no title of its own, so your pages render the title as the heading. The article object matches the payload described on the webhooks page, wrapped in an event name and a status. The secret travels in a request header, so only RankYak writes to your blog.

Your site answers with the address of the new article page, and RankYak shows that address as the live link on the article. If your site answers with something else, you may enter a Blog URL in the connection settings, and RankYak builds the link from that URL and the slug. You may also report the address through the article's actions menu or the API.

The Lovable connection is separate from the webhook in the Developer zone. You should not point both at the same endpoint, since your site would then receive every article twice.

Publishing as drafts

If you would like to review each article before it goes live, enable Publish articles as draft in the connection settings. Each article then arrives with the status draft, your site stores it without showing it, and you decide in your project when it goes live, for example by changing its status in the table. A draft has no address yet, so RankYak leaves the live link empty until you report it.

Updating articles

When an article is refreshed or rewritten in RankYak, it is delivered again with the event article.updated. Your site replaces the stored article by its id, so the page keeps its address and no duplicate appears. However, if you change the slug of an article in RankYak, the site stores the new slug and the old address no longer resolves, so you should add a redirect in your project when an address has already been shared.

Search engines

Lovable renders pages in the browser by default, so a page's title, description, and content arrive after its scripts run. The prompt asks Lovable to prerender the blog pages where the project allows it, and you should check that the article pages are served with their content in the HTML, so search engines read them without running JavaScript.

When something fails

If your site answers with an error or cannot be reached, the article stays unpublished in RankYak. The article page shows the message your endpoint returned, and the owner of the organization receives an email with the same message. Fix the endpoint in Lovable, then publish the article again from its page.

Disconnecting

To stop publishing to your Lovable site, go to Settings, then Integrations, and click Disconnect next to the connection. Publishing stops immediately; articles already on your site are not affected. Connecting again creates a new secret, so you should update RANKYAK_WEBHOOK_SECRET in your Lovable project before the first article is delivered.