Sanka for Craft CMS

Free for Craft CMS 5

Indexing, but instant

Publishing is fast. Being found is not. A new page waits for a crawler that turns up on its own schedule — and for the answer engines it is often not a wait at all, because they never come. Sanka tells Google and IndexNow the moment a page changes, and then shows you which AI engines actually read it.

Sanka

Everything that could be wrong, in the order it would break

Most of what goes wrong with instant indexing is configuration, and the error you get back is a status code. Sanka's diagnostics command answers the question people actually ask — why is nothing being submitted — and prints the fix rather than the symptom.

bash
$ php craft sanka/queue/status

Google Indexing API          ready                12 pending   quota 142/200 (2026-08-23)
IndexNow                     ready                 3 pending
Sitemap resubmission         not configured
    · Sitemap resubmission travels over IndexNow, which is switched off.

$ php craft sanka/queue/drain
15 considered · 15 sent · 0 skipped · 0 retrying · 0 failed

Features

One ledger, several engines, and a second half that deals with the AI crawlers nobody else manages properly.

One save, every engine

Google's Indexing API and IndexNow — which reaches Bing, Yandex, Seznam, Naver and Yep in one call. Publish, update, unpublish and delete each become the right kind of notification.

  • Real multipart batching — 100 URLs, one round trip
  • The IndexNow key file is served from a route, so there is nothing to deploy
  • Bing's index is what ChatGPT Search and Copilot answer from

Never spends quota by accident

Google gives you two hundred submissions a day, per Cloud project, resetting on Pacific midnight. Spending them by accident is the normal failure mode of every tool in this category.

  • The remaining quota is checked before the batch is assembled, and the batch is cut to fit
  • A cooldown means twenty saves while editing cost one submission, not twenty
  • Dry run is on by default, and records what would have been sent

Says why, every time

Every submission is a row in a ledger, and “skipped” is an outcome with a reason on it rather than a silent drop. Failures are translated into the fix, not reported as a status code.

  • A 403 from Google says: add the service account as an owner in Search Console
  • A 422 from IndexNow says: your base URL does not match the domain you are served on
  • Every row records why it was queued, so “why did this cost quota” is answerable later

Which AI actually read your site

Every request from a recognised AI agent is recorded — which one, what it read, what it got. The question stops being a guess and becomes a table.

  • 22 agents, each labelled with what blocking it actually costs
  • Blocking GPTBot costs no visibility; blocking OAI-SearchBot removes you from ChatGPT Search
  • Forward-confirmed reverse DNS tells genuine, forged and unverifiable apart

llms.txt, from your own content

A sitemap tells a crawler what exists. llms.txt tells a model what the site is about and which pages are worth reading — a curated map a model can take in one fetch.

  • Generated from your sections and cached, so it cannot drift from what the site says
  • /llms-full.txt inlines the body text, for sites whose whole value is the writing
  • The crawler policy renders to robots.txt, or to your own template

Is the page worth quoting?

Twenty deterministic checks across structure, attribution, machine readability and citability. Nothing is sent anywhere and nothing is judged by a model, so the same page always scores the same.

  • Every finding that is not a pass carries the fix, not just the complaint
  • Audit one page, or a whole section worst-first
  • It only ever fetches hosts your own Craft sites are configured to serve

Frequently Asked Questions

The questions worth answering before you install it.

Start free, upgrade when the AI half matters

Lite does the whole indexing job for nothing. Pro is $129 with a $99/year renewal and adds llms.txt, the AI crawler policy and visit log, the readiness audit, sitemap resubmission, scheduled sweeps and bulk submit.