Bazi Calculator
A free online Bazi calculator and analysis tool
Today's milestone: DR 6 → 7 in one month — without spending a dollar on links
Quick update from building BaziCalculator.ai solo:
📊 Ahrefs DR hit 7.0 today, up from 6.0 last month. All from manual outreach — developer directories, niche astrology/dIY communities, and one badge collaboration. No paid links, no link farms.
⚠️ The mistake worth sharing: one of those "free badge" exchanges came back to bite me — a navigation site linking to us got flagged as spam. Spent today removing the badge and auditing the rest of my outbound links. Lesson: not all directory exposure is good exposure. Check who links to you, not just how many.
🛠️ Shipped this week:
Verified all 6 guides in /learn render correctly (what-is-bazi, true-solar-time, bazi-vs-western-astrology, and more)
Tightened rel attributes on all external badges (nofollow where required)
The honest constraint: I have a day job and a newborn. Most of this gets built in 1-2 hour windows at night. The DR climb is slow precisely because everything is manual and time-boxed — but it compounds, and zero dollars spent so far.
Next up: finishing the AI reading feature (the fun part where charts meet LLMs without hallucinating your birth data).
1 Comment
Hi Wayne,
Well done with the project so far!
From what I understand, the service is free, so why does the user need to share their email to read the full chart if they don't want to create an account to save it?
The email address associated with birth date, gender, place of birth and even time of birth creates quite a user profile if aggregated, sometimes being enough to identify individuals, so it's worth explaining how this process works, step by step, especially when introducing AI features. A third party certification would be perfect, but probably don't have the budget for that at the moment.
Considering that apart from the email (in a free chart setting), all personal data is sent to an external server for chart calculation, not used in the browser, to help with user privacy, maybe suggest people delay their real time of birth by a couple of minutes or that they input the nearest massive metropolitan city in the exact same timezone line rather than the real location (all of this shouldn’t alter the accuracy of the reading). User privacy should be at the forefront here.
Using the AI to interpret the results is quite good, because the chart itself doesn't tell a lot if you don't know much about Bazi and how to read all the info in it, but as above, data security and privacy should be paramount, as you deal with quite sensitive personal data and any breach might result in legal action.
I hope it helps! Best of luck!