LinkedIn navigation test reorganizes menus and previews

The LinkedIn navigation test groups existing tools into fewer menu entries across desktop and mobile. A separate feed change also exposes more text before readers expand a post. Both should be understood in the context of gradual testing, with interface differences possible by region and language.

Where are LinkedIn's tools moving?

The reported desktop design puts analytics, saved posts and settings under Profile. A More menu brings together games, news, groups, events, newsletters and video. A tool that appears absent from its former position may therefore have moved rather than been removed.

Social Media Today described the changes on October 27, 2026. Mobile users may also encounter consolidated navigation in the lower function bar. LinkedIn said the experience would be tested gradually and could vary across languages and regions, so a screenshot from one account is not a reliable universal instruction for every colleague or client.

Area	Change described in the report
Profile on desktop	Access to analytics, saved posts and settings
More on desktop	Access to games, news, groups, events, newsletters and video
Mobile navigation	Consolidated entries in the lower function bar
Feed text	Longer excerpts before a reader expands the post

Do longer previews guarantee more engagement?

No measured improvement is established by the article. Showing additional text may give a reader more context, but that is a possible benefit rather than a reported lift in click-through or reading time.

The change also raises a practical question for posts built around repeated line breaks and a withheld conclusion. If readers see more of the argument immediately, the artificial boundary used to create curiosity may move. The report does not provide a single preview character limit for all posts, nor does it announce a new ranking formula. Publishers should avoid turning an interface observation into a claim about guaranteed distribution.

Takeaways for marketers

Write an opening that communicates a useful point even if the reader never expands the post. A B2B case example can state the operational problem and the resulting change before introducing supporting detail. This is an editorial recommendation, not a performance result from the test. It puts the part a publisher can control, the clarity of the argument, ahead of guessing exactly where a preview will end.

For team documentation, record the name of the destination as well as its menu location. That makes instructions usable when teammates encounter different test versions. When reviewing post results, note the publication period and visible interface state without attributing every change to navigation: subject matter, audience and creative can also differ. Our Services page outlines support for channel planning and content operations where publishing routines need to stay usable as platforms change.