The niche is clear, but nothing on the page proves it: nine of eleven Experience bullets open with a duty and not one carries a number. Those points are sitting there — rewriting text you already have recovers the most, fastest.
headline
3/5
“Product Designer at Acme” — role and company, no specialism or outcome.about
2/5
Three sentences, all responsibilities; opens with “Passionate designer…”.experience
2/5
Nine of eleven bullets start with a duty; none contain a number.skills
4/5
28 skills; the top three are relevant and endorsed by former colleagues.recommendations
3/5
Two recommendations, both more than three years old.searchability
4/5
Custom URL, location and industry all set; niche keywords present in the headline.photo_banner
— not checked
The pasted screenshots did not include the banner, so this is null, not zero. Photo is present.cadence
2/5
Four posts in the last year; the most recent was five months ago.substance
3/5
Posts share others’ articles with a line of comment; little original point of view.format
2/5
Text-only reposts; no carousels, images or opening hooks.hook
2/5
Opening lines restate the shared article’s title.commenting
1/5
Two comments in six months, both “Great post!”.reactions
2/5
Reacts a few times a month; no pattern of showing up where the niche talks.presence
1/5
Not seen in any industry thread in the window that was read.Nine of eleven bullets are duties. Turning even six into duty→outcome lines with numbers you already have is the single biggest gain — and the facts are already on the page, so this is the fastest points too.
The current three sentences describe a role. A specific, first-person About with one proof point per paragraph moves Profile from Good toward Strong.
One post a fortnight on the niche lifts Content off the floor. It ranks below the rewrites because the points arrive slowly — you have to publish for weeks before they land.
Three options — lead with the niche and the outcome, not the job title.
Option 1First person, one proof point per paragraph. Marked blanks are for numbers only you know.
Before and after, so the duty→outcome move is visible — repeat it on the roles this only sketches.
BeforeWhat makes users finish setup — and where B2B trials quietly die.
Example: “The three onboarding screens where B2B trials go to die”
Running a system a whole org actually uses, not a Figma library nobody opens.
Example: “Why our component count stopped being a bragging right”
Shipping without the spec ping-pong.
Example: “The one Figma habit that ended handoff back-and-forth”