Sitemaps vs IndexNow vs manual submission: which should I use?

They solve different problems and you should use all of them. A sitemap is a pull mechanism — a list engines re-read on their own schedule. IndexNow is a push notification to Bing, Yandex, Seznam, Naver and Yep. Search Console’s Request Indexing is a manual, heavily rate-limited nudge for Google. The Google Indexing API is a programmatic notification officially limited to job postings and livestreams. None of them is a replacement for another.

Last updated 2026-07-28

What is the difference between them, in one table?

The useful axes are: which engines it reaches, whether it is push or pull, how much volume it allows, and what it costs you in setup. Here they are side by side.

When is a sitemap on its own enough?

For a small, stable, well-linked site that publishes rarely, a sitemap plus good internal linking genuinely is enough. If you publish a handful of pages a month and they get indexed within a week, adding submission tooling will not change your outcomes.

A sitemap is also the only channel that is authoritative about your whole site. Push notifications tell an engine about individual URLs; a sitemap tells it what the complete, canonical set is, which is what makes it the baseline everything else supplements.

Two things make a sitemap much more effective, and both are commonly done badly:

When does IndexNow make a real difference?

When you publish or update frequently, and when non-Google engines matter to you. It compresses discovery on five engines from “whenever the sitemap is next read” to minutes, for essentially no effort — one text file and one HTTP request.

It is the highest effort-to-value ratio of the four channels by a distance: no account, no OAuth, no quota negotiation, and volume limits around fifty times the Google Indexing API’s. Full detail in the IndexNow guide.

The catch is the one worth repeating: Google does not participate. If Google is the only engine you care about, IndexNow does nothing for you directly, and you should not let anyone imply otherwise.

When should I use Search Console’s Request Indexing button?

For individual, genuinely important pages — a new cornerstone page, or a page you just substantially rewrote. It is the wrong tool for anything routine, because it is manual and capped at roughly ten to twelve URLs a day per property.

It is worth being clear about what it is not: it is not a queue-jump, and Google states that using it does not guarantee the URL will be indexed. Pressing it repeatedly on the same URL does nothing.

The realistic use is surgical. If you have fixed the reason a page was not being indexed, Request Indexing is how you say “look again now” instead of waiting. If you find yourself wanting to press it fifty times, that is the signal to automate the channel properly — and also, often, a signal that the problem is not submission at all.

Where does the Google Indexing API fit?

Officially, only for pages carrying JobPosting or BroadcastEvent markup. That is Google’s documented scope, and it is the honest answer even though a lot of tooling in this space implies otherwise.

Its practical characteristics — 200 notifications per day, scoped per Google Cloud project rather than per site, free, requiring Search Console-verified ownership — are covered in the Indexing API guide, along with why building a strategy exclusively on it is risky.

The sane way to hold it: a supplementary channel that costs nothing to use if you are set up for it, that you should not depend on, and that does not replace a sitemap for Google.

What is the recommended setup?

Layer all four. A clean sitemap with accurate lastmod as the foundation; IndexNow firing automatically on every publish; Search Console verified so you can inspect and occasionally nudge; and the Indexing API added if your setup supports it.

Doing all four by hand every time you publish is exactly the kind of repetitive work that stops happening after week three. Indexa does it on a schedule: it reads your sitemaps daily, notices which URLs are new or whose lastmod changed, and submits those to Google’s Indexing API and to the IndexNow engines — from your Mac, using your own Google Cloud project and your own IndexNow key, for $19 once with no subscription. Submission is all it does; the indexing decision stays where it always was.