Tag Sprawl on a 420-Post Blog
A SaaS company has blog.example.com with 420 posts, 280 tags, and 18 authors. Sixty percent of tags are used on only one post. Organic sessions are down 22% year over year, while the top 10 posts still drive 70% of blog traffic. The team publishes eight posts per month and has not done a content audit in two years. Internal linking is ad hoc: 35 posts have no internal links in or out, and the blog's tag pages are indexed. A new content strategist wants to build topic clusters, but the sales team wants more bottom-of-funnel comparison pages. The blog sits on a subdomain, and the web team is debating moving it to a subdirectory. The company has HubSpot Marketing Hub Professional and CMS Hub Professional; no dedicated SEO resource.
1. Diagnose the tag problem and propose a HubSpot-executable taxonomy cleanup. What do you do with retired tag URLs?
Read the worked answer
The 280 tags are a structural SEO problem. HubSpot creates an indexable tag listing page for each tag, so 168 single-use tags produce thin pages with one post, little unique copy, and weak internal links. They compete with the posts and dilute crawl paths.
Cleanup: define 12–18 tags that map to real topic clusters, for example onboarding, integrations, pricing, and security. Merge synonyms and misspellings into the survivor. Bulk-edit posts to apply the new tags, then retire the old ones.
Retired tag URLs: create 301 redirects in HubSpot to the closest surviving tag page, or to the blog home if no close match exists. Do not simply delete the tag and let the URL 404. For surviving tag pages, add a short unique intro and links to the pillar post and top posts.
Do not noindex all tags blindly; a well-maintained tag page can support a cluster. Keep tags that earn traffic or serve as cluster hubs, and redirect the rest. Measure indexed tag pages and organic entrances after 60 days.
2. Design a 90-day plan that balances refreshing existing content with creating new comparison pages for sales. Justify the split.
Read the worked answer
Start with the 70% traffic concentration. A 90-day plan:
Days 1–30 - audit and fix: pull top 50 posts by organic sessions and conversions; identify outdated facts, missing CTAs, and cannibalization. Fix the 35 orphan posts by adding links from relevant top posts and cluster pages. Consolidate or redirect overlapping posts.
Days 31–60 - refresh: update 15–20 top posts with current screenshots, examples, and a next-step CTA. Add comparison tables where useful. Build 3–4 pillar pages that link to existing posts; do not create a pillar and leave it orphaned.
Days 61–90 - new bottom-of-funnel: publish 6 comparison or alternative pages tied to sales objections, each with a demo CTA and campaign tracking.
Split: roughly 60% refresh/existing, 40% new. Existing pages already have links and rankings; refreshing them is faster than waiting for new pages. New comparison pages support sales now. Review at 90 days using organic entrances, assisted conversions, and demo requests.
3. Should the blog move from a subdomain to a subdirectory? What evidence would you gather, and what are the risks?
Read the worked answer
Evidence to gather: backlink profile of blog.example.com versus www; organic performance by section; whether subdomain pages already rank; technical effort to move; redirect capacity; analytics continuity; and whether the main domain has stronger topical authority. Google treats subdomains largely independently, so the theoretical benefit is not automatic.
Risks: a migration can lose traffic if redirects are incomplete, internal links are missed, or the move happens during a busy sales period. HubSpot can host the blog on a subdirectory, but it requires domain/DNS work and a full URL map.
Recommendation: do not combine the taxonomy cleanup, content refresh, and domain migration in one quarter. Fix tags and refresh content first; if the business case is still strong, migrate in a low season with a 301 map, updated sitemap, and weekly Search Console monitoring. Otherwise keep the subdomain.