Scottish technical SEO and regulatory differences to plan for

What to take away

Which Scottish institutions change the technical SEO picture

Scotland has its own public sector, and that changes who signs off a site and what they care about. The Scottish Government, its directorates and the agencies they fund publish most of the high-traffic public content north of the border. Accountable officers, not marketing directors, often hold the final say on a release.

Local government adds another layer. Councils across Scotland run separate domains for services, licensing, waste and school admissions. Each domain may have its own content team, its own CMS and its own idea of what a canonical URL looks like. COSLA coordinates council interests nationally, but publishing decisions stay with each council.

Then come the arm's length bodies. These are organisations funded by government but run at a distance, and they frequently inherit a domain from a predecessor body. Legacy redirects, old subdomains and duplicated service pages are common. A crawl will usually surface more of these than the client expects. Examples include Skills Development Scotland and Scottish Enterprise.

NHS health boards are another group to include. Each board publishes service information, patient guidance and recruitment pages, often across several domains. They answer to Scottish Government health directorates and to their own boards.

Regulated sectors matter too. Financial services firms in Edinburgh answer to the Financial Conduct Authority and the Prudential Regulation Authority, both UK-wide bodies. Their marketing sites sit beside secure customer portals, and the two must not be confused by search engines or by users.

Universities and colleges are a category of their own. They hold large estates of course pages, research profiles and prospectus content, and they compete for the same queries as commercial providers. Their technical debt is often measured in decades.

None of this is unique to Scotland in kind. It is unique in concentration. An audit that ignores the public body layer will miss the largest and most regulated sites in the country.

Legal and regulatory differences that affect audits in Scotland

Most web regulation in Scotland is UK-wide. The Equality Act 2010 sets duties on accessibility and non-discrimination in web content, and it applies to service providers and public bodies alike. An audit that treats accessibility as optional is not a defensible audit.

The public sector accessibility regulations sit on top of that. They require public sector websites and apps to meet accessibility standards and to publish an accessibility statement. The guidance on accessibility requirements for public sector bodies explains the scope and the statement requirement in detail.

The technical benchmark is WCAG 2.2. The criteria that matter most in markup work include 2.4.11 Focus Not Obscured (Minimum), 2.5.8 Target Size (Minimum) and 3.3.8 Accessible Authentication (Minimum). That specification is the reference point for any inclusive technical audit.

Data protection is UK-wide, with the Information Commissioner's Office as the regulator. Freedom of information is devolved to the Scottish Information Commissioner. Consent banners, analytics tags and form handling fall inside that remit. A Scottish audit should confirm that tracking behaves the same way for users in Edinburgh, Glasgow and the rest of the UK.

Advertising claims are policed by the Advertising Standards Authority across the UK. For fintechs, the wording of a landing page can create a compliance problem that no amount of schema markup will fix. Flag it and hand it to the legal team.

Where Scottish law does diverge, it is usually in property, criminal and family matters rather than in web publishing. The practical effect on an audit is small, but it does change the vocabulary on legal and property sites. Terms like sasine, missives and confirmation carry specific meanings.

A sensible approach is to treat regulation as a constraint list rather than a research project. Our guide to technical SEO UK regulations sets out the sources worth checking before you scope the work.

The primary sources are legislation.gov.uk for the Equality Act 2010, the gov.uk accessibility guidance for public sector duties, and Google Search Central for indexing rules.

Edinburgh and Glasgow organisation types and their site patterns

Edinburgh and Glasgow hold most of Scotland's digital teams, and their site patterns differ in ways that matter for crawling and indexing.

Edinburgh skews towards government, financial services, professional services and tourism. Sites there often run a corporate domain for marketing and a separate domain or subdomain for customer accounts. Search engines need clear signals about which is which.

The city also has a dense cluster of legal, accountancy and consultancy firms. These sites tend to be small, heavily templated and slow to change. Their main technical problem is usually thin service pages competing with each other.

Glasgow leans towards education, culture, health and public services. Sites are larger, older and more likely to have been built in stages by different suppliers. Subdomain sprawl is common, and so are orphan pages that nothing links to.

The cultural sector in Glasgow brings seasonal traffic spikes. A festival or exhibition can triple traffic for a fortnight, then drop away. Caching, image weight and server capacity deserve a look before the season starts.

Both cities host a growing fintech cluster, though Edinburgh's is larger. Fintech sites combine marketing pages with application flows, and the application flows should normally be excluded from indexing. Get that wrong and you will see login pages in search results.

Patterns repeat across estates. A council waste or licensing service commonly sits on its own subdomain, as in waste.councilname.gov.uk, rather than on a path under the corporate site. The same shape appears in university course finders, where parameters such as ?level=postgraduate&mode=full-time&year=2026 generate thousands of near-identical URLs.

For teams starting from a low base, the lessons in our piece on technical SEO foundations transfer cleanly to Scottish organisations.

Accessibility, public sector duties and Scottish public bodies

Accessibility is where Scottish public bodies feel the most external pressure, and where an audit can do the most good.

The accessibility statement is a page on the site in its own right, and it should be findable, dated and honest about known gaps. The Government Digital Service runs the monitoring programme for public sector statements.

The Equality and Human Rights Commission enforces equality law in Scotland, and the Scottish Public Services Ombudsman handles complaints about public bodies.

2 gives the testable criteria. The ones most often failed in Scottish public sector audits are insufficient colour contrast, missing form labels, keyboard traps in navigation and video without captions. None of these require a rebuild to fix. 2 Captions (Prerecorded).

Accessibility work also tends to improve technical SEO. Clear headings, descriptive link text, labelled forms and captioned media all help crawlers as well as users. The two disciplines share more ground than most teams assume.

Scottish public bodies often commission accessibility audits separately from SEO audits. Where that happens, ask for the accessibility report before you start. It will save you re-testing the same templates.

Our overview of technical SEO rules and ethics covers how to handle findings that sit outside your remit without overstepping.

Crawl, index and structured data checks for Scottish sites

Once the regulatory picture is clear, the crawl itself is familiar work. The differences lie in what you find.

Start with a full crawl of every hostname you can find, not just the main domain. Scottish public bodies and universities frequently run a dozen or more subdomains, some of them forgotten.

Check robots.txt on each host. A disallow rule left over from a staging migration can quietly remove an entire section from search. This is one of the most common findings on legacy Scottish sites.

Review canonical tags across service pages. Councils and arm's length bodies often publish the same guidance on two domains, and neither points at the other. Pick a canonical and enforce it.

Inspect index coverage for parameter duplicates. Booking systems, course finders and event calendars generate thousands of near-identical URLs. Decide which deserve indexing and block the rest.

Structured data is worth attention on public sector sites. Organisation, LocalBusiness, FAQ and Event markup all have legitimate uses, and the official guidance on crawling, indexing and ranking sets out how these are interpreted. Google Search Central is the source for supported types. Check that documentation before you add anything exotic.

Finally, test internal search. On large Scottish public sites, internal search results pages are often indexable and often terrible. Noindex them unless there is a clear reason not to.

Reporting and measurement expectations for Scottish stakeholders

Scottish stakeholders in the public sector are accountable to auditors, committees and the public. That changes what a good report looks like.

Lead with outcomes, not crawl statistics. A committee will not act on a count of 404 errors. It will act on a claim that a service page is invisible to search and that fixing it restores access for residents.

Agree metrics before the work starts. The UK Government's framework for measuring success is a useful model for setting performance metrics and KPIs, and it translates well to Scottish public bodies and their delivery partners.

That framework pushes you towards a small number of measures tied to a service goal. For a council, that might be the share of residents who find a service page without using internal search. For a fintech, it might be qualified applications from organic search.

Report on a fixed cycle. Quarterly suits most Scottish public bodies because it aligns with committee schedules. Fintechs often want monthly, especially around product launches.

Keep a decision log. Record what you recommended, what was accepted and what was deferred. When the same issue reappears a year later, the log answers the obvious question.

If your organisation prefers planned cycles over reactive fixes, our article on when to run a technical SEO ninety day plan explains how to sequence the work.

A Scottish technical SEO planning checklist

Use this before you scope any audit in Scotland. Work through it in order and record the outcome for each item.

A worked example shows how this lands. A Glasgow arm's length body inherits a domain from a predecessor, runs three subdomains and publishes an accessibility statement dated four years ago. The crawl finds a staging robots.txt blocking the main service directory, two competing canonicals on the same guidance page and no captions on the induction videos.

The fixes are unglamorous. Remove the disallow rule, consolidate the canonicals, add captions and rewrite the statement. None of it requires a new CMS. All of it restores access for residents and makes the site legible to search engines.

That is the shape of most Scottish technical SEO work. The regulation sets the boundaries, the institutions set the constraints, and the crawl finds the same familiar problems in an unfamiliar estate. Teams that plan for technical SEO outlook cycles rather than one-off projects tend to keep the gains.

Common questions