Skip to content
Feature

Technical SEO

Technical SEO covers the signals that help crawlers access and render your site. SiteScore reports the technical signals observable from the browser, and clearly distinguishes them from server-side or search-engine-only data.

What this feature checks

7 checks in this category. Every check links to the source markup it inspects.

HTTPS

Protocol, certificate presence, and mixed-content flags.

Mobile viewport

Viewport meta tag and basic responsiveness indicators.

robots.txt

Fetches and surfaces the site’s robots.txt for review.

Canonical & hreflang

Presence and validity of canonical and alternate link tags.

Render-blocking resources

Identifies synchronous scripts and stylesheets in the head.

Image loading attributes

Detects loading="lazy" and decoding hints.

Structured data presence

Flags whether JSON-LD or microdata is present.

How the analysis works

How SiteScore inspects technical seo

A straightforward look at what happens when you run this analysis.

  1. 1

    SiteScore reads the document’s protocol, headers available to the browser, and head tags.

  2. 2

    Where possible it fetches related files such as robots.txt for inline review.

  3. 3

    Findings distinguish what is observable in-browser from what would require server or search-console access.

SiteScore v3.0 Side Panel InspectionLive In-Browser Audit
SiteScore Side Panel: Protocol, TTFB, mixed content, and viewport diagnostics.
SiteScore Side Panel: Protocol, TTFB, mixed content, and viewport diagnostics.
Example findings

What a finding looks like

Each finding includes severity, observed evidence, and a suggested fix. The data below is labeled sample data.

Mixed content detected

3 subresources loaded over http:// on an https:// page.

Critical
Suggested remediation

Update all asset, image, and script URLs to use https://.

Viewport meta tag missing

No <meta name="viewport"> element found.

Warning
Suggested remediation

Add a viewport meta tag so the page renders correctly on mobile devices.

Honest limits

Evidence and limitations

  • Server response headers (e.g., Cache-Control, X-Robots-Tag) are not fully visible to the browser.
  • Crawl stats, index status, and Core Web Vitals field data require Search Console and cannot be reported locally.
  • robots.txt is fetched but not interpreted for crawl directives enforced by search engines.
Practical guidance

How to act on findings

Treat each finding as a starting point. Use the evidence panel to locate the relevant markup, apply the suggested fix, then re-run the analysis to confirm the issue is resolved.

Severity is a guide, not a rule. A warning that affects your primary content may matter more than a critical issue on a low-traffic page.

Combine SiteScore with official tools — Search Console, the Rich Results Test, and PageSpeed Insights — for a complete picture.

FAQ

Technical SEO questions

Run technical seo on your page

Install the SiteScore Chrome extension and analyze the page you have open right now.