Index render User-Agent & Verification Guide

Overview

Index render uses custom User-Agent strings to identify its crawlers when accessing your site. These crawlers serve pre-rendered HTML to search engine bots for better SEO performance on JavaScript-heavy websites.

Recognizing and properly handling these User-Agents ensures your site responds correctly to Index render requests. To prevent spoofing, additional verification methods like reverse DNS lookups are recommended.

How It Works

What is a User-Agent?

A User-Agent is a string that a browser or bot sends to a server to identify itself. It informs the server about the client making the request, including the browser type, operating system, and crawler identity.

Why It Matters

  • Ensures Index render is properly served pre-rendered content.
  • Helps distinguish legitimate crawlers from spoofed bots.
  • Aids SEO optimization by confirming search engines index rendered content.

Index render User-Agent Strings

Crawler Full User-Agent String
Index render Desktop Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/124.0.6367.201-1 Safari/537.36 Index render (+https://github.com/Index render/Index render)
Index render Mobile Mozilla/5.0 (Linux; Android 11; Pixel 5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.6367.201-1 Mobile Safari/537.36 Index render (+https://github.com/Index render/Index render)
Index render Sitemap Worker Index render (+https://github.com/Index render/Index render)
Note: The Chrome version (e.g., 124.0.6367.201-1) represents the Headless Chrome version used by Index render and may change over time.

Security & Spoofing Protection

User-Agent strings can be spoofed. If you need to verify that a visitor is truly Index render, you should perform a reverse DNS lookup.

Steps to Verify a Index render Request via IP

  1. Get the IP address from your server logs.
  2. Run a reverse DNS lookup:
host 142.54.167.130

Example output:

130.167.54.142.in-addr.arpa domain name pointer us-mci1-38.renders.index-render.io.

Then run a forward lookup:

host us-mci1-38.renders.index-render.io

If the IP matches in both directions, the request is valid and from Index render.

Index render Crawler IP Address Ranges

Refer to the official IP Address documentation for the complete and updated list of Index render IP ranges. Use these ranges for firewall or CDN whitelisting.

Best Practices & Tips

  • Always perform reverse DNS lookup to prevent spoofed User-Agents.
  • Do not rely solely on User-Agent strings for authentication.
  • Whitelist official IP ranges for CDN or firewall-level filtering.
  • Account for both desktop and mobile User-Agents if serving device-specific content.
  • Improper verification may lead to indexing issues and incorrect SEO rendering.
© Index render – User-Agent & Verification Documentation