Search Intelligence

What the tools check

• Website SEO audit A sample of up to ten pages of one website: how each one answers, whether it may be indexed, and what it declares.
• Indexability and canonical checker Whether a page can be crawled and indexed, and which address it names as canonical.
• Structured data checker The structured data a page declares, or JSON-LD you paste: its types, and the properties Google requires and recommends.
• Hreflang checker The language versions a page names with hreflang, and whether each one answers, names the page back and may be indexed.
• AI crawler checker Which AI crawlers robots.txt lets fetch a page, what each one is for, and what the page itself tells AI features.

Each finding belongs to one of three groups, the same in every tool:

Surface

What a person following the address meets: the answer, the redirects, the secure connection.

Structure

What the page and its headers declare to a machine.

Presence

Whether search engines may crawl the page, index it and find it.

What a public scan cannot see

A scan reads what any visitor could fetch. What only the site’s owner can see stays out of reach:

• Your analytics: who visits, from where, and what they do.
• Search Console: what Google has crawled, indexed and shown, and for which searches.
• Rankings: where a page appears for a search, which differs by place, device and person.
• Server logs: which crawlers came, and what they asked for.
• Enquiries, calls and sales: whether a page brings in business.
• What Google decides: a page that can be indexed may still not be, and Google may choose another canonical.

How TULUS approaches it

A machine checks what it can read. A person evaluates what that evidence means: whether a warning matters for this business, and what to change first. The checks here are the first half. The second is the work we call Search Presence Engineering.

How Search Presence Engineering works