McCaig's Tower structured visitor system case study

The McCaig's Tower project is an independent, unofficial visitor website. It is not affiliated with a council, tourism body, public authority, or the operators of the landmark.

The project addressed a familiar information problem. Visitor questions span history, access, events, location, language, and practical planning. If those answers are spread across loosely connected pages, both people and machines can struggle to establish which information applies.

The original problem

A useful visitor resource needs more than an attractive landmark page. It must separate durable facts from time-sensitive event details, express location clearly, support visitors in more than one language, and answer common questions without implying official authority.

The architecture therefore needed a controlled content boundary and explicit relationships between the landmark, its location, visitor information, and individual events.

The structured system

The implementation approach combines:

• structured event records rather than event details buried in prose;
• multilingual page architecture with deliberate content ownership;
• local search signals that describe real geographic relevance;
• crawlable visitor answers with clear headings and internal links;
• deterministic answers selected from approved knowledge;
• careful wording about the site's independent and unofficial status.

This structure allows one approved fact to be presented consistently in the relevant page, event record, metadata, and controlled answer without turning every surface into a separate source of truth.

What changed

The important change was architectural. Visitor information became easier to maintain as structured, related content rather than a collection of isolated answers. Events could carry their own dates and details. Language variants could be planned deliberately. The assistant could answer within an approved knowledge boundary and fall back when the source did not contain an answer.

No unsupported traffic, ranking, conversion, or AI citation metric is claimed for this project. Quantitative reporting would require dated analytics and search evidence from the site owner.

What can be generalised

The pattern applies to venues, attractions, event programmes, and organisations serving multilingual audiences. Separate durable facts from changing records, describe entities and locations precisely, and keep automated answers inside reviewed knowledge.

It does not follow that the same page structure or schema should be copied into every visitor website. The content model must reflect the real organisation, publishing process, and evidence available.

For related implementation, see web development in Edinburgh, Answer Engine Optimisation in Edinburgh, and the deterministic assistant.