Pages are created automatically when a bot requests an address through your integration. You can also add them by hand so they're ready before the first bot arrives.

The list

• Rendering: Active or Stopped (a stopped page isn't rendered again automatically).
• Cache date, with the Outdated warning if the comparison found changes on your website.
• A bot's Last request and the Cached URL.
• That page's Maximum time.
• SEO score of what bots get (the original site's on hover).
• Google: clicks and impressions over 28 days, and Indexing, if you connected Search Console.
• Source (you added it or a bot did) and the Robot that requested it.

What you can do

• Add: a URL with its maximum time and whether it renders automatically. Edit also shows which rules applied on the last request.
• View cached page: the exact HTML a bot gets.
• SEO: the page's SEO score with every check.
• Compare with the live site: renders your page now without touching the cache (it uses a render) and tells you whether the cache is up to date or outdated: text similarity, new or removed blocks, key fields (status, title, description, canonical, robots, H1, language, Open Graph, JSON-LD types, words, links, images), the text changes and two screenshots. It's outdated if similarity drops below 95% or the title, description, canonical, robots, H1 or status change. From there you can Recache now.
• Recache: renders the selected pages again; it notifies you when it starts and finishes.
• Delete: removes pages from the cache (in bulk).

Good to know

• Every render and recache (automatic ones too) counts as a plan render, and each new page takes a cached pages slot.
• If your website answers with a server error (5xx) while recaching, the previous version is kept.
• Jazui always strips tracking parameters from addresses (utm_*, fbclid, gclid, dclid, gbraid, wbraid, msclkid, yclid, igshid, mc_cid, mc_eid, _ga, _gl, ref_src): all those variants share one page. For other parameters, use an Ignore parameters rule.
• Automatic recache uses the days of the applicable «Cache days» rule; otherwise the site's, otherwise the account's. It never goes below your plan's minimum and stops if no renders are left.
• To recache from your deployment or CMS, use the cache API.