Technical audit worksheet

Technical SEO Audit: Crawl, Render, Index, Measure

Review the technical path from URL discovery through rendering, canonicalization, indexation, performance, and monitoring.

Build your audit action list

Record your findings, evidence and next checks. This worksheet does not crawl a website. Your inputs stay in this browser.

Report nameReporting periodComparison period and filters

Summary: what changed and what decision is needed?

Finding 1

Affected URLfindingseverityevidenceactionownerverification

Work completedNext actions and ownersSources, filters, annotations and limitations

Preview the report

SEO report
Period: Not supplied
Comparison: Not supplied

SUMMARY
No summary supplied.

AUDIT FINDINGS
1. Untitled finding
URL: 
Priority: Review
Evidence: 
Action: 
Owner: 
Verification: 

WORK COMPLETED
Not supplied.

NEXT ACTIONS
Not supplied.

SOURCES, FILTERS AND LIMITATIONS
Not supplied.

Prepared with RankCrab's free report builder. Values and conclusions are supplied by the author; no live crawl, rank check or causal analysis was performed.

Technical SEO asks whether search systems can reliably find, interpret, choose, and revisit the right URLs. Test the system at template scale and verify with search-engine data.

Map the URL state machine

For each representative URL, record discovery path, status, redirect chain, canonical target, robots directives, rendered content, and indexed state. These signals should agree.

Test templates and edge cases

Sample pagination, filters, empty results, removed products, international variants, JavaScript states, and malformed parameters—not just the homepage.

Separate crawl data from index truth

A crawler shows what your tool observed. Confirm indexing and search behavior with Search Console, manual inspection, server logs where available, and controlled tests.

Questions & answers

How often should I repeat this process?

Repeat it after major releases or migrations and on a regular cadence for pages that drive leads or revenue. Monthly is useful for active sites; quarterly may be enough for small, stable sites.

Which issue should I fix first?

Prioritize blockers that prevent crawling, indexing, rendering, or conversion. Then work from high-value pages and broadly repeated template issues down to isolated cosmetic improvements.