Skip to main content

The Problem: JavaScript and Search Engines

Modern web apps built with React, Vue, or AI builders render content dynamically in the browser. When a search engine bot visits your site, here’s what happens:
User visits → Browser runs JavaScript → Content appears ✅
Bot visits  → No JavaScript execution → Empty page seen ❌
This means your carefully crafted content, meta tags, and product pages may never get indexed by Google or other search engines.

The Solution: Dynamic Rendering

Hado SEO implements dynamic rendering at the edge. We serve different content based on who’s visiting:
Human visitor → Your original app (unchanged, zero latency)
Search bot    → Pre-rendered static HTML (SEO-optimized)
This is the approach recommended by Google for JavaScript-heavy applications.

How Bot Detection Works

Our edge network analyzes incoming requests to identify different types of visitors:
  • Googlebot - Google’s main crawler - Bingbot - Microsoft Bing - DuckDuckBot - DuckDuckGo - YandexBot - Yandex search - Baiduspider - Baidu (China)
  • GPTBot - OpenAI’s crawler for ChatGPT - ClaudeBot - Anthropic’s crawler - PerplexityBot - Perplexity AI search - Applebot-Extended - Apple’s AI features
  • Twitterbot - X/Twitter link previews - facebookexternalhit - Facebook/Meta sharing - LinkedInBot - LinkedIn sharing - Slackbot - Slack link unfurling - Discordbot - Discord embeds

What Gets Pre-rendered

When a bot visits your site through Hado SEO, we render and serve:
Content TypeExampleSEO Impact
Full HTML contentYour page text, headings, paragraphsCore indexable content
Meta tags<title>, <meta name="description">Search result snippets
Open Graph tagsog:title, og:image, og:descriptionSocial media previews
Structured dataJSON-LD schema markupRich search results
Dynamic contentData fetched from APIsComplete page content
HTTP status codes200, 301, 404Proper crawl handling

Caching Strategy

Pre-rendered pages are cached at our global edge network for fast delivery:
PlanCache Refresh Interval
StarterEvery 7 days
ProEvery 3 days
AgencyEvery 3 days

Manual Recrawl

You can trigger manual recrawls from your dashboard:
  • 3 recrawls per hour per domain
  • Useful after deploying content updates
  • Cooldown timer shows remaining time

Architecture Overview

How it works:
  1. All traffic flows through Hado’s edge network via DNS
  2. Bot detection analyzes the User-Agent header
  3. Search bots get pre-rendered, cached HTML
  4. Human visitors pass through with zero added latency

Key Benefits

No Latency for Users

Human visitors bypass prerendering entirely. Your app loads exactly as before with zero added latency.

Global Edge Network

Our infrastructure spans multiple global points of presence for sub-250ms response times worldwide.

Always Fresh Content

Automatic cache refresh keeps your content up-to-date. Manual recrawl available for immediate updates.

Complete Control

Serves static HTML to search engines and AI crawlers to boost technical on-page SEO

Comparison with Alternatives

FeatureHado SEOPrerender.ioSSR Migration
Setup time5 minutesHoursDays/Weeks
Code changesNoneMiddleware requiredComplete rewrite
MaintenanceZeroSDK updatesOngoing
CostFrom $19/moFrom $99/moDeveloper time

Ready to get started?

Set up Hado SEO in 5 minutes with our quickstart guide