Connect your website: setup checklist
What to prepare, where credentials come from and how to finish both sides of a connection.
Choose the route your website supports
Start with your website platform and the address where visitors should read your articles. Select the intended website and open Connections. You must be an owner of its RankYourApp workspace to manage connections or workspace API keys. A member without that role needs the workspace owner to complete those actions. You also need access to the external website’s publishing settings; a managed blog needs access to its domain’s DNS service.
| Your website | Supported setup | What you supply |
|---|---|---|
| WordPress | Direct WordPress posts | HTTPS site address, blog index address, WordPress login username and site-specific application password |
| Framer | Direct CMS publishing | Framer editor project URL, that project's Server API key, collection, field mappings and article URL prefix |
| Lovable, Cursor, Windsurf, Bolt, Replit or a developer-built site | Install our content API on your website | RankYourApp installation prompt and workspace key, server/build access and a deployed public blog |
| Webflow, Wix, Shopify, Squarespace or another platform | Managed blog on blog.yourcompany.com | A domain you control, the exact DNS records shown during setup and a link from your main website |
Which API key or password do I create?
An API key is a secret that lets software connect to a service. Create only the credential required by your selected route.
| Credential or setting | Where it comes from | Where it goes |
|---|---|---|
| WordPress application password | Your WordPress site's Users → Profile | RankYourApp's WordPress Application password field |
| Framer project API key | The correct project's Site settings → General | RankYourApp's Framer Project API key field |
| RankYourApp workspace API key | The installation reveal, or Account → API keys → Create key | Your website's private server/build secret store; sent in X-Api-Key |
| Managed blog DNS records | Connect your own blog domain in RankYourApp | The domain's authoritative DNS service |
| Google Search Console service-account email | RankYourApp's Search Console card | Users and permissions on the correct Google property |
Follow your platform's instructions
- WordPress: create the password and connect
- Framer: create the project key and map the CMS
- Webflow: connect a managed blog and add its menu link
- Wix: connect a managed blog and add its menu link
- Shopify: connect a managed blog and add its menu link
- Squarespace: connect a managed blog and add its menu link
- AI builders: install the prompt and store the key
- Developer API: requests and installation contract
- Developer recipes and downloadable server example
- DNS: add the records at your domain provider
- Google Search Console: property ownership and permissions
Complete the connection from end to end
- Prepare the external account, blog address and required credential or DNS access.
- Enter the details in RankYourApp and complete the platform-specific steps in its guide.
- Deploy your website changes, or finish managed-domain DNS and HTTPS verification.
- Return to RankYourApp and run the connection or installation check. Read and resolve any message shown.
- Finish setup before expecting the writing schedule to start. After a real article is delivered, open its public URL and check its listing, body, images and links.
Connecting Search Console is a separate step for search data. It does not install publishing. Search Console
Paying for RankYourApp uses the hosted checkout and billing portal reached from Plans and billing. You do not need your own Stripe account or Stripe API key to subscribe. Billing help
If someone else manages your website
Send your developer or domain administrator the relevant Help link, the blog address and the non-secret setup requirements. Have the account owner create and enter credentials through the relevant secure fields. Do not send passwords or API keys in support messages or screenshots.
For a managed blog, the DNS administrator needs the records shown for your exact domain. For an API install, the developer needs the installation prompt and access to the production server/build secret store. See replacing credentials before revoking a key used by a live installation.
Still stuck? Email us and tell us what you need help with.