Owning Your Own Name in Search
If someone searches your name after a meeting, whatever they find becomes your reference check. Here is the exact stack I used to make sure they find me.
After a good meeting, people search your name. Whatever comes back is your reference check, and you do not get to be in the room for it.
My name is common. There are other Omar Badrans, and for a long time they outranked me. Fixing that was not a marketing campaign — it was about a day of unglamorous technical work plus patience.
Pick the entity you want to be
Search engines are trying to resolve an ambiguous string into a specific person. Help them. Everywhere you appear, the same descriptor should follow your name — same wording, same order, same spelling.
Mine is "Full-Stack Developer & Application Security Engineer, Alexandria, Egypt." It is on the site, in the page title, in the structured data, on GitHub, on LinkedIn, in the email signature. Consistency is what turns fifteen mentions of a common name into one recognisable entity.
If you do this in two languages, pin both forms together — Omar Badran and عمر بدران — so the two spellings resolve to one person rather than two weak entities.
Structured data is the part most people skip
This is the highest-leverage half hour available. A Person block tells a crawler explicitly what a human infers from context:
{
"@type": "Person",
"name": "Omar Badran",
"alternateName": "عمر بدران",
"jobTitle": "Full-Stack Developer & Application Security Engineer",
"disambiguatingDescription": "Full-stack developer and AppSec engineer based in Alexandria, Egypt, building secure web platforms for clients across the Middle East.",
"url": "https://omarbadran.dev/",
"sameAs": ["https://github.com/...", "https://linkedin.com/in/..."]
}Two fields matter more than the rest. sameAs links your scattered profiles into one identity graph. disambiguatingDescription exists precisely for the problem of shared names — it is your chance to say this Omar Badran, not the others.
Own the domain that is your name
omarbadran.dev outranks a profile page on someone else's platform for the same content, and it is the only address in your stack that cannot be taken away by a platform decision.
Everything else — GitHub, LinkedIn, Behance, X — becomes a satellite that points home. Same photo, same headline, same link. You are not trying to rank fifteen pages. You are trying to rank one page and make fourteen others vouch for it.
Bilingual done properly
If you serve two languages, say so in the markup rather than hoping it is inferred:
<link rel="alternate" hreflang="en" href="https://omarbadran.dev/">
<link rel="alternate" hreflang="ar" href="https://omarbadran.dev/">
<link rel="alternate" hreflang="x-default" href="https://omarbadran.dev/">Then make sure the Arabic content is genuinely Arabic — real translated copy, correct lang and dir on the document, Arabic keywords in the meta description. A language switch that only swaps a few labels does not rank for anything in that language.
Links from real work
Backlinks still decide contested names, and freelancers have an advantage here that most people forget to use: you build websites for other businesses.
A small credit in a client footer, an agreed mention on a partner page, a talk listing, a university profile, a conference bio — each is a page that already has authority pointing at your name. Ten of those beat any amount of on-page tuning, and you earned them by doing the work.
Verify, submit, then wait
Register the domain in Google Search Console and Bing Webmaster Tools, submit sitemap.xml, and check the coverage report a week later to confirm what is actually indexed rather than what you assume is.
Then wait. Name queries move slowly because the engine is cautious about swapping which entity it thinks you mean. In my case it took a few weeks before the picture changed, and a couple of months before it was stable.
Search yourself in an incognito window once a month. It is the only metric that matters here, and it takes ten seconds.
The checklist
- One descriptor, used identically everywhere
Personstructured data withsameAsanddisambiguatingDescription- Your own domain as the canonical home
hreflangplus genuinely translated content if you are bilingual- A handful of real backlinks from work you actually did
- Search Console verified and the sitemap submitted
Need this built properly?
I build secure, fast, bilingual platforms for clients across Egypt, Saudi Arabia, the UAE and Kuwait.
