Website progress

Current Altiatech site structure

This tracker reflects the latest live build, including the current service architecture, partner propositions, internal reference pages and all published case studies.

Reviewed against the live staging site on 12 July 2026. “In progress” pages are live but still require final launch QA.

28 added 3 in progress 5 to work
Quick jump

Showing all pages.

Case studies

Published delivery examples
British Land /british-land
Communications and mobile device management modernisation.
Added
Birmingham City Council /birmingham-city-council
Endpoint security and EDR across a large local authority environment.
Added
Bank of England /bank-of-england
Microsoft SaaS integration within a wider cloud programme.
Added
Scott Dunn /scott-dunn
Digital development and systems integration for luxury travel.
Added
Royal Holloway, University of London /royal-holloway---university-of-london
Surface device programme for education and productivity.
Added
Premium Credit /premium-credit
Long-term cloud, security and digital transformation programme.
Added
Peter Brett Associates LLP /peter-brett-associates-llp
Centralised Exchange upgrade and resilience improvement.
Added
NHS Foundation Trust /nhs-foundation-trust
SCCM proof of concept for a distributed NHS estate.
Added
Lovell Group /lovell-group
System Center proof of concept for IT management improvement.
Added
Investec /investec
Parallels Mac Management implementation and rollout planning.
Added
Dick Lovett Group /dick-lovett-group
Multi-site automotive technology transformation.
Added
British Red Cross /british-red-cross
Windows endpoint modernisation across a distributed charity estate.
Added
University of London /university-of-london
Microsoft Teams Direct Routing and unified communications.
Added
Chartered Institute of Management Accountants /chartered-institute-of-management-accountants
Global managed services, Microsoft 365 and resilience programme.
Added
University of Suffolk /university-of-suffolk
Windows upgrade and endpoint modernisation programme.
Added
No pages match that filter. Try a different keyword, category or status.
Altiatech staging website client review - 12 July 2026

Client-side launch review

Altiatech staging website audit

Review of the current staging site at spixelclientsite2.digital, completed 12 July 2026. The assessment focuses on what a client, procurement buyer, search engine and launch QA reviewer would notice.

29 live customer-facing pages mapped
15 published case studies
8 critical/high launch issues
5 recommended missing pages

Executive verdict

The site now has a strong enterprise structure, a coherent service proposition and an unusually substantial proof library. It feels much closer to launch than the old progress page suggested. However, it is not launch-ready yet because several global staging artefacts are exposed across the site, old and new versions coexist, and the navigation does not always send users to the correct hub page.

What is working well The current pages consistently reinforce the core proposition: modernise, secure, optimise and run IT reliably. The service architecture is clearer, ATRO gives the site a repeatable operating model, and the case studies provide strong enterprise and public-sector proof.

Critical launch blockers

1. Placeholder contact details are present in the global site structure 555-555-5555 / mymail@mailservice.com

These details appear in the shared page structure across the homepage, service pages, contact page and case studies. Even if hidden in one desktop state, they may surface in mobile navigation, accessibility output, search extraction or future edits. Remove them from the global Duda navigation/header source.

2. Internal approval notes are visible to visitors

The repeated assurance area includes wording such as “Accreditation and framework wording should be checked ... before final publication” and “G-Cloud 15 status to confirm”. Replace this with approved final wording or hide the entire assurance block until sign-off.

3. Archive and internal pages are exposed

The public page tree contains an ARCHIVE branch, old page versions, Copy of Home, old About pages and the Working Progress page. Internal build pages should be password-protected or noindexed. Superseded customer pages should be unpublished or redirected.

4. Duplicate live URLs create SEO and user-risk

Examples include /managed-services and /managed-services-v2 , /cloud-ai-enablement and /cloud-ai-enablement-v2 , plus old/new versions for AI Accelerator, Secure Identity, Managed Cyber Security, cost optimisation, About, Contact, Aquila and AltiaLaunchpad. Decide the final clean URL for each page, publish one canonical version and apply 301 redirects from all retired variants.

5. Case Studies has no true hub page

The top-level Case Studies route currently resolves to British Land, the first child page. Build /case-studies as a proper landing page and make the desktop and mobile top-level link point to it.

6. Top-level Services and Partners behaviour needs correction

The live navigation resolves Services to Managed Services rather than the Services Overview hub, and Partners resolves directly to Aquila rather than a partners overview. Top-level labels should link to /services and the chosen partners hub, with child pages beneath them.

7. Legal and privacy journeys are incomplete

No public Privacy Policy, Cookie Policy or Accessibility Statement was found. The contact form consent text is not linked to a privacy notice. Add the pages, link them in the footer and form, and test the cookie banner/preferences.

8. Contact form delivery needs end-to-end testing

Confirm required fields, validation, spam protection, success/error states, notification recipients, CRM routing and mobile usability. Add “End User & Productivity” and “Public Sector / Procurement” to the area-of-interest options.

Navigation, naming and consistency

Issue Client impact Recommended fix
High About is absent from the main top navigation Company credibility is harder to find. Add About to desktop/mobile navigation or place it clearly within Company.
Browser/page titles include internal suffixes such as “2”, “v2” and all-caps labels Looks unfinished and weakens search snippets. Rewrite every SEO title and Duda page label using final public names.
“CHATERED INSTITUTE...” typo Visible professionalism issue. Correct to “Chartered Institute of Management Accountants” in page name, navigation and metadata.
Aquila/Aquilla and AltiaLaunchpad/ALTIA LAUNCHPAD variants Brand naming appears inconsistent. Choose one approved spelling/capitalisation and apply it site-wide.
Footer omits About, Case Studies and legal links Weakens discovery and trust. Add Company, Proof and Legal link groups.

Case-study review

Template inconsistency

Most case studies use a clear client snapshot plus Challenge / Approach / Outcome structure. Scott Dunn and University of Suffolk use noticeably different heading systems and content architecture. Bring them into the approved reusable case-study template.

University of London naming mismatch

The navigation and URL say University of London, while the page headline describes City, University of London. Confirm the correct client identity and align the page title, slug, navigation label and metadata.

Historical technology needs date context

Several stories reference Windows 7, Windows 10, Exchange Server 2013 and Skype for Business. Add a project year or “historical programme” label so the evidence feels credible rather than outdated.

Claim approval

Obtain written client approval for quantified claims such as endpoint counts, user numbers, business growth and deployment scale. Keep a source sheet for every public metric.

Content and conversion

Homepage is comprehensive but overlong

The homepage repeats detailed explanations of ATRO, cloud and AI, optimisation, public sector, partners and Launchpad. Keep the strong proposition, but shorten repeated sections and move proof, client logos and selected case studies higher in the journey.

About page uses older positioning

The About page focuses on an “independent systems integrator” and a short HP/Cisco/Microsoft/Dell vendor list, while the new site positions Altiatech around managed services, cloud, AI, identity, cyber and optimisation. Refresh the page so it supports the new proposition without becoming long.

CTA language is mostly strong but should be standardised

Use a defined set of CTA patterns: “Book a scoping call”, “Discuss your requirement”, “Explore [service]” and “Start a conversation”. Standardise arrow characters and button treatment.

SEO and technical launch checks

  • Choose clean final URLs and implement 301 redirects from every old, copied, -v2 , -2 and -old URL.
  • Set self-referencing canonicals on final pages and noindex internal progress/visual-reference pages.
  • Regenerate the XML sitemap so it contains only final public URLs.
  • Write unique title tags and meta descriptions for all service and case-study pages.
  • Add Open Graph images and social titles for priority landing pages and case studies.
  • Add Organization, Service, BreadcrumbList and FAQPage structured data where appropriate.
  • Check that every navigation and footer link is identical on desktop and mobile.
  • Run broken-link, redirect-chain, 404, image-alt, heading-order and Core Web Vitals checks after URL cleanup.

Accessibility and performance

  • Several extracted images have generic or missing alternative text. Use meaningful alt text for informative imagery and empty alt text for decorative graphics.
  • Keyboard-test both desktop mega navigation and mobile navigation, including focus visibility and Escape behaviour.
  • Check colour contrast on translucent text, pills and cards against dark backgrounds.
  • Ensure all form errors are announced, labels remain visible and consent can be understood without relying on placeholder text.
  • Lazy-load below-the-fold images and logo strips, compress large hero assets and avoid loading duplicate archived page assets.
  • For the Premium Credit video, use a poster image, preload="metadata" or "none", captions where available and a transcript/summary.

Recommended order of work

  1. Remove dummy details and internal notes globally.
  2. Fix desktop/mobile top-level navigation and create the Case Studies hub.
  3. Choose final URLs, redirects, canonicals and archive rules.
  4. Add legal pages and complete contact-form/privacy testing.
  5. Correct naming, page titles, metadata and footer links.
  6. Standardise Scott Dunn and University of Suffolk case studies.
  7. Run responsive, accessibility, browser, performance and SEO crawl checks.
  8. Complete final client approval of claims, accreditations and framework status.

Current framework note

As of 12 July 2026, G-Cloud 14 remains the live agreement and has been extended to 28 October 2026. G-Cloud 15 applications are under review and the published expected live date is 17 September 2026. The staging wording should therefore remain carefully qualified until Altiatech’s award status is formally confirmed.