Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

Lamplight Chimney Sweeps · Philadelphia

How an 8-crew chimney sweep got its service pages back into Google before autumn

+145% organic booking requests by September

6 months · North America · Signal plan · Indexation repair · Hosting & caching · Render-blocking scripts · Core Web Vitals

Sweeps · Inspections · Philadelphia

Organic booking requests (September, year on year)+145%

IThe challenge

The busy season was coming. The website couldn’t be seen.

A plugin had noindexed 24 of 27 service pages, while 14 render-blocking scripts and a slow host left the rest loading in 6.8 s, just before chimney season.

Eight crews, a phone that rings off the hook from the first cold night, and a website rebuilt over the winter. Then a routine plugin update quietly told Google to drop the service pages, and the pages that stayed took nearly seven seconds to appear on a phone. Through the spring, enquiries came mostly from paid lead marketplaces at a steep price per lead. The brief: be findable, and fast, before the leaves turned.

Search demand for chimney services, by month
JanFebMarAprMayJunJulAugSeptOctNovDecPEAK

Index, October = 100 · shaded: the engagement, Apr–Sept

58%of the year’s inspections are booked between September and December.

IIThe inspection

Five layers of creosote, from the firebox up.

We inspected the site the way a sweep inspects a flue: from the bottom, one layer at a time, writing down what each one was blocking and how badly.

Inspection report · lamplightsweeps.example

↓ Firebox

  1. Layer 1

    A plugin hid the service pages

    An SEO plugin update switched the Services post type to noindex. Within weeks, 24 of 27 service pages had dropped out of Google: inspections, liner repair, cap installs and every neighbourhood page.

    The fixReversed the setting, removed the stray meta tag from the theme and asked Google to recrawl every service page.

    3 of 27 indexed

  2. Layer 2

    A crowded shared host

    Server response time averaged 1,420 ms on a busy shared plan with no page cache. Each time the host stalled, Googlebot slowed its crawl.

    The fixMoved to managed hosting with full-page caching and a CDN in front.

    1,420 ms TTFB

  3. Layer 3

    Fourteen scripts before the first word

    A chat widget, three tracking tags, a slider library and two copies of jQuery sat in the <head>: 14 render-blocking requests and 2.3 s before a mid-range phone could paint anything.

    The fixRemoved or deferred 12 of them; one tag manager instead of three; chat loads on first tap.

    14 blocking requests

  4. Layer 4

    A 3.4 MB photo of a rooftop

    The largest element on every page was an uncompressed rooftop photo, lazy-loaded by mistake, so the browser fetched it last.

    The fixServed as AVIF at the right sizes (148 KB), preloaded and never lazy-loaded above the fold.

    3.4 MB hero image

  5. Layer 5

    A sitemap full of the wrong pages

    The XML sitemap listed image attachment pages, tag archives and test pages. Not one service page was in it, and canonicals still pointed at http.

    The fixRebuilt with the 34 pages that matter, canonicals moved to https, resubmitted in Search Console.

    12 of 131 URLs were real pages

↑ Chimney pot

IIIThe sweep

Four tools, used in the right order.

Built on our Signal plan: technical SEO for sites where crawling, indexing and speed decide whether anyone finds you at all.

  1. 1

    Indexation repair

    Traced the noindex to a single plugin setting, reversed it, cleaned the theme and fixed the http canonicals. All 27 service pages were back in the index within five weeks.

  2. 2

    Hosting & caching

    A managed host with full-page caching and a CDN took server response from 1,420 ms to 180 ms. Googlebot’s crawl rate roughly tripled once the host stopped stalling.

  3. 3

    Render-blocking scripts

    Three tracking tags became one tag manager, the slider and the second jQuery went, and the chat widget now waits for a tap. Blocking requests: 14 down to 2.

  4. 4

    Core Web Vitals

    The hero photo was cut from 3.4 MB to a 148 KB AVIF and preloaded. Mobile LCP at p75 fell from 6.8 s to 1.9 s, with CLS and INP staying green.

IVSweep the flue

Brush out each layer and watch the page render clean.

Each band of creosote is one blocker the audit found. Brush them out in any order: the gauges show what each fix does on its own to indexing and to load time on a mid-range phone.

Tap a layer, or use the brush buttons. Arrow keys move between layers.

Layers swept: 0 of 5

Service pages in Google
3 / 27
Server response (TTFB)
1,420 ms
Page appears (LCP, mobile)
6.8 sgood: under 2.5 s
Real pages in the sitemap
9%
What the phone waits for
  • Server 1,420 ms
  • Blocking scripts 2,300 ms
  • Hero image 2,400 ms
  • Layout & paint 700 ms

6.8 s

Google, for chimney inspection philadelphia

lamplightsweeps.example › services › chimney-inspection

Chimney Inspection in Philadelphia | Lamplight Chimney Sweeps

Excluded by a noindex tag: not shown in search at all.

Layer 1: noindex tag

A plugin hid the service pages

What we found

An SEO plugin update switched the Services post type to noindex. Within weeks, 24 of 27 service pages had dropped out of Google: inspections, liner repair, cap installs and every neighbourhood page.

What we did

Reversed the setting, removed the stray meta tag from the theme and asked Google to recrawl every service page.

VMonth by month

6 months, from the firebox to the chimney pot.

  1. APRIL

    Month 1

    Inspect

    Full crawl, Search Console coverage, field data, a load waterfall on a mid-range Android, and booking requests matched to landing pages.

    LCP 6.8 s3 of 27 indexed

  2. MAY

    Month 2

    Unblock indexing

    Plugin setting reversed, stray noindex removed, sitemap rebuilt with 34 real URLs, every service page submitted for recrawl.

    LCP 6.8 s19 of 27 indexed

  3. JUNE

    Month 3

    Re-home

    Managed host with full-page cache and a CDN, tested on staging first, cut over late on a Tuesday between bookings.

    LCP 5.6 s27 of 27 indexed

  4. JULY

    Month 4

    Clear the render path

    Fourteen blocking requests down to two: tags merged into one manager, slider dropped, chat loaded on first tap.

    LCP 3.6 s27 of 27 indexed

  5. AUGUST

    Month 5

    Lighten the page

    Hero photos to AVIF with proper sizes and preload, fonts subset. Mobile LCP reaches 1.9 s in field data.

    LCP 1.9 s27 of 27 indexed

  6. SEPTEMBER

    Month 6

    First frost

    Inspection and neighbourhood pages climb as demand turns. Weekly checks while the crews book out into November.

    LCP 1.9 s27 of 27 indexed

VIResults

Swept clean before the first frost.

Organic booking requests (September, year on year)

+145%

80 → 196 requests in September, year on year

Service pages indexed

3 → 27

3 of 27 service pages were in Google before the fix

Mobile LCP (p75)

6.8 s → 1.9 s

Mobile field data, p75 · good is under 2.5 s

Server response (TTFB)

1,420 ms → 180 ms

Median, managed host with full-page cache

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

Organic booking requests per monthThis yearLast year
050100150200AprMayJunJulAugSept19680

Where the service pages rank now

QueryMar, beforeSept, after
chimney sweep philadelphia#31#3
chimney inspection near menot indexed#4
level 2 chimney inspection philadelphianot indexed#2
chimney liner repair philadelphianot indexed#5
chimney cap installationnot indexed#7
fireplace inspection before buying a housenot indexed#6

Average Google position in Philadelphia; queries shown as searched.

Get a plan like this

Service pages missing from Google, or a site that crawls along on a phone? Start with the Signal plan, or tell us what is blocking yours.

← All case studies