The starting point
VancouverSEO.com had recently returned to public availability. The brief was to improve its ability to compete for Vancouver SEO searches while preserving the existing design and Flor website guide. This is our own site, so the example demonstrates the review and implementation process rather than a client’s commercial result.
The baseline was collected on September 10, 2026 UTC, the evening of September 9 in Vancouver. Public checks included response codes, titles, descriptions, headings, canonicals, source content, internal links and structured data. Google PageSpeed Insights supplied separate laboratory runs for the homepage and SEO service page.
What the crawl confirmed
All 71 sitemap pages returned HTTP 200. Each had one H1, a unique title and description, a self-referencing canonical and an index/follow directive. No broken internal destination was found among the discovered page links.
Those checks established a useful technical baseline. They did not prove that Google had indexed all pages or selected the declared canonical. Authenticated Search Console data was not available for that conclusion.
What needed attention
- The homepage’s main heading described a benefit without clearly naming Vancouver SEO.
- The SEO services page contained approximately 269 main-content words, including shared calls to action.
- Twenty-five descriptions exceeded 200 characters, with several city introductions being reused as metadata.
- The case-studies page had no incoming link from the 71-page crawl and contained no actual project example.
- Public www URLs served duplicate copies even though source-level redirect logic existed.
- The hero image and Google Font loading created performance opportunities.
The performance baseline
| Page and device | Performance | LCP | CLS |
|---|---|---|---|
| Homepage · mobile | 88/100 | 3.3 s | 0.015 |
| SEO services · mobile | 93/100 | 2.6 s | 0 |
| SEO services · desktop | 99/100 | 0.7 s | 0.006 |
These are the original measurements before this update. They are individual lab tests; no site-wide field-performance conclusion or post-launch score is implied. The homepage desktop test did not complete because the testing service returned errors.
How the findings shaped the update
The content work gives the homepage an explicit Vancouver SEO focus, expands service scope and implementation explanations, and connects pricing, team information and project evidence with contextual links. Descriptions are now written separately from longer page introductions. Articles receive visible organizational authorship, accurate update information and practical supporting material.
The performance work creates responsive WebP versions of the existing image and serves the site’s font files locally. Technical changes address canonical URL handling, asset caching and the discrepancy between the source’s routing rules and public responses. Useful existing page addresses are preserved.
October 13 follow-up: 79 live pages checked
A new public crawl on October 13, 2026 checked all 79 URLs in the sitemap. Every page returned HTTP 200 and exposed one title, description, H1 and matching canonical URL. The crawl found no noindex meta directives or unknown internal page destinations. These are public response checks, not a count of pages indexed by Google.
The follow-up identified practical improvements beyond those basics: the homepage used a 254 KiB JPEG despite smaller WebP versions being available; guide links led to service pages; and the resources hub did not make the local SEO articles easy to find. The revised homepage uses responsive WebP images, links directly to the diagnostic and local SEO guides, and explains service scope and customer questions in more detail.
For measurement, the form’s confirmed-save signal is now connected to GA4’s generate_lead event. This records a saved enquiry without sending form contents or an enquiry reference. It does not establish lead quality, attribution or a growth result. The earlier laboratory speed scores above remain historical; they have not been replaced with an assumed new score.
Google-selected canonicals, indexing exclusions and query positions still require authenticated Search Console review. A successful public crawl cannot resolve those questions.
What happens after implementation
A content release is not a ranking result. The next assessment needs Google’s indexing and query data, comparable search periods and confirmed enquiry records. That evidence can show whether the intended pages are appearing for relevant searches and whether visitors are taking valuable actions.
The same distinction applies to a client project: record the baseline, implement an agreed scope, verify the change and evaluate business outcomes over time. A single favourable keyword screenshot or Lighthouse score cannot answer all four questions.