Documentation menu

SEO audits

An SEO audit crawls your website the way a search engine does. It checks every page it finds for technical problems that cost you search traffic. Audits run once when you add a site, then every week. You can also start one yourself once a day.

Add a site under Dashboard → SEO.

Plans

Free Pro Team
Sites 1 3 10
Pages per audit, verified site 50 500 2,000
Pages per audit, unverified site 50 50 50

How the crawl works

  • It starts from your home page and every URL in your sitemap. It reads the sitemap listed in robots.txt, or /sitemap.xml, including sitemap indexes and gzipped sitemaps.
  • It follows links to other pages on the same site. www. and the bare domain count as the same site, and other subdomains don't.
  • It identifies itself as AsniherBot and obeys robots.txt rules for that name.
  • It fetches two pages at a time with a short pause between requests, so it won't overload your server.
  • Each page has 15 seconds to respond. Up to 2 MB of HTML is read per page.
  • An audit stops after 20 minutes even if pages are left. The pages crawled so far are still scored.

Verify your site

Until you verify that you own the site, audits stop at 50 pages, so nobody can use Asniher to crawl a site that isn't theirs. Verify in either of these ways. Both are shown on the site's page with your token.

  • Add <meta name="asniher-site-verification" content="…"> to the <head> of your home page.
  • Or add a DNS TXT record asniher-site-verification=… to your domain.

Then choose Verify now. You can remove the tag after verifying.

What it checks

Errors

  • Pages returning 4xx or 5xx, timeouts and connection errors
  • Internal links to broken pages
  • Redirect loops, or more than 5 redirects
  • Sitemap URLs that don't return 200 or that redirect
  • Pages listed in the sitemap but marked noindex
  • Canonicals pointing to a broken page or to another host
  • Missing titles
  • HTTP scripts, styles or images on HTTPS pages

Warnings

  • Redirect chains (more than one hop)
  • Duplicate titles and meta descriptions
  • Titles over 60 characters
  • Missing meta descriptions
  • Missing H1 headings
  • Images without alt text
  • No mobile viewport
  • Invalid JSON-LD
  • Server responses slower than 1.5 seconds
  • HTML larger than 1 MB
  • No sitemap

Notices

  • Meta descriptions under 70 or over 160 characters
  • Titles under 10 characters
  • More than one H1
  • No lang attribute
  • Pages with fewer than 200 words

Content checks such as titles, descriptions and headings are skipped on pages marked noindex. Each issue on the site's page explains why it matters and how to fix it.

Health score

The score starts at 100. Each type of error costs up to 15 points and each type of warning up to 5, scaled by the share of crawled pages it affects. A site-wide problem, such as a missing sitemap, counts as affecting every page. Notices don't lower the score.

As a guide, 90 or more is healthy, 70 to 89 needs attention, and below 70 has problems that are probably hurting search traffic. After the second audit, the site's page shows the score over time and how many issues were fixed or are new since the last audit.

Fix plans and rewrites with Claude

On Pro and Team, Claude can turn an audit into a plan. Generate with Claude on the site's page reads the audit's issues and writes three to eight steps in order of impact. Each step says why it matters, how to fix it, and how much work it is. Suggest with Claude next to a page with title or description issues reads the page and suggests three titles and meta descriptions within the recommended lengths.

  • Each generation uses one AI action: 10 a month on Pro, 50 on Team. They reset on the 1st of each month, and failed generations don't count.
  • Results are saved with the audit, so reloading the page doesn't use another action. Regenerating does.
  • Claude only sees the audit results and, for rewrites, the text of that page. It can't change anything on your site.
  • Read suggestions before you use them. They're a starting point, not a guarantee.

Google Search Console

On Pro and Team, a verified site can be connected to its Google Search Console property. Connect Search Console on the site's page sends you to Google, where you allow read-only access.

  • The property must be for the same address as the site: a URL-prefix property such as https://example.com/, or a domain property such as example.com. For a domain property, only pages on the site's own address are counted.
  • Asniher imports data every day: up to 16 months of daily clicks and impressions, and the top 1,000 queries and 500 pages for the last 28 days. Google's numbers lag by two to three days, so the 28 days end three days ago.
  • The site's page shows clicks, impressions, average click-through rate and average position, each compared with the 28 days before, the top queries and pages, and Almost page 1: queries at an average position of 8 to 20 that already get impressions. Improving the page that ranks for them is often the quickest way to more traffic.
  • Fix plans from Claude include your top queries and the almost page 1 list, so the plan can put pages that already earn impressions first.
  • If you revoke access in your Google account, the numbers already imported stay on the page and it asks you to reconnect. Disconnect revokes access and deletes the imported data.

Page speed

If the server has a Google PageSpeed Insights key, each audit also records the home page's mobile performance score, Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint. INP comes from real Chrome users and is missing for sites with little traffic.

  • Search & AI visibility monitors check one page much more often and alert you as soon as it can no longer be indexed. Audits look at the whole site once a week and don't send alerts.

Questions about this page? Email support@asniher.com.