From invisible to indexed in under 10 minutes
A linear, no-code-first setup. Pick your platform, point your DNS, customize your meta tags. No plugins. No GitHub. No code.
Day 1Connect your site in 3 steps
These three actions take ~10 minutes and require no code. Most users see Googlebot crawl their pages within the same day.
Paste your site URL
From your dashboard, click 'Add site' and drop your live URL. We auto-detect Webflow, Framer, Bubble, Lovable or Wix. No plugin required.
Point your domain (or use ours)
Keep using your existing domain by adding one CNAME record at your registrar (Cloudflare, Gandi, OVH…). Or start on a free *.rankdeploy.app subdomain to test in one click.
Verify Googlebot now sees you
Run our SEO audit on your live URL. The 'Prerendering' check should flip from 'Empty shell' to 'Content OK' within 2 minutes of activation.
Setup by platform
Each card lists the URL to use, the exact DNS CNAME to point, and the platform-specific gotcha that trips most newcomers.
🎨Webflow
Your URL
Use your *.webflow.io URL or your custom domain.
DNS CNAME
Custom domain → Project Settings → Hosting → use a CNAME pointing to proxy.rankdeploy.app instead of proxy-ssl.webflow.com.
Gotcha
If your CMS uses dynamic routes (e.g. /blog/[slug]), enable 'Auto-discover routes' so we crawl your sitemap.xml and pre-render every page.
🅵Framer
Your URL
Use your *.framer.app URL or your custom domain.
DNS CNAME
Site Settings → Domains → add your domain, then point its CNAME to proxy.rankdeploy.app (instead of cname.framer.com).
Gotcha
Framer's CMS pages don't expose a sitemap by default. Toggle 'Generate sitemap' in your project settings before activating Rank Deploy.
🫧Bubble
Your URL
Use your *.bubbleapps.io URL or your custom domain.
DNS CNAME
App Settings → Domain/email → enter your domain. Add the CNAME to proxy.rankdeploy.app (instead of the IP Bubble suggests). HTTPS auto-provisions in ~5 min.
Gotcha
Bubble's data pages with URL parameters (?user=…) are skipped by default, since they're considered private. Add them to public_routes if you want them indexed.
💛Lovable
Your URL
Use your *.lovable.app URL or your custom domain.
DNS CNAME
Project Settings → Custom Domain → set up your domain, then update the CNAME to proxy.rankdeploy.app instead of the Lovable default.
Gotcha
Lovable apps with auth-gated routes are auto-detected. Only public pages (landing, pricing, blog, docs) are pre-rendered.
🅦Wix
Your URL
Wix uses your custom domain or a *.wixsite.com URL.
DNS CNAME
Settings → Domains → Connect a domain → use 'Pointing method', then add the CNAME to proxy.rankdeploy.app at your registrar.
Gotcha
Wix's Velo (code) pages need 'SEO Indexing' toggled ON in the page settings. Otherwise our crawler won't find them.
Using another no-code builder (Carrd, Softr, Glide…)? Most CNAME setups work the same way. Ask us.
Week 1Customize for SEO
Once Googlebot reads your pages, the next lever is making each one share-worthy and on-brand. Three panels handle the lot.
Custom meta tags per page
Override title, description, and OG image on any page. Auto-fix detects pages missing canonicals or descriptions and proposes fixes you can approve in one click.
Sitemap & robots.txt
We generate sitemap.xml from your discovered pages (priority + lastmod). robots.txt is rebuilt with the right Sitemap: line and disallow rules. No manual edits.
Link previews (Slack, Twitter, LinkedIn)
Once your OG tags are set, every share renders a rich card. Live preview lets you see exactly how each page looks before publishing.
Interactive Troubleshooting
Use our assistant to solve common problems step by step.
Troubleshooting Wizard
Select the type of issue you're experiencing for personalized help.
Frequently asked questions
SEO Glossary
Understanding the technical terms of SEO and pre-rendering.
Pre-rendering
Technique that generates a static HTML version of a JavaScript page in advance, allowing search robots to see the content without executing JavaScript.
Server-Side Rendering (SSR)
Server-side HTML generation on each request, offering always up-to-date content but requiring more server resources.
Single Page Application (SPA)
Web application that loads a single HTML page and dynamically updates content via JavaScript, typical of no-code tools.
Crawler / Robot
Automated program that crawls the web to index page content. Googlebot is Google's main crawler.
Indexing
Process by which a search engine adds a page to its database to be able to display it in search results.
Crawl Budget
Number of pages a crawler will visit on your site in a given time. Fast response time improves this budget.
Sitemap.xml
XML file listing all the pages of your site that you want indexed by search engines.
Meta Description
Short description (150-160 characters) displayed in search results under the page title.
Core Web Vitals
Performance metrics used by Google: LCP (loading), FID (interactivity), CLS (visual stability).
Canonical URL
Primary URL of a page used to avoid duplicate content when multiple URLs display the same content.
No-Code SEO Checklist
Verify that your site checks all the boxes for optimal SEO.
Technical
- Pre-rendering enabled
- Sitemap.xml submitted to Google Search Console
- Robots.txt correctly configured
- HTTPS enabled on all pages
- Loading time < 3 seconds
- Responsive site (mobile-friendly)
Content
- Unique titles on each page (< 60 characters)
- Unique meta descriptions (150-160 characters)
- Single H1 per page with main keyword
- Hierarchical heading structure (H1 > H2 > H3)
- Minimum 300 words per page
- Naturally integrated keywords
Images
- Alternative text (alt) on all images
- Compressed images (< 200 KB)
- WebP format used when possible
- Lazy loading enabled
- Descriptive file names
Performance
- PageSpeed score > 80
- No blocking JavaScript
- Critical CSS inline
- CDN configured
- Browser cache optimized
Monitor indexing & performance
Once your site is connected, the dashboard tracks 5 metrics that actually matter for no-code SEO. Quick reference below.
Bot hits
Count of crawler visits per day, segmented by bot (Googlebot, GPTBot, Slackbot…). Going up = your site is being discovered.
Cache hit rate
% of bot requests served from cache (vs. live-rendered). Higher = faster, cheaper, more bot-friendly.
Render success rate
% of pages we successfully pre-rendered without errors. Below 95% means a page or layout breaks our renderer. The troubleshooting wizard above narrows it down.
Indexed pages (Google)
Pulled from Google Search Console. The number we move. Your goal is to see it climb past your platform's pre-Rank-Deploy baseline.
Pro tip
Connect Google Search Console (Project Settings → Integrations) so we cross-reference your indexed page count with our render success rate. That's how you spot which pages Google is fetching but not indexing.
Ready to ship the 10-minute setup?
Run the free SEO audit on your URL first, no signup needed. You'll see exactly what Googlebot reads (or doesn't) before deciding.
Or read the public changelog.