- Content & schema
- 50tests fired in this category
- modules
- 8dedicated content & schema checks
- every scan
- 299+tests across all categories
Why it matters
Content cannot compensate for a blocked sitemap, conflicting canonical, blank rendered DOM, unreachable page, or soft-404 response. FixWeb starts underneath the content so failures in a lower layer are not hidden by polished copy or metadata.
How it works
FixWeb checks robots.txt and sitemap availability, canonical and noindex agreement, rendered content and console errors, click depth and orphaning, redirect and 4xx integrity, JSON-LD validity, Organization and BreadcrumbList signals, HTTPS, HSTS, mobile layout, soft 404s, and field LCP, INP, and CLS when available.
Site impact
Technical conflicts can keep important URLs out of discovery or indexation, send crawlers to the wrong variant, or make users see a page different from the source markup. Structured data supports eligible features but does not guarantee them. HTTPS, mobile behavior, and Core Web Vitals affect trust and page experience, not rankings in isolation.
How to improve
Publish a 200 canonical-only sitemap and allow required assets. Use one deliberate canonical per content item, reserve noindex for intentional templates, keep key pages within three clicks, and repair orphaned or redirected links. Validate JSON-LD against visible content, enforce HTTPS and HSTS, return real 404s, and optimize field vitals on important templates.
