Everything we ship, in order.

Four busy days. Rabbot now speaks German, has a new name on the App Store and alerts in real time. It also reads your Google Merchant Center account as well as your products. Here is the lot, including the hour I broke something.

Rabbot speaks German

On Sunday Rabbot went German in one go: the app, the alert and digest emails, Sidekick, the App Store listing and all of rabbot.ai, which now lives in German under /de/. If your Shopify admin is set to German, Rabbot follows it.

The honest part: for German admins, App Home loaded blank. I rolled the app back within the hour, fixed it, and switched German on again the same evening, then checked it on a real German admin. Today's release closes the gaps I found after that. The menu, the dashboard, Settings and the evidence lines in alert emails and Slack messages now read in German too.

The app also has a new name on the App Store: "Rabbot: SEO, Feeds & Alerts". It says what Rabbot watches, in four words.

Real time, measured

Rabbot sends real-time alerts by email and Slack. I tested it live: a password page went up on a test store, and the email and the Slack message both arrived 80 seconds later, one second apart.

Rabbot watches your homepage every 5 minutes and catches a store going down in real time. Publish a theme or edit a product, and Rabbot re-checks your store in under a minute. Every other page keeps its scheduled check, from every 10 minutes to once a day.

One fix sits right next to this. When you take a password page down, Rabbot now re-checks every page it had flagged behind it straight away, and each one closes on its own fresh read within the next homepage check.

Merchant Center accounts, not only products

Rabbot already told you when Google disapproves a product. Now it also reads the issues Google raises against your whole Merchant Center account, which are the ones that can stop every product at once:

• Google stopped your products serving. A suspension is a Critical alert, by email and Slack.
• Google warned your Merchant Center account. A warning is a Warning alert by email, because an unfixed warning is how a suspension starts.

Rabbot reads your account every day and confirms when Google clears the issue. That brings Rabbot to 80 checks, each listed with what it looks for at /docs/checks/.

AI shopping agents

Rabbot checks that AI shopping agents can find and buy your products. Honesty first: until Saturday that check could not read most public stores, because Shopify refused the way Rabbot asked. Rabbot now asks the way Shopify expects, and the check reads them. A store behind a password page now reads as "agents are shut out" rather than "could not check", which is the true answer.

Clearer alerts

• Every email, digest and alert now leads with what happened and what to do, in plain active sentences.
• A missing add-to-cart button on a product page names that page in the Blocking sales band, instead of folding into "Your store".
• A product variant or collection whose canonical tag points elsewhere now reads "Page points Google to another URL", rather than calling it a change.
• Sidekick opens with what Rabbot checks and how often, and quotes your last check time exactly as Rabbot logged it.

On rabbot.ai

The site has a new homepage built around what Rabbot catches, new pricing and features pages, and one menu on every page, in English and German. Pricing leads with Starter, Growth and Pro, each with a 14-day trial. The proof sits on the homepage too: a Google-verified app, a Meta-verified Tech Provider, and a TikTok-approved app.

This week I installed Rabbot on a real store of my own, from a clean start, the way a new merchant would. It found things I had missed in testing, and most of this release is the fix list. The result is fewer emails and an easier start.

Fewer emails, and each one means something

A good part of the week went into alerts that fired when nothing had broken. All of these are fixed:

• A sitemap email now means a live page left your sitemap. Adding products, deleting them, or pages Rabbot has not read yet send nothing. My own upload of 24 products sent a "Sitemap changed" warning, and it no longer would.
• A store that answers "too busy" once is read again a few minutes later, and Rabbot only emails if the second read agrees.
• A store that keeps flickering between up and busy opens one Warning that says the store is intermittent, instead of a string of alerts. On paid plans that Warning is an email.
• A robots.txt Rabbot could not fetch (a password page answers with an error) is reported as a gap in monitoring, never as a robots.txt change.
• A site-wide alert that was already sent is not sent again when Rabbot rechecks it, and it no longer claims a page count it does not have.
• When Rabbot moves your store to its main web address, open alerts stay open and nothing emails twice.

Starting out

A new install now gets a setup guide card on App Home: four steps that tick themselves off as you do them, and a copy of the checklist in Settings. App Home also loads in one go, so the dashboard no longer jumps about while it fills in.

The first real install fixed five more things. Add-to-cart is checked on product pages only. A missing meta description is its own finding. The page picker lists the products you chose and always offers Save. Rabbot now watches the address your shoppers see (your primary domain), and a store that had pages split across two addresses joins them up with its history kept.

Emails, digest and Page history

All 14 setup and account emails are rewritten, name your store by its domain, and end with a short unsubscribe link. The welcome email goes a few minutes after you install, and every email shows "Rabbot" as the sender. Each row in the weekly digest now carries clock times in your store's time zone.

On Page history, the one-tap fix card now appears on the row too, with Put it back and Undo. The search visibility card reads in words: "Hidden from search" or "Shown in search".

Sidekick, Shopify Analytics and Settings

Sidekick can now look things up in Rabbot's docs, so a question about a Rabbot alert by name gets Rabbot's own page on it. Results also say when an issue closed, which helps with "since when" questions. Turn Rabbot on in Sidekick's app settings first.

If you switch it on in Settings (every plan), Rabbot marks each Critical or Blocking catch, and when it cleared, on your Shopify Analytics charts under its own name.

In Settings, the MCP panel now says what it gives an agent: read tools plus two guarded actions, dismissing a finding and undoing a one-tap fix. It used to say read-only, which was wrong. The Blocking band also names each channel you are not watching. It had been reading TikTok as Meta.

On rabbot.ai

Two free checkers for a single page: the noindex checker and the redirect chain checker. Every check Rabbot runs is listed with what it looks for at /docs/checks/.

TikTok Ads is now open to every store on Starter, Growth or Pro. You connect it from the TikTok Ads card in Settings, the same way as Google and Meta. Until today it was limited to a small group of stores.

It is labelled "TikTok (Beta)". Beta here means we are still polishing the channel, nothing more.

Once connected, Rabbot reads TikTok's catalogue diagnostics once a day and shows them in the dashboard and the digest, next to the Google and Meta verdicts.

Free cannot connect any channel. Starter has one channel slot, Growth has three, and Pro has every channel. Meta stays live.

In October 2026 Rabbot was accepted into Claude Startups, Anthropic's program for companies building with Claude. The acceptance was confirmed after a re-review this month.

The program gives the company a year of Claude Team seats, API credits, a set of partner tools called the Startup Stack, and office hours with Anthropic's Applied AI team.

Nothing changes in the product for merchants. The credits go into building Rabbot.

Two things shipped this week, and both change what Rabbot is. Until now it only read your store. From today it can put a few things back when you tap, and it can show you what shoppers did while a page was broken.

Start with the gap a cold evaluation of Rabbot named on 4 October. Rabbot could prove the add-to-cart form was in the page's HTML, and it could not see a dead click. It still runs no browser, so the second half is still true. What it does now is read three witnesses for every catch and tell you which ones agree.

The first is integrity: whether the page is broken, which now includes the code files your product form needs. If a file the form depends on stops loading, or loads and fails a syntax check, Rabbot says so. The card names the file, the time and the status your store answered. A syntax check catches syntax errors only, and valid code can still be broken. The card says that too.

The second witness is capability: what Rabbot checked and when, including whether Shopify's own catalogue for shopping agents still offers the product.

The third is outcome: Shopify's own shopper numbers. Rabbot reads them once a day, after your day ends, and reports the morning after. It compares that day with the same weekday in each of the four weeks before, and shows the earlier figures as a range. When your store has too few visits to tell a real change from a quiet day, the card says so and waits. When the other two witnesses look healthy and the numbers fall anyway, Rabbot says it cannot see the cause. It never invents one.

Those numbers come from Shopify's own daily totals, the same reports your admin shows. Rabbot never reads an order or a customer. The revenue line stays off until you switch it on in Settings. Switching it on asks you to approve one more read permission, and Rabbot keeps the totals for 90 days and then deletes them.

Shopper impact is monitored on Growth and Pro, and the card says plainly when a plan does not include it. A money figure, when one appears, is a difference you can check against your own reports. Beside it sit the things Rabbot does not check for: advertising, seasonality, a competitor's move. It is never "Rabbot recovered this much".

The taps are the second thing. When a product's web address changes and the old one shows Page not found, the finding carries two buttons. Keep the new address, and Rabbot adds a redirect from the old one. Put back the old address, and Rabbot restores it and redirects the new one to it. Either way you confirm first, and you can undo for 30 days. Shopify usually adds that redirect itself when you rename an older product.

So the card appears only when the old address really does show Page not found, and Rabbot rechecks it within the hour after a rename. A redirect chain that grew a hop gets a button too: Rabbot points visitors straight at the end of it. That one has no undo, because Shopify does not let a redirect point at an address that is itself redirected. The card says so before you tap. A redirect that sends visitors in a circle gets its own card, and Rabbot can point it back at where it went before.

The same two taps work on an SEO title, an SEO description or a search visibility (noindex) setting that changed on you. Rabbot shows the value it had before, you confirm, it goes back, and the undo stays for 30 days. Rabbot does not know who changed a field, because Shopify records no event for a field edit, so it never says. You say which value is yours. If the same field changes again within 30 days of a fix, Rabbot offers no tap and tells you something keeps changing it.

Some honesty about the write access, because the trust page has said "read-only" since the day it went up. Installing Rabbot still asks for three read permissions and nothing else. Write access is asked for the first time you tap a fix, through Shopify's own prompt. You can say no, and the finding stays open with nothing else changed.

Rabbot never writes on its own, and it never touches price, inventory, availability or your theme. An agent on the MCP server can preview a fix and undo one Rabbot made, and it can never apply one. One-tap fixes are on Starter and above. The trust page, the docs and the comparison pages are being rewritten to say the same thing in the same words.

Every plan still asks for nothing but the three read permissions. One-tap fixes come with Starter, Growth and Pro, each with a 14-day trial.

Sidekick is Shopify's own assistant, the one sitting in the top bar of your admin. From today it can ask Rabbot. The surface is Shopify's work and the credit for it is theirs. My side of it is the answering.

Rabbot is there as six read tools, which just means Sidekick can look at what Rabbot has already found and do nothing else. Rabbot changes nothing in your store. You apply a fix yourself, or Sidekick does with your own permissions, and Rabbot confirms it on the next check.

So you can ask "Using Rabbot, is anything broken on my store?", or "Using Rabbot, what is blocking sales right now?", or, when you know which product is misbehaving, "Using Rabbot, why can nobody buy the Aurora Hoodie?". Between them the six tools cover a whole-store summary, what is stopping sales, open problems by area (search, storefront, site), one product page in detail, what to do about a named check, and what broke and got cleared, up to 30 days back.

An answer is always Rabbot's last completed check, the same data sitting in your dashboard and behind your alerts. Nothing goes off and crawls your store while you wait.

Two things an answer never contains, and you should hear it before you ask rather than after. First, what Google, Meta or TikTok (Beta) reported about your products. Those verdicts stay in the app, deliberately. Second, anything about orders, sales or customers. Rabbot has never held that data and this does not change it.

Then the honest caveats. Give it a few minutes after installing before the first question. If Sidekick answers from somewhere else, or tells you the app is not on in this conversation, start your question with "Using Rabbot," and ask again. Name a product exactly, by title, handle or URL, because a vague name ends the turn with nothing. And an empty list is never an all-clear: every answer also tells you how much of your store is checked, how often, and what is still open outside the bit you asked about. Read that part.

The full write-up is at rabbot.ai/docs/#sidekick. Nothing inside Sidekick will ever mention a plan, compare tiers or ask you to upgrade.

The Shopify App Store listing opened back on 7 July. On 23 August, V1 went live: the version I was willing to announce, and I announced it on this site the same day. This entry is the record of what V1 actually is, plus what has shipped in the few days since.

Install Rabbot and it builds its own watchlist. On Starter, Growth and Pro, Rabbot discovers pages from your sitemap up to your cap of 1,000, 5,000 or 15,000. On the Free plan that is a pick of 20 pages (homepage, top collections, best sellers) that you can swap at any time. From there the schedule moves with each page's own behaviour, between daily and every ten minutes on a paid plan for a page that keeps changing, and between weekly and daily on Free. The homepage gets a heartbeat check about every five minutes on every plan, so a store that has gone dark is caught in roughly five to ten minutes.

The feed side is a cross-check. Rabbot compares what your product catalogue says about a product with what the live page actually shows (price, availability, whether it is still published) and flags a gap as disapproval risk, the chance a shopping channel stops showing that product. Paid plans sweep the full catalogue daily and re-check a product within minutes of a change. Free runs it once, at install.

Channel verdicts, meaning what Google, Meta or TikTok themselves decided about your products, are separate and optional: you turn a channel on in Settings or it stays off. Google and Meta are there today. TikTok was in Beta and open to a limited group of stores at the time. (Update 2026-10-13: TikTok is open to every store on a paid plan. See the entry of that day.)

Since launch day the checks have grown too. Hreflang tags, the lines that tell Google which language or country version of a page to show, are now validated on every plan, and paid plans also catch pages whose language versions stop linking back to each other. A missing add-to-cart control and a password-gated storefront now count as sale-blocking, so Rabbot keeps reminding you until they are fixed. Both can be dismissed, because sometimes you meant to do it: tell Rabbot a change was deliberate and it stops alerting on it.

Around the app, rabbot.ai/docs is now a proper manual, 34 short articles with search, and rabbot.ai/trust lists only the claims you can verify off this site before installing. If an AI assistant does your evaluating for you, that works as well: Rabbot's MCP server, the connection that lets an agent ask Rabbot questions directly, comes with every plan and carries eight read tools plus one guarded write action.

Starter, Growth and Pro each come with a 14-day trial. The Free plan is free forever, no card required.

Same address, rabbot.ai. Everything behind the front door is new.

The site used to run on Cloudflare Pages, a pile of files handed out as-is. Now it runs on a single Cloudflare Worker, a small program that answers every request itself, decides what it's for, and serves it. That's what let me add a proper blog and this changelog: a real writing tool instead of hand-edited HTML. Publishing still needs me to press the button, on purpose.

The move needed a mail-forwarding step too. www.rabbot.ai now redirects to the bare domain, the way old post gets forwarded to a new address. On the day I switched it on, the forwarding missed a few of the parcels. Some of the site's own files (images, stylesheets, the small stuff a page needs to look right) kept answering from the old address instead of the new one. I found it and fixed it the same day.

The building changed. The job didn't. One honest alarm, same-day, every day.