Complete SEO Configuration Guide
Learn how to properly configure GitHub and Netlify for automatic and frictionless deployments.
Rank Deploy is a pre-rendering solution specifically designed to solve indexing problems for sites created with no-code tools like Webflow, Bubble, Framer, or Single Page Applications (SPA). Unlike traditional Server-Side Rendering (SSR) approaches that require a complete architecture overhaul, our pre-rendering technology generates static HTML versions of your pages, allowing Google, Bing, and other search engine robots to crawl and index all your content in hours instead of weeks. Webflow, Bubble, Framer, or Single Page Applications (SPA).
This documentation guides you step by step through setting up your environment: connecting to GitHub for version control, integrating with Netlify or Vercel for continuous deployment, and optimal pre-rendering configuration to maximize your visibility on search engines. Whether you're a developer, marketer, or entrepreneur, follow these instructions to transform your invisible JavaScript site into an organic traffic generating machine.
Quick Start
Connect your GitHub account
Authorize Rank Deploy to access your GitHub repositories to automate deployments.
Add your Netlify token
Create a Personal Access Token on Netlify with the necessary permissions.
Validate the connection
Our system automatically tests permissions before the first deployment.
Deploy in one click
Once configured, each publication deploys automatically to Netlify.
Detailed Guides
GitHub Configuration
- Verify that your repository exists and is accessible
- The default branch (main/master) is detected automatically
- Ensure the Netlify application has access to the repository
- Private repositories require additional permissions
Netlify Configuration
- Create a Personal Access Token in User Settings
- The token must have scopes: sites, deployments
- Connect Netlify to your GitHub account
- Authorize access to desired repositories
Create a Netlify Token
- Log in to your Netlify account
- Go to User Settings → Applications → Personal access tokens
- Click "New access token"
- Give a descriptive name (e.g., "Rank Deploy Integration")
- Copy the generated token (it won't be shown again)
- Paste it in Rank Deploy during configuration
Interactive Troubleshooting
Use our assistant to solve common problems step by step.
Assistant de Dépannage
Sélectionnez le type de problème que vous rencontrez pour obtenir une aide personnalisée.
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
Understanding Your Analytics Metrics
Detailed guide to SEO and crawl performance indicators available in your dashboard.
Crawl Metrics
Bot Hits
Total number of visits by search robots (Googlebot, Bingbot, etc.) to your pre-rendered pages.
A high number indicates search engines are actively exploring your site. A sudden drop may signal a technical issue.
Cache Hit Rate
Percentage of bot requests served from cache rather than generated on the fly.
A high rate (>80%) is optimal: pages are served instantly to bots. A low rate means more latency and server load.
Response Time
Average latency to serve a pre-rendered page to search robots.
Aim for less than 200ms. Fast response time improves your crawl budget and favors better indexing.
Unique Pages
Number of distinct pages visited by bots during the selected period.
Compare with the total number of pages in your sitemap to measure crawl coverage.
Unique Bots
Number of different crawlers that visited your site.
Googlebot is most important, but presence of Bingbot, YandexBot and others indicates good multi-engine visibility.
DevOps & SEO Metrics
SEO Score
Overall SEO health score calculated from multiple technical factors (structure, meta tags, accessibility, etc.).
Aim for a score above 80. Check the details to identify priority improvement areas.
Deployment Success Rate
Percentage of successful deployments out of total attempts.
A rate below 95% indicates recurring build issues that need investigation.
Average Build Time
Average duration of your site builds on Netlify/Vercel.
Long builds (>5min) slow down your update cycle. Optimize assets and dependencies if needed.
Pre-rendering Success Rate
Percentage of pages successfully pre-rendered.
A rate below 100% means some pages fail pre-rendering. Check for JavaScript errors.
Average HTML Size
Average weight of pre-rendered HTML for your pages.
Aim for less than 100 KB. Heavy pages impact loading time and crawl budget.
Geographic Distribution
Distribution of bot visits by country of origin. Useful for identifying where crawlers come from and optimizing latency to those regions.
Top Bots
Ranking of search robots by number of visits. Googlebot should dominate if your goal is Google ranking.
Most Visited Pages
Pages receiving the most bot visits. These pages are prioritized by search engines.
Orphaned Pages
Pre-rendered pages never visited by bots. Verify they are in your sitemap and accessible via internal links.
Optimization Tips
- Regularly submit your sitemap to Google Search Console
- Fix orphaned pages by adding internal links
- Monitor sudden drops in bot hits (potential technical issue)
- Optimize response time by maintaining an efficient cache
- Analyze most visited pages to understand Google's priorities