Spare Site CheckPUBLIC SAMPLE · OUR OWN WEBSITE · 17 SEPTEMBER 2026
A finding needs evidence.
This is an abbreviated sample based on actual checks of Spare’s public pages. It is not client work or a testimonial. Passing checks and uncertainties are recorded alongside issues.
Scope and method
Five public URLs were fetched over HTTPS. Page titles, descriptions, H1 counts and canonical URLs were read from the returned HTML. The advertiser page was also inspected in a browser at its default desktop viewport and at 390 × 844 CSS pixels. The mobile menu was opened and its expanded navigation observed. No forms were submitted and no purchase or login was tested.
1. Review needed: API entry metadata
Priority: low · Not a confirmed indexing defect
The public https://spare.cool/ai response was HTTP 200 with a canonical URL pointing to https://spare.cool, a general advertising description, and no H1 in the initial HTML. In the browser it subsequently navigated into the API console; the destination varied with the existing session. The console’s private contents were not inspected or included.
Impact: a crawler fetching the initial response receives different information from the eventual application destination. Whether this is a defect depends on whether the entry page is intended to be indexed.
Next check: confirm the intended index policy. If this is only a routing endpoint, use an appropriate redirect or explicit noindex policy. If it is intended as an indexable product page, give it product-specific content and metadata. Do not change the canonical without checking the final route.
Reproduce: fetch /ai without executing JavaScript and inspect the canonical and heading markup. Then open the same path in a browser and observe the navigation. This sample does not claim that Google indexed either page.
2. Passed: key public metadata
| Path | HTTP | H1 | Canonical |
|---|
| /en | 200 | 1 | Self |
| /en/advertisers | 200 | 1 | Self |
| /en/faq | 200 | 1 | Self |
| /en/ai-install | 200 | 1 | Self |
All four responses contained nonempty titles and descriptions. This is a basic presence check; it does not establish ranking quality, field performance or search-engine coverage.
3. Passed: observed mobile entry
At 390 × 844, the advertiser headline and primary campaign button were visible and readable, and the illustration fit the viewport. Opening Menu changed its state to expanded and exposed the Product, API services, download, iPhone, advertiser and help links. This observation covers that viewport and entry area, not every device or the full signup flow.
Not tested in this sample
- Real-device behavior, every page’s full mobile layout and keyboard flow
- Checkout completion, authenticated actions or form submissions
- Core Web Vitals field data, Lighthouse scores or performance under load
- Screen-reader compatibility or full WCAG conformance
- Source code, private application data or security vulnerabilities
An ordered review covers the stated five-page service scope and records its own timestamp, tests, evidence and limitations. It will not necessarily find a defect. This sample is intentionally shorter.