SEO Technical Audit — Vospers FF

Technical SEO Audit Report

TECHNICAL

SITE AUDIT

Domain

www.vospersff.com

Audit Date

May 2026

Pages Crawled

26

Crawl Tool

SiteBulb

Prepared By

Solaris Digital

Overview

Executive Summary

Needs Attention

47

/100

Technical Health Index

Based on crawl data across on-page signals, crawlability, linking and content integrity. Performance, authority and AI sections are pending additional data.

3

Critical Issues

5

Opportunities

5

Passing Checks

26

Pages Crawled

0

Broken URLs

0

Duplicate Content

Crawlability & Indexing

Amber

On-Page & Metadata

Critical

Links & Architecture

Amber

Performance & CWV

Amber

Organic Visibility

Amber

AI / LLM Visibility

Critical

Duplicate Content

Passing

JS Rendering

Passing

Security

Amber

Social Meta & OG

Amber

Local SEO

Amber

Sustainability

Passing

Analyst Commentary — Executive Summary

Section 01 — Infrastructure

Crawlability & Indexing

Amber — Review Required

26

Total URLs Crawled

0

Broken Internal URLs

2

Internal Redirects

2

GET Method Forms

0

Duplicate Titles

0

Similar Content

Broken internal URLs (4XX / 5XX)

No internal URLs returning error, not-found, forbidden, or timeout responses. The crawl is clean.

0

Redirect loops & broken redirect chains

No circular redirects or broken redirect targets detected. Redirect integrity is sound.

0

Internal redirected URLs (3XX hops)

2 internal URLs redirect rather than resolving directly. Each redirect adds a request hop, slowing load time and diluting crawl efficiency. Internal links pointing to these should be updated to the final destination.

2

Forms using GET method

2 pages contain forms with a GET method, potentially generating large numbers of cacheable submission URLs, creating crawl budget risk and possible index bloat.

2

Duplicate page titles

No pages share identical title tags. Good for content differentiation across the crawled set.

0

Near-duplicate content

No pages flagged for near-duplicate HTML content. Clean duplication profile across the site.

0

JavaScript rendering issues

No JS-only links or body content detected. Critical content appears accessible in the raw HTML response.

0

Google Tag Manager code detected

26 URLs do not contain a Google Tag Manager code. Verify whether GTM is intentionally absent or has been accidentally omitted — its absence may affect tracking and event management.

26

Analyst Commentary — Crawlability & Indexing

Infrastructure — HTTPS & Headers

Security

Amber — Review Required

Active

HTTPS STATUSType: Active or Inactive

0

MIXED CONTENT ISSUESType: count (0 = none found)

F

SECURITY HEADER SCOREType: A B C D E or F

45

SSL DAYS REMAININGType: number of days

HTTPS enforced site-wide

All pages served over HTTPS. A consistent HTTP → HTTPS redirect must be in place across the entire domain, not just the homepage.

✓ Pass

Mixed content (HTTP resources on HTTPS pages)

HTTP-sourced images, scripts, or stylesheets on HTTPS pages trigger browser security warnings and can affect user trust and crawler behaviour.

✓ Pass

SSL certificate valid & not expiring soon

Certificate must be valid and have at least 30 days remaining. An expired certificate causes immediate browser blocking and loss of all traffic.

✓ Pass

HTTP Strict Transport Security (HSTS)

HSTS instructs browsers to always use HTTPS, preventing protocol downgrade attacks and cookie hijacking. Should include a max-age of at least 6 months.

✗ Fail

Content Security Policy (CSP)

Declares which content sources are trusted, reducing XSS attack risk. Absence is one of the most common unaddressed security gaps on SME websites.

✗ Fail

X-Content-Type-Options: nosniff

Prevents browsers from MIME-type sniffing, stopping certain injection attacks. A simple one-line header addition.

✗ Fail

X-Frame-Options

Prevents the site being embedded in iframes on other domains. Protects against clickjacking attacks — particularly relevant for sites with contact forms.

✗ Fail

Referrer-Policy

Controls how much referrer information passes when a user navigates away. A permissive or absent policy can leak sensitive URL data to third parties.

✗ Fail

HTTP/2 or HTTP/3 protocol in use

Modern HTTP protocols deliver significant load performance improvements through multiplexing and header compression. HTTP/1.1 only is a performance and indirect SEO issue.

✓ Pass

Insecure form actions

Any form submitting data over HTTP rather than HTTPS risks exposing user-submitted data — particularly relevant for enquiry and booking forms.

✓ Pass

Expert Commentary — Security

Section 02 — Content Signals

On-Page & Metadata

Red — Critical Issues

21

Missing Meta Descriptions

20

Multiple H1 Tags

26

Title Tags Too Long

12

H1 Tags Too Long

0

Missing Page Titles

0

Duplicate H1s (Cross-Page)

Meta description missing

96% of crawled pages (25/26) have no meta description. This is a site-wide issue. Meta descriptions directly influence click-through rates — without them, Google auto-generates snippets, often with poor results.

21

Multiple <h1> tags on a single page

20 pages contain more than one H1 heading. Each page should have exactly one H1. Multiple H1s dilute keyword focus and likely point to a CMS or theme-level structural issue.

20

Title tag length too long

Every crawled page (26/26) has a title tag exceeding recommended character limits. Titles beyond ~60 characters are truncated in SERPs, reducing visibility — Google may choose to rewrite them entirely.

26

<h1> tag length too long

12 pages have H1 tags with too many words, weakening their keyword focus. The H1 should be concise and lead with the primary target term.

12

<h1> tag missing

1 page has no H1 tag — a missed fundamental on-page signal for search engines.

1

Missing page title tags

All pages have title tags present. No critical missing-title errors detected.

0

Duplicate H1 tags across pages

No cross-page H1 duplication — no heading-level keyword cannibalization.

0

Duplicate meta descriptions across pages

No duplicate meta descriptions found across the crawled URL set.

0

Analyst Commentary — On-Page & Metadata

Content Signals — Sharing & Knowledge Graph

Social Meta & Open Graph

Amber — Review Required

Open Graph and Twitter/X Card tags control how pages appear when shared across social media and messaging platforms. Beyond sharing, they feed directly into Google's Knowledge Graph and provide AI systems with explicit signals about page context, entity type, and content authority.

26

PAGES WITH OG TAGSType: count (out of 26)

0

PAGES WITH TWITTER CARDSType: count (out of 26)

10

OG IMAGES VALID (1200×630)Type: count (out of 26)

og:title present on all key pages

Controls the headline shown when a page is shared. If absent, platforms fall back to the <title> tag — often a poor sharing experience.

✓ Pass

og:description present on all key pages

Controls the summary text shown in social shares. Without it, platforms auto-pull text from the page — often with unpredictable results.

✗ Fail

og:image present and correct dimensions (1200×630px)

The shared image. Must be at least 1200×630px to render correctly on all platforms. A missing or undersized image results in blank or broken share cards.

✗ Fail

og:url matches the canonical URL

The og:url should exactly match the self-referencing canonical. Mismatches can confuse social scrapers and create duplicate signal issues.

✓ Pass

og:type set correctly

Should be "website" for the homepage, "article" for blog/news content, "product" for product pages. Correct typing helps the Knowledge Graph categorise the entity.

✓ Pass

og:site_name set

Identifies the brand behind the content. Used by Google in Knowledge Graph entity association and by platforms in share card attribution.

✓ Pass

twitter:card present (summary_large_image recommended)

"summary_large_image" produces a full-width image card on X/Twitter — significantly higher click-through than the default small card format.

✗ Fail

twitter:title and twitter:description present

Without these X/Twitter falls back to OG tags, which may not be optimised for the platform's character limits and card layout.

✗ Fail

twitter:image present and valid

Dedicated Twitter card image. Minimum 300×157px, maximum 4096×4096px. Can differ from the OG image if the optimal crop differs by platform.

✗ Fail

Social share preview tested (Facebook, LinkedIn, X)

All three platform debuggers should be run against the homepage and at least one key landing page to verify real-world rendering.

✓ Pass

Expert Commentary — Social Meta & Open Graph

The Open Graph foundation is solid - all 26 pages carry og:title, og:type, og:site_name and og:url consistently. Three gaps need addressing.

First, og:description is absent sitewide, directly linked to the missing meta descriptions - most WordPress SEO plugins (Yoast, RankMath) use the meta description as the og:description automatically, meaning Priority Action #01 resolves this at the same time once plugin settings are confirmed.

Second, only 10 of 26 pages have OG images at the required 1200×630px minimum; the remaining 16 produce blank or broken share cards when shared on LinkedIn, Facebook or Slack etc. -  a significant missed opportunity for engagement. Each service page should have a dedicated featured image at the correct dimensions.

Third, there is zero Twitter/X Card implementation across the site - adding twitter:card: summary_large_image via the SEO plugin is a quick configuration task that delivers meaningfully higher click-through rates on X and in any platform that reads Twitter Card metadata, including Slack and many messaging apps.

Section 03 — Internal Linking

Links & Architecture

Amber — Opportunities Found

26

Images Missing Alt Text (Linked)

12

Non-Descriptive Incoming Anchors

6

Non-Descriptive Outgoing Anchors

4

Links With No Anchor Text

Anchored images with no alt text

All 26 pages contain linked images without alt text. For linked images, alt text functions as anchor text — without it, Google receives no signal about what the target page contains. This is both an accessibility failure and an SEO opportunity wasted site-wide.

26

Backlink anchor text quality

External sites linking to this site using non-descriptive, generic or spammy anchor text. Strong, descriptive backlink anchors pass valuable signals; weak or manipulative ones do not — and at scale can indicate negative SEO or PBN involvement worth a disavow review.

12

Internal links using generic anchor text

Internal links between pages on the site that use generic anchor text (e.g. "click here", "read more"). Descriptive anchors help search engines understand the destination page and contribute to healthier internal link equity flow.

6

Internal links with no anchor text at all

4 pages contain followed internal links with completely empty anchor text — no context is communicated about the linked page.

4

Page with only one followed internal link

1 page has only a single followed internal link pointing to it, making it near-isolated in the site architecture and limiting the equity it receives from other pages.

1

Analyst Commentary — Links & Architecture

Section 04 — Speed & Experience

Performance & Core Web Vitals

Amber — Review Required

95

PAGESPEED DESKTOPType: score 0–100

70

PAGESPEED MOBILEType: score 0–100

D

PINGDOM GRADEType: A B C D E or F — from Pingdom performance score (90–100=A, 80–89=B…)

Largest Contentful Paint (LCP)

Load performance of the main visible element. Source: PageSpeed. Target: under 2.5s · 2.5–4.0s Needs Improvement · over 4.0s Poor

1.1s

Interaction to Next Paint (INP)

Google's responsiveness metric. Source: PageSpeed Field Data (top section). Only shown if the site has sufficient real-user traffic — enter N/A if absent.

N/A

Cumulative Layout Shift (CLS)

Visual stability during load. Source: PageSpeed. Target: under 0.1 · 0.1–0.25 Needs Improvement · over 0.25 Poor

0

Total Blocking Time (TBT)

Lab proxy for interactivity. Source: PageSpeed main metrics row. Target: under 200ms · 200–600ms Needs Improvement · over 600ms Poor

20ms

Time to First Byte (TTFB)

Server response speed. Source: Pingdom → click first request in waterfall → note "Wait" time. Or PageSpeed Diagnostics → "Reduce initial server response time". Target: under 200ms (AI-optimal) · under 600ms (SEO standard)

1230.4ms

Page Load Time (Pingdom)

Total page load time. Source: Pingdom results page — headline "Load Time" figure. Target: under 1.8s · 1.8–3.0s Needs Improvement · over 3.0s Poor

2.05s

Analyst Commentary — Performance & Core Web Vitals

The desktop PageSpeed score of 95 is excellent - well inside the "Good" band and a sign of a technically sound build. The mobile score of 70 sits at the upper end of "Needs Improvement" and is the more strategically important figure since Google uses mobile-first indexing for all sites in 2026. The individual Core Web Vitals paint a positive picture: LCP at 1.1s is comfortably inside the 2.5s target, CLS is a perfect 0, and TBT at 20ms is negligible. The site's rendering performance once loading begins is genuinely strong.

The standout concern is Time to First Byte at 1,230ms - more than double the 600ms SEO standard. TTFB measures how long the server takes to respond before any content is sent to the browser; it does not affect how fast the page looks once loading begins, but it delays everything downstream: Googlebot crawl efficiency, PageSpeed lab scores, and - increasingly important in 2026 - AI retrieval systems such as Google's real-time indexing pipeline, which use a sub-200ms threshold when deciding whether to fetch and serve content during live query windows. The Pingdom D grade is driven by this same issue.

Improving TTFB on a WordPress site comes down to three levers, in order of ease:

First, page caching is the single highest-impact change. Without it, WordPress builds every page from scratch on each visit - PHP execution, database queries, template rendering. A caching plugin (WP Super Cache is free; WP Rocket is the premium benchmark at ~£50/year) pre-builds pages as static files, typically bringing TTFB from 1,000ms+ to under 200ms without changing hosting.

Second, Cloudflare edge caching. The site already sits behind Cloudflare. Enabling HTML caching rules, or upgrading to Cloudflare's APO (Automatic Platform Optimisation) for WordPress at approximately $5/month, serves cached pages from the nearest Cloudflare edge node rather than the origin server - capable of reducing TTFB to under 100ms globally.

Third, hosting quality. If the site is on shared hosting, this is a hard ceiling regardless of caching. Managed WordPress hosting (SiteGround GrowBig or equivalent) typically delivers TTFB of 150–400ms before any caching is applied.

Implementing page caching alone is likely sufficient to move TTFB from red to green and should substantially improve the Pingdom grade at the same time.

Section 05 — Search Performance

Organic Visibility

Amber — Partial Data

6,740

Impressions (12mo)

100

Organic Clicks

1.5

AVERAGE CTRType: percentage e.g. 3.2

28.1

AVG. POSITIONType: avg position e.g. 14.3

2

DOMAIN RATING (AHREFS)Type: score 0–100

80

Referring Domains

Google Search Console — verified & active

Confirm GSC property is verified and returning data for this domain. Enter Yes (green) or No (red).

YES

GSC errors reported

Total errors flagged in Search Console. Advisory vs. structural indexing errors should be differentiated.

7

Non-brand queries: high impressions, low CTR

Filter GSC → Performance → Queries → exclude brand terms → sort by Impressions → flag any query with 50+ impressions and CTR below 3%. These represent pages ranking but not compelling clicks — a keyword targeting or title/description optimisation opportunity. Enter the count of such queries once GSC data is available.

14

Pages with average time on site ≤ 10 seconds

No pages are recording critically low engagement times. No immediate content quality red flags from time-on-page signals.

0

Organic keyword footprint (GSC, 90 days)

Source: GSC → Performance → Search Results → set date to last 90 days → count total rows under the Queries tab. This is the number of unique search terms the site appeared for. For context on quality, also note the top 1–3 non-brand terms by impressions in the commentary.

512

Analyst Commentary — Organic Visibility

The headline GSC figures tell a consistent story: 6,740 impressions over 12 months but only 100 clicks, producing a 1.5% average CTR. With an average position of 28.1, the site is appearing in search results primarily on pages 2 and 3 - visible enough to generate impressions but not positioned to drive meaningful click volume. Both figures are addressable through the on-page and content work already identified in this audit.

The most actionable immediate step from the GSC data is to filter non-brand queries by impressions, identify those generating 50+ impressions at CTR below 3%, and treat each as a targeting gap - the page is ranking for the term but the title or description isn't compelling enough to earn the click. Improving meta descriptions and title tags (Priority Actions #01 and #04) should directly improve CTR on these terms. Some notable examples of valuable terms driving impressions but not clicks are "Surveyors Farnham", "Valuation Surveyor Wrecclesham" and "Building Surveying Expert Witness Surrey".

Domain Rating of 2 reflects the relatively recent merger and rebranding as Vospers, Friend & Falcke - building backlinks through trade associations (RICS directory presence is confirmed), local business directories and PR around specialist services will be the primary long-term lever for improving organic authority and position.

Search Visibility — Local & Entity Signals

Local SEO & Knowledge Graph

Amber — Review Required

For location-serving businesses, local search visibility is often the highest-converting SEO channel. Google Business Profile completeness, NAP consistency, and LocalBusiness schema collectively build the entity signals that underpin both local pack rankings and Knowledge Graph representation — increasingly relevant to how AI systems identify and cite local businesses.

77

GBP COMPLETENESS SCOREType: % complete e.g. 75

YES

NAP CONSISTENTType: Yes or No

54

Review Count (GBP)

4.6

AVG. STAR RATINGType: rating e.g. 4.2

4

GBP PHOTOSType: number of photos

Google Business Profile — claimed & verified

The GBP listing must be claimed and ownership verified. An unclaimed listing can be edited by anyone and sends weak local ranking signals.

✓ Pass

GBP — name, address and phone number accurate

Core NAP data must exactly match what is displayed on the website. Any discrepancy weakens local authority signals and confuses Google's entity understanding.

✓ Pass

GBP — primary and secondary categories set correctly

The primary category is the single most influential GBP ranking factor. Secondary categories expand the terms the listing can rank for.

✓ Pass

GBP — business hours complete and accurate

Missing or incorrect hours reduce user trust and are a common GBP completeness gap. Special hours (public holidays) should also be updated.

✓ Pass

GBP — business description present (up to 750 characters)

The description should include primary keywords and location naturally. It is not a direct ranking factor but supports entity context.

✗ Fail

GBP — photos present (exterior, interior, team, products/services)

Listings with photos receive significantly more direction requests and website visits. Minimum 10 photos across multiple categories is recommended.

✓ Pass

GBP — review response rate

Responding to reviews (both positive and negative) is a local ranking signal and a trust indicator for prospective customers and AI citation systems.

✗ Fail

NAP consistent across site, GBP, and key citation sources

Name, Address, and Phone should be identical (not just similar) across the website footer, contact page, GBP, Bing Places, Yell, and any directory listings.

✓ Pass

LocalBusiness schema on site

JSON-LD schema with @type: LocalBusiness (or more specific subtype), name, address, telephone, and openingHours. This is the primary on-site entity signal for both Google and AI systems.

✗ Fail

Google Maps embed on contact / location page

An embedded map reinforces the physical location entity signal and improves the contact page experience for users.

✗ Fail

Knowledge Panel present in Google for brand name search

A Knowledge Panel confirms Google has established a confident entity understanding of the business. Absence suggests entity signals need strengthening across GBP, schema, and Wikipedia/Wikidata.

✗ Fail

Bing Places and Apple Maps listings claimed

Bing and Apple Maps are secondary but meaningful local visibility channels, particularly relevant as AI assistants (Copilot, Siri) use these data sources directly.

✗ Fail

Expert Commentary — Local SEO & Knowledge Graph

The Google Business Profile shows a strong foundation: 54 reviews at a 4.6-star average is an excellent trust signal and reflects well on the firm's service quality. However, with only 4 photos uploaded and no business description set, the profile is missing two of GBP's most influential completeness signals. Google uses the business description as contextual entity data for local pack ranking, and photos as a trust and relevance signal - both are quick additions. Adding a full description (up to 750 characters) and a representative set of photos - exterior, interior, team and service-related imagery - would meaningfully improve local pack visibility.

The absence of LocalBusiness JSON-LD schema is the other priority fix; without it, Google must infer the business's address, phone number, service areas and categories from unstructured page content alone. Adding schema via the SEO plugin is a one-time configuration task that strengthens both local rankings and Knowledge Graph representation, and is increasingly relevant to how AI systems identify and cite local businesses in response to query-based searches.

We also note the brand's knowledge graph/business profile listing doesn't always appear unless the specific location is also searched (e.g. "Vospers, Friend & Falcke Farnham") which suggests there is work to be done to push the primary brand profile and reference the other related branches.

Section 06 — AI Search Readiness

AI / LLM Visibility

Red — Critical Issues

AI-powered search engines — ChatGPT, Perplexity, Google AI Overviews and others — are now material discovery channels. Optimising for them requires a distinct technical framework that sits above and beyond traditional SEO. The six areas below define current best practice.

01 / 06

Bot Access & Crawlability

AI crawlers must be explicitly permitted in robots.txt and whitelisted in your WAF. Blocked bots mean invisible content.

GPTBot allowed in robots.txt

OAI-SearchBot allowed in robots.txt

ClaudeBot / Claude-Web allowed

PerplexityBot allowed

Google-Extended allowed

WAF / Cloudflare not blocking AI agents

02 / 06

Server-Side Rendering

Unlike Googlebot, most AI crawlers cannot execute JavaScript. Critical content must be in the raw HTML response.

No JS-only links detected (confirmed by crawl)

No JS-only body content detected

Core content accessible in response HTML

No infinite scroll blocking critical content

03 / 06

Semantic HTML & Vector Hygiene

AI models break pages into vector chunks. Semantic HTML and clean content boundaries improve extraction accuracy and relevance scoring.

Semantic tags in use (<article>, <main>, <section>)

Sequential H1 → H2 → H3 hierarchy

Cookie banners isolated from core content

Navigation boilerplate separated from body

H2/H3 sections form self-contained concepts

04 / 06

Server Response Time (TTFB)

AI RAG systems operate on tight latency budgets. TTFB above 600ms risks the site being skipped during live retrieval windows.

TTFB < 200ms (optimal for AI retrieval)

TTFB < 600ms (minimum acceptable threshold)

Consistent server response under load

05 / 06

Structured Data (Schema.org)

JSON-LD schema gives AI systems explicit, machine-readable confidence in content type and authority. No longer optional for brands that want to be cited in AI answers.

Organization schema implemented

Article / Product schema on relevant pages

FAQPage schema where appropriate

JSON-LD format (preferred over Microdata)

No schema validation errors

06 / 06

Metadata & Preview Directives

Restrictive meta tags prevent AI from using your content in answers. Timestamps signal freshness — a key citation ranking factor.

No nosnippet / data-nosnippet directives

No restrictive max-snippet:0 limits

Published / last-updated dates visible in HTML

Dates in schema (datePublished / dateModified)

Descriptive, semantic URL slugs

Self-referencing canonical tags present

Analyst Commentary — AI / LLM Visibility

The AI visibility assessment reveals a technically capable foundation undermined by three critical gaps.

The best result is on server-side rendering: all 26 pages deliver core content in raw HTML with no JavaScript-only links or body content. Since approximately 69% of AI crawlers cannot execute JavaScript, this ensures the site's content is accessible to the full range of AI indexing systems - a genuine advantage that reflects well on the build quality.

The robots.txt configuration is also clean: Yoast generates a permissive User-agent: * Disallow: file, meaning all AI crawlers - GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended - are explicitly unrestricted. One outstanding verification is the Cloudflare WAF configuration; during this audit all automated fetch attempts were blocked at the CDN layer, which is consistent with Cloudflare's Bot Fight Mode or WAF bot-blocking rules being active. Approximately 27% of sites behind Cloudflare unknowingly block AI crawlers at this level regardless of robots.txt. This should be verified in the Cloudflare dashboard under Security → Bots.

The most urgent technical finding is TTFB at 1,230ms - more than double the 600ms minimum AI retrieval threshold. AI retrieval augmented generation (RAG) systems operate on tight latency budgets and will skip content served this slowly during live query windows. Implementing WordPress page caching (Priority Action from the Performance section) directly improves AI visibility alongside conventional search performance.

Structured data is entirely absent. No Organisation, ProfessionalService, LocalBusiness or Article schema has been implemented anywhere on the site. This is the primary lever for AI citation accuracy: without machine-readable entity declarations, AI systems must infer the firm's name, services, location, RICS credentials and service area from unstructured HTML - a process that produces lower-confidence citations and reduces the likelihood of the firm appearing in AI-generated answers to queries like "RICS surveyor Farnham" or "chartered surveyors Surrey". Adding JSON-LD schema via the WordPress SEO plugin is a one-session task and the highest-impact single AI visibility improvement available.

The heading hierarchy issue (20 of 26 pages with multiple H1 tags) carries direct AI relevance: AI models use heading structure to identify content boundaries and chunk pages into indexable concepts. Multiple H1s create ambiguous content signals that reduce extraction accuracy - connecting directly to Priority Action #02.

Section 07 — Environmental Impact

Sustainability

Green — All Passing

CO₂ produced per page visit

Source: websitecarbon.com. Global average ~0.5g per visit. Target: under 0.3g = good. 0.3–0.6g = average. Over 0.6g = poor.

0.13 g

Carbon rating

A+ to F scale from websitecarbon.com. A+/A/B = clean (green), C/D = average (amber), E/F = poor (red).

B

Cleaner than X% of tested pages globally

Relative percentile from websitecarbon.com. 75%+ = good (green), 50–74% = average (amber), under 50% = poor (red).

69 %

Analyst Commentary — Sustainability

Section 08 — Recommendations

Priority Action Plan

Action Required

Actions are ordered by impact and urgency. Critical items affect the majority of the site and should be addressed first. Amber items are optimisation opportunities that compound the gains once critical issues are resolved.

#	Recommended Action	Section	Pages	Priority	Status
01	Write and implement meta descriptions for all 26 pages — unique, keyword-relevant, under 155 characters	On-Page	25/26	Critical	Red
02	Resolve multiple H1 tags — likely a CMS theme issue; each page must have exactly one H1	On-Page	20/26	Critical	Red
03	Add descriptive alt text to all linked images — use keyword-relevant descriptions reflecting the linked page's content	Links	26/26	Critical	Red
04	Shorten and optimise all title tags — lead with primary keyword, keep under 60 characters	On-Page	26/26	High	Amber
05	Update internal links pointing to the 2 redirect URLs — link directly to final destinations	Crawlability	2	High	Amber
06	Review non-brand organic queries with high impressions but low CTR (under 3%) in GSC — these represent ranking opportunities where titles or descriptions are not compelling enough to earn the click. Filter GSC Performance → Queries, exclude brand terms, sort by Impressions.	Organic	4	High	Amber
07	Replace generic anchor text with descriptive, keyword-relevant alternatives site-wide	Links	12 incoming	Medium	Amber
08	Add internal links to the near-isolated page — ensure it receives equity from at least 3–5 relevant pages	Links	1	Medium	Amber
09	robots.txt AI crawler audit — confirmed pass. Yoast-generated `User-agent: * Disallow:` permits all AI crawlers including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended. Verify Cloudflare WAF settings are not overriding this at the CDN layer.	AI / LLM	robots.txt	Medium	Green
10	Implement JSON-LD schema — minimum: ProfessionalService / LocalBusiness (with address, telephone, geo, openingHours), Organization, and BreadcrumbList on all pages. No schema currently exists on the site. Highest single impact action for AI visibility and Knowledge Graph presence.	AI / LLM	Site-wide	Medium	Red
11	Review GET method forms — assess POST method to prevent URL proliferation and crawl budget risk	Crawlability	2	Low	Amber
12	Verify Google Tag Manager status — confirm whether deliberately absent or accidentally removed	Crawlability	26/26	Low	Amber
13	Confirm HTTPS enforced site-wide and fix any mixed content issues	Security	Site-wide	High	Green
14	Add missing security headers (HSTS, CSP, X-Content-Type-Options) — run securityheaders.com	Security	Server config	Medium	Red
15	Implement Open Graph tags on all key pages — og:title, og:description, og:image (1200×630px), og:url	Social / OG	All pages	High	Amber
16	Add Twitter Card tags — twitter:card (summary_large_image), twitter:title, twitter:description, twitter:image	Social / OG	All pages	Medium	Red
17	Audit GBP completeness — categories, hours, description, photos, review responses	Local SEO	GBP listing	High	Amber
18	Verify NAP consistency across website, GBP, Bing Places, Yell and key directories	Local SEO	Multi-source	High	Green
19	Add LocalBusiness JSON-LD schema with full address, telephone, openingHours and geo coordinates	Local SEO	Site-wide	Medium	Red
20	Claim and optimise Bing Places and Apple Maps listings to strengthen entity signals for AI assistants	Local SEO	Off-site	Low	Red
21	Set /category/uncategorized/ and /author/ pages to noindex via WordPress SEO plugin — these WordPress archive pages add no value and waste crawl budget	Crawlability	2 pages	Critical	Red
22	Add H1 tag to /insights/ page — currently the only page with no H1 at all	On-Page	1 page	High	Red
23	Write meta descriptions for the two new landing pages (/book-today-level-2 and /book-today-level-3)	On-Page	2 pages	High	Amber
24	Suppress the Server HTTP response header to stop leaking web server software and version number	Security	Server config	Medium	Amber
25	Fix protocol-relative resource on homepage — change // to https:// in the resource URL	Security	Homepage	Low	Amber

Analyst Commentary — Final Recommendations

Vospers, Friend & Falcke enters this audit in a stronger position than many comparable professional services firms - a clean crawl profile, no broken links, solid HTTPS implementation, excellent Core Web Vitals on desktop, and a genuinely impressive Google Business Profile review record. The issues identified are systematic rather than structural: they reflect configuration and content gaps that are well within reach of a focused development sprint rather than anything requiring fundamental rebuilding.

The five priorities most likely to produce measurable results, in order of impact:

1. Metadata - highest immediate SEO impact. Writing unique meta descriptions for all 26 pages, consolidating H1 tags to one per page and shortening title tags to under 60 characters collectively improve how the site appears in every search result. These three actions drive CTR improvements across the entire keyword footprint and should be treated as a single coordinated sprint.

2. Server response time - TTFB. At 1,230ms the site's server response time is its most significant technical liability, limiting both Google crawl efficiency and AI retrieval. A WordPress page caching plugin resolves this in a single implementation session and is the highest return-on-investment technical change available - it also lifts the Pingdom and PageSpeed mobile scores simultaneously.

3. Structured data - the long-term authority builder. Implementing LocalBusiness / ProfessionalService JSON-LD schema is the missing piece for knowledge graph presence, local pack authority, and AI citation. It establishes the firm as a defined, machine-readable entity rather than just a collection of web pages - the foundation from which lasting search visibility is built.

4. Security headers - a quick developer win. Four of the five failing headers (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy) can be added in under an hour. The Content Security Policy is more complex given the site's third-party scripts and should be scoped as a separate piece of work with careful testing.

5. Indexability cleanup. Noindexing the two WordPress archive pages, fixing the two internal redirect hops, and adding alt text to linked images are all low-effort, high-signal improvements that clean up the crawl profile and complete the technical housekeeping.

Addressed in this sequence the site moves from its current 47/100 Technical Health Index to a score in the 75–85 range, and positions Vospers, Friend & Falcke strongly for both traditional search and the AI-powered discovery channels that are increasingly driving professional services enquiries in 2026.