IndexNow lets a law firm notify participating search engines when a public URL is added, updated, or deleted. It can make content discovery more responsive, but a successful submission does not guarantee crawling, indexing, rankings, or AI citations.
For a firm publishing attorney profiles, revising practice pages, or correcting an existing guide, the practical question is whether the publishing workflow sends the right notification and leaves evidence that someone can verify. This walkthrough explains how to set up IndexNow in WordPress, interpret its responses, and report the result without overstating what happened.
A website can tell a participating search engine that a URL changed instead of relying entirely on the engine to discover that change during a later visit. The notification identifies the URL; it does not upload a replacement article or instruct the engine where to rank it. Microsoft’s IndexNow setup guide explicitly says that using the protocol does not guarantee crawling or indexing.
Keep the stages separate when explaining the work to a managing partner:
| Stage | Evidence to retain | What it does not establish |
|---|---|---|
| Content changed | Published revision, URL, and change timestamp | That any search engine knows about the change |
| Notification received | Submission response and receipt information | That the page was fetched or indexed |
| Page crawled | Relevant engine’s crawl information or verified crawler logs | That the preferred URL was selected for indexing |
| Page indexed | Engine-specific URL inspection or indexing evidence | That it ranks for a particular query |
| Page cited in an AI answer | Observed answer, platform, query, date, and linked URL | That IndexNow caused the citation or that every AI platform uses it |
This distinction gives attorneys a useful answer to “Is the new page live in search?” A receipt means the notification worked. It does not answer every question farther down the table.
Build a small event checklist into the editorial process. Our recommended starting points are:
A notification should follow the actual public change. Do not send a draft URL because the article is awaiting approval. For a deleted page, the intended outcome may be removal from an index; “not indexed” is not automatically a failure.
Keep intake submissions, client portals, preview links, and other private resources out of the publishing notification queue. IndexNow is not an access-control system. Use the firm’s normal privacy and technical controls for those resources.
When enabling an integration for the first time, start with ongoing changes. Bing’s guidance advises against submitting an old archive simply because those pages changed before adoption. Avoid repeatedly sending unchanged pages to make a dashboard look active.
Check the SEO plugin, hosting configuration, and CDN. Record which system sends IndexNow requests and who maintains it. Adding a second plugin makes troubleshooting harder if nobody knows which system produced a receipt.
For a WordPress site that needs a standalone option, the IndexNow plugin published by Bing Webmaster Tools generates and hosts the verification key and submits creation, update, and deletion events in the background. Its listing also describes manual submissions and recent submission records. Review the current plugin requirements and exclusions before deployment.
The following navigation follows Rank Math’s current IndexNow documentation; labels can change between versions.
Rank Math documents automatic submission for configured content and excludes URLs marked noindex from automatic submission. Check those settings before treating a missing notification as an error.
A plugin can serve a key dynamically, so the absence of a physical file in a hosting file manager does not by itself prove the setup is broken. Test the actual key URL without a WordPress login. It should return the expected key text, rather than a login form, firewall challenge, or branded error page.
For manual implementations, the IndexNow protocol documentation describes a UTF-8 text file named for the key at the host root. A different file location requires the appropriate keyLocation; a file in a subdirectory has a restricted URL scope. Confirm that the submitted host, including any www or subdomain, matches the implementation.
Do not substitute a WordPress administrator password or hosting credential for an IndexNow key. Use the integration’s generated verification value.
Illustrative example only: the following uses the reserved example domain and a dummy key. It is not a submission from a client website. Most WordPress editors should let their selected integration construct the request.
A developer could send a JSON POST request to https://api.indexnow.org/indexnow with Content-Type: application/json; charset=utf-8:
{
"host": "www.example.com",
"key": "0123456789abcdef0123456789abcdef",
"keyLocation": "https://www.example.com/0123456789abcdef0123456789abcdef.txt",
"urlList": [
"https://www.example.com/attorneys/jordan-lee/",
"https://www.example.com/practice-areas/estate-planning/",
"https://www.example.com/retired-office/"
]
}
In this fictional workflow, the biography was added, the practice page was revised, and the retired office page was deleted. The request uses the same URL list format for all three. The website must return the intended content, redirect, or removal response when an engine subsequently visits.
The key file in the example would contain only the dummy key shown above. Replace the domain, key, file location, and URLs with the verified production values when implementing your own integration. The protocol permits up to 10,000 URLs in one POST; that is a batch limit, not an indexing commitment.
Use the Bing response definitions and the IndexNow FAQ when interpreting the submission result. These are responses from the notification endpoint, not HTTP status codes for the law firm’s article itself.
| Response | Meaning | Recommended check |
|---|---|---|
| 200 | URL notification received successfully | Retain the receipt; assess crawling and indexing separately |
| 202 | Request received, with processing or initial key verification pending | Confirm key accessibility and review subsequent results |
| 400 | Invalid request format | Check JSON, URL formatting, and required fields |
| 403 | Key verification problem | Check that the accessible key file contains the expected value |
| 422 | Host or protocol-schema mismatch | Check URL hosts, key format, and applicable key-location scope |
| 429 | Too many requests | Investigate duplicate senders and use controlled retry handling |
A recurring failure deserves a fix, not an endless sequence of manual retries. Assign an owner to investigate the integration and record when the fault was resolved.
We recommend keeping the editorial change and the submission result in one record. Include the URL, event type, change time and timezone, sending integration, submission time, response, retry history, and next check. This is a proposed operating template, not a measurement of client performance.
| Field | Synthetic example entry |
|---|---|
| URL and event | /practice-areas/estate-planning/; substantive update |
| Public change | 18 November 2026, 09:00 UTC |
| Notification | 09:01 UTC; chosen WordPress integration; HTTP 200 |
| Receipt conclusion | Notification received; indexing not established |
| Follow-up | Assigned owner to review engine-specific receipt and URL inspection |
Compare the local submission record with receipt information in Bing Webmaster Tools, as Microsoft’s setup guide recommends. Then inspect the URL’s crawl and indexing information independently. A cached plugin notice or a successful manual test alone does not establish that future automatic events will work.
After a plugin update, migration, or firewall change, test the workflow again using a genuine content change. Check deletion handling too, rather than assuming it behaves exactly like publication.
Do not label a successful IndexNow submission “submitted to every search engine” or “added to all AI answers.” The protocol serves participating engines. An AI product’s retrieval, citation selection, and display are separate processes.
For Google, follow Google’s documented recrawl methods: URL Inspection for a small number of URLs and sitemaps for larger sets. Google also says a crawl request does not guarantee inclusion. Our Google Search Console guide for law firms covers that separate workflow.
For Microsoft AI measurement, use observed report data with its stated coverage. The Bing AI Performance report walkthrough explains how to interpret citations and grounding queries. An IndexNow receipt does not establish that a particular update caused a later citation.
If a notified page remains absent from an index, investigate its response, canonical URL, indexing directives, internal discovery paths, and usefulness. Review crawler access separately using our guide to AI crawlers and robots.txt for law firms. Sending the same URL again will not repair an underlying website problem.
IndexNow works best as a maintained step in publishing: approve the change, verify the public page, send the notification, retain the response, and check the search outcome separately.
Best Law Firm Ads helps firms connect technical website work with search visibility and useful reporting. Explore our SEO & Search Visibility services to build a publishing workflow your team can verify and maintain.
IndexNow is a protocol for notifying participating search engines that a URL was added, changed, or deleted. It is a discovery notification, not a command to index or rank the page.
No. A received notification does not guarantee a crawl, index inclusion, a ranking, or an AI citation. Verify each outcome with the appropriate engine or platform.
Check for an existing integration first. Configure the chosen plugin’s public content types, verify its key location, and test a real publishing event while reviewing the submission history.
Match the changed URL to its timestamp and endpoint response, then check receipt information in Bing Webmaster Tools. Use separate URL inspection evidence to evaluate indexing.
No. Keep Google verification, sitemap management, URL Inspection, and indexing checks in Search Console. An IndexNow response is not a Google indexing report.
No. Notify genuine additions, updates, and deletions. Repeated submissions of unchanged URLs do not demonstrate better discovery or justify an indexing claim.
Yes. Maintain those discovery paths alongside notifications. IndexNow does not replace a coherent site structure, accurate sitemap, accessible pages, or useful content.