SEO audits

The SEO page audits a page on one of your tracked sites. It reads the page the way a search engine would, runs it through Google Lighthouse, and reports what is holding it back — meta tags, content structure, technical setup and crawler files, in one place.

#Running an audit

Open SEO in the sidebar, pick a site, and enter the path you want checked — / for the homepage, /pricing for a specific page. Hit Analyze.

Audits are scoped to sites in your workspace: the URL has to be on that site's domain. This is a tool for the properties you own, not a general-purpose scanner.

#The scores

Four rings come straight from Lighthouse, measured on the mobile profile Google indexes with. They use Lighthouse's own thresholds: 90 and above is good, 50-89 needs work, below 50 is failing.

• SEO — crawlability, meta tags, link text, mobile friendliness.
• Performance — load speed and Core Web Vitals.
• Accessibility — contrast, labels, landmarks.
• Best practices — security, deprecated APIs, console errors.

The Overall ring is half Lighthouse and half the on-page issues found by the audit itself. When Lighthouse is unavailable it falls back to the on-page half alone.

#What each tab covers

• Overview — the score, how the issues break down by severity and by area, the trend across recent runs, and the fixes worth doing first. Start here.
• Meta tags — title and description with length meters against the lengths search results actually display, a preview of how the page reads on a results page, canonical URL, Open Graph and Twitter Card tags, and the full tag list.
• Content — word count, heading structure, keyword density with common words filtered out, readability, and every image with its alt text.
• Technical — HTTPS, viewport, structured data, status code and response time, robots.txt and sitemap, plus Core Web Vitals for mobile and desktop side by side.
• Links — every link on the page checked for a live response, so broken links, redirect chains and timeouts surface before a visitor finds them. Defaults to showing only the problems.
• Schema — your JSON-LD validated against schema.org: which types you declare, what breaks a rich result outright, and the optional properties that would make one stronger.
• Crawl — a multi-page crawl from this page outward, for the site-wide problems a single-page audit cannot see: orphaned pages, broken internal links, and how deep pages sit.
• Search — the organic traffic actually arriving, by engine and landing page, from your own tracking rather than a third-party console.
• Compare — this page beside competitor URLs you add, on the on-page signals, so the gap is a list rather than a hunch.
• Suggestions — the Lighthouse audits this page failed, each with a plain-language fix, estimated savings, and the specific files responsible.

#This is our crawler, not Google's

Everything in an audit — the scores, the Crawl tab, the link checks — is Quantalog requesting your pages itself. None of it is Googlebot, and none of it reflects what Google has actually crawled or indexed. An audit tells you what a search engine would find today; it cannot tell you what Google already did.

For real Googlebot activity — which URLs are indexed, when they were last crawled, what Google chose to skip — use Google Search Console. The two answer different questions and are worth reading side by side.

#What a crawl covers

One crawl visits at most 30 pages. On a larger site the summary says how many of your sitemap URLs that covered, and the findings describe only the pages actually checked — a clean result across 30 of 60 pages is not a clean result for the site. This cap is ours; search engines crawl as much of your site as they choose to.

Some findings are also worth reading with judgement rather than fixing outright. A broken outbound link is the common case: sites behind bot protection answer 403 to any automated request, ours included, while resolving normally in a browser. Open the URL yourself before treating it as broken.

#Sharing a report

Share publishes one audit at a link anyone can open — no account needed. It is per report, so publishing one never exposes the rest of the site's history.

You choose what the reader sees, section by section. The score, issues, technical checks and performance are on by default; meta tags, content, the full link list and structured data start off, because those can carry internal URLs and staging paths you never meant to hand over. Anything switched off is stripped on the server, so it is not merely hidden — it never reaches the page.

#Exporting

Export report opens a print-ready version of the audit — headline score, summary, issues, technical checks and performance opportunities, laid out for paper. Print it or save it as a PDF from your browser's dialog to hand a client something self-contained.

#History

Every audit is kept. The history table under the report lists past runs with their score and issue count, so you can confirm a fix moved the number and see when a regression crept in. Click a row to open that report.