I Bought `anshu.uk` — Here’s Why Every Developer Should Own Their Name

Most developers treat portfolios as a side project.

I decided to treat mine like infrastructure.

👉 Live: https://www.anshu.uk/

🧠 The Problem: You Don’t Exist on Google

Search “Anshu” and you’ll see:

Academics
Chefs
Consultants
Random profiles

There are hundreds of people with the same name across industries. ()

If you don’t actively build your presence, Google assigns your identity for you.

⚙️ The Strategy: Treat Your Name Like a Product

Instead of building just another portfolio, I approached this as:

“How do I rank my name like a startup ranks its product?”

So I bought:

Short. Clean. Memorable. Brandable.

🏗️ What I Built

The site is not just a portfolio — it’s a central identity hub.

Core components:
👨‍💻 About (clear positioning)
🧠 Tech stack (Golang, microservices, distributed systems)
🚀 Projects (proof of execution)
🔗 External links (GitHub, LinkedIn)

Everything points back to one thing:

“This is the Anshu you’re looking for.”

🔗 Why a Personal Domain Matters

1. You control your SEO surface

Platforms like LinkedIn or GitHub:

You don’t own them
You don’t control ranking fully

Your domain = your authority layer

1. Google understands entities, not just pages

When everything links together:

anshu.uk → GitHub → LinkedIn → Articles → Backlinks

Google starts treating you as a single entity

1. It compounds over time

Unlike social media posts:

Blog posts rank for years
Backlinks increase authority
Your name becomes searchable
📈 The Real Goal (Not Just a Portfolio)

I’m not trying to “have a website”.

I’m trying to:

Rank for “anshu developer”
Then “anshu golang”
Eventually just “anshu”

This is a long-term SEO play (6–12 months minimum).

🧱 What Most Developers Get Wrong

They:

Build a portfolio once
Never update it
Don’t distribute content
Don’t build backlinks

Result:

Dead site. Zero traffic. No discoverability.

🚀 My Execution Plan
Phase 1 — Foundation
Domain + portfolio
Clean positioning
Phase 2 — Content Engine
Articles on:
Microservices
Kafka / Temporal
Backend scaling
Phase 3 — Distribution
Dev.to
Medium
GitHub
Communities
Phase 4 — Backlinks
Guest posts
Open source
Mentions
🧠 Key Insight

You don’t become searchable by accident.

You become searchable by:

Repetition
Authority
Distribution
⚠️ Reality Check

This is not a hack.

No shortcuts
No instant ranking
No AI spam

This is:

Consistent output + strategic positioning

📌 Final Thought

If your name is common, you have two options:

Compete randomly
Systematically dominate your niche

I chose the second.

If you’re a developer and don’t own your name yet:

You’re building on rented land.