Submitting a URL is a receipt that a search engine received it, not a promise that it will be crawled, indexed, or ranked, and the only tools worth trusting are the ones that say so.
Indexing is where a lot of business owners get sold magic. A URL submission can notify participating search engines that a page was added, changed, or deleted, but it cannot force a crawl, cannot force ranking, and cannot fix a thin page. The page still needs to exist, load, link, and answer the search. Submission is a receipt, not a guarantee.
This article is about what submission actually does, what the two big protocols (sitemaps and IndexNow) promise in their own documentation, what Google does and does not accept, and how WALO wires the whole thing into a panel an owner can run without reading a spec. It includes two real receipts from AMH's own sites, because NU's rule is that a claim with a number needs a record behind it.
The problem owners actually have
A cafe owner in Livermore pays someone to build a new menu page and a page for catering. The pages go live on a Friday. Two weeks later she searches "catering Livermore" and her page is nowhere. She searches the exact title of the page and it is still nowhere. She calls the builder, who says "it takes time." She reads a forum thread that says to "submit the URL to Google," finds a tool that promises "instant indexing," and pays for a month. The tool reports "submitted" with a green check. Another two weeks pass. Still nowhere.
What actually happened is a chain of small failures that the green check cannot see. The catering page was not in the sitemap, because the builder's template only listed the pages that existed when the site launched. No page on the site linked to it except a footer link that was hidden on phones. The page's title was "Untitled" because the template's title field was never filled. And the "instant indexing" tool she paid for submitted the URL to a protocol that Google does not participate in, so the only search engine she cared about never heard from it.
The owner's problem is not that submission does not work. It is that submission is the last of five steps, and the tools that sell it rarely check the first four. The proper flow is simple to say: publish the page, put it in the sitemap, link to it from a relevant page, verify the canonical URL, submit the URL where the platform allows it, then check later whether it was crawled or is ranking. The tool that does all six is rare. The tool that does only step five and calls it done is common.
How the industry handles it today
There are two protocols worth understanding, and they do different things.
A sitemap is a file, usually sitemap.xml, that lists the URLs on a site. Google's documentation describes it as a way to tell Google which pages and files you think are important and provide information like when each page was last updated. Search engines fetch the sitemap on their own schedule. It is a standing inventory, not a push notification. Google's build guide also lists the limits: a sitemap file can hold up to 50,000 URLs and be up to 50 MB uncompressed, and larger sites split into multiple files with an index.
For years there was a shortcut for telling Google "the sitemap changed, come look," called the sitemap ping. Google retired it. The Search Central blog post from June 2023 is titled "Sitemaps ping endpoint is going away," and it says the unauthenticated ping requests were being ignored and the endpoint would be deprecated. What remains for Google is submitting the sitemap in Search Console, which requires proving ownership of the property, and the URL Inspection tool, which lets an owner request indexing for a single page. Google's help page for that tool states two things directly: "There is a daily limit to how many index requests you can submit," and "submitting a request does not guarantee that the page will appear in the Google Index." If you want many pages indexed, the help page says to submit a sitemap.
IndexNow is the second protocol. It was announced by Microsoft Bing in October 2021 as "a simple ping protocol" so that "search engines know that a URL and its content has been added, updated, or deleted." The documentation at indexnow.org describes how it works. A site proves ownership by hosting a UTF-8 text key file at its root, or at a location it names in each request. A submission is an HTTP request with the URL and the key, or a POST with a JSON list of up to 10,000 URLs. The documentation says a successful request returns HTTP 200 and then adds the sentence that this entire article turns on: "The HTTP 200 response code only indicates that the search engine has received your URL." The FAQ adds that sending more than 10,000 URLs in one POST may fail with HTTP 422.
Which engines participate is public. The protocol's own machine-readable list at indexnow.org names Bing, Yandex, Seznam.cz, Naver, Yep, the Internet Archive, and Amazon's crawler. Google is not on that list. A tool that says it will "get you indexed on Google" via IndexNow is describing something the protocol does not do. IndexNow is a Bing-and-partners lane, and that is useful, but it is not the Google lane.
Cloudflare is the third piece of the record, because a large share of small-business sites sit behind it. Cloudflare's Crawler Hints feature supports IndexNow natively, per its documentation: it uses a cache-status miss as the signal that content has likely changed and sends that to IndexNow's crawler. Cloudflare announced the support on October 18, 2021. Cloudflare's docs also note a sensible limit: responses with a 4xx or higher status are not reported. For a site on Cloudflare, that means some IndexNow notifications may already be happening automatically on cache misses, which is one more reason the owner should not pay a third party for "instant indexing."
Bing has its own console too, and it is worth a sentence because IndexNow is Bing's protocol. Bing Webmaster Tools lets a verified owner submit sitemaps and URLs directly, and its getting-started checklist walks through verification, sitemap submission, and the reports that show what Bing crawled. Its webmaster guidelines describe what Bing wants from a page, which overlaps heavily with Google's: clear titles, real content, crawlable links, and no tricks. For an owner who has already done the Google work, Bing's console is a twenty-minute addition and it is where the IndexNow submissions can be seen landing.
What none of these protocols do is decide whether the page deserves to be indexed. A submission tells an engine that a URL exists or changed. The engine then decides, on its own schedule and by its own rules, whether to fetch it, whether to keep it, and whether to show it. Those three decisions are what the owner actually wants, and no protocol makes any of them. Google's guidance on crawl budget is aimed at large sites, one million pages or ten thousand rapidly changing pages, and says smaller sites generally do not need to worry about it. But every site, large or small, can see in Search Console's Page Indexing report the bucket called "Discovered - currently not indexed," which means Google knows the URL exists and has chosen not to fetch or index it yet. No submission protocol empties that bucket. Better pages, better links, and time do.
How WALO does it
WALO puts indexing in two places: a panel on the SEO Pro web tool, and a lane in the Cloudflare connector. Both follow the same rule the site states everywhere else: check first, submit real pages, and say what the submission does and does not mean.
Indexing actions: the panel
On walohq.com/seo/, below the audit and the Landing Page Builder, there is a panel titled "Indexing actions." Its first line is the whole philosophy in one sentence: "Submit real verified pages. IndexNow checks the key and sitemap before sending. Google requires Search Console ownership, so connect it through WALO first."
The panel has two cards, and they are honest about which engine each one reaches.
The IndexNow card says: "Checks the key file, reads sitemap.xml, dedupes URLs, then submits to Bing-supported discovery." That is four steps, not one, and the order is the point. Checking the key file first means WALO verifies that the site actually hosts the ownership proof the protocol requires, before firing anything. Reading sitemap.xml means the list of URLs comes from the site's own inventory, not from a guess. Deduping means a sitemap with a trailing-slash version and a non-slash version of the same page does not get submitted twice. And "Bing-supported discovery" is the honest name for where IndexNow goes.
The Google card says: "Connect Search Console through WALO OAuth, verify the property, then submit sitemap.xml there." There is no "submit to Google" button, because there is no such thing. There is a Connect Search Console button, which starts the OAuth connection, and an Open Google Console button, which takes the owner to Google's own tool for the parts only an owner can do.
After the audit runs on a site, the panel's status line changes to a plain instruction. In the capture below, after scanning WALO's own site, it reads: "Ready. For walohq.com: upload an IndexNow key file if needed, then submit. Google: connect Search Console through WALO, then submit /sitemap.xml."
The FAQ answer, verbatim
WALO's FAQ asks "Can it get my site on Google?" and answers: "It helps. WALO submits your pages through IndexNow and shows you exactly what to do in Google Search Console. It gets you index-ready fast; Google's own approval is still Google's." The phrase "Google's own approval is still Google's" is the limit stated as a feature. The companion rank-alert article covers the Search Console side in more detail, including the FAQ's note that new sites show no rank data until they start appearing.
Detect: new and changed URLs from the sitemap
The original short version of this article listed four steps for WALO's indexing flow: detect, submit, Google lane, receipt. Detect is reading the sitemap and comparing it against what was submitted before. A sitemap is an inventory; the difference between today's inventory and yesterday's is the list of new and changed pages. WALO's Cloudflare connector describes the ongoing version of this as "Submit updated pages and keep sitemap/robots clean after approved content changes." The words "after approved content changes" tie the submission to the approval log: a page gets submitted because an owner approved publishing it, not because a crawler noticed a cache miss.
Submit: valid pings only, where supported
Submit is the IndexNow POST, with the key checked and the URL list deduped. The protocol's limit of 10,000 URLs per request is respected by batching. The response code is recorded. That recording matters because, as the protocol's own documentation says, 200 means received, nothing more.
Google lane: guide the owner through ownership
The Google lane is a guided handoff. Search Console ownership cannot be delegated to a tool without the owner's authorization, so WALO connects through OAuth and then points at the two things only the owner's console can do: verify the property and submit the sitemap. The free scan page describes the same handoff in its "Sitemap and indexing" check: it "checks sitemap and robots signals, then points you toward IndexNow, Google Search Console, and Bing Webmaster Tools."
Receipt: URL, response, timestamp, next check
Receipt is the part the "instant indexing" tools skip. Each submission is stored as the URL that was sent, the response code that came back, the time, and the date of the next check. The next check is a later look at whether the page was crawled or is appearing, which is the only way to know whether the submission led anywhere. Without the next check, a receipt is just a log line.
The Cloudflare lane
The second place indexing lives is the Cloudflare connector. WALO's Connect Cloudflare page lists IndexNow among the reasons Cloudflare is "the best first power connector," alongside DNS, email trust, Pages deploys, and Turnstile.
The IndexNow card on that page reads: "Submit updated pages and keep sitemap/robots clean after approved content changes." Next to it sit the lanes that make the rest of the five-step flow possible: Pages and deploys ("Best path is GitHub plus Cloudflare Pages so approved commits build cleanly"), and the traffic check that tells the owner whether humans arrived after the page was indexed.
The safety model on that page is four steps: Scan ("Read zones, DNS, routing, Pages, and site state"), Plan ("Show what is missing or conflicting in plain language"), Approve ("Wait for approval before DNS, deploy, or security changes"), and Verify ("Check live pages, no 404, and email/DNS records after changes"). Submitting a URL is a read-only act from the site's perspective, so it does not need the heavy approval that a DNS change needs. But the "verify" step applies: a page that returns a 404 should never be submitted, and Cloudflare's own Crawler Hints documentation makes the same choice by not reporting 4xx responses to IndexNow.
Two receipts from AMH's own sites
NU prints records. Here are two from the AMH fleet that show what submission does and does not do.
Apiary: 23,352 URLs, all accepted, most still not indexed
Apiary is AMH's community library, a large site with a sitemap of more than 23,000 URLs, most of them under its community section. On October 29, 2026, the full sitemap, 23,352 URLs, was submitted through IndexNow in three batches, each under the protocol's 10,000-URL limit. All three batches returned HTTP 200.
That is the receipt. Here is the rest of the record, from the Search Console coverage export for the same site on the same day: 6,254 URLs indexed and 17,127 not. Of the not-indexed URLs, 13,483 were in the "Discovered - currently not indexed" bucket, which is Google saying it knows the pages exist and has not fetched them yet. Another 3,447 were marked "Server error (5xx)," which traced back to an outage in August when the site's compute budget was exhausted and it served errors for a stretch. On October 29, forty of those URLs were picked at random and fetched with a Googlebot user agent. All forty returned 200. The site was fine; Google's record was stale.
Three lessons sit in that one receipt. First, 23,352 accepted submissions changed nothing about the 13,483 pages Google had chosen not to crawl, because IndexNow does not reach Google and because "discovered, not indexed" is a crawl-priority decision, not a notification problem. Second, a 5xx error count in Search Console can describe an outage that ended two months ago, and the right response is to sample the live site before assuming anything is broken now. Third, the IndexNow submission was still worth doing, for the engines that do participate, and it cost nothing but a few minutes.
walohq.com: the sitemap that "couldn't fetch"
The second receipt is smaller and more common. In mid-2026, Search Console reported that it "couldn't fetch" the sitemap for walohq.com. The sitemap file itself was fine: it returned 200, was valid XML, and every one of its URLs returned 200 on the correct host. The failure was a malformed entry that had been submitted in the console months earlier as the path "/XML" with an unknown type. The fix was entirely inside Search Console: remove the bad row and submit sitemap.xml. After that, the status flipped to Success with 37 pages discovered, in August 2026.
The lesson is that "couldn't fetch" in a console is a claim about what was submitted, not necessarily about what the site serves. Check the file first, then the submission.
A third, quieter receipt: the pages that were empty to crawlers
There is one more AMH record worth including because it is the kind of failure that no submission tool can detect. In August 2026, an audit of walohq.com found that a dozen of its pages, built with a design tool that packs the page content into script blocks and unpacks it in the browser, shipped an essentially empty body to any crawler that does not run JavaScript. The head tags were excellent: title, description, canonical, Open Graph, structured data, all present. The body, to a no-JavaScript crawler, was a loading splash. The fix was to insert a static copy of each page's real text into the HTML so crawlers could read it, and all twelve sitemap pages were fixed and verified the same day.
Google's own JavaScript SEO documentation explains why this matters: Google can render JavaScript, but rendering is a separate, later step from crawling, and many other crawlers do not render at all. A page can return 200, be in the sitemap, be submitted through every protocol, and still be invisible, because what the crawler fetched had no words in it. WALO's own project notes carry the rule that came out of that day: fetch the page and look at the HTML; do not trust the status code.
Under the hood, in plain English
The chain for a WALO indexing action is: the owner publishes or approves a page, WALO reads the site's sitemap, compares it with what was submitted before, confirms the IndexNow key file is where the protocol requires, dedupes the list, sends it in batches under the protocol's limit, records the response and time, and schedules a later check. For Google, the chain is: connect Search Console through OAuth, verify the property, submit the sitemap in the console, and read the Page Indexing report later.
The approval model is the one on WALO's Connect page: "Connecting is not permission. WALO drafts first, shows exactly what changes, and waits. Nothing writes to code, DNS, payments or a public feed without your word." The four steps are Ask, Stage, Approve, Verify.
For indexing specifically, submission is the low-risk end of that model. Publishing a page or changing a sitemap on a connected site is the higher-risk end, and that runs through Walrus Tusk, the AMH engine inside WALO that the Agent Board page describes as "dry run first, then a health check, then auto-rollback." A deploy that breaks the sitemap gets rolled back before anything is submitted.
The Browser Agent lane on the Connect page is the verify step made concrete: "Checks pages, screenshots, 404s and forms after an approved runner is connected." For indexing, that is the tool that catches the catering page returning 404 before anyone submits it.
What WALO does not do is pretend. It does not claim to submit to Google through IndexNow. It does not report "indexed" when the record says "received." The FAQ's "Google's own approval is still Google's" is the plain-English version of the protocol's "only indicates that the search engine has received your URL."
What it costs and what is free
Only what the site states. SEO Pro, including the Indexing actions panel, is labeled "Free - nothing to install." The free scan page says "Free scan. No coding needed." WALO's FAQ says the core runs on free infrastructure, the first week is free, and there are no per-message fees, with only certain add-ons (some rank data, premium voice) carrying a small cost. The home page describes a free core and paid Power AI and Teams tiers without listing prices on the pages read for this article.
IndexNow itself is free; Bing's page describes it as "a free, open-source protocol." Google Search Console is free. Cloudflare's Crawler Hints feature is documented as part of Cloudflare's caching features. The paid "instant indexing" services the cafe owner found charge for a thing that is free at every layer underneath them.
Honest limits and what is still being built
IndexNow does not reach Google. Google is not on the protocol's participating list, and WALO's panel says "Bing-supported discovery" for that reason. The Google lane is Search Console, which the owner must authorize and verify.
A 200 from IndexNow means received. The protocol's documentation says so. It does not mean crawled, indexed, or ranked, and the Apiary receipt above shows a 23,352-URL submission sitting next to 17,127 not-indexed pages on the same day.
Google's URL Inspection tool has a daily limit on requests and does not guarantee indexing. For many pages, Google's own advice is to submit a sitemap and wait.
"Discovered - currently not indexed" is a crawl decision. No submission empties that bucket. Better pages, internal links, and time do. For very large sites Google's crawl budget guide applies; for most small businesses it does not.
Pages that render only in the browser can be invisible to crawlers that do not run JavaScript, even with perfect head tags and a 200 status. WALO's audit reads the HTML; the owner should too.
Sitemaps built by templates can miss new pages. The sitemap is the inventory WALO reads, so if the catering page is not in it, it does not get submitted. Fix the inventory first.
Cloudflare's Crawler Hints may already be notifying IndexNow on cache misses for a Cloudflare-fronted site. A manual submission is not harmful, but the owner should know it may be a duplicate of what the edge already sent.
Nothing here makes the next check automatic for every engine. The receipt stores a next-check date; whether the page appears is still something that gets read from the engine's own report.
A 30-day playbook
Week one: inventory. Run SEO Pro on your site and read the "Sitemap and indexing" result. Open your sitemap.xml in a browser and confirm the new pages are in it. If they are not, that is the first fix, and no submission matters until it is done. Open each new page and read the HTML source, not just the rendered page: is the text there? Is the title filled in? Is there a canonical tag pointing at the page itself?
Week one, second task: link. Add a link to each new page from a relevant page that already gets traffic, in the body, not only the footer. A page with no internal links is a page Google has little reason to prioritize.
Week two: connect and submit. Host the IndexNow key file at your site's root, or confirm it is already there. In the Indexing actions panel, submit. Record the response. Then connect Search Console through WALO, verify the property if it is not already verified, and submit sitemap.xml in the console. If the console says it could not fetch the sitemap, check for a malformed row before you check the file.
Week three: wait and sample. Do not resubmit daily. Check the Page Indexing report once. If a page is in "Discovered - currently not indexed," the move is to improve the page and its links, not to submit again. If the report shows 5xx errors, fetch a sample of those URLs yourself before assuming the site is down; the errors may describe a past outage.
Week four: measure arrival. Use WALO's "real views" check on the new pages to see whether humans arrived, and the companion rank-alert flow to see whether the pages appear for their target phrases. A page that is indexed but gets no impressions is a relevance problem, which is the companion keyword-gap article's territory.
After thirty days, settle into the rhythm: submit when you publish, check the report monthly, and read the HTML every time a template changes.
FAQ
Does submitting a URL get it indexed? No. The IndexNow documentation says a 200 response "only indicates that the search engine has received your URL." Google's URL Inspection help says a request "does not guarantee that the page will appear in the Google Index." Submission is a notification.
Does IndexNow work for Google? Google is not on the protocol's published list of participating engines, which names Bing, Yandex, Seznam.cz, Naver, Yep, the Internet Archive, and Amazon. WALO's panel calls the IndexNow lane "Bing-supported discovery" for that reason. For Google, submit the sitemap in Search Console.
What happened to pinging Google with my sitemap? Google deprecated the sitemap ping endpoint, announced in June 2023. Submit sitemaps in Search Console instead.
How many URLs can I submit through IndexNow at once? Up to 10,000 per POST request, per the protocol's documentation and FAQ. More than that may return HTTP 422. WALO batches under the limit.
What is the key file? A UTF-8 text file containing your IndexNow key, hosted at your site's root or at a location you name in each request. It proves you control the host. WALO's panel checks for it before submitting.
My Search Console says "couldn't fetch" my sitemap. Is my site broken? Check the file first: open it, confirm it is valid XML and returns 200. Then check the submission: a malformed row in the console produced exactly that message on walohq.com in 2026, and the fix was removing the row and resubmitting sitemap.xml.
Why does Google show thousands of my pages as "Discovered - currently not indexed"? Because it knows they exist and has not chosen to crawl them. That is a priority decision, not a notification problem. The Apiary receipt in this article shows 13,483 such pages on the same day a 23,352-URL submission was accepted.
My page returns 200 and is in the sitemap. Why is it invisible? Read the HTML source. Pages that only render in the browser can ship an empty body to crawlers that do not run JavaScript. Twelve pages on walohq.com had that problem in August 2026 and were fixed with static content in the HTML.
Should I bother with Bing Webmaster Tools? Yes, if only because IndexNow is Bing's protocol and Bing's console is where you can see those submissions land. Verification and sitemap submission there take minutes, and WALO's free scan points you to it alongside Search Console.
How often should I resubmit? When you publish or change a page, once. The protocol's documentation recommends automating submission at the moment content is added, updated, or deleted, not re-sending the same list daily. Repeated identical submissions do not move a page up any queue.
Is any of this paid on WALO? The Indexing actions panel is part of SEO Pro, which is labeled free. IndexNow and Search Console are free. WALO's FAQ notes that some rank data may be a small-cost add-on; submission is not among the things it lists.
Where to learn more
The other WALO product articles in this batch on Nothing Unseen:
- Competitor keyword gaps, for the pages worth publishing in the first place.
- Rank alerts and competitor watch, for the Search Console side and what happens after a page is indexed.
- Email campaigns for local service, for the follow-up side of the same business.
- Shorts content engines and WALO Creators: the agentic content desk, for the creator side of WALO.
The product: WALO, WALO SEO Pro with the Indexing actions panel, the Connect Cloudflare page, and the WALO FAQ. WALO is made by AMH, Artificial Mind Hive. The Apiary receipt is from Apiary.
Sources (the record)
- IndexNow documentation: key file, up to 10,000 URLs per POST, "HTTP 200 only indicates that the search engine has received your URL" — IndexNow.org
- IndexNow FAQ: bulk submission limits and HTTP 422 — IndexNow.org
- IndexNow participating search engines list (Bing, Yandex, Seznam, Naver, Yep, Internet Archive, Amazonbot) — IndexNow.org
- IndexNow at Bing: "a free, open-source protocol" — Microsoft Bing
- IndexNow announcement, October 2021 — Bing Webmaster Blog
- Cloudflare Crawler Hints documentation: IndexNow support, cache-miss signal, 4xx not reported — Cloudflare Docs
- Crawler Hints update: Cloudflare supports IndexNow (Oct. 18, 2021) — Cloudflare Blog
- Sitemaps ping endpoint is going away (June 2023) — Google Search Central Blog
- Learn about sitemaps — Google Search Central
- Build and submit a sitemap (size and URL limits) — Google Search Central
- URL Inspection Tool: daily limit, no guarantee of indexing — Google Search Console Help
- Page Indexing report, including "Discovered - currently not indexed" — Google Search Console Help
- Large site owner's guide to managing your crawl budget — Google Search Central
- Introduction to robots.txt — Google Search Central
- What is URL canonicalization — Google Search Central
- Understand JavaScript SEO basics (crawling, rendering, indexing) — Google Search Central
- Bing Webmaster Tools getting started checklist — Microsoft Bing
- Bing Webmaster Guidelines — Microsoft Bing
- WALO SEO Pro: Indexing actions panel — walohq.com
- WALO Connect Cloudflare: IndexNow and SEO lane, Scan/Plan/Approve/Verify — walohq.com
- WALO free website SEO scan: sitemap and indexing check — walohq.com
- WALO FAQ: "Can it get my site on Google?" — walohq.com
- WALO Connect page: "Connecting is not permission," Browser Agent lane — walohq.com
- Apiary — apiarybee.com
Originally published on Nothing Unseen, an Artificial Mind Hive (AMH) site. AMH is owned by Austin Little. Product pictures are screenshots of the live sites; tap any picture to open the product.