Built with WordPress and Prism, hosted on Fastly behind Cloudflare. Domain registered in 2020.
jina.ai is built with WordPress, hosted on Fastly behind Cloudflare. It measures traffic with Google Analytics and Google Tag Manager. It sends email through Amazon SES.

| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 6 Nov 2026 | |
| WordPress Plugins1 | ||
| – | 6 Nov 2026 | |
| JavaScript Frameworks & Libraries3 | ||
| – | 6 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 6 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| – | 6 Nov 2026 | |
| CDN & Hosting4 | ||
| – | 6 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 6 Nov 2026 | |
| Transactional Email2 | ||
| – | 6 Nov 2026 | |
| Consent Management & Privacy1 | ||
| – | 6 Nov 2026 | |
| Fonts & Icon Fonts3 | ||
| – | 6 Nov 2026 | |
| Translation & Localization1 | ||
| – | 6 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
Read from the live site on 7 Nov 2026: the colors its CSS sets, and how much of the first screen each one covers in a screenshot.
Sites whose colors sit closest to these, whatever they're built with.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
aspmx.l.google.comalt2.aspmx.l.google.comalt1.aspmx.l.google.comalt4.aspmx.l.google.comalt3.aspmx.l.google.comikon7jxh22lhfkx3rl7nfces6escmyb3fnklh4odoph5wxoai4zq.mx-verification.google.comoswald.ns.cloudflare.comleah.ns.cloudflare.comgoogle-site-verification=iYwJdfkF1tYVYkg9AEjax5e4Eh9XmyzxtGXn4s2cfPgfirebase=sefo-api-keystripe-verification=c3bfd2d8529951adf10c6a85bf87596ca9072a9694bf404311eeb7846f6423e1google-site-verification=K-qFWzvxAyM7zbAyP2uaDE-C76IjDI6tL8Wqx5CA52Epwa-site-verification=eQGPkRPm1m-yFAxeZ-prf0miVDoX2iKvoZnheQvViQA=google-site-verification=XhuID1ixR8645-ejz-77HKLd5S1IlYuDX_3xFz8IpAUv=spf1 include:_spf.google.com include:amazonses.com include:_spf.firebasemail.com -allmongodb-site-verification=HlefKtT1NrCRaMTdTxSq9PKym1p8byhWv=DMARC1; p=reject; rua=mailto:97c78defd75c4779969ec4960677d295@dmarc-reports.cloudflare.net# robots.txt for jina.ai
#
# This file did not exist: https://jina.ai/robots.txt returned 404, which meant two
# things at once - search engines had no machine-readable pointer to the sitemap (the
# deploy generates one at /sitemap.xml, and 140 URLs in it), and nothing anywhere told
# a crawler that the signed-in application area is not content.
#
# WHY /api-dashboard/ IS DISALLOWED, AND WHY NOT ALL OF IT
#
# An earlier version of this comment justified the block by saying every dashboard
# snapshot "carries a logout affordance and none a login form". That was wrong, and it
# is worth recording why, because the mistake is easy to repeat: what the snapshots carry
# is <i class="q-icon material-symbols" aria-hidden="true" role="presentation">logout</i>.
# With an icon ligature the text content IS the icon's name - the browser paints a glyph
# and the word never means anything to a reader, and the element says so twice over with
# aria-hidden and role="presentation". Reading it as a UI label reads typography as prose.
# (The "Log in" strings in the same files are preload hrefs and a nav item, so their
# absence from a dashboard page proved nothing about auth state either.)
#
# The evidence that does hold is how much a visitor can actually read. Counted over the
# prerendered snapshots, with script, style, svg and icon-ligature markup removed:
#
# /api-dashboard/fact-checking/ 13 words /api-dashboard/token-counter/ 43 words
# /api-dashboard/image-rerank-test/ 16 words /api-dashboard/deepsearch-chat/ 74 words
# /api-dashboard/semantic-.../ 25 words /api-dashboard/contact-sales/ 80 words
#
# Fifteen of the twenty-six are under 200 words, and those fifteen are tool surfaces: a
# heading, some form labels ("State ID Choice Type Instructions Option Score") and inputs.
# There is no article there for a crawler to index, and a search result that leads to a
# form the crawler could not fill is worse for the visitor than no result. Those are the
# URLs kept out.
#
# What is NOT kept out, on purpose:
#
# /api-dashboard/pricing/ 459 words the pricing copy - /pricing/ returns 404,
# so this is the only answer on the site to the
# highest-intent commercial query there is
# /api-dashboard/playground/ 261 words descriptive copy about what the API does
#
# Blocking those two would hide the most useful prose behind the same blanket rule that was
# written for empty tool shells, so they are allowed explicitly. Google resolves conflicting
# rules by longest match; the Allow lines are listed first as well, for crawlers that take
# the first match instead.
#
# The two lists must agree. scripts/gen-sitemap.js no longer keeps its own copy of that
# decision - it reads this file and drops any URL this file blocks, so "do not crawl" in
# robots.txt and "please crawl" in sitemap.xml cannot drift apart again. That contradiction
# is what produces the Search Console state "Indexed, though blocked by robots.txt", which
# is the same lesson as the canonical fix in src/composables/useMetaTags.ts.
User-agent: *
Allow: /api-dashboard/pricing/
Allow: /api-dashboard/playground/
Disallow: /api-dashboard/
# The same decision in the other nine languages. /api-dashboard/ is a decision about the
# dashboard, not about its English spelling: /de/api-dashboard/embedding/ answers 200 today and
# is the same 13-word form surface as its English twin, so leaving the locale paths open while
# the English one is closed describes a rule the site does not actually have.
# The two Allow lines repeat per locale on purpose. A crawler evaluates the URL in front of it,
# longest match winning, so "pricing is allowed" written once in English does not carry over to
# /de/api-dashboard/pricing/ - and a sitemap that advertises a URL this file forbids is exactly
# the contradiction the rest of this file exists to avoid. The deploy gate checks both directions.
Disallow: /de/api-dashboard/
Disallow: /fr/api-dashboard/
Disallow: /es/api-dashboard/
Disallow: /it/api-dashboard/
Disallow: /zh-CN/api-dashboard/
Disallow: /zh-TW/api-dashboard/
Disallow: /ja/api-dashboard/
Disallow: /ko/api-dashboard/
Disallow: /ru/api-dashboard/
Allow: /de/api-dashboard/pricing/
Allow: /fr/api-dashboard/pricing/
Allow: /es/api-dashboard/pricing/
Allow: /it/api-dashboard/pricing/
Allow: /zh-CN/api-dashboard/pricing/
Allow: /zh-TW/api-dashboard/pricing/
Allow: /ja/api-dashboard/pricing/
Allow: /ko/api-dashboard/pricing/
Allow: /ru/api-dashboard/pricing/
Allow: /de/api-dashboard/playground/
Allow: /fr/api-dashboard/playground/
Allow: /es/api-dashboard/playground/
Allow: /it/api-dashboard/playground/
Allow: /zh-CN/api-dashboard/playground/
Allow: /zh-TW/api-dashboard/playground/
Allow: /ja/api-dashboard/playground/
Allow: /ko/api-dashboard/playground/
Allow: /ru/api-dashboard/playground/
Allow: /
Sitemap: https://jina.ai/sitemap.xml
| – |
| 6 Nov 2026 |
| – | 6 Nov 2026 |
| – |
| 6 Nov 2026 |
| – | 6 Nov 2026 |
| – | 6 Nov 2026 |
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |
| – | 6 Nov 2026 |