Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Ahrefs for mobile SEO: audit and fix mobile issues

Updated · 7 min read

Short answer In Ahrefs Site Audit, open the project's crawl settings, set the crawler's user agent to Mobile, add a free Google PageSpeed Insights API key, and recrawl. Then fix slow mobile pages, missing viewport tags and content that phones don't get. A verified site can run this on Ahrefs' free plan.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

How to set Ahrefs Site Audit to crawl as a phone

Change one setting and add one key. Ahrefs Site Audit crawls as a desktop browser by default. Google does the opposite:

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile-first indexing best practices)

Steps, as of Ahrefs' help pages in November 2026:

StepWhereWhat to do
1. Verify your siteAhrefs accountProve you own it. Free Site Audit works only "for verified websites" (Ahrefs Free)
2. Switch to mobileProject settings > Crawl settings > Robots instructionsSet the user agent to Mobile instead of Desktop (Ahrefs Help: Site Audit settings)
3. Add a PageSpeed keyProject settings, Core Web Vitals (CWV) sectionPaste a free API key from Google; wait for the green "Valid" check (Ahrefs Help: Core Web Vitals)
4. Turn on JavaScriptCrawl settingsSwitch on "Execute Javascript" if your pages build their content with scripts, as many site builders do (Ahrefs Help: Site Audit settings)
5. RecrawlSite AuditSettings apply only to new crawls, not one already running (same page)

The user agent is the name a crawler gives a website when it asks for a page. Ahrefs' mobile one presents itself as Chrome on an Android phone (Ahrefs: AhrefsSiteAudit bot). Ahrefs says the Robots instructions section is only for verified projects (Ahrefs Help: Site Audit settings).

Step 3 is the one people skip, and it is the one tied to the mobile setting:

"If you want mobile PageSpeed Insights data, make sure to select the Mobile AhrefsSiteAudit User Agent." (Ahrefs Help: Core Web Vitals in Site Audit)

Will a mobile crawl find anything new?

On most small business sites, fewer new issues than you'd expect. If your site uses responsive design (one page that resizes to fit the screen), Google says "the content and the metadata are the same on the mobile and desktop version" (Google Search Central). Broken links and missing titles show up in either crawl.

The mobile crawl earns its keep in three cases:

  • Speed data. Mobile Core Web Vitals come only with the mobile user agent (above). Phones are usually slower, so this is where most real problems sit.
  • Different mobile pages. If your site serves different HTML to phones (dynamic serving) or runs a separate mobile site (like an m. address), the mobile crawl is the only way to see what Google indexes.
  • Script-built pages. With JavaScript on, the crawl shows what a phone actually renders. See JavaScript SEO audit for that check.

Not sure which setup you have? See responsive design and SEO.

Where to find the mobile results

Use two places in Site Audit, as of November 2026 (Ahrefs Help: Core Web Vitals in Site Audit):

  • Performance report: charts of speed across all pages, and which pages have Google data at all.
  • Page explorer > Manage columns > PageSpeed Insights: adds every speed column per page, ready to sort or export.

Two kinds of numbers land there. CrUX columns are field data: real Chrome users' visits, from Google's Chrome User Experience Report. Lighthouse columns are lab data: one simulated test load. Google's Core Web Vitals measure real-world experience, so sort by the CrUX columns first.

Ahrefs warns that "less popular pages may have no data or only partial data in CrUX". For a small site, expect many blanks. Then use the Lighthouse columns as a rough guide.

Ignore the FID columns. Google replaced First Input Delay with Interaction to Next Paint (INP) as a Core Web Vital on March 12, 2024 (web.dev).

What to fix first

Fix what Google measures, slowest important page first. Google's "good" lines (Google Search Central: Core Web Vitals):

Ahrefs columnWhat it measuresGoodUsual fix
CrUX LCPTime until the main content showsUnder 2.5 secondsSmaller hero images, faster hosting. See mobile page speed
CrUX INPDelay after a tapUnder 200 millisecondsFewer heavy scripts: chat widgets, trackers, sliders
CrUX CLSHow much the page jumps while loadingUnder 0.1Set image sizes; reserve space for banners and ads
Lighthouse mobile issuePhone layout problems Lighthouse foundNo issueFix what the details column names

Google says it "highly recommend[s]" good Core Web Vitals, and that this aligns with "what our core ranking systems seek to reward" (same page). It is one factor among many, not a switch.

A common Lighthouse mobile problem is a missing viewport tag, the line that tells a phone to fit the page to its screen. The standard value is "width=device-width, initial-scale=1" (Chrome for Developers: Lighthouse viewport audit). Most site builders add it for you.

If your mobile pages differ from desktop

Run a desktop crawl, export it, switch to mobile, recrawl and export again. Then compare by page. Google's best practices name what must match (Google Search Central):

CheckWhy
Same pages and main contentContent only on desktop is content Google may not use
Same robots meta tagsA noindex on mobile can keep the page out of Google
Same titles and meta descriptionsGoogle reads the mobile ones
Same structured dataRich results come from the mobile version
Content shown without a tap"Google won't load content that requires user interactions"

Advanced mobile SEO covers these parity checks in depth.

Isn't the Mobile Usability report in Search Console easier?

It's gone. Google retired Search Console's Mobile Usability report, the Mobile-Friendly Test and its API starting December 1, 2023, and pointed people to Lighthouse instead (Google Search Central Blog, 2023). Search Console still has a Core Web Vitals report. See what replaced the report.

Do you need paid Ahrefs for this?

Usually not, if you only audit your own site.

Option (November 2026)PriceWhat you get for this job
Ahrefs Free$0Site Audit on verified sites, 5,000 crawl credits a month per project (Ahrefs Free)
Starter$29/monthMore Site Explorer and Keywords Explorer access (Ahrefs Free)
Lite$129/month100,000 crawl credits, Rank Tracker, 5 projects for sites you don't own (Ahrefs pricing)
Standard$249/month500,000 crawl credits (same page)

Prices are in US dollars, billed monthly, before tax; annual billing saves "up to 17%" (Ahrefs pricing). A crawl credit is one page: only internal HTML pages that load normally (status 200) use them; redirects and errors don't (Ahrefs Help: crawl credits). So 5,000 credits covers a typical small site several times a month.

Pay when you want to track rankings on phones. Rank Tracker has a "Mobile" view of every tracked keyword, competitors included (Ahrefs Help: mobile rankings).

Without Ahrefs, run single pages through PageSpeed Insights and read the Core Web Vitals report in Search Console. Both are free and use the same Google field data.

Example

A plumber with a 40-page responsive site

Desktop and mobile crawls flag the same 6 broken links. The mobile PageSpeed columns show the home page's LCP at 4 seconds, from a 3 MB hero photo. Compressing it is the one fix that matters. Cost: $0 on Ahrefs Free.

A clinic with an old m. mobile site

The mobile crawl finds 60 pages; desktop finds 90. Thirty service pages exist only on desktop, so Google may not use them. The fix is a responsive rebuild, not page-by-page patches.

A shop with a JavaScript store theme

With "Execute Javascript" off, product pages look empty. Turned on, they render fine, but INP is 400 milliseconds from three tracking scripts. Removing one unused script is the first test.

FAQ

Why are the CrUX columns empty?

Google only has field data for pages with enough Chrome visits. Ahrefs says less popular pages may have none. Use the Lighthouse columns, or the site-wide data in PageSpeed Insights.

Should I crawl both desktop and mobile?

Only if your site serves different pages to phones. With responsive design, the mobile crawl alone is enough.

Do I need a developer?

For image compression and removing plugins, usually not. For a separate mobile site or a script-heavy theme, usually yes.

Is a mobile audit a one-time job?

No. Site Audit can run on a schedule you set in project settings (Ahrefs Help: Site Audit settings). Monthly suits most small sites; see how often to audit.

Different for you?

Keep learning

NextAhrefs for on-page SEO: step-by-step page fixesHow to use Ahrefs Site Audit, Site Explorer and Keywords Explorer to fix titles, headings, images and internal links on your own pages, and what's free.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Ahrefs Help: How should I configure my Site Audit settings?
  2. Ahrefs Help: How to see Core Web Vitals and other speed metrics in Site Audit
  3. Ahrefs Help: How are crawl credits in Site Audit spent?
  4. Ahrefs Help: How to see your mobile rankings on Rank Tracker
  5. Ahrefs: AhrefsSiteAudit bot
  6. Ahrefs: Site Audit
  7. Ahrefs: Ahrefs Free
  8. Ahrefs: Plans and pricing
  9. Google Search Central: Mobile site and mobile-first indexing best practices
  10. Google Search Central: Understanding Core Web Vitals and Google search results
  11. Google Search Central Blog: The role of page experience in creating helpful content (2023)
  12. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
  13. Chrome for Developers: Lighthouse viewport audit