SEO campaign

# Local Van SEO campaign · v2 19 November 2026 · Review and launch plan The v2 review build covers all ten existing town routes. Chichester, Portsmouth and Southampton remain the proposed first release cohort. The seven other drafts can be reviewed in parallel for operational coverage, service capacity and local evidence. Use the exact metadata mapping for route decisions and the WordPress staging handoff for implementation and rollback. The objective is to earn Google UK organic position 1 for selected commercial queries in the towns Local Van serves. Begin with Chichester, Portsmouth and Southampton. Track organic listings and Google Maps separately at fixed locations and on mobile and desktop. Prioritise qualified quotes and completed bookings when choosing what to improve. Rankings and timelines depend on competition, location and execution. ## What the public audit established - The homepage targets affordable removals, house moves, man and van and instant pricing through its title, descriptions and body. None of the 49 audited public HTML responses contained a meta-keywords tag. Google ignores that tag for indexing and ranking. [Google supported meta tags](https://developers.google.com/search/docs/crawling-indexing/special-tags) - The robots file points to a Yoast sitemap index. Its 12 children contained 95 distinct URLs, including test, demo, template, inventory and commerce URLs. Review whether each URL serves a useful search purpose before changing its indexing status. The homepage, the ten city pages and several support pages have duplicated descriptions. Homepage headings repeat across responsive variants and booking UI. [Public sitemap](https://local-van.com/sitemap_index.xml) · Source evidence - The homepage has no direct links to the ten city pages. Competing city-related articles may overlap the local landing pages. The Southampton body includes Portsmouth copy. The Portsmouth and Chichester pages reuse Southampton image text. The Guildford page lives at the existing misspelled slug and its corrected spelling currently returns 404. Sitemap inventory · [Southampton](https://local-van.com/southampton-removals/) · [Guildford](https://local-van.com/guilford-removals/) - One production homepage fetch measured 440,388 bytes of decoded HTML, 98,194 bytes transferred as gzip, 40 unique script sources and 21 stylesheet URLs. This is a page-weight observation. Google field performance and actual rankings still need measurement. [Google page experience](https://developers.google.com/search/docs/appearance/page-experience) - Local Van's site publishes a Google share identifier in its organisation markup. Its contact page and Yell record match on telephone and Chichester postcode. Confirm the Google listing and eligibility with the owner before editing or creating anything. [Contact](https://local-van.com/contact-us/) · [Yell listing](https://www.yell.com/biz/local-van-chichester-9979269/) · [Google Business Profile guidelines](https://support.google.com/business/answer/3038177) ## Keyword and landing-page ownership The terms below are research seeds. The tracking CSV contains the core pilot query set, a Search Console UK Web starter cohort for the seven additional towns and empty observation fields. Confirm which phrases generate demand and leads before expanding the page set. | Priority | Intent and query seeds | Primary destination and change | | --- | --- | --- | | P0 | Brand and general quote · Local Van, Local Van removals, instant removal quote | [Homepage](https://local-van.com/). Give visitors clear house-removal and man-and-van entry points, link to priority towns and lead with the quote. Keep the transactional step at [/instant-price/](https://local-van.com/instant-price/). | | P0 | Chichester removals, house removals Chichester, man and van Chichester | [Chichester](https://local-van.com/chichester-removals/). Add practical move preparation and local loading guidance. Obtain an approved local job example. | | P0 | Portsmouth removals, house removals Portsmouth, man and van Portsmouth | [Portsmouth](https://local-van.com/portsmouth-removals/). Correct inherited Southampton labels and add Portsmouth-specific parking and access guidance. | | P0 | Southampton removals, house removals Southampton, man and van or man with a van Southampton | [Southampton](https://local-van.com/southampton-removals/). Remove the Portsmouth mismatch and lead with Southampton move planning. | | P1 | Bognor Regis, Worthing, Brighton, Bournemouth, Crawley, Horsham and Guildford removals or man and van | Retain each live sitemap route. Confirm current operational coverage and real local evidence before expanding content. Begin with towns showing Search Console impressions and capacity. | | P1 | What size removal van, moving van size guide | [Van size guide](https://local-van.com/van-size-guide/). Give it a unique informational title and description and link relevant advice to it. Give the [quote page](https://local-van.com/instant-price/) its own transactional metadata. | | P2 | Furniture collection, Marketplace collection, student removals, storage transport, upright piano transport | Homepage services and relevant city sections first. Add a dedicated page where customer demand, verified service detail and useful original material justify it. | Direct organic examples include Transport Executive and Hampshire Man & Van in Chichester, Man and a Van Southampton and Van and Man Southampton, and Man and Van Portsmouth and Mr Tee Removals. Compare clarity of the quote path, useful service coverage and local proof. For Maps, check the named businesses during the fixed-location baseline, including Regis Removals, Breeze Removals, Pack & Stack Removals and Mr Tee Removals. Their current pack positions remain unverified. Competitor and query evidence ## 30 / 60 / 90 days The checkpoints start once the owner authorises production work and the WordPress source, rollback path and measurement access are established. | When | Priority and owner | Work and acceptance | | --- | --- | --- | | Days 1–10 | P0 · SEO and owner | Export UK Web Search Console data for the previous 28 days, prior 28 days and available prior-year period, split by page, query and device. Record local searches at city-centre and one confirmed served postcode per pilot town. Baseline organic quote starts, completed bookings and customer enquiries with existing consent controls. Capture Business Profile and citation records where access exists. | | Days 1–20 | P0 · WordPress engineer | Back up content, theme, plugins and database and verify restore to controlled staging. Trace the duplicate-description emitters. Remove the duplicate at source, use one meaningful H1 per page, set `en-GB` and `en_GB` where appropriate, and harmonise the visible page, titles, social cards and schema. Test raw and rendered HTML across the changed routes. | | Days 1–30 | P0 · WordPress engineer and SEO | Preserve live routes. Review `/home-test/`, demo testimonials, template/category URLs, inventory and checkout/cart for user purpose, inbound links and current indexation. Apply a targeted redirect for a genuine replacement, `noindex` where a utility should remain usable, or 404/410 for a confirmed obsolete record. Remove ineligible URLs from the sitemap. Keep pages crawlable for Google to see their `noindex`. Check live inspection after release. | | Days 1–30 | P0 · Design and QA | Approve homepage and pilot city content, then bring the design into the existing Avada/WordPress stack on protected staging. Keep the existing booking shortcode, operational settings, quote, cart, payment and confirmation integration. Compare a link-first homepage with the live embedded quote before selecting the production treatment. Require mobile, keyboard, quote and sandbox payment regression checks and a working rollback. | | Days 15–45 | P1 · WordPress engineer | Inventory dependencies by template and defer or omit scripts only where staging proves they are unnecessary. Use responsive images with reserved space and local fonts where suitable. Audit mobile quote rendering and interaction separately from marketing pages. Compare controlled lab runs with consent states and follow field p75 for LCP ≤2.5 s, INP ≤200 ms and CLS ≤0.1 where data exists. | | Days 30–60 | P1 · SEO and owner | Publish approved pilot changes on their current URLs. Validate qualified canonicals, descriptions, headings, sitemap and cross-links. Inspect each pilot in Search Console. Add one real permissioned job example and helpful local move information for each pilot before widening the rollout. Audit existing Business Profile categories, hours and service areas with the owner. | | Days 45–75 | P1 · Owner and SEO | Reconcile accurate existing citations. Approve relevant local partnerships and resources that can earn editorial mentions, such as a student move checklist or a removal-day access guide. Invite genuine customers to leave an honest review through an owner-approved workflow. Avoid incentives, review gating and paid links. | | Days 60–90 | P2 · SEO and owner | Compare matched 28-day windows for pilot landing pages. Investigate lost clicks, cannibalisation and quote drop-offs. Expand into existing towns and service content where demand, capacity and job proof overlap. Review map coverage at the same locations and assess the position-1 objective per query/location/device. | [Google canonical guidance](https://developers.google.com/search/docs/crawling-indexing/canonicalization) · [Page experience](https://developers.google.com/search/docs/appearance/page-experience) · [Google spam policies](https://developers.google.com/search/docs/essentials/spam-policies) ## URL, schema and release checklist 1. Keep the existing homepage, town, guide, advice, quote, shop and account destinations. Correct Guildford spelling in visible copy without changing the existing slug. If a later slug change is approved, use one permanent redirect, update internal links and the sitemap, then verify the old and new URLs and monitor signals. Review city articles against each city’s main landing page before keeping, consolidating or redirecting them. 2. Emit exactly one self-canonical on each released indexable page. Keep preview protection during review and use authenticated staging for online QA. On production only, verify intended status, HTML robots directives, headers and sitemap entries after release. Verify no staging URLs appear in production canonicals or links. 3. Use a single consistent Organization identifier and a clean WebSite/WebPage graph. The pilot previews include factual Service markup. Add LocalBusiness markup only once the owner confirms the properties and publishing eligibility. City service pages do not establish a storefront. Validate syntax, check rendered values against visible content and test applicable results with Google tools. [Google LocalBusiness documentation](https://developers.google.com/search/docs/appearance/structured-data/local-business) 4. Run the quote flow in staging using test mode across van types, stops, loading help, optional extras, availability, checkout, successful and declined payment, confirmation and recovery after an interrupted attempt. Check postcode, contact and payment handling. Confirm existing pathways for survey, login, driver signup, customer terms and box shop. Verify the rollback by restoring the prior staging build. Pre-agree the owner and thresholds for traffic/booking anomalies before enabling a production release. ## Measurement - Fix the sampling points before launch: Chichester, Portsmouth and Southampton city centre and one operator-confirmed outer service point each. Record actual place, local timestamp, device, query, organic rank and result URL. In separate rows, capture local pack and Maps placements and listing links. Use repeatable manual checks or an approved tool. When a result is absent within the inspected range, record the range examined. [Google local ranking factors](https://support.google.com/business/answer/7091) - In Search Console, use **Performance → Search results → Web**, country United Kingdom, and query/page/device filters. Export branded and non-branded cohorts with clicks, impressions, CTR and average position. Use URL Inspection for Google canonical and indexing decisions, and compare changed URLs and non-pilot towns for context. [Search Console Performance report](https://support.google.com/webmasters/answer/7576553) - Preserve the live analytics implementation until reviewed. Define `quote_cta_click`, `quote_started`, `quote_completed`, confirmed `booking_completed`, `survey_click` and verified enquiry conversions. Prefer confirmed booking events deduplicated by a non-PII transaction identifier. Exclude postcodes, names, payment details and phone numbers from analytics payloads. Validate event ordering and consent in staging. Count an outbound survey click as interest until a confirmed booking signal is available. Keep conversion totals at the landing-page, source, device and matching date-window level. Enter them on separate page-level rows in a working copy of the worksheet, since Search Console queries cannot attribute individual bookings. Use Notes to record the reporting window. - Day 30 target: baseline recorded, staged quote/checkout acceptance signed off, targeted leakage decisions logged. Day 60 target: every approved pilot page has one H1, description and self-canonical and passes inspection; dashboard reports quote and booking funnels. Day 90 target: compare UK non-brand organic clicks, qualified quote starts and completed bookings against baseline and record progress toward top three and position 1. Set numeric growth targets after the baseline is known. First-party input still needed for live campaign measurement and release is owner-granted Search Console and Business Profile access, WordPress staging/source with restoration evidence, and an approved analytics and sandbox payment test path.