Technical checks should verify what search engines and users can actually access, not assume that a markup type or tool guarantees visibility.
Movie structured data
Evidence required: rendered page markup, visible film details, and the applicable structured-data documentation. Pass or fail: pass when markup is valid, supported, and consistent with visible content; fail when required properties are missing, values conflict with the page, or markup describes content the user cannot see.
Severity: high when the mismatch affects important film or venue information. Owner: web engineering or the team that controls templates. Corrective action: repair the generator or template so markup reflects the page source of truth. Validation: retest the rendered page and compare structured values with the live film page.
Event structured data
Evidence required: special-screening or festival pages, visible dates and venue details, and rendered markup. Pass or fail: pass when eligible event information is represented accurately; fail when dates, venue, status, or ticket details are stale or inconsistent.
Severity: high for active events. Owner: events marketing with engineering support. Corrective action: update the event page and the system that generates its markup. Validation: inspect the live page and test the rendered structured data without promising a rich result.
Mobile booking performance
Evidence required: real-device testing, page performance diagnostics, network behavior, and the path from film discovery to ticket selection. Pass or fail: pass when core pages load reliably and the ticket path remains usable; fail when slow assets, scripts, or handoffs block or materially delay the transaction.
Severity: critical when users cannot complete the booking journey. Owner: engineering and ticketing platform owners. Corrective action: remove avoidable bottlenecks, compress assets, and address third-party failures where the theater has control. Validation: retest on representative mobile devices and connections.
URL and crawl hygiene
Evidence required: crawl export, canonical targets, indexation signals, and examples of film and location URLs, including the preserved example /movies/film-title route. Pass or fail: pass when important pages have stable, readable URLs and unnecessary parameters do not create duplicate crawl paths; fail when session-based or duplicate URLs fragment discovery.
Severity: medium to high depending on scope. Owner: web engineering. Corrective action: standardize route patterns, canonical handling, and internal links at the template level. Validation: crawl the site again and confirm representative URLs resolve as intended.
Expired film pages and 404 handling
Evidence required: crawl errors, traffic or links to expired film URLs, current navigation, and the purpose of each retired page. Pass or fail: pass when an expired page remains useful, redirects to a genuinely relevant successor, or returns the correct status when no replacement exists; fail when users or crawlers land on broken or misleading destinations.
Severity: medium, rising when important inbound links or active user paths are affected. Owner: web content with engineering support. Corrective action: choose the correct disposition page by page instead of redirecting every retired film to a generic destination. Validation: recrawl affected URLs and test representative external and internal links.