SEO Strategy

How to Build a Personal Brand That Google and AI Search Can Understand

There is a version of personal branding that is about photography and fonts. This is not that.

This is about a narrower problem: when a search engine or an AI system encounters your name, does it know who you are, what you do, and whether you can be relied on? Because increasingly the answer to a question about your field gets assembled rather than listed, and the systems doing the assembling need to identify a source before they will use one.

Entities, not keywords

Google stopped treating your name as a string of characters years ago. It tries to resolve names to entities — things with attributes and relationships. An entity has a job, a location, a body of work, connections to other entities.

Two people with your exact name might exist. If your information is scattered and inconsistent, a system cannot tell whether it is looking at one person or three, so it hedges, and hedging means not citing you.

The goal is to make yourself unambiguous. Not famous — unambiguous.

Start with one place that is definitely you

Social profiles are rented. The platform decides what your page looks like, who sees it, whether it exists next year. A domain you own is the only address you control, and it should be the canonical answer to "who is this person".

That page needs to state plainly: your name, what you do, where you are, what you have made, how to reach you. Not aspirational language — checkable facts. "SEO specialist and content strategist based in Kathmandu" is an attribute. "Passionate about digital excellence" is not.

Then everything else points at it.

Make it machine-readable

This is where structured data earns its place, and it is the step almost everyone skips. When I audited 34 Nepali websites, only 53 per cent had any JSON-LD at all, and only seven had a Person node.

A Person schema block lets you state, in a form a machine reads without ambiguity: this is my name, this is my job title, this is where I am, these are the languages I work in, these are my profiles elsewhere, this is my photograph.

The sameAs property is the important one. It lists the other profiles that are the same person — your LinkedIn, your Instagram, your publisher page. That is what lets a system collapse the scattered mentions into one entity.

Two rules. Everything in your schema must be visible on the page as well; markup describing things the page does not say is a spam signal. And it must be true — no invented job titles, no awards you did not receive, no credentials you do not hold. Structured data is a set of claims, and false claims are worse than no claims.

Be consistent everywhere

This is unglamorous and it is most of the work.

Same name spelling. Same job description. Same city. Same photograph. Across your site, your LinkedIn, your Instagram, your author bios, your Google Business Profile if you have one.

If you are "Diwakar Bhatt" in one place and "D. Bhatt" in another, an "SEO Specialist" here and a "Digital Marketing Expert" there, based in "Kathmandu" and "Nepal" and "Koteshwor", you have made yourself harder to resolve for no benefit.

The photograph matters more than people expect. Using one consistent image across every profile gives systems a strong signal that these accounts are the same person. It is the cheapest disambiguation available.

Have something that is actually yours

Here is where this stops being a technical exercise.

Consistency makes you identifiable. It does not make you worth citing. A system deciding whether to use you as a source is looking for something it cannot get from ten interchangeable pages.

That means original material. Data you collected. Work you can point at. A position you hold that others do not. First-hand knowledge of something specific — a market, a language, a craft.

The audit I ran for this cluster is an example of the principle: 34 sites, measured on a stated date, with the method published. It is not a large study. But it is a number that exists nowhere else, so a system answering a question about Nepali website quality has a reason to reach for it that it does not have for the twentieth restatement of general SEO advice.

You do not need to be an authority on everything. You need to be the obvious source on something narrow.

Depth in one area beats presence in five

The instinct is to cover everything you could theoretically be hired for. It weakens the entity.

If your site covers SEO, web design, social media, graphic design and video, you have told the system that you are moderately associated with five things and strongly associated with none. Pick the thing you want to be known for and go deep enough that the association is unmistakable.

This has a second-order benefit: depth is what produces the original material in the previous section. You cannot have a genuinely new observation about a field you cover at surface level.

Do not sand off the parts that make you specific

Most personal branding advice pushes toward a narrower, more professional, more generic presentation. I think that is usually wrong, and it is wrong for entity reasons as well as human ones.

I do SEO and content work, and I write poetry and short stories in Nepali. Those look unrelated. Conventional advice says separate them.

But the combination is precisely what makes the entity distinctive. There are many SEO specialists in Kathmandu. There are considerably fewer who also publish Nepali literature, and that intersection is unambiguous in a way that "SEO specialist" alone can never be. It also happens to be true, which matters more.

The specific things about you are not noise to be removed. They are what makes you resolvable.

A short checklist

  1. One page you own that plainly states who you are and what you do.
  2. Person schema on it, with sameAs pointing at every profile that is genuinely you.
  3. The same name, role, location and photograph everywhere.
  4. Every profile linking back to that one page.
  5. At least one piece of work that exists nowhere else.
  6. Depth in one area rather than coverage of five.
  7. No invented credentials, anywhere, ever.

Most of that is an afternoon. The fifth item is the one that takes real time, and it is the one that decides whether any of the rest matters.

You can see how I have applied this to my own site on the about page, and if you want a look at how your own entity is currently resolving, get in touch.