typo3-indexnow — new pages in the index within minutes.

TL;DR — Does this fit my setup?

Use it if

• new articles or product pages should appear quickly in Bing and the AI search engines
• pages go live on a schedule and the search engine should learn it at the start time, not days later
• removed or hidden pages should leave the index quickly

Do not use it if

• the TYPO3 scheduler does not run: a scheduler task sends the submissions every five minutes
• you want to reach Google, which does not take part in IndexNow
• you run TYPO3 < 14 or PHP < 8.5

Effort

One Composer package and one line in the site configuration. No key to generate, no file to upload, no cron job to set up.

How it works

Editor saves, moves, deletes               start time passes
workspace is published                            │
   │  DataHandler hook                            │  scan per run
   ▼                                              ▼
Queue tx_kohindexnow_queue   (one row per page and language)
   │
   ▼
indexnow:run   (scheduler, every five minutes)
   │  build the URL, check the rules, group by host
   ▼
one request per host ──► api.indexnow.org ──► Bing, Yandex, Seznam and others

A changed page is announced even when it is now hidden, deleted or noindex. The engine has to re-crawl to learn that. Its parent page goes with it, because a new article changes the list it appears in.

No key to manage

The key is derived per host from the installation's encryption key (HMAC-SHA256). Every replica computes the same one, every host gets its own, nothing is stored. A middleware serves the key file at /<key>.txt.

What is never announced

A submission cannot be recalled, and every participating engine receives it. So the extension checks what may go out before every request.

The site setting indexnow.deniedHostSuffixes blocks further hosts.

New content in Bing, ChatGPT search and Copilot sooner? I help with the setup, detail pages for news or products, and monitoring the submissions. Get in touch →

Installation and activation

Two steps

1. Install the package: composer require koh/typo3-indexnow, then vendor/bin/typo3 extension:setup. The setup creates the scheduler task that runs indexnow:run every five minutes.
2. Add the set to every site that should announce, in config/sites/<site>/config.yaml:

dependencies:
  - koh/indexnow

The first run with an active host announces the whole site once. That is the go-live; afterwards only changes go out.

Commands

vendor/bin/typo3 indexnow:status        # per host: active or why not, key file, queue
vendor/bin/typo3 indexnow:run           # what the scheduler task runs
vendor/bin/typo3 indexnow:submit-all    # queue every indexable page again

indexnow:status answers “why is nothing being sent?”.

Site settings

Delivery: queue, retry, give up

Nothing expensive happens while an editor saves. The hook remembers the records and writes the queue once at the end of the DataHandler run. URLs are built later by the worker, from the raw page record, which is why a deleted page still has a URL. Saving a page twenty times before the next run announces it once.

HTTP goes through TYPO3's configured client: proxy, CA bundle and HTTP.allowed_hosts apply, ten-second timeout, no redirects.

Extending and limits

Three PSR-14 events

• ResolveRecordPagesEvent: which pages show a changed record. The default is the page it is stored on. A record rendered on a detail page elsewhere (news, products, events) needs a listener from the extension that owns it.
• BeforeUrlsSubmittedEvent: add URLs that change with pages, such as a feed or an llms.txt.
• AfterUrlsSubmittedEvent: what was sent and how the engine answered, for monitoring.

Limits

• Google does not take part. For Google, the sitemap and Search Console remain.
• IndexNow is a hint, not a guarantee: whether and when a page is indexed is the engine's decision.
• An announced URL cannot be recalled. Hence the rules above.

Common pitfalls

• The scheduler does not run. The queue fills up and nothing goes out. indexnow:status shows the queue length.
• Wrong application context. Outside Production nothing is announced. That is on purpose, but it often raises the question why staging stays silent.
• Detail pages of records. News or product records usually live in a folder. Without a listener for ResolveRecordPagesEvent, their detail page is not announced.
• A new encryption key. The key depends on it. Replacing the encryption key gives new IndexNow keys; that is allowed, the engine reads the new file.