Origin<>SERA<>Crawler request flow¶
Prerequisite¶
-
You must have an account created on Nitrogen dashboard to view the SERA statistics
-
SERA must be configured to receive the requests from bots
Flow¶
A typical request flow with SERA integration looks like this :

Page serving workflow :
(This is shown at left-hand side of flow in Yellow color)
Crawlerrequests are received onN7 CDN- If the
N7 CDNhas page available in cache/storage - it is returned back tocrawler- If the page page is unavailable in cache/storage :
- If a failover is not configured - a 404 is returned to
crawler - If a failover is configured - the request is forwarded (proxied) to
origin serverOrigin serversends the responseSERAreceives it, and sends it tocrawler
- If a failover is not configured - a 404 is returned to
- If the page page is unavailable in cache/storage :
Page rendering workflow :
(This is shown at right-hand side of flow in Yellow color)
SERAreads the configured sitemaps at configured schedules, and makes respective page requests to theorigin serverOrigin serverserves the pageSERA:- Renders the page in the same manner browser renders it for users.
- Then optimizes it from bot perspective, keeping only the content relevant for bots.
- And then caches it on the CDN POP closest to GoogleBot origin
Notes¶
Please also go through the different scenarios mentioned here