Craftsmanship since 1983.
A website that no longer matches it.

Change the canonical to https://field-shelters.co.uk/ and 301 /index.php to /. Inspect the homepage in Google Search Console after deployment.

Use one clean homepage URL, redirect index.php, and define a deliberate policy for irrelevant query parameters. Do not blanket-block URLs before Search Console inspection.

Publish a valid XML sitemap containing only canonical 200-status URLs and a minimal robots.txt referencing it. Submit the sitemap in Search Console and Bing Webmaster Tools.

Add self-referencing canonicals and unique titles such as “16 mm Shiplap Field Shelter Prices” and “19 mm Loglap Field Shelter Prices”. Preserve existing URLs during any rebuild.

Use one descriptive H1 per page, logical H2/H3 sections, and ordinary lists for locations. Match visual size with CSS rather than heading level.

Write unique search and social metadata for every indexable page. Add a deliberate 1200 × 630 sharing image using a real project photograph.

Replace lists with concise delivery coverage and a postcode checker. Create location content only where there is unique, useful proof. Remove copied shed copy from equestrian specifications.

Confirm one authoritative name, address, phone, hours, postcode, email, company number, and VAT record. Proofread all migrated copy with the business owner.

Add valid, visible-content-matched Organisation/LocalBusiness, Product/Offer, and BreadcrumbList markup. Add FAQ markup only to genuine visible FAQs and follow current search-engine eligibility rules.

Create concise answer blocks for mobile vs static, sizes, cladding, skids, roofing, tack rooms, VAT, delivery/offloading, assembly, maintenance, and planning considerations.

State the relationship plainly: the approved legal entity, trading/site name, workshop address, and parent website. Use consistent naming and organisation identifiers.

After verifying ownership, link the correct Google Business Profile and active social profiles. Reference them with appropriate organisation markup; do not invent profiles.

Replace the auto-loading hero carousel with one responsive, preloaded hero image; minimise render-blocking work and validate improvements across multiple runs and real-user data.

Load only the active hero. Produce correctly sized AVIF/WebP sources with a JPEG fallback, and defer all non-critical galleries.

Set intrinsic dimensions, use responsive srcset/sizes, lazy-load below-fold media, and retain meaningful alt text. Keep the LCP image eager and high priority.

Remove unused libraries, bundle only necessary CSS/JS, defer non-critical scripts, use font-display: swap, preconnect deliberately, and set versioned long-lived static caching.

Remove the duplicate/early initialisation or execute it only after dependencies load. Add automated smoke tests for navigation, carousel, gallery, forms, and console errors.

Create a concise mobile-first journey: value proposition, product choices, starting prices, proof, delivery, FAQs, and persistent call/quote actions. Move detail to focused pages.

Add a short quote flow capturing product, size, cladding, mobile/static, roof, add-ons, postcode, access notes, and preferred contact. Keep click-to-call visible.

Link the correct shelter image, remove placeholder # controls, and use descriptive anchor text rather than “Click Here”. Test every product action before launch.

With permission, organise reviews by product/location/date and add project case studies. Update the footer automatically and verify all founding, guarantee, and pricing claims.

Define accessible colour tokens, retest every component state, and do not rely on colour alone to identify links. Target WCAG 2.2 AA contrast.

Prefer a static hero. If carousels remain, implement correct semantics and controls; title the map iframe and make the menu accessible name include its visible label.

Add skip navigation, landmarks, logical headings, visible focus, underlined inline links, keyboard testing, zoom/reflow testing, and manual screen-reader checks.

Remove unnecessary legacy code or upgrade after compatibility testing. Review Bootstrap and all plugins, then add dependency monitoring and a patch owner.

Add and test an appropriate header baseline, including CSP report-only before enforcement. Suppress version disclosure and verify secure cookie attributes where applicable.

Inspect the exact URL in Search Console, review indexed URL anomalies, check server/file/logs and scheduled tasks with the host, rotate credentials if evidence warrants, and request reindexing after cleanup.

Have the data controller/legal adviser verify processor disclosures, lawful basis, retention, consent records, and cookie behaviour. Place a concise privacy link beside the form.