Technical tab
The Technical tab checks HTTPS, robots, canonical, security headers, cloaking, and the detected technology stack.
The Technical tab covers the server- and markup-level signals that affect how a page is crawled, secured, and trusted. These checks decide whether a page can be reached and rendered at all, and whether what a bot sees matches what a browser sees. A content-level audit cannot surface these problems.
Technical signals
A field grid reports each signal with a status:
- HTTPS, Robots — index, Robots — follow, and Canonical URL — the core crawl and index directives
- Hreflang, Mobile viewport, and Character encoding
- HSTS — whether a
Strict-Transport-Securityheader is present - Security headers — how many of the recommended headers are set, and which are missing
- AI crawler visibility — a cloaking and render-parity check (see below)
AI crawler visibility
This check compares what the page serves to a bot over a raw HTTP fetch against what it renders in a browser. It reports a divergence score from 0 to 100 where 0 is healthy (the two match). A high score means significant content appears only after JavaScript runs. That content may never be seen by LLM crawlers such as GPTBot, Claude, and PerplexityBot, or by Googlebot's first render wave. An expandable static-vs-browser evidence table breaks the gap down by SEO-weighted signal: words, headings, schema, links, and images.
A large static-vs-browser gap is usually a render problem, not deliberate cloaking. It is key content that only exists after JS execution. Either way the effect is the same: crawlers that read raw HTML miss it. Serving that content in the initial HTML (SSR or pre-rendering) is the fix.
Technology stack
A technology stack card lists the detected frameworks, CMS, plugins, analytics, CDN, and libraries, grouped by category with a confidence score. It is the same detection surfaced as "Built with" on the Metadata tab. Here it is shown in full.
On paid tiers, the Technical AI Audit reviews these signals and prioritizes fixes.
