This website has been created specifically to serve as a controlled testing environment for the SiteScan analysis platform. Every page on this site is carefully crafted to trigger specific detection rules within our suite of automated SEO and accessibility analyzers. By maintaining a predictable set of issues, we can verify that each analyzer correctly identifies problems and generates appropriate warnings or errors in the final report.
The test site contains two categories of pages. The first category consists of clean baseline pages that follow all best practices for search engine optimization, accessibility, and structured data. These pages establish the statistical baseline that certain analyzers need, particularly the soft-404 detection system which compares page content length against the site median. The second category contains deliberately broken pages, each targeting one or more specific analyzer modules.
The following pages represent properly structured web content. They include correct heading hierarchies, appropriate meta descriptions, valid Open Graph tags, self-referencing canonical URLs, and sufficient content length. These seven pages form the statistical foundation that allows content-length-based analyzers to function correctly. Each baseline page contains between two hundred and four hundred words of unique descriptive text that differs substantially from all other pages on the site.
Each of these pages is intentionally designed with specific issues that should be detected by one or more SiteScan analyzers. The problems range from missing metadata and broken links to poor heading structure and invalid Open Graph implementations. Together they provide complete coverage across all thirteen active analyzer modules currently deployed in the platform.
Note: An orphan page (orphan-page.html) also exists on the server but is intentionally NOT linked from any page, to test analyzer 023 E01 detection.
These pages demonstrate the structured data generator. Only the wine tasting page has JSON-LD Event schema. The others contain rich event information (dates, prices, locations, organizers) that the generator can use to create structured data automatically.
When the SiteScan crawler processes this site, it follows every internal link starting from this homepage. The crawler collects page content, HTTP status codes, heading structures, meta tags, and all other relevant data into structured JSON files. These files are then passed through the analyzer pipeline, where each module examines the data for specific categories of issues. A successful test run should produce at least one warning or error from every active analyzer module.