Skip to content
enChange language
Open menu

Audit engine

Find what limits your organic growth — and prove it

SEO Masterize audits your site across crawling, indexing, rendering, structured data, performance and AI-search readiness. Every finding shows the evidence it came from, how confident we are, and how to verify the fix.

Free initial check. Nothing is changed on your site.

The free check inspects one URL over HTTP: crawling, indexing, on-page, structured data, internationalisation and AI-readiness. Rendering and Core Web Vitals need a real browser, so the free check reports them as not measured rather than guessing. The paid audit runs those.

See a finding in full

What makes a finding trustworthy

  • Evidence attached to every finding
  • A stated confidence level
  • A fix you can actually apply
  • An acceptance test you can re-run

What is an organic growth audit?

An organic growth audit is a structured inspection of the things that decide whether search engines and AI answer engines can find, understand and trust a website. It covers whether pages can be crawled and indexed, whether the rendered page matches what the server sent, whether structured data is valid and matches visible content, how the site performs on real devices, and whether the content answers the question a person actually asked. A useful audit does not stop at a list of problems: it shows the evidence behind each one and tells you how to confirm the fix worked.

How it works

  1. 01

    Give us the address

    We check the URL is reachable and safe to crawl before anything is charged. If a firewall blocks us, you find out then — not after paying.

  2. 02

    We collect, then we judge

    Deterministic rules run first, over evidence we actually captured. When a model is configured, it only writes the explanation — from a finding that already passed, quoting the evidence it was given. Every finding says which words are its own and which come from our rule catalogue.

  3. 03

    You fix, we re-verify

    Each finding carries an acceptance test. Re-run it after you deploy and the status changes because the rule passed, not because someone ticked a box.

One finding, in full

This is the unit of value. Not a count of problems — one problem, with the material it rests on.

See every finding on this site, live

INDEX.CANONICAL.PRESENT

Canonical points to a URL that redirects

/products/wireless-headphones

HighObserved

Evidence

GET /products/wireless-headphones          200
  <link rel="canonical" href="/p/wireless-headphones">

GET /p/wireless-headphones                 301 → /products/wireless-headphones

canonical target resolves in 1 hop, not 0

Confidence

95%
95%

Google Search Central — canonicalization

Why it matters

A canonical is a hint about which URL should be indexed. When it points at a redirect, the signal is ambiguous: the destination has to be resolved before the hint can be honoured, and consolidation of ranking signals is left to chance. On a template that repeats across a catalogue, one mistake becomes thousands.

How to fix

Point the canonical directly at the final 200 URL. In most template engines the canonical is built from a stored slug that was never updated after the product URL changed — fix it at the source, not per page.

How to verify

Request the page again and confirm the canonical target returns 200 with no redirect hop.

What we audit

Every dimension produces findings with evidence, or reports honestly that it could not be measured.

Crawling and indexing
Status codes, redirect chains, canonicals, robots directives, sitemaps, and whether the pages you care about can actually be reached.
Rendering
What the server sends compared with what a browser ends up with. Content that only exists after JavaScript runs is content a crawler may never see.
Structured data
Valid JSON-LD that matches the visible content. Markup describing something the user cannot see is a policy violation, not an optimisation.
Performance and experience
Largest Contentful Paint, layout shift and page weight, measured in a real browser on a throttled connection. Lab measurements, and labelled as such — this product connects to no external data source, so it has no field data and does not pretend to.
On-page structure
Title, description, headings and whether the page states its subject where a reader and a parser both find it.
AI-search readiness
Whether your pages state their claims clearly enough to be quoted, and whether your entity is consistent across the site.
International
Whether each page declares the language it is written in, where a reader's browser and a search engine both look for it. hreflang reciprocity and x-default are not audited yet — see the methodology page, which lists what is live and what is not.
Transport and access
Whether the page is served over HTTPS, and whether what came back is your page or a refusal from something in front of it.
Trust signals
Whether the page says who wrote it, when it was written, and how to reach you. What a reader can check — never a judgement about whether to believe you.

Questions people actually ask

Does the audit change my site?

No. The crawler only reads. It never submits forms, never logs in, never posts, and never follows an action that would alter state. Nothing we do requires write access to anything you own.

Do I need to install anything?

No. A public URL is enough, and it is all we use. We do not connect to Search Console, Analytics or anything else — everything in a report was observed from outside your site, the way a search engine sees it.

Will this guarantee better rankings?

No, and any tool that promises it is lying. We can tell you what is broken, how confident we are, and how to prove the fix landed. Ranking depends on competitors, intent and systems nobody outside the search engine can observe.

What is GEO, and is it different from SEO?

GEO — generative engine optimisation — is about being findable and quotable inside AI answers rather than only in a list of links. In practice it rests on the same foundations as SEO: content that can be crawled, understood and trusted. It is a different surface, not a different discipline, and no one can guarantee a citation in an AI answer.

What if my site blocks crawlers?

We detect that before charging you. A firewall challenge is reported as 'could not be measured', never as a problem with your site — reporting a bot wall as a missing title would be a false finding, and we treat those as defects.

Is my free check private?

The free check stores no report of the site you check. Your result is rendered once, in the response to your own request, and the page carries a noindex directive so it never enters a search index. One thing is written down: a one-way fingerprint of the address you came from — an HMAC, never the address itself — in a single row that counts the 3 checks per hour you are allowed. Every copy of this site shares that row, which is what makes the published number the real one, and it is deleted when your hour closes. A stored report is a different thing, and the difference is the point: it belongs to the account that paid for it, no other account can read it, and a share link is revocable and can be given an expiry. If you have never signed in, there is no stored report of yours to ask about, and that fingerprint is the only thing this site has held.

Start with the free check

One URL, real findings, no card. If the paid audit is not obviously worth it after that, do not buy it.

Analyse my siteRead the methodology first