Information ArchitectureTYPENORMLabs5 minSeptember 11, 2026

Reuters UX Teardown: A Search That Sorts Like a Wire

A UX teardown of Reuters' signed-out read flow: dependable section fronts, an article page that gives the reader its figures early, and a search that ranks 14,934 matches by the clock, then leaves a Business story at the top of a Technology filter.

Search Reuters for artificial intelligence and the first of 14,934 matches is a story about state elections in Saxony-Anhalt. It is an hour old. Nothing has malfunctioned. The control above the list reads Sort by: Newest, and at that moment the German far right was the newest thing moving on the wire. Reuters ranks its search the way a wire has always ranked copy: by when it arrived.

This teardown draws on six signed-out states shot at 1440×900 on 7 September 2026, viewed from Brazil: the Technology front, a lead story, that story's summary and opening paragraphs, an unfiltered search, the same search narrowed to Technology, and the World front.

1 / 6

Technology front page

A single image-led story dominates the first editorial row, while smaller headlines remain visible below for fast scanning and comparison.

View full flow (6 screens)

The section front is one template

Technology and World are the same page with different copy in it. An oversized section word. A lead story on the left carrying a headline, a two-sentence deck and a relative timestamp, set against a dominant photograph on the right. Three supporting headlines starting at the fold. The masthead above them holds the same nine beats, the same My News, the same search, the same Sign In and Register pair, in the same order, at the same size.

Learn one beat and you have learned the rest. That is consistency and standards earning its keep, and doing it cheaply enough that a newsroom can run dozens of sections without designing dozens of pages.

The persistence holds under scroll. Move down into a story and the black LSEG strip and the navigation stay pinned to the top of the window. The advertising above them does not come along.

What the article page hands over early

Summary and story body
Summary and story bodyA four-point summary compresses the report before the opening paragraphs, while linked company tickers offer a direct route into market context.

The byline carries two timestamps: September 7, 2026 4:20 AM GMT-3 · Updated 8 hours ago. The absolute one is rendered in the reader's own offset, so nobody has to do the arithmetic. The relative one answers the question a reader actually has, which is whether this is still current. Three controls sit beside it: save, an Aa text-size toggle, share. They are attached to the article they act on. No floating rail.

Above the body sits a tabbed module, Summary selected by default with Companies next to it, holding four bullets: the new foldable series is priced from $2,980, it ships with a new in-house chip, Xiaomi has launched a foldable of its own, and Apple launches on Wednesday. Those are the figures the story is about, and they arrive before the story asks for any reading time. The opening paragraphs then run in full. Companies named in them are linked out by ticker, 1810.HK and AAPL.O, for a reader who came for the market.

The newsletter pitch waits until after those paragraphs, then appears inline, set off by a red rule, in the flow of the page. Nothing in this capture covered the headline or cut the body short, which is not a given for a signed-out news page. The Post runs its subscription card over the story's own display type.

The search sorts by the clock

The results page is well built for scanning. The query stays editable in its field above the heading. The count is stated plainly. Every card prints its section and its age above its headline, World · 1 hour ago, Business · 12 hours ago, so a reader can judge a result's information scent without opening it. Section and date-range controls hold a stable left rail.

What the page does not offer is another way to order the list. Newest is the default, and in the collapsed control it is the only option on show. Order 14,934 matches by arrival time and the top of the list answers a different question from the one typed into the box: it reports what happened most recently among stories that mention the phrase.

The Saxony-Anhalt result makes the point. A minute later, the World front led with a story from the same hour on the same subject. So the first slot went to whatever crossed the wire last. Relevance never entered into it. That slot is where a searcher looks first.

Reuters says as much itself. Directly under the filters sits a paragraph in its own words: We are continually enhancing our website, including our search experience. We welcome feedback which you can provide using the feedback tab on the right of the page. The tab it refers to is genuinely there, pinned to the right edge on every state we captured.

The Technology filter and the Business card

Technology filter applied
Technology filter appliedThe applied section stays visible and the count drops to 7,907, yet the first card is still labeled Business — a visible mismatch between filter promise and results.

Applying the Technology section does visible work. The count drops from 14,934 to 7,907, the Section select reads Technology, the URL gains &section=technology, and the surrounding layout holds still. Three surfaces, three confirmations of visibility of system status, with nothing left for the reader to infer.

Then the first card reads Business · 12 hours ago.

A capture cannot tell you why. The story is OpenAI's incident report to the European Commission, and it may carry more than one section internally, with the card showing a primary label the filter never matched on. What a capture can tell you is what a reader sees: a control labelled Technology, and immediately beneath it a result labelled Business. The filter and the card disagree in public, and they disagree in the one position the reader is most likely to read. This is the gap between the system's model and the reader's, sitting in the first row of results.

The honesty of the cards is what makes it visible. A results list that printed no category would have hidden this completely. The ordering compounds it: the sort stays on Newest after filtering, so narrowing the pool removes some of what sat above the good matches without ever lifting them.

The ad band above the masthead

Every one of the six states opens on an advertisement positioned above the Reuters masthead: two EY units, a video unit, a Hulu and Disney+ banner also duplicated into the right rail, and a Brazilian property ad. On the Technology front, that band plus the LSEG strip plus the navigation push the first editorial headline just past the halfway line of a 900-pixel window.

Ad load varies by session and by region. This capture ran from Brazil and drew fares in reais, Portuguese copy and one unit with an Arabic call to action. The slot itself is fixed. It sits above the brand.

What this means for your product

Filter feedback is not result feedback. Here the count, the select and the URL all updated correctly the moment Technology was applied. A team watching state-change telemetry would see a filter working perfectly, and the top result would still be labelled Business. The check that catches this isn't instrumented and can't be: somebody reads the first three results after applying each filter and confirms they are what the label promised. It takes a minute per filter. Skip it and no dashboard you own will ever show you this.

The sort control is the cheaper fix, and Reuters is halfway to it already. The page says Newest, in plain language, directly above the first card. What is missing is a second option, because recency-only is a strong opinion to hold about every query a reader will ever type.

Take it further

The lens behind this teardown is the UX Clarity framework, the same one we apply in a Full UX Audit. It asks one thing of an interface: can a reader tell what they are being shown, and why it arrived in that order? For how that scoring turns into prioritized fixes, read what a real UX audit looks like.

Scope and limits: six public pages, signed out, one viewport, one session on 7 September 2026, requested from Brazil. Nothing was submitted, so no account was created, no sign-in, no newsletter, no share, no purchase, and no advertisement was opened. Live journalism moves, so the headlines, the 14,934 and 7,907 counts, the relative dates and every ad unit named here belong to that hour and that region. The capture covered the product flow only; the homepage landing sat outside it.

Sources: NN/g — Consistency and Standards · NN/g — Information Scent · NN/g — Visibility of System Status · NN/g — Match Between System and Real World · NN/g — Filters vs. Facets.

Ready to find out whether your filters are telling your users the truth? Apply for a Full UX Audit →

Free UX Snapshot for 50 Product Teams

Apply now and get a complimentary UX Snapshot — our rapid clarity audit delivered in 48 hours. Limited to the first 50 products.

Apply for Free UX Snapshot

Related

Interaction Design

TechCrunch UX Teardown: The Reading Mode That Drops the Date

A UX teardown of TechCrunch's read flow: one switch turns the feed into a dense scan queue and carries the preference into the next section — then removes the timestamp and the content type the returning reader came for.

TYPENORMLabs · 5 min · September 10, 2026

Web
Media & Entertainment
Interaction Design

UX Writing

Sentence Case vs Title Case in UI: What the Major Design Systems Actually Do

Sentence case has become the default across Microsoft, GOV.UK and Material 3, while Apple still capitalises its buttons. A look at what each convention specifies, why title case is expensive to enforce, and how to write the rule so a team stops re-deciding it.

TYPENORMLabs · 7 min · September 10, 2026

UX Writing
Web

Information Architecture

Mobbin UX Teardown: The Answer Is Always One Click Down

A UX teardown of Mobbin's signed-out browse flow: a platform switcher that leaves the model alone, a topic that gets three names in three hops, and a flow gallery that hides the one annotation worth paying for.

TYPENORMLabs · 7 min · September 14, 2026

Web
SaaS
Information Architecture