Instant indexing (IndexNow)
Normally a search engine finds a new post whenever it next crawls your site — which might be hours, might be weeks. IndexNow flips that around: the moment you publish, Bloggable tells the engines the URL exists.
One submission reaches every participating engine, including Bing, Yandex, Seznam and Naver.
Google doesn't use IndexNow. For Google, connect Search Console — that's the equivalent there, and the two are complementary rather than alternatives.
Switching it on
Set per blog, in the same place as analytics:
- Blog settings → Indexing, or
- Integrations → Indexing (main nav)
Flip Instant indexing (IndexNow) on. That's the whole setup — there's no account to create, no API key to fetch and nothing to paste.
Behind the scenes Bloggable generates a verification key and starts serving it from your blog's own address. You'll see the key and its address on the card once it's on.
What happens from then on
- You publish a post → that post's URL and your blog's homepage are submitted.
- You update a published post → submitted again, so the engines re-read it.
- You unpublish a post → submitted as well. Telling an engine to re-crawl a URL that now returns "not found" is the fastest way to get it dropped from the index.
Scheduled posts are submitted when they actually go live, not when you schedule them.
Submitting the posts you already have
Switching IndexNow on only affects what you publish from then on. To submit your existing archive, press Submit all published posts on the same card.
That sends your homepage plus every published post, newest first. You can do it once an hour — the engines rate-limit sites that resubmit their whole archive repeatedly, and that limit is applied to your site's reputation, not ours.
You shouldn't need it more than once. The automatic per-publish submission is the normal path.
Does this need a custom domain?
No. Unlike Search Console, IndexNow works on a Bloggable address too.
The reason is how ownership is proved. IndexNow asks for a key file served from the site being submitted, and it treats that file as vouching for URLs at or below its own folder. For a blog on your own domain the key sits at the root. For a blog at getbloggable.com/b/your-blog, the key sits inside /b/your-blog/ — so it vouches for your posts and nothing else on the shared domain.
The one case that can't work: a blog set to redirect to your own site rather than serve its own pages. There's nowhere for us to put a key file on a site we don't host. Submit from that site instead, and Bloggable will tell you so rather than failing quietly.
Reading the result
The card shows the last submission — when it ran, how many URLs were accepted, and any error.
- "URLs accepted" — the engines took the list. It doesn't promise indexing; nothing does. It means the URL is now queued rather than waiting to be discovered.
- "IndexNow could not verify the key file" — the key file isn't reachable. Most often this is a blog whose address changed recently, or one whose custom domain isn't resolving. Open the key address shown on the card; it should return the key as plain text.
- "The submitted URLs don't match the verified key location" — the blog's address changed after the last submission. Publishing anything will re-submit against the new address and clear it.
- "Too many submissions" — the hourly manual limit, or the engines' own. Wait and try again; automatic submissions carry on regardless.
Regenerating the key
There's a Regenerate key button. You almost certainly don't need it — the key is public by design, it proves control of the site precisely by being served from it, and there's nothing to leak.
It's there for the rare case of a submission failing verification against a stale key. Be aware that regenerating retires the old key file immediately, so any submission still being verified against it will fail.
Turning it off
Flip the switch off. The key file stops resolving and nothing further is submitted. URLs already indexed stay indexed — IndexNow is a notification, not a permission.