IndexNow key generator, lastmod audit and Bing / ChatGPT access test

Verify in seconds whether Bingbot and OAI-SearchBot can index your site, check if crawlers trust your sitemap <lastmod> dates, and generate a complete IndexNow setup with key download.

Example: ,

Free & instant: verifies Bingbot + OAI-SearchBot access for ChatGPT Search & Copilot, audits <lastmod> date entropy in sitemap.xml, and generates a downloadable IndexNow key file + curl & GitHub Actions workflow.

Short answer

Fast visibility in ChatGPT Search and Microsoft Copilot depends on clean HTTP 200 access for both Bingbot and OAI-SearchBot, honest per-page <lastmod> dates in sitemap.xml (not uniform build timestamps), and instant push pings via the IndexNow protocol. Our tool checks all three and generates your <key>.txt verification file, curl command and GitHub Action for free.

What you get for free

Right away in the browser, no email needed

  • Side-by-side reachability cards for Bingbot and OAI-SearchBot (robots.txt + live HTTP)
  • Sitemap.xml <lastmod> entropy check exposing fake single-timestamp deployments
  • Instant 32-character hexadecimal IndexNow key with 1-click <key>.txt file download
  • Ready-to-run curl batch POST command and .github/workflows/indexnow.yml pipeline

100% free, zero sign-up: download your verification key file and deploy in 2 minutes.

IndexNow vs sitemap.xml vs llms.txt: How Discovery Protocols Work Together

Comparison of modern URL discovery and AI indexing mechanisms

MechanismWho Reads ItPrimary Technical Role
IndexNow (POST API)Microsoft Bing, Copilot, Naver, Seznam, YepInstant push alert within seconds of publishing or updating a URL
sitemap.xml + <lastmod>Googlebot, Bingbot, PerplexityBot, OAI-SearchBotComplete canonical URL inventory with per-page modification dates
/llms.txt (Markdown)LLM agents & AI documentation readersCurated priority map of your most important commercial & help pages

Sources: IndexNow.org specification, Microsoft Bing Webmaster Blog and Google Search Central.

Read our full architectural comparison in llms.txt vs robots.txt vs sitemap.xml and our analysis of ChatGPT Search, Bing indexing & Organic GEO.

How to Fix Artificial <lastmod> Dates in Next.js & CMS Sitemaps

  • Content-hash tracking: Compute a SHA-256 hash of rendered main content at build time and only advance <lastmod> when visible text actually changes.
  • CMS database timestamps: Pull real post_modified_gmt dates rather than regenerating a static timestamp across unchanged pages.
  • Pair with full AI bot testing: Inspect all 15 AI crawlers in our AI Crawler & robots.txt Checker, build your llms.txt file, or see our SEO & GEO plans (from €450 net/mo).

More free tools

Frequently Asked Questions: IndexNow, Bing & ChatGPT Search

ChatGPT Search blends OpenAI’s own OAI-SearchBot crawl index with Microsoft Bing’s web index (which also grounds Microsoft Copilot). When new service pages or pricing updates sit unindexed in Bing - or when your WAF blocks Bingbot or OAI-SearchBot - generative answers rely on outdated competitor pages instead.

IndexNow is an instant push-indexing protocol backed by Microsoft Bing, Naver, Seznam and Yep. Instead of waiting for periodic polling crawls, a single HTTP POST request notifies api.indexnow.org whenever URLs are created or updated, and participating engines share the ping automatically. Google does not use IndexNow and relies on accurate sitemap <lastmod> timestamps.

Many static-site and SSR build scripts stamp every URL in sitemap.xml with new Date().toISOString() on every deploy. When 100% of your URLs share one identical timestamp, date entropy collapses to 1 unique value - both Google and Bing explicitly state they ignore unverified boilerplate <lastmod> dates.

Place the downloaded UTF-8 <key>.txt file in your public web root (for Next.js inside public/, for WordPress/Nginx in the document root next to robots.txt) so https://yourdomain.com/<key>.txt returns HTTP 200 with the key string.

The official IndexNow JSON endpoint accepts up to 10,000 URLs per HTTP POST batch for a verified host. Best practice is to submit only URLs whose rendered content hash actually changed during your deployment.

Have a project in mind? Let’s price it!

Fill out our quick form and receive a tailored proposal within 24 hours.

WHAT YOU GET AFTER SENDING

  • Clear quote and priority roadmap within ≤ 24 h on business days
  • Quick review of indexation issues, keywords and AI visibility for your domain
  • Direct reply from the SEO specialist running the work - no sales rep
  • Office: ul. Grzybowska 5A, 00-132 Warszawa
  • Phone: 518 815 055
  • E-mail: kontakt@ai-seo-company.pl
  • Opening hours: Mon-Sat 7 am-11 pm, Sunday closed
  • NIP: 5253090237
  • Response Time: Within 24 h on business days, usually sooner
Prefer to talk? Call us518 815 055

No sales rep - an SEO specialist replies in ≤ 24 h · free quote

Plan and source (optional)

The controller of your data is AI SIGNALS COMPANY Prosta Spółka Akcyjna (brand: AI SEO COMPANY), ul. Grzybowska 12/14 lok. B-3, 00-132 Warsaw, Poland. We process the form data to answer your enquiry and prepare an offer. We send it by e-mail to our team (e-mail provider: Resend) and store it in a Google spreadsheet. After you submit the form, your browser passes Google an enquiry event with your hashed e-mail address, to measure ad performance. You have the right to access, rectify and erase your data, and to object to processing. Details are in our privacy policy.

We reply within 24 h on business days. No sales rep - you hear from the person doing the SEO.

Start your project →