Page checks with DataSEO
/search
API with
type: deep
Illustrative workflow. Inspect URLs and crawl websites to investigate metadata, page status, links and technical checks. Use browser-based analysis only where the selected route and site require it.
Choose a URL or a crawl
Instant page analysis starts with a URL. A site crawl uses task-based collection with a target and crawl limits; confirm the scope before submitting a large site.
Inspect response status, page title, description, canonical signals and available content checks. Investigate the affected URL before treating every warning as a ranking issue.
Use crawl results to review internal links and broken destinations. A blocked or unreachable page may be a crawl limitation rather than a deleted page.
Review status and metadata
Sites that rely on JavaScript may need browser-based collection. Rendering and Lighthouse routes have different setup and processing requirements from a basic HTML check.
Inspect the link structure
Choose rendering deliberately
Lighthouse is a lab measurement for a particular run. It is not a substitute for real-user Core Web Vitals, and results vary with the page and test conditions.
- Keep the original crawl settings and compare affected URLs after a fix. Record the status, check name and observation date so the report explains what changed.
- Instant page analysis starts with a URL. A site crawl uses task-based collection with a target and crawl limits; confirm the scope before submitting a large site.
- Inspect response status, page title, description, canonical signals and available content checks. Investigate the affected URL before treating every warning as a ranking issue.
- Use crawl results to review internal links and broken destinations. A blocked or unreachable page may be a crawl limitation rather than a deleted page.
Sites that rely on JavaScript may need browser-based collection. Rendering and Lighthouse routes have different setup and processing requirements from a basic HTML check.
Separate lab and field performance
Verify after remediation
Lighthouse is a lab measurement for a particular run. It is not a substitute for real-user Core Web Vitals, and results vary with the page and test conditions.
Workflow example
Keep the original crawl settings and compare affected URLs after a fix. Record the status, check name and observation date so the report explains what changed.Choose a URL or a crawl
Instant page analysis starts with a URL. A site crawl uses task-based collection with a target and crawl limits; confirm the scope before submitting a large site.Review status and metadata
Inspect response status, page title, description, canonical signals and available content checks. Investigate the affected URL before treating every warning as a ranking issue.Inspect the link structure
Choose rendering deliberately
Use crawl results to review internal links and broken destinations. A blocked or unreachable page may be a crawl limitation rather than a deleted page.
- Sites that rely on JavaScript may need browser-based collection. Rendering and Lighthouse routes have different setup and processing requirements from a basic HTML check.
- SERP data: P50 7.1 seconds and P95 11.1 seconds.
Separate lab and field performance
Verify after remediation
- Lighthouse is a lab measurement for a particular run. It is not a substitute for real-user Core Web Vitals, and results vary with the page and test conditions.
- Keep the original crawl settings and compare affected URLs after a fix. Record the status, check name and observation date so the report explains what changed.
- Instant page analysis starts with a URL. A site crawl uses task-based collection with a target and crawl limits; confirm the scope before submitting a large site.
- Inspect response status, page title, description, canonical signals and available content checks. Investigate the affected URL before treating every warning as a ranking issue.