Double check the user agents whitelisted for every deployment, since you may not need all of them, or you might want to add some

Every deployment can also be used as a Edge Cache API. You can simply forward requests to us when you detect a bot in a user agent.

This is the recommended way to deploy.

Seeing a WRCacheHit header with a value of 1 indicates the cache was hit - but you can safely forward any requests since we will simply fetch origin if it's not in the cache. If it's from a crawler that doesn't support JS we'll pre-render it, if the the client does support JS it'll be rendered on the fly.


# Change YOUR_DEPLOYMENT_ID to your Webrender Deployment ID
<IfModule mod_rewrite.c>
RewriteEngine On
<IfModule mod_proxy_http.c>
RewriteCond %{HTTP_USER_AGENT} googlebot|bingbot|yandex|baiduspider|facebookexternalhit|twitterbot|rogerbot|linkedinbot|embedly|quora\ link\ preview|showyoubot|outbrain|pinterest\/0\.|pinterestbot|slackbot|vkShare|W3C_Validator [NC,OR]
RewriteCond %{QUERY_STRING} _escaped_fragment_
# Only proxy the request to Webrender if it's not a static asset
RewriteRule ^(?!.*?(\.js|\.css|\.xml|\.less|\.png|\.jpg|\.jpeg|\.gif|\.pdf|\.doc|\.txt|\.ico|\.rss|\.zip|\.mp3|\.rar|\.exe|\.wmv|\.doc|\.avi|\.ppt|\.mpg|\.mpeg|\.tif|\.wav|\.mov|\.psd|\.ai|\.xls|\.mp4|\.m4a|\.swf|\.dat|\.dmg|\.iso|\.flv|\.m4v|\.torrent|\.ttf|\.woff|\.svg))(.*) http://YOUR_DEPLOYMENT.webrender.io/$2 [P,L]