DEV Community

Just a Side Project
Just a Side Project

Posted on Originally published at justasideproject.blogspot.com

I Registered This Blog With Three Search Engines in One Afternoon (And Discovered IndexNow Doesn't Work on Blogger)

Two weeks after this blog went live, Google Search Console was still reporting exactly zero impressions -- not low, not slow, literally zero, for every single query, for the entire period. Typing the blog's own name into Google turned up nothing. That's normal for a two-week-old site with no backlinks, but it was still the push I needed to stop assuming Google alone would eventually notice this blog existed, and go register it everywhere I reasonably could in one sitting: Google, Naver, and Bing, back to back, on the same afternoon.

Three tools, three different ideas of "prove you own this"

All three services want the same basic thing -- confirm you control the site, then hand over a sitemap so their crawler doesn't have to discover every page by accident -- but each one insists on a different mechanic for the ownership check, and Blogger's specific limitations (no root file uploads, no server-side control) ruled some of them out before I even started.

Service Verification method used Worked on Blogger?
Google Search Console HTML meta tag in <head> Yes
Naver Search Advisor HTML meta tag in <head> (file-upload option explicitly unsupported on Blogger) Yes
Bing Webmaster Tools Imported directly from an already-verified Google Search Console property Yes -- no separate verification needed at all

The Bing import turned out to be the pleasant surprise of the afternoon. Because Google Search Console was already set up, Bing offered to pull the verified property and its sitemap straight from Google's records, with no separate proof-of-ownership step. What I expected to be the same 10-minute dance a third time took closer to ninety seconds.

The one tool that flatly doesn't work on Blogger

Encouraged by how easy Bing was, I went looking for one more thing: IndexNow, a protocol Microsoft and a handful of other search engines use to let a site push "this URL just changed" notifications instead of waiting to be crawled. It sounded like exactly the kind of thing that fits an automated publishing pipeline -- one more API call at the end of publish.py, and every new post would announce itself immediately instead of waiting for a crawler to stumble onto it.

IndexNow's ownership proof is different from the other three: it requires hosting an actual text file, named after your API key, at the root of your domain -- something like https://yourdomain.com/a1b2c3.txt. Not a meta tag, not an import. A real static file, at a real path, that the search engine fetches directly. Blogger has no mechanism for that. There's no file system, no root directory you can write to -- the entire platform is built around posts and pages served through Blogger's own templating, not arbitrary static files. Meta tags work because Blogger lets you edit the theme's HTML. A standalone file at the domain root is a different category of access that Blogger simply doesn't grant, to anyone, at any tier.

The workaround that shows up in most guides is to host the key file somewhere else entirely -- GitHub Pages, Netlify, any static host -- and point IndexNow's keyLocation parameter at that instead. It would technically work. It would also mean standing up and maintaining an entire second free-tier hosting account for the sole purpose of holding one text file, in a project whose whole premise has been staying inside a single Google-centric, zero-infrastructure footprint. That trade felt backwards, so I skipped it -- one manual URL submission per new post, across three dashboards, is a smaller cost than a permanent second hosting dependency for a feature that only saves a few days of crawl delay.

What actually changed by the end of the afternoon

Nothing showed up in search results that day -- registration and indexing are two different clocks, and only one of them moves fast. What did change is that all three services now know this blog exists and where its sitemap lives, which is the precondition for showing up at all rather than a guarantee of it. Naver in particular is worth being honest about: even fully registered, external blogs are generally understood to rank behind Naver's own blog platform in Naver's results, so "registered" here means "eligible to appear," not "will appear prominently."

The concrete next check is whether Google's Search Console starts reporting a nonzero page count under "indexed," and whether Bing's dashboard shows the submitted URLs moving out of "pending." Both of those are just a matter of checking back in a week or two -- there was no more setup left to do that afternoon, which for a zero-budget, single-person pipeline felt like its own small milestone.

Related reading

Top comments (0)