How we build — and what we will not ship
Written by Vigen G. Architecture, trust format, indexing rules, hard limits.
1. Product face
The homepage is the Lab of instruments — compressors, removers, converters, timers — not an AI chat wrapper. If a feature is expensive or experimental, it gets its own URL and may stay noindex until it earns trust. We do not build the brand around SEO articles.
2. Zero-upload architecture
Files are read with the File API, processed with Canvas / WebAssembly / pdf-lib in memory, and downloaded back to you. There is no file upload API for tool payloads. Analytics, if present, do not receive your documents. Details: Lab Note — Why zero upload and Privacy Policy.
Experience
Notes describe what broke, what we refused, and how the UI was shaped by real workflows — freelancers, sellers, developers.
Expertise
Presets and math must match the UI. A page that only changes a title word without different logic does not publish.
Authority
Named founder, About, Methodology, Lab Notes. Organization schema points to a Person — not an anonymous “team.”
Trust
Disclaimer of limits, no medical/legal guarantees, no clickbait. Privacy claims must match the architecture.
3. Trust format: Lab Notes, not a Blog farm
Default voice is founder field notes. We do not open a high-volume Blog for keywords. Docs appear when a tool needs operational how-to. Blog posts, if ever, are rare and case-driven.
4. PSEO discipline
- Uniqueness through logic and data (presets, rates, formulas, widget state) — not rewrite.
- Large offline matrices are fine; only an allowlisted best layer enters the sitemap.
- Pilot first. Valve about 50–100 new indexable URLs per day after GSC looks healthy.
- Sitemap is primary discovery. Indexing API accelerates; it does not replace quality.
5. Link hierarchy
Traffic pages point up to hubs and sideways into the matching tool. Pillars point down into the best traffic and into products. No orphan PSEO. AI or experimental URLs must not drain internal links away from tools and Lab.
Disclaimer. VeloTools provides browser utilities for files and focus. Outputs are not certified for regulated use. We do not diagnose health, law, or tax outcomes. If a claim cannot be verified in the product UI, it does not belong on the page.