IndexPilot compares your sitemap with Google Search Console and Yandex Webmaster, finds the pages search engines have missed and sends them for recrawl — gradually, within the daily API limits, for every site you run.
Free for one site · €5 / month for each extra site
50,000
URLs per sitemap
30
commands per message
2
languages: EN, RU
/reindex_yandex https://site.com/sitemap.xml
Task #12 started: reindex_yandex.
site.com → Yandex: sent 183 of 200/day, 41 in the queue.
How it works
Three steps from a sitemap to pages in search.
1
Connect your search consoles
Send a Google service-account JSON key for each site and connect Yandex Webmaster through OAuth right in the chat. The bot finds which properties every key owns by itself.
2
Send a sitemap
One command checks every URL of a regular or index sitemap and answers with a TSV report of the pages that are not indexed.
3
Let the queue work
Missing pages go to a per-site queue that spends each day's API quota and tops itself up every few minutes — until the queue is empty.
Everything the bot does today
Built for people who run several sites and are tired of clicking "Request indexing" one URL at a time.
Index check by sitemap
Reads regular and index sitemaps (up to 50,000 URLs, gzip included). Google: one Search Analytics export marks pages with impressions as indexed, the rest go through URL Inspection in parallel. Yandex: the sitemap is matched with "Pages in search", Cyrillic domains and paths included.
Reindex only what is missing
Reindex commands queue only pages with a known "not indexed" status — an unknown status is never treated as missing. By default Google relies on the bulk export alone; add exact for a per-URL inspection.
Recrawl queue with daily limits
One queue per site with its own daily limit: Yandex quota is read from the API, Google is counted per service-account key. The queue survives restarts, never loses a batch, retries quota and 5xx errors tomorrow and keeps refused URLs with the reason.
Site overview
One command collects pages in search and excluded, pages with Google impressions, sitemap size, Yandex SQI, site problems, backlinks, broken links, Ahrefs Domain Rating and search traffic — with the change since the previous check next to every number.
Search traffic trends
Clicks and impressions from Yandex and Google for the last 30 days against the 30 before, the daily average and the latest day against the one before it.
History of every figure
A snapshot per site and day is kept for more than a year. Export it as TSV or watch the charts on your dashboard.
Many sites, one bot
Every Google site has its own key and quota; the bot picks the key by the URL itself and refuses a domain nobody owns before wasting a request. Yandex hosts are matched by domain too.
Background tasks
Long jobs run in the background with a live counter, percentage and ETA. The bot keeps answering, and any task can be cancelled.
Batch commands
Send up to 30 commands in one message, one per line. They run in order and one failure does not stop the rest.
Personal web dashboard
The bot publishes your sites, metrics, queue and tasks to a private page with its own link. Reset the link at any time.
English and Russian
Choose the bot language with one tap. Background tasks answer in the language of the command that started them.
Setup without a server console
Yandex OAuth, Google keys, Ahrefs key and code updates are all done from the chat. Secrets are masked and stored with private file permissions.
Your data, on a private page
Send /web to the bot and get a personal link. The page refreshes itself from the bot: sites, history charts, the queue and running tasks.
Index, links and traffic of every site with day-to-day changes
Queue by site: waiting, sent today, daily limit, refused URLs
Background tasks with progress
No secrets ever leave the bot: tokens and keys stay on its server
indexpilot · Dashboard
3Sites
412Queued URLs
200Sent today
Yandex: pages in search, 90 days
site.com → Yandex
shop.site.com → Google
Commands
The full list is in the bot: /help.
Check and reindex
/check_google https://site.com/sitemap.xml
check sitemap URLs in Google, TSV report
/check_yandex https://site.com/sitemap.xml
check sitemap URLs in Yandex, TSV report
/reindex_google https://site.com/sitemap.xml
queue pages Google has not indexed (exact — per-URL check)
/reindex_yandex https://site.com/sitemap.xml
queue pages Yandex does not show in search
Recrawl queue
/recrawl_yandex URL URL …
queue a list of URLs (or send it as a file)
/recrawl_google_all https://site.com/sitemap.xml
the whole sitemap into the queue without a check
/queue
queue state and today's limit
/queue_run
send now, as much as the limit allows
/queue_rejected
URLs the API refused, with the reason
/queue_clear [google|yandex]
clear the queue
/tasks
background tasks and their progress
Site overview
/site_info site.com site2.com
site overview with changes since the last check
/site_history site.com
every stored snapshot as TSV
/web
personal dashboard link (/web_reset — new link)
Keys and settings
/set_google_key
add a Google service-account key for a site
/google_sites
Google sites and the key of each
/yandex_app CLIENT_ID CLIENT_SECRET
connect Yandex Webmaster through OAuth
/set_ahrefs KEY
free Ahrefs API key for Domain Rating
/language
choose English or Russian
/update
pull the latest code and restart
Simple pricing
Every feature on every plan. You pay only for additional sites.
No tool can: search engines decide. IndexPilot makes sure every page is checked and requested, and shows you what happened.
What do I need to connect Google?
A Google Cloud service account with the Search Console and Web Search Indexing APIs enabled, added as an Owner of the property. One key per site — the bot detects the properties itself.
Is the Google Indexing API allowed for any page?
Officially Google intends it for JobPosting and BroadcastEvent pages. For other sites use the check and the sitemap, and decide yourself whether to use /reindex_google.
How does the Yandex check work?
The sitemap is compared with "Pages in search" from Yandex Webmaster. If Yandex has no data for a new site yet, /recrawl_yandex_all sends the whole sitemap.
What happens when the daily limit runs out?
The rest stays in the queue and is sent automatically when the quota resets. A quota refusal pauses only the sites sharing that key.
Where are my keys stored?
On the bot's server only, with private file permissions. The website receives figures and statuses, never tokens or key files.
Your sitemap is waiting
Open the bot, send /start, choose a language and check your first site in a minute.