Check what a crawler receives from your page
Enter a page you run and pick a crawler. We request the page the way that crawler does, load it again in a browser, and show the two side by side.
Page to check
Loading
Something went wrong. Try again.
No check yet
Type the address of a page you run, choose a crawler such as Googlebot, then press Check page. The result appears here.
What each one received
Sample data| Measure | Crawler | Visitor |
|---|
To have crawlers receive the rendered version of your pages, sign up for a token and follow the install steps.
Sign upWhat the check does
The first request is one plain fetch with the crawler's name in the User-Agent header. Whatever your server sends back, before any script runs, is what we count. The second request loads the same page in a real browser, and counts what a visitor would read.
Each view is reduced to a few figures: the HTTP status, the number of words, whether the page has a title and a meta description, how many h1 headings and links it holds, and how many JSON-LD blocks. The page itself is not kept, and neither is its address.
The check is free and needs no account. The browser view draws on a shared daily allowance, so on a busy day it can be missing. The crawler view still shows.
What rendering your own pages means
Many sites build their content in the browser. A visitor sees a finished page, while a request that does not run scripts can receive a shell with a few lines of HTML. Your own middleware stays in front of your site. When a request comes from a crawler on its list, the middleware asks RenderSwap to load the page in a browser and return the finished HTML. Everyone else gets your site as it is today.
If the two columns match, your pages already work for that crawler and you need nothing from us. If the crawler column is far shorter, rendering your pages would close the gap. To set it up, add your domain, copy the snippet for your stack from the install page, and check again.