Skip to content
ToolCargo

Site Audit · for agencies & freelancers

Pre-launch checks for the client sites you manage.

Catch a stray noindex, a canonical pointing at staging, broken links or a missing link preview before your client does. Run checks in the browser or from your AI assistant, re-run after fixes, compare, and hand over a clean report.

  • ✓ Free: 50 checks a month, no card
  • ✓ Saved history, before/after compare
  • ✓ Printable client report
  • ✓ Tested with Claude Code and Claude (claude.ai)
site-audit · audit_page

Enter any public page. This runs the same engine your assistant calls — live, not a recording.

Who it helps

Small teams responsible for several client websites.

Web studios, freelance developers and marketers who launch, redesign or migrate client sites — and need a quick, repeatable check of the things that quietly break search visibility and sharing. If you already pay for a full SEO suite for keyword data, this is the fast pre-launch pass, not a replacement.

What it checks on each page

  • Indexing blockersnoindex in meta or headers, robots.txt rules, canonical pointing elsewhere
  • Titles & snippetsmissing, duplicated or truncated titles and meta descriptions
  • Link previewsOpen Graph / X tags and whether the preview image loads, its size and type
  • Broken links404s, unreachable hosts and redirect chains on a page
  • Structured dataJSON-LD that doesn't parse or misses basic properties for its type
  • Page basicsstatus, redirects, h1, alt text, language, viewport, hreflang, HTTPS

What it doesn't do

  • Checks one page at a time from the HTML the server sends — it doesn't crawl sites or run JavaScript.
  • No rankings, traffic, keyword data or Core Web Vitals, and it can't tell you whether Google has indexed a page.
  • Sites behind bot protection may block us; the report says “blocked” instead of pretending to audit.
  • Private, staging-behind-VPN and localhost URLs are refused by design.

Example report

What a report looks like

Real output of audit_page for https://example.com/ (a reserved demonstration domain), run on 11 September 2026. It's an example, not a customer's site. Every issue shows the evidence we saw, why it matters and what to change.

Score
76/100
High
0
Medium
4
Low
4
Passed
6

Audit completed (HTTP 200).

To fix (8)

  • MediumNo canonical link

    Evidence: No <link rel="canonical"> in the served HTML

    Why it matters: The canonical tells search engines which URL to index. A missing, relative or conflicting one can split or misdirect indexing.

    Fix: Add <link rel="canonical" href="https://example.com/"> (or the preferred URL).

  • MediumTitle is only 14 characters

    Evidence: Example Domain

    Why it matters: The title is the main headline in search results and browser tabs; missing or truncated titles lose clicks.

    Fix: Describe the page's topic more specifically.

  • MediumMissing meta description

    Evidence: No <meta name="description"> tag in the served HTML

    Why it matters: Search engines often use it as the snippet under the title; without one they pick text themselves.

    Fix: Add a 70–160 character summary; search engines may use it as the snippet.

  • MediumNo Open Graph tags

    Evidence: None of og:title, og:description, og:image, og:url found

    Why it matters: Social platforms and chat apps build link previews from Open Graph tags; without them previews are plain or wrong.

    Fix: Add og:title, og:description, og:image and og:url so links render as rich cards.

  • LowAbout 17 words of text in the HTML

    Evidence: 17 words of visible text in the served HTML (before any JavaScript runs)

    Why it matters: If the served HTML contains little text, crawlers that don't run JavaScript see an almost empty page.

    Fix: If the content is rendered by JavaScript, use server-side rendering or pre-rendering so crawlers see it; otherwise add substantive text.

  • LowNo twitter:card tag

    Evidence: No <meta name="twitter:card"> tag

    Why it matters: X uses twitter:card to decide between a small and a large preview.

    Fix: Add <meta name="twitter:card" content="summary_large_image"> for large previews on X.

  • LowNo structured data found

    Evidence: No JSON-LD blocks and no microdata in the served HTML

    Why it matters: Structured data can make pages eligible for richer search results when it matches visible content.

    Fix: Consider JSON-LD for your organisation, products, articles or breadcrumbs where it matches visible content.

  • LowMissing headers: HSTS, X-Content-Type-Options, Content-Security-Policy, Referrer-Policy

    Evidence: Not a ranking factor; listed as hygiene.

    Why it matters: These headers reduce common browser attack risks. They are hygiene, not a ranking factor.

Severity rule. High: blocks indexing, sharing or the page itself. Medium: likely reduces visibility, click-through or preview quality. Low: best practice or hygiene; fix when convenient.

Scope. This is a check of one page's served HTML and response headers. Not checked: content rendered by JavaScript, Core Web Vitals and real-user speed, rankings, traffic or keywords, whether Google has actually indexed the page, other pages on the site (no crawling). The score is a heuristic (high −12, medium −5, low −1), not a ranking prediction.

Built for the fix-and-check loop

  1. Step 1

    Audit

    Paste a URL in the browser, or ask your assistant to audit it. Every run is saved to your private history.

  2. Step 2

    Fix

    Work down the list — high impact first. Each item says what we saw and what to change.

  3. Step 3

    Re-run & compare

    One click re-runs the page and shows what was fixed, what's new and what's still left.

  4. Step 4

    Share

    Print or save a clean PDF report, or download Markdown to paste into a ticket or client email.

From your AI assistant (MCP)

Or ask Claude to run the checks for you

Connect once, then ask in plain language. Four focused tools; results land in the same history.

audit_page

Audit a page

Fetch one public URL and check status, redirects, title, meta description, canonical, noindex, headings, image alt text, Open Graph tags, JSON-LD structured data, hreflang and HTTPS headers. Returns prioritised findings with fixes.

check_links

Check links on a page

Extract the links on a public page and test each one (HEAD, falling back to GET). Reports broken links, unreachable hosts and redirects that should be updated.

check_crawl_rules

Check crawl and index rules

Evaluate robots.txt for a given crawler, meta robots and X-Robots-Tag, the canonical link, and whether the URL appears in the site's XML sitemap. Answers: can this page be indexed?

check_social_preview

Check the social link preview

Read Open Graph and Twitter card tags, fetch the preview image and check its type, size and dimensions. Shows what a shared link card will be built from.

Tested with Claude Code, Claude (claude.ai), MCP Inspector. Other clients are documented but not yet tested — see client setup.

More connectors are planned, not built

Listed so you can tell us what to build next. None is available yet.

Request a connector

Try it on a client page today

Free plan, no card. Paid plans aren't on sale yet.

Create free account