Semrush Site Audit Core Web Vitals vs Audra: What Page Sampling Misses

Semrush Site Audit generally checks the first 10 crawled URLs with a 200 OK HTTP status, often including the homepage, rather than measuring Core Web Vitals across an entire site. This Semrush Site Audit Core Web Vitals comparison shows how to identify the pages behind the sample, expand testing to meaningful templates, and report performance findings without treating a 10-URL set as a full-site verdict.

The direct answer: how Semrush selects Core Web Vitals pages

Semrush states that Site Audit normally chooses the first 10 pages in its crawl that return a 200 OK status. When the crawl source is the website itself, the homepage and pages linked from it are commonly represented because they tend to be found earliest. When the source is a sitemap or an imported URL list, the first 10 eligible URLs in that sequence are generally selected instead. Semrush keeps that analyzed-page list stable between crawls so its historical charts compare like with like. (semrush.com)

That rule is useful, but it has a boundary: it creates a controlled sample, not a complete core web vitals assessment. A 500-page ecommerce site may have its homepage, category pages, and a few editorial URLs represented while missing the product templates where third-party reviews, image galleries, variant selectors, and payment-related scripts add substantial weight.

A practical interpretation is:

• 10 pages can show whether a selected reference group improved or regressed.
• 10 pages cannot reliably represent every page type, device experience, or business-critical journey.
• The crawl order matters. A template that is discovered late may not appear in the default group even if it drives revenue or leads.
• A 200 OK response is a technical eligibility gate, not proof that a URL is strategically important.

For a small brochure site with 8 to 10 indexable pages, the sample may cover most of the website. For a store, marketplace, publisher, SaaS site, or multilingual domain, it is more likely to be only a narrow slice.

Why the 200 OK rule and crawl order change the result

A 200 OK HTTP status tells a crawler that the server successfully returned the requested resource. It is a sensible requirement for a page-level performance check: a redirect, 404, blocked URL, or server error is not a stable destination for Lighthouse-style page analysis.

However, status codes do not rank business importance. Consider a site with these pages:

1. / — homepage, 200 OK
2. /services/ — service hub, 200 OK
3. /about/ — company page, 200 OK
4. /blog/ — blog archive, 200 OK
5. /blog/old-announcement/ — low-traffic article, 200 OK
6. /product/enterprise-plan/ — high-converting landing page, 200 OK
7. /checkout/ — customer-critical flow, potentially excluded or inaccessible to a public crawler

If internal navigation causes older content to be found before the enterprise landing page, a first-ten rule can report acceptable performance while the commercial template remains untested. That is not a flaw in a fixed sample; it is a reason to label the result accurately.

Semrush also allows users to edit the analyzed-pages list and add up to 10 URLs, then recrawl to refresh the metrics. Its documentation cautions that if a selected page later becomes unavailable, historical data for that page can be removed. (semrush.com) This makes manual selection useful for a focused release check, such as comparing a homepage, category, product, lead-generation landing page, and article template.

The limitation remains the same: a manually selected 10-page list is a stronger sample, not an exhaustive site-wide measurement.

Semrush Site Audit Core Web Vitals: sample tracking versus audit coverage

The most useful distinction is between trend tracking and audit coverage.

Where a fixed 10-page sample works well

A fixed list can be effective when the goal is to answer a narrow recurring question: did the selected pages become slower after a deployment, consent-management update, redesign, or tag-manager change? Because Semrush keeps the set stable, a score change is less likely to be caused solely by swapping one URL for another. That consistency is valuable for monthly reporting.

For example, an agency could retain these 10 URLs for six months:

• Homepage
• Primary service page
• Lead-generation landing page
• Main category page
• Representative product page
• Blog article
• Pricing page
• Contact page
• Documentation page
• Campaign destination page

That set becomes a repeatable release-monitoring panel.

Where it falls short

A core web vitals audit should also ask whether the tested URLs reflect the templates that matter. A fixed list may miss:

• Paginated category and search-result pages
• JavaScript-heavy product-detail pages
• Long-form articles with ads or embeds
• Local location pages
• Logged-out account, cart, or checkout entry pages
• International or language-specific templates
• Pages receiving the most organic sessions or conversions

This is why a broader crawl-based workflow can complement Semrush. Audra is positioned as a local desktop audit agent: it can inspect a larger selected crawl scope and bring Lighthouse performance results together with SEO, accessibility, broken-link, best-practice, and AI answer-engine visibility checks. The aim is not to replace a fixed trend sample, but to make the underlying audit population visible and reviewable.

Teams comparing issue presentation may also find the Semrush Site Audit Issues vs Audra: A Fix-First Review useful when deciding whether a dashboard-oriented workflow or a prioritized local report better suits a client engagement.

Build a reproducible page-selection plan before running tests

The best answer to “how many pages should be analyzed?” is not always a number. It is a documented selection rule that another consultant, developer, or client can repeat.

A practical selection plan starts with a template inventory. Instead of selecting URLs because they happen to be near the top of a crawl, identify the page types that share code, assets, or user journeys.

A repeatable selection framework

For a site with more than 10 URLs, select at least one representative URL from each material template, then add business-priority URLs and known-risk pages.

Then record the exact list, device assumptions, run date, test location if applicable, and whether the result is laboratory or field data. This makes a client report defensible: it states what was tested, why those URLs were chosen, and what was not measured.

For larger sites, expand the selection with a traffic-led layer. Export the highest-traffic organic landing pages from Google Search Console or web analytics, then cross-check them against the template inventory. A low-traffic product page can represent a template; a high-traffic article deserves individual attention even if it shares a template with other posts.

How to measure Core Web Vitals beyond the Site Audit sample

A broader workflow usually needs more than one source because no one tool answers every question. Google distinguishes between field data, which reflects real-user experiences, and lab data, which is collected in a controlled test environment. PageSpeed Insights can show both where sufficient CrUX data exists, while Lighthouse is primarily a lab diagnostic tool. (web.dev)

Use Google Search Console for site-level field-data patterns

Google Search Console’s Core Web Vitals reporting is useful for identifying groups of URLs that have real-user performance problems. It is not a substitute for inspecting individual templates, but it can reveal whether a pattern affects mobile users, desktop users, or a cluster of similarly structured pages.

Search Console evidence is especially valuable when a team needs to prioritize by user impact rather than by a one-off synthetic test. Its grouping logic and reporting window can also make results differ from a Semrush crawl, which is why a direct comparison should not assume one dataset is wrong. Google Search Console vs Semrush Core Web Vitals: Why Results Differ explains the practical reasons the two workflows may produce different-looking outcomes.

Use CrUX for field data at URL or origin level

The Chrome UX Report, commonly called CrUX, is Google’s dataset of anonymized real-user Chrome experiences. It can provide field data for an individual URL or the broader origin when enough qualifying traffic is available. Pages without sufficient traffic may not have URL-level field data, which is a data-availability constraint rather than evidence that the page performs well.

The important reporting rule is simple: label CrUX values as field data and do not compare them as if they were identical to a controlled Lighthouse run. The Semrush Site Audit vs CrUX: Core Web Vitals Data Collection comparison provides further context on these different collection methods.

Use PageSpeed Insights and Lighthouse for diagnosis

Google PageSpeed Insights is useful when an auditor needs to inspect a particular URL and see diagnostic opportunities. Lighthouse supports controlled analysis of loading, responsiveness proxies, layout stability, accessibility, best practices, and SEO. Google’s Core Web Vitals tools guidance separates diagnostic lab workflows from field-data monitoring because each solves a different problem. (web.dev)

For a site audit, this can become a two-stage process:

1. Use Search Console and CrUX to identify real-user priorities and affected groups.
2. Use PageSpeed Insights, Lighthouse, or a crawl-based local auditor to reproduce and diagnose representative URLs.

Lab data versus CrUX field data: what a report should say

A report becomes misleading when it presents every performance number as the same type of measurement. Core Web Vitals include Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), but their meaning depends partly on how the data was collected.

Google’s documentation describes PageSpeed Insights as using both lab and real-world data, with CrUX supplying the field-data component when it is available. (developers.google.com) A page can therefore have a poor lab score while field data passes, or pass a lab run while field users struggle because of slower devices, networks, interaction patterns, cache states, or third-party variability.

A precise report might say: “The tested product template showed a lab LCP concern in a Lighthouse-style run. CrUX URL-level data was unavailable, so this is a diagnostic finding rather than a confirmed field-data failure.” That language preserves the value of the test without overstating certainty.

Semrush versus Audra for page selection and reporting

Semrush and Audra can serve different parts of an audit program.

Semrush Site Audit is advantageous for teams that already rely on the wider Semrush platform for rank tracking, competitive research, and recurring cloud-based site health monitoring. Its fixed analyzed-page behavior can support trend continuity, and the manual list is useful when a team needs to watch up to 10 named URLs. Semrush’s own rule is transparent once documented: first eligible 200 OK pages by crawl order, or the first eligible entries in the configured sitemap or URL list. (semrush.com)

Audra is more focused on a local-first audit workflow. Its desktop model is useful when a consultant wants to crawl a selected site scope on macOS or Windows, review many pages rather than only a preset Core Web Vitals sample, and give a client one report covering performance, technical SEO, accessibility, links, best practices, and AI visibility checks. That matters when the central question is not merely “did 10 tracked pages change?” but “which templates and pages should be fixed first?”

The practical differences are:

• Sampling transparency: Semrush provides a controlled 10-page Core Web Vitals group; Audra supports a wider crawl scope that the auditor can inspect and explain.
• Local processing: Semrush uses a cloud platform; Audra performs its audit workflow on the user’s computer.
• Report usability: Semrush suits teams working inside a multi-tool SEO dashboard; Audra suits a focused audit deliverable that combines several technical dimensions.
• Recurring cost: Semrush is part of a subscription suite, while Audra uses a one-time license model for its core desktop audit.

Neither approach removes the need for judgment. A broader crawl can create more findings than a small team can act on, while a 10-page sample can be too narrow for a varied site. The right workflow makes the chosen scope explicit.

Which should you choose?

Choose Semrush Site Audit Core Web Vitals when the organization already uses Semrush, needs a stable recurring sample, and can define 10 strategic URLs for ongoing monitoring. This works particularly well for a relatively small site or for a monthly scorecard where consistency matters more than exhaustive coverage.

Choose Audra when an agency, consultant, marketer, or site owner needs to investigate a broader crawl, compare multiple page types, and turn the work into a local, client-ready technical audit. It is especially suitable for a site with distinct templates—such as a Shopify store with collection and product pages, a publisher with articles and archives, or a SaaS site with documentation and conversion pages.

Use both a controlled sample and field-data tools when Core Web Vitals influence a major redesign, migration, or performance remediation project:

• Keep a fixed 10-page panel for trend continuity.
• Test representative templates across the broader site.
• Prioritize URLs with traffic, revenue, lead, or support significance.
• Validate real-user impact in Google Search Console and CrUX where data is available.
• State clearly whether each conclusion comes from lab data, field data, or both.

The strongest result is not a single green score. It is a reproducible explanation of which pages were measured, which user journeys they represent, what the data type means, and what should happen next.

Verdict

Semrush’s first-ten-200-OK selection method is a sensible way to maintain a consistent Core Web Vitals reference sample, and its manual list gives users control over the exact 10 URLs monitored. It should not, however, be described as a whole-site Core Web Vitals measurement on a complex website.

Audra is the better fit when page-selection transparency and broader local audit coverage are the priority. A practical audit program can use a stable Semrush sample for trends, CrUX and Search Console for real-user evidence, and a wider crawl-based review to ensure that high-value templates are not left outside the report.

FAQ

How many pages does Site Audit select for Core Web Vitals analysis?

Semrush Site Audit generally selects 10 pages for its Core Web Vitals analysis. The eligible pages are the first URLs found in the crawl that return a 200 OK HTTP status. Semrush keeps the selected group stable across crawls to support historical comparison, though users can replace the analyzed list manually with up to 10 URLs. (semrush.com)

Which pages does Semrush Site Audit choose for its Core Web Vitals check?

For a standard website crawl, Semrush usually chooses the first 10 crawlable 200 OK pages, commonly including the homepage and URLs linked from it. For sitemap-based crawling or an uploaded URL list, it generally takes the first 10 eligible URLs in that sequence. The exact set depends on crawl discovery order and URL accessibility. (semrush.com)

Does Site Audit always analyze the homepage first?

The homepage is commonly included when Site Audit crawls a website because it is usually the initial discovery point and returns 200 OK. It is not an absolute guarantee in every configuration: sitemap order, imported URL lists, redirects, bot restrictions, or an unavailable homepage can alter eligibility and sequence. The analyzed pages must be accessible to the crawler. (semrush.com)

Why does Site Audit select pages with a 200 OK status code?

A 200 OK status indicates that the server successfully returned the requested page, making it a valid candidate for page-level analysis. Redirects, errors, blocked pages, and unavailable URLs do not provide the same stable target for Core Web Vitals testing. Still, 200 OK is only an eligibility criterion; it does not mean the page is high traffic or commercially important.

How can a team measure Core Web Vitals for more than the pages Site Audit selects?

A team can manually choose up to 10 URLs in Semrush, then broaden coverage with a template-led URL list, Lighthouse or PageSpeed Insights tests, and a crawl-based audit tool such as Audra. For real-user evidence, use Google Search Console and CrUX where sufficient traffic data exists. Combine representative templates with top traffic and conversion URLs rather than relying only on crawl order. (semrush.com)

What is the difference between lab data from PageSpeed Insights or Lighthouse and field data from CrUX?

Lab data is a controlled synthetic test used to diagnose a specific URL under defined conditions. CrUX field data aggregates real Chrome user experiences over time, when enough data exists. PageSpeed Insights can show both types. Lab results help find likely causes; field data indicates whether users have experienced the issue at scale. (web.dev)