Making my portfolio findable: an SEO pass on my own site
Service pages, structured data, a hero that paints before JavaScript, and why my projects stopped being 'the squad'. How I made my portfolio findable.
I rebuilt this site a few weeks ago and I was proud of it. A player card you can flip, a Lagos clock, a Barça mode. Then I searched for "Next.js developer in Nigeria" and it was nowhere.
That's not surprising once you think about how search works. Google does three jobs: it finds pages, understands them, and ranks them for a search. My site was strong on personality and weak on all three. There was no page about the things people search for, nothing machine-readable said what I offer, and nothing told search engines when a page changed.
So I spent some time doing the boring work properly. Here's what moved, and what I learned doing it.
1. Google ranks pages, not people
If someone searches "TypeScript developer in Nigeria" and you don't have a page about TypeScript development, you can't rank for it. It doesn't matter how good your home page is.
So the site now has a page for each thing I actually do: Next.js, Node.js, backend engineering, TypeScript, React, full-stack, performance and SEO, e-commerce and fintech. Each one has its own intro, proof from real work, related projects and FAQs.
They're all driven by one typed data file and one template:
export type Service = {
slug: string;
/** The search phrase: used in the title, URL and H1 kicker. */
keyword: string;
/** What visitors see in lists and cards. */
label: string;
intro: string[];
proof: string[];
faqs: { q: string; a: string }[];
// ...
};Adding a service is adding an object, not building a page.
What I didn't do is create fifty near-identical pages ("Next.js developer Lagos", "...Abuja", "...Port Harcourt"). Google calls those doorway pages and treats them as spam. Nine pages with real, different content beats fifty copies.
2. Keywords are for robots, labels are for people
My first version used the search phrase everywhere. The services list on the home page read "Next.js developer in Nigeria, Node.js developer in Nigeria, TypeScript developer in Nigeria..." It looked exactly like what it was: someone trying to rank.
Here's the thing: repeating a phrase in visible text doesn't help. Google reads the <title>, the URL, the main heading and the meta description. So I split the two jobs. That's what keyword and label are for:
- Title, URL, meta description and breadcrumbs: "Next.js developer in Nigeria"
- A small line above the page's main heading: the same phrase, said once
- Every list, card and link people read: "Next.js development"
Search engines get the signal, and people get plain English.
3. Structured data: the barcode on the box
Structured data (JSON-LD) is a hidden block of JSON that states facts in a shared vocabulary, schema.org. People read the label on a product; the scanner reads the barcode. This is the barcode.
Every page now describes me as a Person and a ProfessionalService serving Nigeria and remote clients worldwide. Service pages add a Service and an FAQPage, and inner pages add breadcrumbs. Everything links together by @id, so search engines see one connected profile instead of scattered fragments.
One small detail that matters more than it looks:
/** Escape "<" so JSON-LD can never close its own <script> tag. */
export const jsonLd = (data: unknown) => ({
__html: JSON.stringify(data).replace(/</g, "\\u003c"),
});Without that, a description containing </script> would end the tag early and inject HTML into the page. The data is mine today, but escaping costs nothing and it's one less thing to think about later.
4. A bug no tool could see
Some headings on this site are built from separate spans so each line can be styled:
<span className="block">Lagos-built.</span>
<span className="block">World-shipped.</span>On screen it looks perfect, because each span sits on its own line. But the text a crawler reads is Lagos-built.World-shipped., a single word that doesn't exist. TypeScript is happy, the build passes, and the browser looks right. You only see it by reading the raw text. The fix is one explicit space:
<span className="block">Lagos-built.</span>{" "}
<span className="block">World-shipped.</span>5. Speed is a ranking signal, and my hero was slow
The hero slider faded in when the page loaded. That sounds harmless, but it meant the biggest thing on the screen stayed invisible until JavaScript had downloaded and React had started up. On a mid-range phone on mobile data, that's a long time to look at nothing. The time until the main content appears is called Largest Contentful Paint, and Google measures it.
Three changes fixed it:
- The first slide renders fully visible in the server HTML. Motion's
initial={false}skips the entrance animation on first load. - Slides two and three only mount after the first paint. The phone doesn't download or render what you can't see yet.
- The progress bar is driven by a ref instead of React state. Before, it re-rendered the whole hero sixty times a second just to move a thin line.
Mobile Lighthouse, with throttling on, now scores 99, with LCP at 1.7 seconds.
6. Helping search engines find pages
The last job is discovery:
- Sitemap and robots.txt. The sitemap lists every service page, and robots.txt keeps crawlers out of the API, sign-in routes and the moderation page.
- IndexNow. Every production build sends the fresh sitemap to Bing and other search engines, so they hear about new pages right away instead of waiting to come back on their own.
- llms.txt. More people now ask ChatGPT or Perplexity to "find me a Next.js developer". So there's a plain-text summary of who I am and what I do at /llms.txt, generated from the same data as the site so it never goes stale.
7. Writing for the people who hire you
The last change wasn't technical. My projects were "the squad", the contact form was a "transfer bid", and testimonials were "post-match interviews". I loved it. But a founder in London deciding whether to trust me with their product shouldn't have to decode football terms to find my work.
So the squad is now Projects, the transfer form is now Hire, and the copy speaks to clients first. The old URLs redirect permanently (a 308), so every link I've ever shared still works and search engines carry the old pages' ranking over to the new ones:
async redirects() {
return [
{ source: "/squad", destination: "/projects", permanent: true },
{ source: "/transfer", destination: "/hire", permanent: true },
];
},The personality is still here, just in the right places: the player card, the Barça slide, a penalty shootout on the 404 page. Matchday mode only takes over for people who've opted into Lagos time.
What's left
- Code is about a third of SEO. The rest is submitting the sitemap to Google Search Console and Bing Webmaster Tools, getting links from other sites, and writing things like this post.
- New pages take weeks to show up in search. Rankings for competitive phrases usually take a couple of months to settle.
I'll write a follow-up with real Search Console numbers once there's something worth reporting.
If you're building something and need it to be fast and findable, let's talk.