SmarterSEO
Pricing
Sign inBook a demoStart free
SmarterSEO

SEO research, tracking and reporting for agencies and in-house teams. Credits or your own DataForSEO key.

Support: support@smarterseo.com

© 2026 SmarterSEO

Features
Keyword researchRank trackingLocal SEOAI search visibilityCompetitor researchBacklinksSERP toolsTechnical SEOSearch Console & AnalyticsClient reporting
Use cases
SEO agenciesLocal SEO agenciesIn-house teamsFreelancersContent teamsLink builders
Product
PricingIntegrationsAPI & MCPChangelogAffiliate programStart freeSign in
Resources
BlogHelp centreAffiliate programAboutContactFAQTermsPrivacyRefunds
Help centre/Technical SEO/Site audit
/
Help centre home
Start here
  • Getting started
  • Billing and credits
Account
  • Account and team
  • Affiliate program
Research tools
  • Keyword research
  • Competitor research
  • Backlinks
  • SERP tools
  • AI search
  • Technical SEO
    • Log file analysis
    • IndexNow
    • Check mentions
    • Sitemap Extractor
    • Site audit
Projects
  • Rank tracking
  • Local SEO
  • Search Console and analytics
  • Content tools
Reporting
  • Reporting and automation
  • API and MCP

Site audit

Crawl a project's site, see every broken, duplicated, slow or blocked page with a fix, measure Core Web Vitals on the pages that matter, and watch the health score move from run to run.

6 min readUpdated 18 Nov 2026About 0.03 credits per crawled page, plus about 1 credit per page rendered for Core Web Vitals; pages the crawler does not reach are refundedapp.smarterseo.com/p/[slug]/technical/audit↗

Site audit crawls a project's website, checks every page it reaches and turns the results into a scored report: a health score, a list of issues with the pages affected and how to fix each, the full page table, broken and nofollow links, redirect chains and Core Web Vitals for the most-linked pages. Run it again later and every number shows the change since the previous run.

#What it does

The crawler starts at the URL you give, follows internal links up to the page cap and records each page's status, title, description, headings, canonical, word count, size, load time and links. From those it derives about 45 issue rules in six categories: content, indexing, links, speed, structured data and technical. A separate, smaller crawl renders the most-linked pages in a browser to measure Largest Contentful Paint, Cumulative Layout Shift and Time to Interactive.

Everything runs on the data provider's crawler, so a crawl of a thousand pages takes minutes, not hours, and nothing is fetched from your own servers twice.

#Before you start

  • Site audit lives inside a project: open the project, then Technical → Site audit. One audit per project; it keeps every run.
  • Only owners, admins and members can set up or run an audit. Viewers can read every report.
  • Decide how many pages to crawl. The cap is 1,000 pages per crawl on every plan, including Agency and the lifetime license; the crawler takes the pages it reaches first from the start URL. If your site needs more, email support@smarterseo.com and we raise the cap for that workspace.
  • Sites that block crawlers return nothing. Allow the user agent RSiteAuditor, or set your own under Advanced options, before the first run.

#Setting up

  1. Click Set up the audit.
  2. Check the Start URL. It is filled from the project's domain; change it to a section such as https://example.com/blog/ to audit only that part.
  3. Choose Pages to crawl, at most, up to 1,000. You pay only for pages the crawler reaches, so a cap higher than the site costs nothing extra.
  4. Leave Measure Core Web Vitals on a sample of pages ticked and pick the sample size (50 by default, up to 500). The pages with the most internal links are rendered first.
  5. Tick Render JavaScript on every page only for sites that build their content in the browser. It multiplies the base price by ten.
  6. Advanced options hold crawl-in-sitemap-order, keyword density, a custom user agent and the delay between requests.
  7. The cost line shows the credits before you confirm. Click Create audit; the first crawl starts at once unless you untick Start the first crawl now.

#While it runs

The page shows a progress meter with pages crawled against the cap and refreshes on its own. Small sites finish in a couple of minutes; a 1,000-page crawl usually takes ten to twenty minutes because the crawler paces itself to the site. When the main crawl is scored the report appears, and the Core Web Vitals sample continues in the background with its own meter; vitals fill in under the Vitals tab when it finishes.

A run that ends early says why next to Pages crawled: "limit exceeded" means the cap was reached, "empty queue" means the crawler ran out of links.

#Reading the report

Tiles. Health score out of 100, weighted by how many pages each issue affects, with the change since the previous run. Pages crawled against the cap. Errors, Warnings and Notices count pages with at least one issue of that severity.

Overview. The ten issues affecting the most pages, the status-code split, click-depth distribution, how many pages are indexable, the average load time and the health score of every completed run.

Issues. Every rule found, with severity, category, pages affected, the change since the last run and a one-line fix. Click an issue for the list of pages with the detail behind each (the broken target and anchor, the canonical, the chain). CSV and Copy Clip export either table.

Severity Examples
Error 4xx or 5xx page, broken internal link, redirect loop or chain of 3+ hops, canonical to a broken page, missing or duplicate title, duplicate content, server response over 3 s, page served over HTTP
Warning Missing description, title over 60 or description over 160 characters, missing or multiple H1, thin content, orphan page, non-indexable page, canonical to a redirect, images without alt, page over 3 MB, structured data errors, LCP over 2.5 s, CLS over 0.1
Notice 2-hop redirect, short title, page more than 4 clicks deep, nofollow internal link, broken external link, render-blocking resources, duplicate description, no structured data, low readability, deprecated HTML

Pages. Every crawled URL with status, title, depth, word count, inbound links, load time and issue count. Filter by URL text, status band, indexability or a single issue. Click a page to open it: meta tags, canonical, its issues with fixes, the links that need attention, its vitals, and two buttons that cost about a credit each: Lighthouse (desktop or mobile scores for performance, SEO, accessibility and best practices with the headline audits) and Screenshot (a full-page capture).

Links. Broken internal links, broken external links and nofollow internal links, each with the source page, target, anchor and status. Orphan pages are listed under Issues.

Redirects. Every chain and loop with each hop, and the final URL to link to instead.

Vitals. The rendered sample, slowest LCP first, with LCP, CLS, TTI and FID coloured by Google's thresholds.

#Running again

Click Run audit at any time; one crawl per project runs at a time. Each completed run is kept and the Run picker opens older ones. Issue counts and the health score show the change against the previous run so you can see what a fix did.

The automation trigger Site audit finished fires after each run with the page count, issue counts and health score, so a client can get an email when a crawl completes. See Automations.

#Costs

Cost: About 0.03 credits per crawled page (0.3 with JavaScript rendering), about 1 credit per page in the Core Web Vitals sample, and about 1 credit for each Lighthouse run or screenshot you request. A 1,000-page crawl with a 50-page vitals sample is about 80 credits. Pages the crawler does not reach are refunded.

On a lifetime license the crawl is billed to your own data provider account at its page rates.

#Tips and gotchas

  • Start with a cap of 100 on a new site to check that the crawler gets in; raise it once the first run looks right.
  • A sitewide template error shows as one issue on almost every page. Fix the template and the next run clears all of them.
  • "Duplicate meta tags" and "charset mismatch" on every page usually come from a theme that prints the same tag twice; they are notices, not emergencies.
  • Broken internal links on many pages with the same four targets mean a navigation link is dead. The Issues detail lists the anchor text so you can find it in the menu.
  • Deleting the audit deletes its runs. Change the start URL or the cap under Settings instead.

#Related

  • Sitemap extractor
  • IndexNow
  • Log file analysis
  • Credit costs by tool
Previous← Sitemap Extractor
Didn't find what you needed?Contact support →
On this page
  • What it does
  • Before you start
  • Setting up
  • While it runs
  • Reading the report
  • Running again
  • Costs
  • Tips and gotchas
  • Related