Webflow

Choose the supported connection

For a managed blog, choose Another website platform in RankYourApp and the managed placement at blog.yourcompany.com. You need a domain you control and access to its DNS records. Articles are hosted on that subdomain; this route does not write them into a Webflow CMS collection.

RankYourApp's current customer connection does not ask for a Webflow API token, collection ID or OAuth app. You do not need to create those for the managed route.

Connect the blog domain

1. Request the records under Connect your own blog domain in RankYourApp.
2. Add each record at the DNS provider for your domain. Keep the records that serve your existing Webflow website.
3. Return to RankYourApp and click Check DNS, HTTPS and installation.
4. Continue when Live domain verified appears, then open and copy the live HTTPS blog address.

DNS instructions and provider guides

Add Blog to your Webflow navigation

1. Open the Webflow project in the Designer. If it has no Navbar, open Add Elements (A) → Elements → Other, then add Navbar to the canvas. Keep an existing navigation design when there is one.
2. Select an element in the Navbar and open Settings → Navbar settings → Add link.
3. Select the new nav link. In the Settings panel, open Nav Link settings and choose Type → URL. Enter your verified live blog address in URL, such as https://blog.yourcompany.com.
4. Set Text to Blog, or your preferred label. For primary Blog navigation, set Open in → This tab. Reopen the link settings to check that the address and label were saved.
5. Test the link in the Designer’s preview, then review unrelated unpublished changes before publishing the website.
6. Check the link on the public website and mobile menu after publication.

Use the live blog address returned by your setup. Webflow’s official navbar instructions

Existing Webflow blogs and custom API installations

If you already use a Webflow CMS blog, connecting a managed subdomain creates a separate destination. It does not import, replace or redirect those existing CMS posts. Preserve their URLs and decide any migration separately. Existing blogs

To use your own site's article path through the Developer API, your developer must implement the public installation contract, including server-rendered or freshly built article HTML, secret storage, sitemap updates and real 404s. A Webflow embed or browser-side API call alone does not meet that contract. No native Webflow CMS connector is offered by the current form.