Making my portfolio Google-ready

I bought wendeson.com.br this week and spent the afternoon setting up everything that usually gets postponed: DNS zone, redirects, canonical, structured data. I documented every step, because this is exactly the kind of work that quietly falls off the priority list until it becomes a problem.

The first real problem: I had three different URLs serving the same homepage — the new domain, the www version, and the old wendeson.vercel.app. To Google, that reads as three pages competing for the same authority, splitting backlinks and ranking signals that should all live in one place.

The fix wasn't picking the “right” URL. It was making every other one point to it, with a permanent redirect.

Next came JSON-LD. A block of structured data helps Google understand the page represents an actual person, not just loose text:

Two obvious things were still missing, and I'd never stopped to add them: robots.txt and sitemap.xml. In Next.js that's a few lines each (app/robots.ts and app/sitemap.ts), and without them Google is guessing what exists on the site instead of knowing.

Result after running PageSpeed Insights on mobile: 97 performance, 100 accessibility, best practices and SEO. None of these numbers prove Google will find me — only that once it does, it won't have a reason to ignore me.

// layout.tsx
const personJsonLd = {
  "@type": "Person",
  name: "Wendeson Gomes",
  jobTitle: "Frontend Engineer",
  url: "https://www.wendeson.com.br",
};