SEO4Ajax vs Prerender / Brombone

The feature tables below show the advantages of using SEO4Ajax compared to Prerender (SaaS) and Brombone.

1. User interface

The user interface allows configuring the service and managing manually the snapshots stored in the cache among other things.

SEO4Ajax Prerender Brombone
Backend console Yes Yes No
Analytics (bots) Yes Yes No

2. API

The API is responsible for serving snapshots to bots and offering a way to control the cache programmatically.

SEO4Ajax Prerender Brombone
API Features
Full
Add/remove snapshots, manage sitemaps, configure the service etc.
Basic
Add snapshots
Intermediate
Add snapshots and manage sitemaps
Sitemaps generation Yes No No
On-the-fly snapshots
Yes
Configurable by user-agent
Yes
Always active
No
Service Level Agreement
Yes
Up to 99.9%
Yes
Up to 99%
No

3. Crawler features

The crawler is responsible for keeping the cache up-to-date. For this purpose it controls scrapers which are responsible for doing snapshots on the website.

SEO4Ajax Prerender Brombone
Snapshot caching Yes Yes Yes
HTTP redirect & error caching
Yes
Automatic caching of redirects, pages not found (4xx), and errors (5xx)
No No
Capture of inner links
Yes
Configurable
No No
URL rewriting
Advanced
URL rewriting based on regular expressions with optional custom HTTP status or redirect
Basic
Query parameters stripping
None
Cache on facebook Yes No No
Custom recache periods
Yes
Via URLs rules defined in the settings, the sitemaps and the API
Yes
Via the sitemaps and the API
Yes
Via the sitemaps and the API (limited to enterprise plan)
Email alerts
Yes
Quota overage, scraping errors, unreachable website
Yes
Quota overage
No

4. Scraper features

The scraper is responsible for doing snapshots. For this purpose it uses a pool of web browsers to interpret web pages, execute all the scripts, and save the resulting snapshots in a cache.

SEO4Ajax Prerender Brombone
Based on an evergreen desktop browser
Yes
Chrome
No
PhantomJS (latest version)
No
PhantomJS (unknown version)
Page capture debug
Yes
The activation of debug logs during a capture is accessible via the administration console or the API.
Yes
The capture can be debugged on a desktop by installing the open-source version of Prerender, configuring it and testing the capture.
No
The source-code of Brombone is closed. The capture can however be debugged on a desktop by installing the proper version of PhantomJS, configuring it and testing the capture.
Fault tolerance
Yes
Any failed capture (e.g. 5xx errors, network errors, blank pages) is retried 3 times.
No No
Third-party resources blocking
Configurable
Predefined
Read-only configuration
None
Multilingual site support
Yes
No No
Custom HTTP headers Yes No No
Custom user-agent string Yes No No
Framework agnostic Yes Yes Yes
Open-source implementation Not yet Yes No
Disclaimer: these comparison tables may not be exhaustive and are based on the documentation, the source-code when available, provided by each service (updated: April 2016).

By using our site you agree to our use of cookies - Learn more - Hide this message