Contact Info
Edinburgh
What does technical SEO involve for Edinburgh websites?
Technical SEO for an Edinburgh website removes the obstacles that stop search engines finding, rendering and indexing the pages that matter. Here that often means deep collection and archive catalogs with image viewers and faceted search, Gaelic and English versions linked with hreflang, visitor sites whose booking engines and calendars create endless URLs, and servers that must cope with festival traffic. I audit remotely and write fixes your developers can build.
Last reviewed by Vikas Saroj
Edinburgh hosts many of Scotland's national cultural institutions, archives and public bodies, alongside heritage organizations, universities with special collections, and a large visitor economy of attractions, tours and accommodation. Their websites share some awkward traits: very deep catalogs, content in Gaelic as well as English, booking systems run by third parties and traffic that surges during the festivals and at Hogmanay.
I audit these sites remotely, find where crawling, rendering or indexing breaks down, and translate each finding into a ticket with evidence and a test, ready for whoever maintains the site. The build stays with your developers or agency; my job is to make sure they know exactly what to change and why.
What I Do
Every finding comes with evidence, a suggested fix and a way to test it, so changes can be prioritized against everything else your developers are doing.
I map how search engines reach object, record and item pages in a collection or archive, find records that are orphaned or hidden behind search forms, and design browse paths and sitemaps that expose them.
I test whether digitized items shown in image viewers, and script-heavy collection pages, render titles, captions and descriptions that search engines can index, and recommend server-side fallbacks where they do not.
For Gaelic and English sites, I check hreflang pairs, language switchers, URL patterns and partially translated sections, so each language version reaches the right searchers and neither undermines the other.
I review how third-party booking engines, availability calendars and date parameters interact with your site, closing crawl traps and making sure the pages that sell are the ones that get indexed.
Before the festivals and Hogmanay, I review caching, image delivery and server response with your hosting provider, so pages stay fast and reachable for crawlers when visitor traffic climbs sharply.
When organizations merge, rebrand or move to a new content management system, I build redirect maps, test the staging site and monitor indexing afterward, so links and records built up over many years are not lost.
How I Work
See the site as a crawler does
Crawl with and without scripts
Compare sitemaps with indexed pages
Inspect server logs where available
Test viewers, forms and calendars
Fixes ranked by impact and effort
Group issues by template
Write tickets with acceptance tests
Agree priorities with developers
Plan around peak seasons
Check fixes on the live site
Retest after each release
Watch indexing and crawl stats
Monitor speed during peaks
Report progress to stakeholders
Edinburgh's websites are shaped by what the city does. National museums, galleries, libraries and archives publish catalogs of objects, manuscripts and records. Public bodies headquartered in the city publish guidance, consultations and services, some in Gaelic as well as English. Universities and research institutes run sprawling sites with special collections and repositories. And the visitor economy depends on attraction, tour and accommodation sites built around booking systems that someone else maintains.
These sites rarely fail in ordinary ways. Their problems come from scale and structure: catalogs too deep for crawlers to reach, records that appear only after a search form is submitted, image viewers that hide text from search engines, language versions that compete with each other, and calendar pages that multiply without end.
Many of these organizations also work under constraints that shape how fixes are delivered: procurement rules for appointing web agencies, accessibility regulations for public sector websites and change boards that approve every release. My UK technical SEO consultant page covers national topics such as cookie consent, VAT-inclusive product markup and separate UK and Irish versions. This page stays with the patterns that recur among Edinburgh's institutions and visitor businesses.
A collection website may hold far more record pages than its navigation can show. If the only way to reach an object, manuscript or archive file is to type into a search box, crawlers will never find much of it, and useful records stay invisible to the people searching for a maker, a place or a family name.
The fixes are structural. Browse paths by subject, place, person and period give crawlers routes into the catalog. XML sitemaps list every record worth indexing, and record pages carry stable URLs and unique titles and descriptions drawn from the catalog data. Faceted search inside the collection should not create crawlable combinations of every filter; only a few facet pages deserve a place in the index.
Digitized items add a rendering problem. Many institutions display images through viewers built on the International Image Interoperability Framework or similar tools, and the transcription, caption or description may load only after scripts run. I test what a crawler actually receives and recommend server-rendered text alongside the viewer where it is missing. Structured data for artworks, books and archival items can describe records consistently, and script rendering in general is covered on the JavaScript SEO page.
Some Scottish public bodies, cultural organizations and Gaelic-medium education providers publish content in Gaelic as well as English, often as part of a Gaelic language plan. Technically, a bilingual site needs the same care as any multilingual site, plus a few extra decisions because the Gaelic version is often partial.
Each page with a translation should declare both versions with hreflang, using the language code for Scottish Gaelic alongside the matching English page, with reciprocal references and a sensible default. Pages without a Gaelic version should not point to an English page as though it were a translation. Language switchers should link to the equivalent page rather than the home page, and the site should not force visitors into a language based on browser settings alone, a habit that can also confuse crawlers.
URL patterns, translated titles and descriptions, and the Gaelic forms of place and organization names all matter to people searching in Gaelic, even though that audience is small. The Gaelic wording itself belongs with fluent Gaelic speakers, on your staff or at a translation partner; my role is to make the structure work. The same principles apply to visitor sites with French, German, Spanish or other language versions, covered in the next section.
Tour operators, attractions and accommodation providers in Edinburgh rarely build their own booking systems. The booking engine is typically a third-party service, shown in an iframe, on a subdomain or on another domain entirely. That arrangement creates predictable technical issues: product pages whose prices and availability are invisible to crawlers, duplicate tour or room pages hosted by the booking provider, and analytics that break when visitors cross domains.
Availability calendars are a classic crawl trap. A calendar that links to the next day, week or month, with the date in the URL, can generate an endless series of near-empty pages, and crawlers spend their time there instead of on the tour and room pages that matter. Keeping calendar URLs out of the crawl and holding one canonical page per product usually solves it.
Visitor sites also add languages quickly, sometimes through automatic translation plugins. Machine-translated pages that are thin, inconsistent or not linked with hreflang can do more harm than good. I review which languages earn their place based on where your visitors come from, check the hreflang setup and ask that every translation be produced or reviewed by native speakers, whether from your own staff or from a local partner. The Core Web Vitals page covers the speed problems that booking widgets often cause.
During the August festivals and at Hogmanay, traffic to many Edinburgh sites rises sharply, from venues and ticketing pages to restaurants, transport and accommodation. If pages slow down or time out, visitors leave, and crawlers that meet repeated server errors may visit less often. Before the peak I review caching, image sizes, third-party scripts and server response with your hosting provider, and agree a short list of checks to run daily while traffic is high.
Public bodies and cultural organizations also merge, rebrand and change platforms from time to time. Each move risks losing the links, rankings and indexed records built up over many years. I build redirect maps from the old URLs, test the staging site, check that records keep stable addresses and monitor indexing afterward. The SEO migration page describes that process.
All of this is delivered remotely. Your in-house developers or agency stay in charge of the code, while I write tickets with acceptance tests, respect your release and change approval process and retest after each release. Accessibility requirements for public sector sites sit with your accessibility lead; technical SEO fixes should support them and never work against them. For wider search strategy in the city, see the SEO consultant in Edinburgh page; where catalog or booking data flows from a back-office system, the Edinburgh ERP consultant page covers that side.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure where growth is leaking?
Share your goals and current funnel with me. I will look at search, ads and CRM data together and tell you where the next lead is most likely to come from.
FAQ
Usually because crawlers cannot reach them. If records appear only after a search is submitted, or sit many clicks deep, they are rarely discovered. Browse paths by subject, place and person, complete XML sitemaps, stable record URLs and unique titles and descriptions fix much of the problem. I check server logs where available to see what crawlers actually request.
Yes, for the pages that have a Gaelic equivalent. Each translated pair should reference the other, and pages without a translation should simply stand alone in English rather than pointing to a Gaelic page that does not exist. The language switcher should lead to the equivalent page where there is one, and the Gaelic text should be checked by fluent speakers.
Yes. Even when the booking engine sits on another domain or inside an iframe, your own tour, room or ticket pages can carry indexable descriptions, prices where appropriate and clear links into the booking flow. I also check calendar URLs for crawl traps and cross-domain tracking, and send the provider specific requests where their setup causes problems.
Yes. A review of caching, image delivery, third-party scripts and server capacity with your host, completed well before the busiest weeks, lowers the risk of slow or failing pages when traffic rises. A short daily check during the peak catches problems early, and major releases are best planned for the quieter months.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
