Get your pages indexed.
Send new and changed pages to Bing and other search engines with IndexNow, automatically once your key is verified. For Google, see which pages it indexed, and the reason it gives for the rest.
Nobody can force Google to index a page. Request Indexing shows what Google decided, and why.
Google's Request indexing button is in Search Console.
Open URL Inspection in Search Console, paste the full URL, and select Request indexing. A request asks Google to crawl the URL. Google sets a daily limit on these requests.
How to Request Indexing in Google Search ConsoleRequest Indexing reads Google's verdict for the URLs in your sitemaps, so you do not inspect them one by one.
Find the stage where your pages stop.
The Why pages stop card follows your inspected URLs through four stages. Start at the biggest drop.
- 1 Inspected
- 2 Crawled
- 3 Indexable
- 4 Indexed
| Reason | First fix |
|---|---|
| Google does not know the URL. | First fix Add it to your sitemap. Link to it from a page Google already indexed. |
| Google knows the URL but has not crawled it. | First fix Link to it from your indexed pages. Cut thin URLs, such as empty tag pages. |
| Google could not fetch the URL. | First fix Check robots.txt, server errors, logins, and redirects. |
| A signal tells Google to skip the URL. | First fix Look for a noindex tag. Make sure the canonical points to the page itself. |
| Google crawled the page and chose not to index it. | First fix Compare it with similar pages on your Site. Improve it, or merge it into the stronger page. |
IndexNow for Bing and others. Google's reason for each sitemap URL.
Send pages with IndexNow
IndexNow notifies Bing and other participating search engines about any page type. Google is not one of them. Once your key is verified, Request Indexing sends new and changed sitemap URLs for you.
Every sitemap URL, with its reason
Request Indexing inspects the URLs in your sitemaps with URL Inspection, within your Free allowance. Each URL shows Google's verdict and reason.
What changed
Coverage over time, and the URLs whose verdict changed in the last 28 days.
Watched URLs
Keep scheduled URL Inspection evidence for pages you choose. This does not request indexing.
Sitemaps
What you declared, what Google discovered, and what drifted between the two.
Request Indexing also keeps your Search Console history past Google's 16-month window, within your Free allowance.
From Search Console to Google's answer in four steps
Sign in with your Google account
One OAuth sign-in. We read your Search Console data. The only changes we make there are a sitemap submission and a property you add and verify.
- Search Console and Indexing API access
- Revoke any time from your Google account
- Tokens encrypted at rest
Choose an account
to continue to Request Indexing
Search Console and Indexing API access
See every site in one place
Every verified property in one list, with its indexing rate and Search Console metrics. No more switching tabs.
- Totals across every property you own
- Filter by domain, path, or status
Send new and changed pages with IndexNow
Publish your IndexNow key file and verify the key. Automatic sending then sends new and changed sitemap URLs after each sitemap update.
- Bing and other participating search engines. Google is not one of them.
- Any page type on your site.
- A receipt records the notification outcome.
- For job posting and livestream pages only, you can also submit to Google's Indexing API.
# The IndexNow request. Request Indexing sends it for you.
curl -X POST https://api.indexnow.org/indexnow \
-H "Content-Type: application/json; charset=utf-8" \
--data '{
"host": "www.example.com",
"key": "8d7a3c1e6f2b4a90",
"urlList": [
"https://www.example.com/blog/new-post",
"https://www.example.com/pricing"
]
}'See what Google decided
Your dashboard shows the index status Google reports for each URL, read through gscdump. No more refreshing Search Console.
- Status per URL
- Coverage over time
- Indexed, not indexed, and the reason Google gives
Learn how to ask Google, and how to read its answer.
How to Request Indexing in Google Search Console
Request indexing for one URL with Search Console's URL Inspection tool: the steps, who can do it, the daily limit, and what a request does not prove.
Indexing API for blog posts
Ordinary blog posts are outside Google's supported Indexing API use. Learn what to use instead, and what an accepted request proves.
How the Indexing API works
What the API supports, what a notification response means, when Google requires approval, and how it differs from URL Inspection.
Step-by-step tutorial
Create a Google Cloud project and service account, give it Search Console ownership, and send your first eligible notification.
Node.js implementation
Send one URL_UPDATED notification with googleapis, read the failures, and tell notification metadata apart from index status.
Bulk URL submission
Send eligible URLs one request at a time, see how multipart batches differ, and keep a result for every URL.
Quota & rate limits
200 publish requests a day, 180 metadata reads a minute, the Pacific Time reset, and how a tool's own limit differs.
Weighing another tool? Read how Request Indexing compares with Indexly and SEO Gets or what replaces the closed Tag Parrot.
Who builds it, and what it can touch.
Read every line on GitHub.
Maintainer of Nuxt SEO. Building Request Indexing since 2024.
We read your Search Console data. The only changes we make there are a sitemap submission and a property you add and verify.
Deleting your account removes every Team you own and all Sites and data in them. You also lose access to Teams you joined. Google can keep the access you gave Request Indexing. Remove it in your Google Account.