How to Fix Crawl Errors and Broken Links on Your Scottish Business Website
Crawl errors and broken links quietly erode your search rankings, often for months before you notice the drop in traffic. Google's crawler visits your site, hits a dead end, and logs the failure. Repeat that across dozens of pages and your site starts to look unreliable. For Scottish businesses competing in tight local markets, from Edinburgh's financial district to Aberdeen's energy sector, that credibility loss translates directly into missed enquiries.
What Crawl Errors Actually Are
A crawl error occurs when a search engine bot attempts to access a URL on your site and receives an error response instead of a page. The most common types are 404 errors (page not found), 301 or 302 redirect chains that loop or timeout, and server errors returning a 5xx status code. Soft 404s are particularly deceptive: the server returns a 200 status but serves a "page not found" message, so Google indexes an empty shell.
Broken internal links compound the problem by preventing link equity from passing between pages. A service page that earned backlinks from three local directories loses its value the moment the URL changes and no redirect is set. Broken external links are a separate issue but still damage user trust.
How to Audit Your Site Before Fixing Anything
Fix nothing until you have a complete picture. Running repairs blindly creates redirect chains and orphaned pages faster than it resolves them.
Tools Worth Using
Screaming Frog SEO Spider is the standard starting point for most technical audits. The free version crawls up to 500 URLs, which covers many small Scottish business websites outright. For larger sites, Google Search Console's Coverage report is free and reflects how Google itself sees your URLs, making it the most authoritative source for crawl data. Ahrefs Site Audit and Semrush's site health tool add backlink context, showing which broken pages still carry inbound links worth preserving.
Export your crawl data to a spreadsheet. Sort by status code so all 404s, 5xx errors, and redirect chains appear in grouped rows. This makes prioritisation straightforward.
Prioritising What to Fix First
Not every error deserves equal urgency. Fix in this order:
- Pages that still receive inbound links (internal or external) and are returning 404s.
- Any URL listed in your XML sitemap that is returning an error status.
- Redirect chains longer than two hops, which slow page load and dilute equity.
- Orphaned pages (accessible by crawl but not linked from anywhere on the site).
- Soft 404s, particularly on product or service pages.
How to Fix Broken Links on Website
The fastest reliable fix for a broken internal link is to update the href attribute in your CMS to point to the correct live URL, or to set a 301 redirect from the old URL to the new one. Which approach you choose depends on whether the original URL still appears in external links or sitemaps.
If no external source points to the old URL, simply updating the internal link is cleaner. If directories, trade bodies, or partner sites in Scotland link to the old URL, a 301 redirect preserves that equity and routes users correctly without requiring every third party to update their link.
For WordPress sites, the Redirection plugin manages 301 redirects without server-level access. On Shopify, redirects are handled inside the Navigation settings. Developers working directly on Apache or Nginx servers should add redirect rules to the `.htaccess` file or the server configuration block respectively.
After setting redirects, re-crawl the affected URLs to confirm they return a 200 status. Remove or update any internal links pointing to the old URL so the redirect is only a fallback for external traffic, not a permanent crutch inside your own site structure.
Fixing Server Errors and Redirect Issues
A 5xx error means your server failed to fulfil the request. Causes include exhausted PHP memory limits, database connection failures, or misconfigured server rules. On shared hosting (common among smaller Scottish businesses), a 503 Service Unavailable error often signals a hosting plan being overwhelmed by traffic or a runaway plugin process.
Check your server error logs first. Most cPanel hosts expose these under Metrics. If the errors are intermittent rather than persistent, monitor uptime with a free tool like UptimeRobot to capture the pattern before contacting your host.
Redirect chains occur when URL A redirects to URL B, which redirects to URL C. Each hop adds latency and dilutes PageRank. Audit all redirects with Screaming Frog's redirect chain report and collapse each chain to a single direct 301 pointing to the final destination URL.
Submitting Fixes to Google
Once your corrections are in place, tell Google rather than waiting for its next scheduled crawl. In Search Console, use the URL Inspection tool to request indexing for individual pages that were previously returning errors. For bulk recrawl requests, submit an updated XML sitemap under Sitemaps in Search Console.
Search Console usually processes recrawl requests for smaller sites within a few days. You will see the Coverage report update as errors are resolved and valid pages increase. Monitor the report weekly for the first month after a significant fix to catch any regressions introduced during the repair process.
Preventing Errors from Returning
A one-time audit is not a maintenance strategy. Set a recurring monthly crawl using Screaming Frog or a monitoring platform, and configure Search Console email alerts for coverage spikes. If your site runs WooCommerce or a product catalogue, check for broken links after every product deletion or URL restructure.
Content migrations are the most common cause of large-scale broken link events. If your agency or developer is restructuring your site's URL taxonomy, insist on a redirect mapping document before migration begins, not after. Scottish business directories like Scoot, Yell, and local chamber websites often hold deep links to inner pages. A URL change without a redirect immediately breaks those citations.
Internal linking audits are worth running quarterly. Pages that age out of your navigation but retain backlinks should stay live or redirect permanently, never simply disappear.
Frequently Asked Questions
How to Fix Broken Links on Website
Update the internal link in your CMS to point to the correct live URL, or set a 301 redirect from the old URL to the new destination. If external sites link to the old URL, a 301 redirect preserves that link equity. After the fix, re-crawl the URL to confirm it returns a 200 status, then update any internal links pointing to the old address so the redirect only catches external traffic.
What Tools Can I Use to Find Crawl Errors on My Scottish Business Website?
Google Search Console's Coverage report is free and shows exactly how Google sees your URLs, making it the most authoritative source. Screaming Frog SEO Spider crawls up to 500 URLs for free, which is sufficient for many small Scottish business sites. Ahrefs Site Audit and Semrush add backlink context, showing which broken pages still carry inbound links worth preserving with a redirect.
What Is the Difference Between a 404 Error and a Soft 404?
A 404 error means the server explicitly returns a 'page not found' status code, which search engines recognise as a missing page. A soft 404 occurs when the server returns a 200 (success) status but the page content itself says nothing was found, such as an empty search results page. Google may index soft 404s as low-quality pages, so they need to be identified and either corrected or removed from your sitemap.
How Long Does It Take Google to Recognise Crawl Error Fixes?
After you submit fixes via Google Search Console's URL Inspection tool or by uploading an updated XML sitemap, most smaller sites see the Coverage report update within a few days. Larger sites or pages with low crawl priority can take one to three weeks. Monitoring the Coverage report weekly for the first month after a fix helps you catch any regressions quickly.
How Can I Stop Broken Links from Reappearing on My Website?
Set a recurring monthly crawl using Screaming Frog or a site monitoring platform, and enable Google Search Console email alerts for coverage spikes. Before any URL restructure or content migration, require your developer or agency to produce a redirect mapping document. Pay particular attention to product or category deletions, as these are the most common sources of new 404 errors on e-commerce and service sites.