619K impressions in 6 months for a security integrator

Lynx's engineers write world-class documentation for their own clients — spec sheets, install guides, compliance notes. None of that expertise was reaching the public-facing site in a search-friendly form. Instead, service pages leaned on generic industry language that competed with every other integrator's generic industry language.

The audit found a second, more mechanical problem underneath the content issue: significant JavaScript rendering gaps meant Googlebot was seeing a stripped-down version of key pages, missing headings and body copy that only rendered client-side. Impressions were creeping up on the thin server-rendered shell; clicks stayed flat because the shell didn't say anything compelling.

We also found weak internal linking between the industry pages (commercial, education, healthcare, government) and the service pages (access control, surveillance, fire alarm) that should have been feeding each other authority and context.

We ran the same audit-first playbook we run on every engagement: crawl, index coverage, JS rendering diff (rendered vs raw HTML), canonicals, internal links, sitemap accuracy. Every fix logged with an owner and priority so nothing sat in a backlog undone.

Sixty-two distinct technical issues were resolved, the largest cluster being render-blocking scripts that delayed content painting past the point Googlebot's rendering budget typically allows on a crawl pass.

• Technical fix log: 62 issues resolved
• JS rendering diff run across all commercial templates
• Sitemap + canonical accuracy pass

We rewrote every service page with commercial intent — access control, commercial surveillance, fire alarm systems — with clear entity signalling (what the service is, who it's for, what compliance standards it meets) and internal links back to the industry pages that actually convert.

This is where the engineering documentation paid off: once we had permission to mine it for plain-language explanations, the pages stopped reading like brochures and started reading like the answer to a specific buyer's specific question — which is exactly the signal both users and ranking systems reward.

• Rewrote 18 service + industry pages
• Entity-first structure: what, who-for, compliance standard
• Internal links rebuilt between industry and service verticals

LocalBusiness and Service schema went onto every relevant page, giving both search engines and AI-answer surfaces a structured description of what Lynx does and where it operates, rather than requiring inference from unstructured prose.

In parallel, we ran a full Google Business Profile overhaul: category audit against three primary categories, twelve distinct services listed with descriptions, defined service areas, and a weekly posting cadence that kept the profile active rather than dormant.

• LocalBusiness + Service schema on 24 pages
• GBP: 3 categories, 12 services, weekly posts

Beyond the core service page rewrites, we built a smaller content programme around compliance and buyer-education topics — fire code requirements, access control system selection criteria — the kind of question a facilities manager searches before they're ready to talk to a salesperson.

This content was deliberately structured with direct-answer paragraphs near the top, since it does double duty: ranking for informational queries and increasingly surfacing in AI-generated answers where citation-friendly structure matters as much as authority.

Unlike a consumer brand, a B2B security integrator's link opportunities are narrower — trade associations, industry directories, and genuine case-study placements with the facilities and security publications the buyer persona actually reads. We prioritised quality and topical relevance over volume here, since irrelevant link velocity is a liability in a niche this specific.

Google Search Console was the primary source of truth for this engagement because the client's core question — are we ranking for the queries that convert — is best answered by GSC's query-level click and impression data rather than a third-party rank tracker's proxy metrics.

We built a monthly reconciliation that split queries into commercial vs informational buckets, so the team could see clearly that click growth was coming from the commercial bucket the rewrite targeted, not from incidental informational traffic.

The JS rendering fix should have shipped in week one rather than being sequenced behind the full audit — it was the single highest-leverage fix in the entire engagement, and every week it sat unfixed cost the site rendering budget on every subsequent crawl.

We'd also start the GBP category audit earlier; it turned out categories were misconfigured in a way that was actively suppressing local pack visibility, and catching that in month one rather than month two would have compounded an extra month of local impressions.

Month 1: technical audit, JS rendering diagnosis, and fix-log triage.

Month 2: rendering fixes ship; sitemap and canonical cleanup complete.

Month 3: on-page rewrites begin on highest-traffic service pages first.

Month 4: remaining service + industry pages rewritten; schema deployment begins.

Month 5: GBP overhaul complete; weekly posting cadence begins; compliance content published.

Month 6: full measurement reconciliation; +16% click lift confirmed against the prior six-month period.

Clicks grew +16% over the previous 6-month period on 619K impressions. Average position is now 17.3 — the top of page 2 and climbing, with the CTR curve trending in the right direction as the site earns more page-1 features on the commercial queries it now actually targets.

If your organic impressions are healthy but clicks aren't following, don't reach for more content first — check whether Googlebot can actually see what you've already written, and whether that content targets the commercial query, not the adjacent informational one. Technical visibility and on-page intent alignment usually solve more of the problem than volume.