Does your website crawler actually render JavaScript, or does it only inspect the HTML?
Modern websites are not always simple collections of static HTML pages.
JavaScript frameworks, dynamic navigation, client-side rendering, hydration problems, and dynamically generated internal links can make technical investigations more complicated.
A crawler that only collects raw HTML may not reveal every issue affecting a page.
SERPSpur approaches technical auditing with a Node.js and Headless Chromium crawling environment.
Its 140+ point website audit covers several important areas:
Technical SEO
HTTP status codes.
Redirect chains.
Canonical tags.
Heading hierarchy.
Internal and external links.
Structured data and JSON-LD.
Open Graph information.
Performance
Lighthouse v11 reporting.
LCP, INP, CLS, FCP, and TTI.
Mobile and desktop performance.
CrUX field information.
Rendering filmstrips.
Asset transfer sizes.
Image Optimisation
Broken images.
Missing ALT text.
Oversized image files.
Incorrect image dimensions.
Missing lazy loading.
WebP and AVIF opportunities.
Internal Linking
Orphan page detection.
Internal link graph analysis.
Competitor backlink gaps across up to four competing domains.
Security
SSL/TLS.
Mixed content.
CSP.
HSTS.
Referrer-Policy.
SRI.
Cookie security flags.
The platform also provides Site Strength, Website Health, security indicators, historical audit snapshots, and estimated monthly monetisation leak information.
Other integrated capabilities include keyword research, historical backlinks, seven-engine rankings, AI/GEO visibility, TAI™ traffic investigation, white-label reports, and a developer REST API.
I'm interested in hearing from technical SEOs: Which issue does your current crawler struggle to identify most often?
Top comments (0)