Tag archives
412
of 600 tag archives indexed
ReasonNot payable: thin content
Most tags held one to three posts. Together they took 38% of Googlebot’s visits, and 23 of them outranked a service page for its own query.
A fictional business. The figures are a modelled scenario, not a client result.
Nilgiri Chartered · 40-person chartered accountancy firm · Pune
Every service page back in the index, +205% organic enquiries
Pune, India · 10 months · Signal plan · Finance & professional
The challenge
A slow WordPress site with 600 tag archives and cloned city pages: Google indexed the tags while the ‘GST registration Pune’ page dropped out.
The firm had grown by word of mouth across Pune for twenty years, and its WordPress site had grown the same way: a tag for every post, a copy of each service page for every town a client came from, and a theme that never quite worked on a phone. Google was clearing the wrong cheques. Tag archives were indexed and ranking, while the GST registration page, the one new clients actually search for, kept dropping out of the index.
Index statement · month 0
| Account | URLs | Indexed |
|---|---|---|
| Tag archives | 600 | 412 |
| City duplicates | 46 | 31 |
| Service pages | 14 | 5 |
| Blog, home & about | 88 | 71 |
Googlebot spent 38% of its visits on tag archives.
The audit
We crawled the whole site, read three months of server logs and opened every service template on a mid-range Android phone over 4G.
412
of 600 tag archives indexed
ReasonNot payable: thin content
Most tags held one to three posts. Together they took 38% of Googlebot’s visits, and 23 of them outranked a service page for its own query.
46
near-identical city pages
ReasonDuplicate instrument
Six services cloned for up to nine Maharashtra towns, with only the town name changed. Google indexed 31 of them and picked its own canonical for the rest.
0/14
service pages that work on a phone
ReasonInstrument mutilated
Fee tables ran off the screen, a sticky header covered the enquiry button and the fonts swapped late. With mobile-first indexing, this is the version Google judges.
6.1 s
median mobile LCP
ReasonPresented late
A page builder, 31 plugins and uncompressed photos of the office: 3.4 MB per page over a 4G connection.
The plan
Built on our Signal plan: technical SEO only, no content campaign, ten months from the first crawl to the last re-crawl.
Counterfoil Nº 01
Every tag was set to noindex for six weeks so Google could see the signal, then removed with a 410. The blog moved into 8 categories with proper introductions.
412 → 0 tag pages indexed
Counterfoil Nº 02
The city copies were merged into the service pages with 301 redirects. Each service page is self-canonical and says plainly which towns the firm serves.
46 redirects into 14 service pages
Counterfoil Nº 03
Page builder out, a lean theme in. Plugins cut from 31 to 9, photos resized and served as WebP, fonts self-hosted with a fallback that does not shift the layout.
Mobile LCP 6.1 s → 1.9 s
Counterfoil Nº 04
Every service template rebuilt for a 360-pixel screen first: fee tables that stack, an enquiry button that stays put, tap targets sized for a thumb.
14 of 14 service pages work on a phone
The clearing house
Each cheque is one URL. Its amount is the organic clicks it earns a month, its signature is the canonical, and the MICR line along the bottom carries the status code and two Core Web Vitals. Choose month 0 or month 10, then present the cheques and see what Google clears and what it sends back.
In tray
Clearing slot
Drag a cheque here, or tap one in the tray.
Status codeLCP, s CLS Serial
Cleared · indexed
Nothing yet
Returned · out of the index
Nothing yet
Ten months
Service pages in the index, out of 14
Months 1–2
A full crawl, three months of server logs and every template tested on a phone. The baseline: 412 tags and 31 city copies in the index.
Months 3–4
All 600 tags set to noindex and taken out of the sitemap. Six weeks later they were removed with a 410, and the blog was regrouped.
Months 5–7
46 city copies merged into 14 service pages with 301 redirects. The page builder replaced by a lean theme, plugins cut from 31 to 9.
Months 8–10
Mobile templates finished, images and fonts fixed, sitemaps resubmitted. By month 9 all 14 service pages were in the index.
Results
Organic enquiries / month
+205%
19 → 58 enquiries a month from organic search
Tag pages indexed
412 → 0
plus 46 city copies redirected
Service pages indexed
5 → 14 of 14
all indexed, 9 of them on page one
Mobile LCP
6.1 s → 1.9 s
median, service templates, mid-range Android on 4G
Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.
Core Web Vitals on mobile
The tick marks Google’s “good” threshold. Grey: month 0. Green: month 10.
| Account | Month 0 | Month 10 |
|---|---|---|
| Tag archives | 412 | 0 |
| City duplicates | 31 | 0 |
| Service pages | 5 | 14 |
| Blog, home & about | 71 | 79 |
| Query | Month 0 | Month 10 |
|---|---|---|
| gst registration pune | #31 | #4 |
| company registration in pune | #24 | #3 |
| statutory audit firm pune | #14 | #2 |
| tds return filing pune | 50+ | #5 |
| ca firm in pune | #18 | #6 |
| gst consultant pimpri chinchwad | #40 | #7 |
Google positions, mobile, searched from Pune. Modelled.
Our Signal plan starts with the same audit: a full crawl, your server logs and a phone in hand.