Field notes
What we learned running an indexing tool in production
Every number in these posts comes from our own database and Search Console property. That includes the results where our own tool did nothing, because those turned out to be the useful ones.
We Built an Indexing Tool and Google Ignored It: What 30 Real Submissions Taught Us About Getting Pages Indexed
Our indexing tool pushed pages to Google's Indexing API and got a 200 OK every time. Search Console showed those same pages had never been crawled. Here is what the data actually says about getting a new site indexed.
Read the field notesHow to Get a New Website Indexed by Google: A Checklist That Actually Works
A step by step checklist for getting a new site into Google, with a way to verify each step worked rather than assuming it did. Written from what we measured on our own domain.
Read moreDiscovered vs Crawled, Currently Not Indexed: What Each Search Console Status Means and How to Fix It
Discovered means Google has not fetched your page. Crawled means it fetched the page and passed. The two statuses need completely different fixes, and mixing them up wastes weeks.
Read moreInstant Indexing Tools: What They Can and Cannot Do, From Inside One
What the Google Indexing API officially supports, what IndexNow reaches, why ping services stopped working, and how the two minute indexing claim is actually produced.
Read moreHow to Get Event Pages Indexed Fast: A Guide for Event and Ticket Publishers
Concert and fixture pages have a deadline. Here is how to structure, publish and submit them so Google picks them up while the search demand is still there.
Read moreWhat SwiftIndex actually does
We push pages on domains you have verified in Google Search Console through the Indexing API, send IndexNow for Bing and Yandex, then check live search results to confirm what landed. Anything Google does not index is refunded automatically. For URLs on sites you do not control, we are honest that no tool can force a Google crawl.
See how SwiftIndex works