# Adventise website: observed content audit

Date: 25 September 2026
Project: Adventise's own website. This is first-party site evidence, not a client performance case study.

## Method

Inspect all 2,896 locally generated HTML artifacts except internal error artifacts. Extract main content, metadata and links. Traverse ordinary HTML anchors from the homepage, resolving configured redirects. Compare representative live pages; 49 public URL requests were made, including sitemaps and two exploratory URLs that were not internal-link defects.

## Finding 1 — incomplete discovery paths

Baseline: 1,215 indexable registry routes were outside the homepage-reachable local anchor graph: 719 location routes, 469 industry/service routes and 27 location/industry/service routes.

Proposed action: expose supported markets and industries through browseable alphabetical directories and link those directories from the existing hubs. Preserve URLs. Repeat the same graph traversal after a production build.

Acceptance: each retained indexable registry route is reachable through an ordinary anchor path or has a documented dynamic-route exception independently checked over HTTP.

## Finding 2 — enquiry mismatch

Observation: the site advertised PPC, content and web design, but the contact form focused on link building and Maps. A service query could preselect the wrong option.

Proposed action: use one shared service vocabulary in contact choices, URL preselection and notification labels. Separate a general marketing review from the dedicated local SEO intake.

Acceptance: each advertised service has a corresponding selectable topic; legacy query parameters resolve to a sensible topic; pending and confirmation text accurately describe a submitted enquiry.

## Finding 3 — overstated local timing

Observation: a local SEO FAQ claimed Maps dominance within 30–60 days.

Proposed action: replace fixed ranking expectations with scope, implementation milestones and measurement caveats. Add Business Profile eligibility before discussing setup or verification.

Acceptance: rendered copy and shared service data contain no fixed Maps-position promise.

## Limits

This audit did not measure Google-selected canonicals, rankings, Search Console indexation, traffic, qualified leads or revenue. Sitemap inclusion and a clean HTML graph do not establish those outcomes. Repeated paragraphs are an editorial diagnostic, not a Google policy verdict. The implementation case study records subsequent technical checks separately.