Five discoverable problems. Two can damage an active process before you get a chance to speak. Ordered by exposure risk.
Read the first section, fix the first two items today. Everything else can wait until this week.
P0 — Fix today
1. The private essay is publicly served
What it shows: /what-do-you-count returns the complete document to any visitor. No authentication. The full TinyFish pricing and commercial strategy content loads before the client-side password overlay renders. The homepage links directly to it with a teaser.
Why this costs you: Any recruiter who clicks the homepage link reads internal commercial strategy from your current employer. A crawler that indexes it surfaces TinyFish pricing language in search results tied to your name. I flagged this in the last issue. Still live. The localStorage gate makes it worse than having no gate: it looks like you tried to protect it and didn't know how.
Fix action:
- Add server-side authentication or redirect unauthenticated requests to a 401/403. If your hosting platform doesn't support per-page auth, replace the file content with a redirect to the homepage.
- Remove the homepage link and teaser.
- Add
<meta name="robots" content="noindex, nofollow">to the page head as a secondary measure. - Create a
robots.txtfile (currently returns 404) with a disallow rule for/what-do-you-count. - Check the Wayback Machine (
web.archive.org) for cached copies. The page has been publicly served with no robots.txt for at least five weeks — archival crawlers may have captured it. If a copy exists, submit a removal request through archive.org's exclusion process. Removal takes days, not hours. The realistic discovery path for a recruiter runs through Google and your homepage, not the Internet Archive. But a hiring manager with a competitive-intelligence habit could find it, and the content is sensitive enough to warrant the removal request.
Verification: Incognito window. Navigate to junochen.com/what-do-you-count and junochen.com/what-do-you-count.html (the .html version 308-redirects to the clean URL; test both). You should see a 401, 403, or redirect. Confirm the homepage no longer links to it. After the fix, use Google's URL removal tool to clear any cached version from search results.
If someone already read it:
"That's a private piece about pricing strategy at my current company — it shouldn't have been publicly accessible, and I've fixed that. If the thinking behind it is relevant to what you're evaluating, I'm happy to walk through it live."
Confidence: High. Factual, brief, and the offer to walk through it converts the exposure into an invitation.
2. UAT Sentinel is listed but outside the approved portfolio boundary
What it shows: The homepage reads "Four live agents built solo" and lists Carrier IQ, UAT Sentinel, Retail Velocity, and Brand Pulse. The published portfolio approves three for external use. UAT Sentinel is explicitly excluded.
Why this costs you: A recruiter clicks through. Later, in a portfolio review, you can't speak to it in depth. That gap between what the portfolio promises and what you can deliver in conversation creates a credibility question — and the question won't stay contained to UAT Sentinel. They'll wonder what else on the site is soft.
Fix action: Remove UAT Sentinel from the homepage. Change the count to three or drop the count entirely. If UAT Sentinel is ready for external scrutiny, formally revise the portfolio boundary to include it. Make that decision deliberately, not by accident of what's currently deployed.
Verification: Load the homepage. UAT Sentinel should not appear in the agent list or be linked anywhere on the site.
If someone already saw it:
"I've built more agents than I show publicly — UAT Sentinel is one I pulled from the portfolio because the client engagement is still active. The three that are up represent the range I can speak to freely."
Confidence: High. Selectivity framed as professional judgment, which is what it is.
P1 — Fix this week
3. Google may still be serving "Product Designer" as your site title
What the research shows: The live homepage title reads "Design Leadership for High-Stakes Systems." But public crawler retrievals disagree with each other: one index shows the updated title, another still returns "Juno Chen — Product Designer" from a copy crawled roughly two months ago. Google's own indexed version can't be confirmed without Search Console access.
Why this costs you: A recruiter Googles your name before visiting the site. If the search result snippet says "Product Designer," that label writes the first theory before the portfolio opens. By the time they see the leadership-forward homepage, they're reconciling it against a title that already told them something different. The species assignment started in the search result.
Fix action:
- Log into Google Search Console. Run a URL Inspection on
https://junochen.com/. Compare the "Google Index" tab (what Google currently serves) against the "Live Test" tab (what Google sees now). If the indexed version still says "Product Designer," request re-indexing. - Re-indexing can take up to two weeks. Check back in 3–5 days.
- While you're in Search Console, inspect
/what-do-you-countand request removal if it's indexed.
Verification: Search site:junochen.com in Google. The result title should read "Juno Chen — Design Leadership for High-Stakes Systems." If it still shows the old title after requesting re-indexing, use the Removals tool to temporarily suppress the old cached version while the new one propagates.
If a recruiter mentions seeing "Product Designer":
"I updated the site a few weeks ago — Google's cache can lag. The current version reflects where I am now, which is design leadership for high-consequence systems."
Confidence: High. Brief, factual, redirects to the current positioning without dwelling on the old one.
4. LinkedIn cross-reference contradicts the portfolio positioning
What it shows: Signed-out LinkedIn displays "Juno Chen - TinyFish | LinkedIn" with a description about "human-AI collaboration in enterprise web automation." The headline and role titles are masked from signed-out visitors. Third-party directories list the TinyFish role as "Head of Product, Platform & Developer Experience" — accurate, but product-led.
Two gaps:
- No visible design-leadership signal in the public LinkedIn surface. A recruiter checking LinkedIn before or after visiting the portfolio finds a product identity.
- The Alibaba title may not match the portfolio's "Head of Design and Research, North America." Third-party directories show it without the "North America" qualifier. The signed-in version hasn't been verified.
Why this costs you: Recruiters cross-reference. If the portfolio says design leadership and LinkedIn says product leadership, the recruiter decides which one is real. They'll usually go with LinkedIn because it's the platform they trust for employment history. The mismatch doesn't disqualify you, but it introduces a question you'd rather not have in the room.
The signed-out surface is what I can verify and what a recruiter sees first. The signed-in headline and experience titles are masked from my view; those are checks only you can run.
Fix action:
- Update your LinkedIn headline to lead with design leadership language. Something like "Head of Design | Enterprise Platforms & AI-Native Systems" — whatever is accurate and aligns with the portfolio.
- Check the TinyFish experience entry. If it says "Head of Product, Platform & Developer Experience," you probably can't change the title if that's the title. But make sure the role description emphasizes design leadership scope.
- Verify the Alibaba entry reads "Head of Design and Research, North America" to match the portfolio.
- Confirm no entry anywhere on the profile says "Product Designer."
Verification: Sign out of LinkedIn. Search your name. Read what appears. Sign back in and review every experience entry title against the portfolio.
No verbal fallback needed here. This is a silent fix. If someone asks about the product-vs-design framing at TinyFish, that's a positioning conversation, not an artifact problem.
P2 — Fix when P0 and P1 are done
5. No social preview image; platform caches unverified
What it shows: The homepage serves correct OG and Twitter Card text metadata — title and description both say "Design Leadership for High-Stakes Systems." But there is no og:image or twitter:image tag. When someone pastes your URL into LinkedIn, Slack, or a message thread, the platform decides what image to show, or shows nothing.
Why it costs you: A link preview without an image looks unfinished. Without an explicit image tag, you can't control what platforms cache. If an older version of the site had an image that platforms stored, that cached image may still appear even though the text metadata is current. LinkedIn's preview cache couldn't be verified through the Post Inspector from a signed-out session, so the current state is unknown.
Fix action:
- Add
og:imageandtwitter:imagetags pointing to a designed preview card — your name, the leadership-forward title, clean. Size at 1200x630px for broad platform compatibility. - After deploying, use LinkedIn's Post Inspector (signed in) to force a cache refresh. Paste your URL, inspect, confirm the new image and text appear.
- Do the same with Twitter's Card Validator if you share links on X.
Verification: Paste https://junochen.com/ into a new LinkedIn post draft (don't publish). The preview should show your designed image card with the correct title. Repeat in Slack and any messaging platform where you share links with contacts in hiring processes.
No verbal fallback needed.
Sequence
Two hours today: Fix the essay (server-side protection + remove homepage link + check archive.org), remove UAT Sentinel from the homepage, deploy both.
Thirty minutes tomorrow morning: Log into Search Console and request re-indexing.
LinkedIn and the preview image are this-week tasks. They matter, but they won't blow up an active conversation the way a publicly served pricing document will.
If the artifact is something you control, change the artifact. The verbal fallbacks cover the gap between when someone might have already seen the broken version and when the fix propagates.
- Google's actual indexed state: The only way to confirm whether Google is still serving "Product Designer" is an owner-run URL Inspection in Search Console, which compares the indexed copy against a live test and shows the crawl date.
- LinkedIn's signed-in profile fields: Third-party directories like The Org list the TinyFish title as "Head of Product", but the exact headline and experience titles visible to signed-in recruiters can only be verified from inside your account.
- Wayback Machine exposure window: The essay has been publicly served without a robots.txt for weeks, and archive.org's exclusion process takes days to execute once a removal request is submitted — check whether a cached copy exists before assuming the server-side fix closes the gap.
- Platform preview caches after fix: LinkedIn's Post Inspector requires a signed-in session to return URL-specific results, so confirming that your corrected OG metadata has propagated to LinkedIn, Slack, and X previews is a post-deploy verification step you'll need to run yourself.