Why Every Product Person Needs a Personal Website in 2026

If you work in product, you should have a personal website in 2026, and not as an online resume. Build it as the one product you own end to end. It's the cheapest go-to-market playground you'll ever get: you set the positioning, write the landing page, choose the channels, define the conversion goal, and read the analytics, with no sales team or brand guidelines in the way.

There's a second reason, and it's about timing. The web now mostly answers questions instead of sending people to sources. When someone checks you out, a site that clearly says who you are and what you've shipped is the source you control.

Why 2026 changes the math

Three shifts make owning your source more valuable than it was five years ago.

AI answers are replacing clicks. Ahrefs analysed 300,000 keywords and found that by December 2025, AI Overviews cut the click-through rate of the top-ranking page by about 58%. In Pew's browsing study, users clicked a regular result in 8% of visits when an AI summary appeared, versus 15% without one.

There's a nuance most posts miss. The same Pew study found that only 8% of one- or two-word searches triggered an AI summary. A Google search for your name is usually short, so it still mostly returns plain links. The bigger change is that people now ask chatbots. OpenAI said in July 2026 that its products had passed 1 billion active users. "What has this person built?" is increasingly a prompt, not a search, and the answer is put together from whatever material about you the model can find.

Feeds are rented reach. Richard van der Blom's analysis of more than 1.8 million LinkedIn posts found that views fell about 47% and engagement about 39% in 2025. LinkedIn is still where product people find each other, but the platform sets the distribution rules and can change them any quarter.

Real authorship is becoming a ranking signal. In October 2026, Google updated its people-first content guidance to call fabricated author profiles deception, citing AI headshots, invented names, and false credentials, and said it treats them as a sign of a low-quality page. As AI-generated content floods the web, a verifiable person with a track record is worth more.

My inference from all three: when fewer people click through, the quality of your source page matters more, because the summary is only as good as what it was built from. I haven't seen a study that measures this for personal sites, so treat it as reasoning, not a finding.

Your website as a GTM playground

Most PMs see one slice of go-to-market. Marketing owns the top of the funnel, sales owns the close, and you see a dashboard in the weekly review. A personal site gives you the whole loop on a small scale, with real people on the other end.

GTM stage	On your site	What you'll learn
Positioning	One line: what you do, for whom	Whether strangers get it in five seconds
Messaging	Homepage and case-study copy	Which framing of your work actually lands
Distribution	LinkedIn, X, newsletters, communities, AI answers	Which channel sends people who stay
Conversion	One goal: booked calls, subscribers, inbound leads	How small copy changes affect intent
Measurement	Analytics, events, UTM tags	How little vanity metrics tell you
Iteration	A monthly change log	Whether you can ship small and often

Positioning: write the one-liner and test it

"Senior PM, passionate about AI" doesn't position you. "I help B2B teams turn AI pilots into shipped features" does. Write three versions and show each to five people outside your company. Ask them what they think you do. Whichever version they repeat back most accurately wins. That's a positioning test, the kind you'd run for a product, done on yourself.

Distribution: find your real channel

Tag every link you share with UTM parameters and watch which channel brings people who read past the homepage. You'll probably find that the channel with the most likes isn't the one sending your best visitors. Seeing that first-hand is worth more than reading about it.

Conversion: pick one goal and stick to it

A site with five calls to action doesn't have a conversion goal. Pick the one that matters this quarter, whether that's consulting calls, newsletter sign-ups, or recruiter messages, and make it the obvious next step on every page. Track it monthly.

The AEO lab: see how machines describe you

This is the experiment most relevant for product people building AI features. Once a month, ask ChatGPT, Claude, Gemini, and Perplexity the same question: "Who is [your name] and what have they built?" Log the answers in a spreadsheet. Then change your site: sharpen the bio, add structured case studies, fix inconsistent job titles across profiles. Watch whether the answers change over the following months.

You'll learn a lot about retrieval, citation, and how models handle ambiguity, which is exactly what you need to know if you ship AI products. You'll also be honest with yourself about how slow and noisy that feedback loop is.

One thing not to over-invest in: llms.txt. It's a community proposal from Jeremy Howard, not a ratified standard, and a May 2026 review found it does not measurably improve your odds of being cited by the major assistants. Add one if you're curious, then spend your time on clean, indexable pages with specific content.

Know the limits of the lab

Be honest about what this playground can't do:

• No real A/B testing. A personal site rarely gets enough traffic for statistically significant results. Treat changes as directional, and pair your analytics with conversations.
• You're not your users. A site about you has a vain and biased product owner. Get outside eyes on positioning, or you'll end up optimising for your own taste.
• It costs time. Plan for a weekend to launch and an hour a month to maintain. If you can't commit to that hour, ship a single static page and leave it alone. A neglected blog does more harm than a small page that's kept current.

It's also the best proof that you ship

Product hiring has always had a credibility gap: the resume says you shipped, but the interviewer can't see it. A personal site closes that gap. Positioning, copy, analytics, a change log, maybe a teardown of what didn't work: together, that's evidence of product judgment that a resume can only claim.

For consultants and founders it does the same job for clients. The site becomes where a LinkedIn post, a talk, or a chatbot answer sends people to make up their minds.

Ship the MVP this weekend

Treat it like any product launch: smallest useful version first, then iterate.

1. Register a domain in your own name. It's the one thing worth paying for, and it keeps you off rented land.
2. Write the positioning line. Use the test above.
3. Add a short third-person bio that a host, an organiser, or an AI system could copy as is.
4. Write three to five case studies: the problem, what you did, and the outcome, with numbers where you're allowed to share them.
5. Choose one call to action and put it on every page.
6. Set up privacy-friendly analytics and UTM conventions before you share the link anywhere.
7. Keep a public change log. It forces you to iterate, and it shows you do.

Host it on a static platform with a free tier, and link to it from every profile you have.

Who can skip this

If your career runs entirely through internal networks and you have no plans to move, this is lower priority. Privacy is a valid reason to skip too. But if you consult, freelance, found companies, change jobs every few years, or ship AI products, your site is part of your go-to-market whether you build it or not. The only question is who writes it: you, or a summary of whatever the internet has on you.

The takeaway

Product people talk about owning the outcome. A personal website is the rare place you can own all of it: positioning, channel, conversion, and how the machines describe you. Set a 90-day goal for it this week, the way you would for any product, and review the numbers every month.