Frequently asked questions

A Google API that tells search bots a URL is new or updated. Google scopes it officially to JobPosting and BroadcastEvent content, but in practice it lands as a strong 'please crawl this URL now' hint for any page.

A web app where you sign in with Google and push URLs through the Indexing API and URL Inspection API from one paste-box. The free daily quota covers casual use, and a $2.99 pack covers the bigger jobs like migrations and launches.

No. Google decides what gets indexed, and no tool can promise otherwise. What we do is push your URLs through Google's own Indexing API on your own Search Console access, which is the strongest crawl signal you can send. The rest is Google's quality classifier, not us.

Yes. It runs on Google's own OAuth flow. You sign in, we get scoped access to your verified Search Console properties, and we call the Indexing and Inspection APIs as you. No service accounts, no shared credentials.

Yes. The Bing tab pushes URLs through the IndexNow protocol (Bing, Yandex) and to Bing Webmaster Tools. Bing's retrieval index also feeds ChatGPT Search and is a major Perplexity source, so submitting to Bing is how you reach those AI assistants too.

Index pushes URLs to Google's Indexing API. Status bulk-runs URL Inspection so you can see what Google has on file. Audit deep-dives a single URL across PageSpeed Insights, structured data, and canonical/robots signals.

The free daily quota costs nothing. Need more, buy a one-time pack: $2.99 for 50 credits. There is one wallet — a credit covers one URL through the indexer, status checker or auditor, a site report costs 2, and an AI citation check costs 5 because it queries every AI engine at once. Free quota spends first, credits pick up the rest. Need several packs, buy them in one go: pick the number of credits you want at checkout and it's a single payment at the same $0.06 a credit — 200 credits is $11.96, not four trips through checkout. Ceilings: 150 credits a day, up to 200 credits bought per day, and credits stay in your wallet for a full year (365 days) after purchase.

Yes — there is one wallet. The same credits cover submissions, status checks, audits, site reports (2 credits) and AI citation checks (5 credits, because one check asks every configured engine — ChatGPT, Gemini, Claude — whether they'd cite your site, so it is several model calls rather than one request). On the AI Visibility plan ($19.99/month) checks stop costing credits entirely: 25 a day, resetting at midnight UTC, with the automatic weekly re-checks behind drop alerts drawing on that same allowance. Every new account starts with enough credits for one citation check, and the AI score plus the AI-retrieval scan of your Search Console queries stay free and unlimited.

Only if you want one. Credit packs are one-time: buy a pack, use it, buy another when you need it. The monthly plans stay optional — AI Visibility ($19.99) for AI-citation monitoring, Power ($29) for indexing automation, Agency ($99) for client work. All three are month-to-month, cancelled from Settings whenever you like.

Free quotas reset at midnight UTC: 15 indexer, 20 status checks, 20 audits per user. Power and Agency users get 50 indexer / 2,000 status / 10,000 audit per day. Past the free quota you spend credits, up to 150 a day per user. Google's own caps sit on top of all that: 200 indexing publishes per day per project, 2,000 inspections per day per property.

Eventually — a year (365 days) after purchase. That is deliberately long: a pack bought for a migration should still be there when the migration actually ships. Nothing auto-renews and nothing resets monthly.

If a paid batch fails to submit (network error on our side, Google API outage), email support and we'll refund it. Submissions that complete but don't end in indexing aren't refundable. That's Google's quality decision, not a delivery failure.

No, one pack per checkout. Need more, buy another pack, up to 200 credits per day in total. Keeping it to one pack keeps refunds and expiry simple. For higher legitimate volume, email support and we'll lift the daily cap.

Because the Indexing API needs Google to verify you own the URLs you're submitting. We use your own OAuth grant against your own Search Console, so there's no shared service account to add as a property owner and no manual setup per site.

openid, email, profile, webmasters.readonly, and indexing. webmasters.readonly buys read-only access to your verified Search Console properties. indexing is the one that lets us call the Indexing API on your behalf.

Your Google email and profile, an encrypted refresh token, the URLs you've submitted, and whatever Google's APIs sent back (indexed verdict, last crawl, and so on). No page-content scraping, no analytics pixels, no marketing list.

Yes. Settings → Delete my data wipes your user record and every batch, and revokes the OAuth refresh token. You can also pull our access yourself at myaccount.google.com/permissions.

No third-party analytics, no marketing pixels, no Google Analytics. We log requests server-side for debugging, and those logs roll off on their own.

Submission to the Indexing API takes seconds and shows URL_UPDATED in our UI. Indexing itself happens at Google's pace: minutes to hours for healthy domains, days to weeks for new or low-authority sites. Run Status checks the next day to see where you stand.

You get the reason per URL: quota hit, property not verified, robots blocked, and so on. Retry the batch from your history in one click. Free retries come out of your daily quota, paid retries open a new checkout.

The Indexing API gets the URL into the crawl queue. If Google's quality classifier then says no, more pushing won't change its mind. Audit the page instead. The usual culprits: thin content, a missing canonical, weak internal linking, or low overall site authority.

Only if the content changed meaningfully. Run the Pre-check before a paid batch to see Google's current verdict per URL, then skip the ones already indexed.

Yes, up to 50 URLs per paid batch. The Sitemap picker pulls URLs from your sitemap or sitemap index so you don't copy-paste a thing.

Same underlying API. The difference is volume and batching. Search Console holds you to one URL at a time and a few requests a day. Our Status tool checks up to 50 URLs per batch and exports the results as CSV.

Indexing API: 200 publish requests per day per Google Cloud project, shared with the free indexer tier, and we track it in real time. URL Inspection API: 2,000 inspections per day per property, 600 per minute per property.

JobPosting and BroadcastEvent. For those two, the Indexing API is the official channel and Google honors it strongly. For everything else — blog posts, products, landing pages — it acts as a strong crawl hint, and indexing stays at Google's discretion.

Yes. IndexerNow is platform-agnostic. So long as your site is verified in Google Search Console and the URLs are publicly reachable, the platform doesn't matter. The blog carries dedicated playbooks for the major ones.

Yes. After you sign in, IndexerNow lists every verified property your Google account owns and routes each URL to the right one automatically.

Each locale variant is its own URL and can be pushed on its own. Verify each locale's domain or subdirectory in Search Console, then submit. The multi-region playbook in the blog walks the full setup.

Verify it first. Search Console offers DNS TXT, HTML file, HTML tag, Google Analytics, and Google Tag Manager methods. IndexerNow can't submit URLs for properties you don't own.

Only if your robots.txt lets the answer-time AI crawlers in: ChatGPT-User, Claude-Web, PerplexityBot, OAI-SearchBot, Meta-ExternalFetcher. Run our free AI Crawler Access Checker on your domain and we'll show which AI bots reach you, which get turned away, and where your stance contradicts itself.

Depends where you land on training. The common 2026 pattern splits the difference: block training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot, Applebot-Extended) to stay out of model training, but let answer-time fetchers (ChatGPT-User, Claude-Web, PerplexityBot) through so you keep the citation traffic. Our AI Crawler Access Checker flags when the two contradict each other.

No. Google-Extended controls Gemini training and AI Overviews. Regular Googlebot, the crawler that feeds Search, is a separate user-agent and carries on untouched.

A proposed markdown manifest you publish at /llms.txt, much like robots.txt, giving AI assistants a curated, link-rich tour of your site. It doesn't gate access; robots.txt does that. What it does is ground their answers in the right pages. IndexerNow generates one from your sitemap in the AI search hub.

Get indexed in regular Google Search first, since AI Overviews draw from the same index. Then: don't block Google-Extended in robots.txt, publish substantive content with a clear extractable answer in the first paragraph, add FAQPage / HowTo / Article schema, and keep dateModified fresh. Citation candidates nearly always come off the first organic page.

Both lean on Bing's retrieval index, so submit to Bing via the IndexNow tab. Allow ChatGPT-User, OAI-SearchBot and PerplexityBot in robots.txt. Write pages with self-contained, quotable answers in the first viewport. Pair that with an llms.txt for cleaner citations.

A 0-100 score we compute for any domain from 8 signals: HTTPS, sitemap, structured data, canonical, Open Graph, robots.txt AI bot policy, llms.txt presence, and a homepage title. It's a quick sweep for the obvious discoverability gaps across Google and AI search. Free at /tools/discoverability-score.