SEO audit: full website audit tool

Use cases

Site Audit: when to use it

Onboarding a new SEO client
Post-migration or redesign verification
Periodic audit to maintain technical health

Site Audit: how it works

01

The crawl

Miraqo's crawler visits the site's pages like a search engine, following internal links and the sitemap.
02

The checks

Every page that responds goes through the 68 checks: HTTP status, meta tags, content, links, resources and security.
03

The score

Issues are grouped by severity and weighed into site health, with the pages involved.

Site Audit: 68 technical checks, with priorities already sorted

What gets checked

68 checks on every page, split into errors, warnings and notices by how much they weigh on the site.

Blocking errors404 and 5xx pages, broken internal and external links, redirect loops, mixed content, pages without a title or H1.
Content and meta tagsMissing, too long, duplicate or irrelevant titles and descriptions, multiple H1s, thin or duplicate content.
Indexing and structureCanonicals, noindex, robots.txt, sitemap, hreflang, orphan pages and redirect chains.
Performance and securitySlow or heavy pages, render-blocking resources, compression, caching, HTTPS, HSTS and expiring SSL certificates.

Priorities already sorted

The issue list starts from what matters most, not from what is most frequent.

Site health from 0 to 100A score that weighs every issue by severity and by the number of pages involved.
Fix these firstThe heaviest issues at the top of the overview, with the number of pages for each.
Every issue, page by pageFor each item, what is wrong, how to fix it and on which URLs.
Thresholds and checks to fitAdjustable title and description lengths and minimum word count, checks that can be excluded: recalculation is instant, with no new crawl.

The site explored in detail

Beyond the issues, everything the crawler saw, in filterable tables.

PagesHTTP code, indexability, title, depth and response time for every crawled URL.
LinksInternal and external links with anchor text, follow or nofollow, and the status of the target.
ResourcesImages, JavaScript, CSS and fonts loaded by the pages, with size, compression and HTTP code.
Redirects and duplicatesRedirect chains step by step and groups of pages with the same title, description or content.

Over time, and ready for AI

Every audit is saved: the site can be followed over time, including from the AI assistants’ point of view.

Comparing two auditsBefore and after side by side: health, crawled pages and issues, category by category.
Scheduled crawlsAn audit every week or every month on the chosen day, or only when started by hand.
JavaScript renderingFor sites that load content through JavaScript, switched on automatically when needed.
AI crawlers and llms.txtWhich AI assistants are blocked by robots.txt and what each bot governs, plus a check for the llms.txt file.

The SEO audit is the technical crawl of the site. Miraqo visits the pages one by one, the way a search engine would, and records for each of them the HTTP status, title and description, internal and external links, images, structured data and response time. At the end you get a health score from 0 to 100 and a list of issues already sorted by severity: blockers first, then warnings, then suggestions.

The report has ten tabs, including issues, pages, links, duplicates, redirects and Core Web Vitals, and every entry explains what is wrong and on which URLs. In the settings you choose how many pages to crawl, whether to render JavaScript, which URLs or parameters to skip, and whether to repeat the crawl weekly or monthly. Every audit is kept, so after a fix you compare before and after on the same scale.

Questions about site audit

Up to the maximum number of pages set for the project. Every page that responds with HTTP 200 counts as one credit; redirects, errors and unreachable pages use no credits.

You can trigger a new scan whenever you like, or schedule it at your preferred cadence.

It's a 0-to-100 grade summarising the site's technical health. It drops when blocking errors are found and rises as you fix them.

Yes. Core Web Vitals are measured on a sample of pages, the homepage and one for each page type, and have a dedicated page: Performance.

Yes. The "Technical audit" section goes into the PDF report, which can be scheduled and emailed, or shared through a read-only link.

Yes. Miraqo maps the internal link structure and flags orphan pages or unreachable URLs.

Usually a firewall or Cloudflare blocks outside crawlers. Allow the MiraqoAuditBot user agent and run the audit again: the "Audit blocked" guide explains the steps.