Google asks for something simple, worded in a way that scares people: before you can apply for production, your app must have gone through a closed test with at least 12 testers opted in continuously for at least 14 days.QuestionAnswerWho is affected?Personal developer accounts created on or after 13 November 2023Who isn't?Organization accounts, and personal accounts created before that dateHow many testers?12 minimum, at the same timeFor how long?14 days, consecutiveWhat breaks the counterA tester who leaves the program. If they come back, their 14 days start overWhat unlocks the next stepThe Apply for production button on the Play Console dashboardHow long Google takesUsually seven days or lessSource: Play Console Help — App testing requirements for new personal developer accounts, checked 11 September 2026.Two clarifications that save a lot of anxiety. First, the counter tracks your testers' opt-in, not your builds: shipping a new release to the closed track during the 14 days resets nothing. Second, it really is 12 Google accounts — not 12 devices, not 12 five-star reviews.
The SEO of a PWA rests on a simple principle: for a page to show up in search results, an engine first has to visit it, read it, and index it. That visit — the crawl — isn't something you trigger. The engine decides when it comes back, at its own pace.For a static site, that wait barely matters. For an app whose content is alive — a media outlet publishing several times a day, a store whose prices and stock keep shifting, a schedule where events appear and expire — it's a genuine drag. You've already done the work: the content is live, up to date, ready to be found. But it sits there waiting on a crawler that hasn't come back yet. In the meantime, it's sometimes an old version of the page — or nothing at all — that surfaces in results.
If you've published your PWA, it's serving a robots.txt right now — the first thing any crawler reads, and the file that decides what happens next: which parts of your site get fetched, and by whom. Yours has been saying yes to everyone.Everything below concerns that web version of your app. Your iOS and Android apps aren't crawled by anyone, and the tab only appears once your PWA has been published at least once — before that, there's no file to configure.That was a defensible answer. It just wasn't one you made — and the population it answers has changed. A few years ago, a crawler on your content was Google, Bing, or a scraper you didn't care about. Today a growing share of that traffic belongs to AI companies, and they don't all want the same thing from your pages. Treating them as one block means choosing between all of them and none of them.The new tab splits them into four families, in plain language: search engines (Google, Bing and the others that list your site in their results), AI answers (ChatGPT, Claude or Perplexity citing your site when they answer), AI training (robots collecting your content to train their models), and on-demand reading (someone asks an AI to open one specific page of your site). Four families, because those are four different deals.
eCommerce
Memberships
Chatbot
Online Courses
Bookings
Travel guide
Events
Content Creators
Pickup & Delivery
Newspaper
Radio
Schools
Faith
Organizations
Restaurant
Grocery
Custom apps
Employee Communication
NO CODE APP BUILDER
TECHNOLOGY
WHY GOODBARBER?
Design
PRODUCT RESOURCES
TOPICS
MOBILE APPS RESELLERS
DISCOVER