A page can rank well and bring in nothing. Visitors land, don't find their answer on the first screen, and leave. SXO (Search Experience Optimization) starts from that problem: work on search, user experience and conversion on the same page, at the same time.
In this article, we separate what Google actually says about user experience from what gets repeated without a source, then share the checklist for a Webflow page that needs to rank, read well and convert.
Originally published in 2022, fully updated on October 6, 2026.
What is SXO?
SXO, short for Search Experience Optimization, means optimizing a page across the whole search journey: before the click (being found, earning the click), during the visit (understanding quickly, reading comfortably on mobile) and at the end (taking the next step). It brings together three disciplines that often work in silos: SEO, UX design and conversion rate optimization (CRO).
It's an industry term. Google's own documentation talks about page experience and helpful, reliable, people-first content, two ideas that overlap heavily with SXO.
SXO vs SEO: what changes
| SEO | SXO | |
|---|---|---|
| Starting question | Which queries does the page rank for? | What does the person typing this query want, and what should they do next? |
| What you work on | Keywords, markup, technical setup, links | The same, plus the first screen, mobile readability, perceived speed, the path to action |
| What you measure | Impressions, rankings, clicks | The same, plus engagement and conversions by landing page |
| Who's involved | SEO, content | SEO, content, design, development, marketing |
SXO doesn't replace SEO. Without indexing, clean markup and content that answers the query, there's no visitor to convert. SXO adds one question to every decision: does this help the person who lands on the page?
What Google actually says about user experience in 2026
Plenty of SXO articles claim that "Google rewards user experience" without saying how. Google Search Central's documentation is more precise, and more nuanced.
There is no single signal
On its page experience documentation (updated September 22, 2026), Google writes: "There is no single signal. Our core ranking systems look at a variety of signals that align with overall page experience" (Google Search Central). In other words, there's no single page experience score that pushes a page up or down.
The same page sets an important limit: Google always tries to show the most relevant content, even if the page experience is sub-par. Good page experience makes the difference when several pages answer the query equally well. It won't rescue an off-topic page.
Google lists six self-assessment questions: good Core Web Vitals, pages served over HTTPS, content that displays well on mobile, no excessive ads, no intrusive interstitials, and main content that's easy to tell apart from the rest.
Core Web Vitals count, with precise thresholds
Google says Core Web Vitals are used by its ranking systems, while noting that good scores don't guarantee a top ranking (Google Search Central).
| Metric | What it measures | Good |
|---|---|---|
| LCP (Largest Contentful Paint) | how long the largest visible element takes to render | 2.5 s or less |
| INP (Interaction to Next Paint) | how quickly the page responds to a click, tap or key press | 200 ms or less |
| CLS (Cumulative Layout Shift) | how much the layout shifts while loading | 0.1 or less |
These thresholds are assessed at the 75th percentile of page loads, separately for mobile and desktop (web.dev). INP replaced FID as a Core Web Vital on March 12, 2024 (web.dev). If a guide still talks about FID, it's out of date.
And mobile is what counts: Google crawls and indexes sites using their mobile version (Google Search Central).
Helpful content is part of core ranking
The helpful content system, launched in 2022, became part of Google's core ranking systems in March 2024 (Google Search Central). There's no separate "helpful content update" to wait for anymore: whether a piece was written to help someone or to attract traffic is assessed continuously. Google spells out its criteria in its guide to creating helpful, reliable, people-first content.
What we removed from this article
You'll often read that time on page or bounce rate affect rankings. The Google pages cited here don't mention them, so we don't build a strategy on them: these metrics help you understand a page, not rank it. Same goes for promises like "SXO multiplies your conversions by 2 to 4": we couldn't find any original study behind those numbers, so we don't repeat them.
Start from search intent
SXO starts before the page: you need to know what the person typing the query wants. Four questions usually cover it.
- What are they looking for? A definition, a comparison, a price, a provider. Look at Google's top results for the query: their format (guide, list, service page, tool) tells you what Google considers useful.
- What do they already know? "sxo" on its own and "sxo vs seo" don't call for the same page: the second assumes the reader already knows SEO.
- What must they see on the first screen? The short answer, or at least a clear signal they're in the right place.
- What's the next step? Reading a case study, comparing offers, requesting a quote. A page with no next step loses the visitor it worked to win.
When a query mixes several intents, pick the one that matches the page's goal and link to another page for the rest, rather than covering everything in one place.
Writing SXO content
Content built for SXO can be skimmed without losing the thread. Good practices to apply:
- The main answer comes in the first lines, before the context.
- H2 and H3 headings say what the section contains: someone who only reads the headings should understand the page.
- One paragraph, one idea. Comparisons go in a table.
- Figures are dated and linked to their source.
- Visuals explain something (a diagram, an annotated screenshot) instead of decorating.
- The call to action matches the next step of the intent, not just the business goal.
These rules also help with visibility in AI search: a clear passage that answers a question on its own is easier to reuse in a generated answer.
The SXO checklist for a Webflow page
The table follows the order of a visit, from the search result to the action, and shows where to run each check in Webflow.
| Stage | What to check | Where, in Webflow or elsewhere |
|---|---|---|
| Search result | The title and meta description reflect the intent and give a reason to click | Page settings for a static page, the collection's SEO fields for CMS pages |
| First screen | The H1 answers the query, one sentence says what the page offers, the main action is visible without scrolling on mobile | Designer, mobile view |
| Structure | One H1, descriptive H2s, no skipped heading levels | Navigator panel, tag setting on Heading elements |
| Main image | Eager loading (not Lazy), WebP, known width and height to avoid layout shifts | Image element settings, Assets panel |
| Core Web Vitals | LCP, INP and CLS in the green on mobile | Search Console Core Web Vitals report, PageSpeed Insights |
| Scripts | Every third-party script (chat, tracking, embeds) has a reason to be there; unused ones are removed | Site and page Custom code, Embed elements |
| Mobile | Buttons and links large and spaced enough for a finger, no cut-off text, no horizontal scroll | Designer mobile view, then a real phone |
| Interstitials | No pop-up hiding the main content on arrival | Page interactions and pop-ups |
| Action | One primary call to action per page, a form reduced to the fields you need | Designer, form settings |
| Measurement | A form submission fires a single key event in GA4, and you can tie it to the landing page | GA4, Tag Manager |
The main image
It often determines LCP. Lazy-loading it delays the first screen. The sizes and formats to use are in our guide to website image sizes and formats.
Scripts
INP depends mostly on the JavaScript running on the page. On a Webflow site, slowdowns rarely come from Webflow itself and more often from tools added over time. We cover the method in how to improve website loading speed.
Touch target size
WCAG 2.2 accessibility guidelines set a minimum of 24 × 24 CSS pixels for a target (success criterion 2.5.8, level AA), with exceptions when targets are spaced far enough apart (W3C). For important buttons, go bigger.
Measuring: which tools, which metrics
SXO is managed page by page, by cross-checking three sources.
- Google Search Console gives you impressions, rankings and clicks by query and by page, plus the Core Web Vitals report, built on data from real Chrome users (the CrUX report) and grouped by similar pages, on mobile and desktop (Search Console Help).
- Google Analytics 4 gives you engagement rate and conversions by landing page. In GA4, a session is "engaged" if it lasts longer than 10 seconds, has a key event, or has two or more page views; bounce rate is the share of sessions that weren't engaged (Google Analytics Help).
- A behavior analytics tool shows, through heatmaps and session recordings, where visitors click, scroll and drop off. Microsoft Clarity is free (Microsoft Clarity); Hotjar does the same job and adds surveys.
The approach recommended in the first version of this article still holds:
- Start with the pages that get the most traffic or matter most to the business.
- Find landing pages that get visits but lead nowhere, then watch session recordings for those pages.
- Have someone who doesn't know the page test it, and watch without helping.
- A/B test major changes (call to action, form, structure) before rolling them out.
- Repeat every month.
For the conversion side, our complete CRO guide covers tactics and testing tools.
Our take
SXO is mostly common sense that gets lost as soon as SEO, design and marketing work in their own corners: the page ranks well but the first screen doesn't say what you sell, or it looks great but nobody finds it.
We're wary of two things. First, the numbers attached to SXO: we've never seen the source behind the "+200% conversions" claims going around. Second, the obsession with scores: a 100 on PageSpeed Insights is worthless if the page doesn't answer the query. Google says it itself: relevance comes before page experience.
What works is putting SEO, design and development around the same page, with the same checklist. At Digidop, we handle design and development through our web design work, built for a site that converts. For SEO, we work with our partner agency Vydera, an AI-native visibility agency.
Frequently asked questions
What is the difference between SEO and SXO?
SEO aims to get a page into the search results. SXO aims to make that page answer the person who lands on it and lead them to the next step. SXO includes SEO; it doesn't replace it.
Do time on page and bounce rate matter to Google?
Google's documentation on page experience and on its ranking systems doesn't mention them. It cites Core Web Vitals, HTTPS, mobile display, ads, interstitials and how easy the main content is to find. Engagement rate is still a good way to spot a page that disappoints, but it isn't a documented ranking lever.
Which tools should I use to start with SXO on a small budget?
Google Search Console, Google Analytics 4, PageSpeed Insights and Microsoft Clarity are free. Together they cover queries, engagement, Core Web Vitals and on-page behavior.
Are Core Web Vitals enough to rank well?
No. Google states that good Core Web Vitals don't guarantee a top ranking, and that it shows the most relevant content even when page experience is sub-par. They break ties between pages that answer the query equally well.
Do I need an SXO agency?
What you need most is for SEO, design and development to work together on the same pages. An agency that designs and builds the site with search in mind covers most of it. At Digidop, our site audits cover UX, SEO, technical setup and the CMS, and our web design is built for conversion.
Sources
- Google Search Central: understanding page experience · Core Web Vitals and Google Search results
- Google Search Central: guide to ranking systems · creating helpful content
- Google Search Central: mobile-first indexing is complete
- web.dev: Web Vitals · INP becomes a Core Web Vital
- Search Console Help: Core Web Vitals report · Google Analytics Help: engagement
- W3C: WCAG 2.2, target size (minimum)
.webp)
