Hreflang
HTML, XML sitemap and HTTP-header alternates, self references, reciprocal targets, indexability and canonical consistency.
Technical SEO · EN / ES / DE and beyond
Crawl a website and inspect hreflang, canonicals, indexability, redirects, duplicate content, sitemap coverage, orphan candidates, internal links, metadata and structured data — without a black-box SEO score.
Same-origin crawl · Language-balanced sitemap discovery · Live or staging-aware interpretation · Public HTTP/HTTPS targets · Up to 100 pages synchronous · 250–1,000 pages via background worker · Completed reports kept for 7 days
Audit results
—
Click any metric for an explanation and the URLs or checks behind that value.
Action plan
Multilingual intelligence
Coverage insights
SEO opportunities
Environment
Repeated patterns
URL normalization
Audit comparison
| Page | Lang | Hreflang | Canonical | Indexability | Issues |
|---|
What it checks
HTML, XML sitemap and HTTP-header alternates, self references, reciprocal targets, indexability and canonical consistency.
Missing and duplicate titles/descriptions with language-aware duplicate handling and low-severity display heuristics.
Missing, invalid or multiple canonical tags and pages that canonicalize elsewhere.
Open Graph and Twitter/X metadata plus image URL, status, content type, detectable dimensions and explicit check coverage.
robots.txt rules, sitemap discovery, crawl coverage, orphan candidates, crawl depth, contextual links and independent checks for uncrawled link targets.
JSON-LD syntax parsing, discovered schema types and cautious semantic checks for common rich-result structures.
Exact body-content duplicates, conservative language detection, H1 structure, thin-content heuristics and missing image alt attributes.
Redirect chains, temporary redirects, sitemap redirects, host aliases and same-host links using a different scheme or port.
Repeated issue root causes, canonical-preferred host inference, and the sitemap, internal-link, hreflang, canonical, redirect or start signal that brought each URL into the audit.
Compare a previous CSV or JSON export locally to see new and fixed issues, added or removed pages, and important metadata changes. JSON gives the most precise issue matching.
Mark pre-launch audits as staging, treat intentional noindex/robots protection as expected, and compare staging paths to production even when the hostname changes.