On the evening of 23 October I opened Search Console for the weekly review. The property list did not contain blog.niejing.top. No impressions, no clicks, nothing to compare. Fifteen Chinese posts and eight English posts had shipped with zero build errors, and the domain was returning NXDOMAIN on both AliDNS and Google DNS.
So the review moved one step earlier. Between a finished draft and a reader there are five gates. This week I passed two.
What shipped
| Date | Chinese | English | |
|---|---|---|---|
| 10-19 | 6 | 4 | 2 |
| 10-20 | 3 | 1 | 3 |
| 10-21 | 3 | 1 | 3 |
| 10-22 | 2 | 1 | 2 |
| 10-23 | 1 | 1 | 1 |
| Total | 15 | 8 | 11 |
Scope: file dates in content/posts, content/posts-en, and content, from 19 to 23 October. The Chinese drafts averaged 93.2 on the internal de-AI-tone check, lowest 85.
A good score means the draft is publishable. It says nothing about whether anyone reads it.
The five gates
| Gate | What you check | This week |
|---|---|---|
| 1 Build | Run python3 blog/build.py, count ERROR lines |
0, pass |
| 2 Storage | Open the site root, confirm index returns 200 | 200, pass |
| 3 Domain | dig the root domain, read status and ANSWER |
NXDOMAIN, fail |
| 4 Property | Site visible in Search Console, sitemap submitted | Missing, fail |
| 5 Data | Impressions and clicks, even single digits | None |
The test is one line: a site is live when all five pass. The first two decide whether a page opens. The last three decide whether anyone finds it.
Why gate three held for five days
The deploy script ends with a line telling you to verify against the object storage default domain. That advice is correct. The default domain served the homepage with a 200, and the sitemap listed 63 URLs. The root domain is a separate DNS record. No CNAME had been added, so lookups came back empty.
The first post went live on 19 October. I checked again on 24 October. For five days, none of the 15 posts had started its indexing clock.
The time arithmetic is lopsided. Fifteen posts at 40 minutes each is 10 hours of work. One DNS record takes 10 minutes. A 60-to-1 ratio, and the smaller number was the one missing.
Four fixes, in order
- Add the record: point
blogat the object storage external endpoint, using the CNAME or A record the provider documents - Wait out the TTL, then query two public resolvers. The status should read NOERROR with at least one address in ANSWER
- Add the property in Search Console and verify by DNS TXT. It survives a server move, unlike an HTML file check
- Submit
sitemap.xml, then read the status back the next day. Submit a separate copy in Bing Webmaster Tools
Do not write the next post until these four are done. Until the chain is connected, a new draft is one more file sitting in a bucket.
What next week's review will contain
Three numbers: impressions, clicks, and pages with at least one ranking query. If all three are zero, write zero. "Still building up" is not a number.
Before traffic arrives, the only useful signal is whether URLs in the sitemap move from submitted to indexed. That single line matters more than the post count.
Where this applies
It fits anyone running their own site and publishing their own drafts, especially a first launch. A site that has been live for six months has usually cleared these gates already, and its bottleneck sits in content and internal links. Marketplace sellers can skip this: the platform owns indexing, and the seller owns listings and keywords.
FAQ
How long before a new site shows impressions and clicks
Once the domain resolves, the property is verified, and the sitemap is submitted, expect the first scattered impressions in 3 to 14 days. Single digits are normal in the first two weeks. Track indexed pages, not clicks.
The domain opens but Search Console shows nothing. What first
Check the sitemap read status. "Submitted" does not mean "downloaded". Look at the last download time and the discovered URL count. If the sitemap was read and indexed pages stay at zero, check robots rules and canonical tags.
Can I skip Search Console and use a third-party tool
You lose query-level data and real impression counts. Third-party estimates differ from the actual console by a wide margin. The property is free, so there is no reason to skip it.
Do the Chinese and English sites need separate properties
Yes. Different domains are different sites, and each needs its own sitemap submission. For an English site on Cloudflare Pages, DNS TXT verification is the least fragile option.
Last updated: 2026-10-24