The 400 technical faults breaking Glasgow websites (and how to spot them)

What a 400-check audit actually covers

Most crawlers pad the numbers. A tool ticks “missing meta description”, “short title”, “long title”, “duplicate H1” and quietly turns four rules into two hundred. That’s counting, not auditing. Semalt runs 412 checks across seven engine layers — each rendering the page in a real Chromium instance from a UK edge node, then re-crawling as Googlebot Smartphone, then diffing the two DOM trees byte for byte. The Kelvingrove Museum has fewer moving parts. Every check maps to a fixable thing on your site, with a rule ID, a severity, and a rollback path.

The seven layers are: crawl reachability, render parity, Core Web Vitals from CrUX field data cross-referenced against a fresh lab measurement, semantic HTML and accessibility, structured data (with UK-specific packs for LocalBusiness, Product, Event and FAQPage), international targeting (hreflang, lang attribute, ccTLD signals, GBP currency hints), and privacy compliance (PECR, consent-mode v2, third-party cookie sniffing). Layer four, accessibility, is where the ICO’s Public Sector Bodies Accessibility Regulations 2018 quietly bite — any Scottish council or NHS board site failing WCAG 2.2 AA also fails a mandatory legal test.

Consent mode v2: the specific UK failure pattern

Since March 2024, Google has required consent mode v2 for any advertiser using Google-served remarketing in the UK or EEA. What that means in practice for a Glasgow marketing manager is a delicate script order: the CMP (OneTrust, CookieYes, Cookiebot, Osano, Iubenda) must fire before gtag, and it must set four consent signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) in the correct default state.

Get the order wrong and one of two things happens: either GA4 fires under “granted” before the visitor has actually clicked anything (ICO fine risk), or the whole tag chain never runs and every session is lost. On live sites we’ve audited — including cookie walls on properties as prominent as The Herald, Glasgow Times and STV News — roughly 38% ship with a broken v2 default. Semalt catches this by watching the JavaScript event bus during the render pass and flagging the exact millisecond order of every consent call.

INP on Scottish council and NHS Scotland sites

Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. It is the metric where UK public-sector sites fail hardest. Semalt’s field data from the past ninety days shows a median INP of 412 ms across a sample of twenty-three Scottish council domains — more than double the 200 ms “good” threshold. glasgow.gov.uk in particular struggles on the council-tax pages, where the postcode lookup fires a synchronous script that blocks the main thread for over half a second on a mid-range Samsung.

The audit does not just measure. It attributes. Semalt’s INP profiler records the specific script filename, function name and line number responsible for the longest blocking task on every URL, then groups them by root cause. In our Scottish council sample, 71% of the INP debt came from three sources: legacy jQuery UI datepickers, unoptimised Google Maps embeds on “find a service” pages, and cookie banner script bundles above 90 KB gzipped.

Hreflang for UK / GB / en-gb / en-scot

Every UK site that operates internationally — and there are more of them in Glasgow than you might guess, from Vision Direct to OVO Energy to a small independent whisky exporter — runs into hreflang confusion at some point. Google accepts en-GB but not en-UK. It accepts en-scot as of March 2024 but only recognises it in a limited experiment. And any hreflang entry to a URL that itself does not return a matching return tag is silently ignored.

Semalt renders every language variant, extracts every hreflang set, and builds a bidirectional graph. Missing return tags, self-referencing errors, mismatched canonical + hreflang, http vs https drift — all flagged, all fixable in the built-in template. For an OVO Energy-style operator with pages in en-GB, en-IE and de-DE, the graph is often the first time anyone has seen the entire relationship map on one screen.

LocalBusiness structured data with GBP priceRange

For any Glasgow local business trying to appear in the map pack or in richer SERP treatments, LocalBusiness schema is table stakes. The most-missed field on UK sites is priceRange, which Google explicitly recommends using currency-appropriate symbols. Semalt’s schema linter checks not just presence but locale sanity: it will flag a Glasgow-based restaurant page that declares priceRange: "$$" when it should be "££", and it will warn if the currency inside a Product offer disagrees with the ccTLD signal or the primary language.

Case study: Merchant City Barbers, six-branch group

A Glasgow barbershop group with six branches — Merchant City, Finnieston, Southside, West End, Shawlands and Partick — commissioned an audit in April 2026 after a six-month traffic slide from the map pack. Semalt’s audit surfaced 187 findings across the six location pages. Three findings, however, accounted for over 80% of the ranking loss:

1. Consent mode v2 misconfiguration. Their CookieYes bundle set the default to “granted” and then correctly denied on load. Google’s ads.txt crawler was seeing the initial “granted” state and misattributing conversions.
2. LocalBusiness schema on the wrong URL. Each branch page pointed the @id at the homepage instead of the branch URL, so Google was folding all six branches into a single entity.
3. INP of 630 ms on the “book now” button, caused by a chat widget bundle from a third party that added 340 KB of JavaScript.

Fixes shipped in nine days. By the end of week six, all six branches were back in the top three of the map pack for their neighbourhood, and online bookings were up 43% versus the pre-audit baseline. The finance director was happy enough with the £2,900 audit fee that she extended the retainer for the year.

How Semalt prioritises the fix list

Every crawler generates too many findings. What separates a useful audit from a wall of red icons is prioritisation. Semalt scores each finding on three axes: ranking impact (based on 12-month regression tests across the Semalt panel of tracked domains), legal risk (PECR, UK GDPR, PSBAR 2018), and fix cost (developer minutes, template availability, deployment friction). The output is a single sorted list where the top ten items usually recover 80% of the value.

Semalt audit vs. Screaming Frog vs. Sitebulb

More in this series: The Glasgow traffic GA4 never shows you, SEO changes in 3 minutes, not 6 weeks, Reading your Glasgow rivals' playbook.

FAQ

How often should a Glasgow site be audited?

For a typical Scottish SME, once a fortnight is plenty. Semalt runs the audit automatically on that schedule and only alerts you when a new critical finding appears or an existing one regresses. Log in and pick the schedule.

Does the audit crawl staging environments?

Yes, with HTTP basic auth or IP allow-list. Many of our Glasgow customers point Semalt at their Netlify preview URLs or their staging environment on Fasthosts, and we run a full audit before the change reaches production.

Will it flag issues that only appear on mobile?

Yes. Every URL is rendered on both a desktop Chromium and a Moto G Power emulation. Findings that only appear on mobile are tagged, and INP field data comes from the mobile-only CrUX slice.

Can it audit a search.gov.uk-style faceted search page?

Yes. Semalt has a specific rule pack for faceted navigation that checks robots handling of filter parameters, canonical consistency, and index bloat. This is a common cause of ranking loss on UK public-sector sites.

Does it integrate with Google Search Console?

Yes. Every finding is joined against Search Console data for the last 16 months, so you can see whether a rule triggered on URLs that actually generate impressions. A broken H1 on a URL nobody searches for should not be a priority.

Does it feed AutoSEO?

Yes. The prioritised fix list is what AutoSEO consumes to apply on-page changes. See the AutoSEO overview for details.