The business
A useful website audit needs to show where a finding came from. A list of scores alone is not enough to choose a repair or explain it to a business owner.
Internal Tool Evidence level · Delivered capability
Surveyor: website findings you can inspect
An internal technical-SEO crawler that turns page-level observations into a local report and exports for human review.
- Client
- DVlad — internal project
- Sector
- Website quality and technical SEO
- Role
- Audit workflow design, implementation and verification
- Period
- 2026 · internal development
- Services
- Technical website checks · SEO implementation · Website care
- Tools
- Python · HTTPX · SQLite · HTML and CSV reports
The real problem
Collect page-level observations, keep crawl behavior restrained, and make findings easy to inspect before recommending a change.
My responsibility
I built the local crawling, issue evaluation and reporting workflow. Client recommendations still require reviewing the findings in context.
- Public pages only, with robots exclusions, an identified crawler and rate limits.
- No JavaScript rendering, authenticated crawling, backlink index or keyword-volume database.
- A crawl result does not establish Core Web Vitals, search rankings or conversion impact.
What was built
The solution, in modules
01
Collect the observation
The crawler records page facts in a local database and evaluates them against a defined issue catalog.
02
Make the finding inspectable
A self-contained HTML report and page/issue CSV exports give the operator concrete locations to review.
03
Keep uncertainty visible
Pages that appear to need JavaScript rendering are marked for a rendered check. Reports are audit input, not an automatic recommendation or a claim that every defect has been found.
System view
From a website to a scoped fix
- 01
Define the crawl
Choose the site, page limit and allowed public scope.
- 02
Collect page facts
Respect crawl restrictions and keep the observations locally.
- 03
Review the findings
Inspect affected pages and distinguish defects from limits of the crawler.
- 04
Choose and verify a fix
Make a scoped change, then check the affected behavior again.
Inspectable proof
Proof you can inspect
Sanitized artifacts show the underlying work without exposing client identities, credentials, private dashboards, or customer data.
-
Local verification scope
Regression evidence for the crawler and reporting implementation, not a client audit or live search-performance result.
- Tests
- 9 passed
- Target
- Temporary local test fixtures
- Public requests during the test
- None
Evidence
What backs this up
-
Isolated regression suite, September 23, 2026
VerifiedNine automated tests passed against temporary local test fixtures. No public site was crawled for this verification.
-
Report formats
Project recordThe implementation produces a local database, self-contained HTML report, page export and issue export.
-
Business impact
PendingNo ranking, traffic, revenue or conversion improvement is inferred from a technical test pass.
Results & current state
What's true today
-
Findings have page-level context.
The report and CSV exports retain the collected page observations and affected locations.
-
Crawling and recommendation remain separate steps.
The tool reports observations and limitations; the operator reviews them before choosing work.
Need help finding the useful fixes on your site? Start with a short website brief.
Describe your setup in a few sentences. You'll get a plain answer about whether and how I can help.