The blog post at collections/_posts/2025-10-23-time-tracking-software-for-architects.md was ranking in Google for “time tracking software for architects” but getting no clicks.
Body text in .single-blog-content-body p (in assets/css/pages/blog.scss) appeared heavy and hard to read across all blog posts.
Searched “time tracking software for architects” and found:
CTR problem:
Typography problem:
InterDisplay is a display font — designed for headings, not body text. At body sizes it has wider letter shapes and heavier strokes than a standard text face. Combined with tight line-height and washed-out color, it made paragraphs feel dense and hard to scan.
BEFORE: "Time Tracking Software For Architects"
AFTER: "Time Tracking Software for Architects: How to Choose the Right Tool"
Adds a hook (“How to Choose”) that differentiates from pure listicles while matching commercial intent.
BEFORE: "Discover how integrating project management and accounting can boost profits
and streamline operations. Learn key strategies for financial project success."
AFTER: "Choosing time tracking software for your architecture firm? Here's what
actually matters — from phase-level tracking to integrated invoicing —
and how to find the right fit."
Now directly addresses the search intent and contains the primary keyword.
| Element | Before | After |
|---|---|---|
| Word count | ~4,000 (fluffy) | ~2,500 (tight) |
| Content angle | Educational (“why you need tracking”) | Commercial (“how to choose the right tool”) |
| Drum positioning | Final paragraph only | Throughout, with 2 inline CTAs |
| H3 subheadings | 10+ nested | 0 (bold lead-ins instead) |
| External sources | yaware.com, archivemarketresearch.com | AIA 2024 Firm Survey, Deltek AE Clarity Report, SPI Research |
| Internal links | 2 | 6 |
| Images | Generic CDN stock photos | Drum product screenshots from homepage set |
| CTA messaging | Mismatch (“14-day trial” copy / “Book a Demo” button) | Aligned: “Book a free demo” throughout |
File: assets/css/pages/blog.scss — .single-blog-content-body
/* BEFORE */
p {
font-size: 1.25rem;
line-height: 150%;
margin: 1rem 0;
color: $neutral-600; /* #4b5565 */
}
/* AFTER */
p {
font-size: 1.125rem;
font-weight: 400;
line-height: 170%;
margin: 1.5rem 0;
color: $neutral-700; /* #364152 */
}
/* BEFORE */
strong { font-weight: 800; color: $neutral-900; }
/* AFTER */
strong { font-weight: 600; color: $neutral-900; }
800 loaded InterDisplay-Bold which was far too heavy inline. SemiBold (600) provides enough emphasis.
/* BEFORE */
li {
font-size: 1.25rem;
font-weight: 500;
line-height: 2.5rem;
}
/* AFTER */
li {
font-size: 1.125rem;
font-weight: 400;
line-height: 170%;
margin-bottom: 0.25rem;
}
List items were heavier than paragraphs (500 vs inherited 400), creating visual inconsistency. Fixed line-height uses relative value matching paragraph rhythm.
Before drafting any blog post:
| Property | Value | Rationale |
|---|---|---|
| font-size | 1.125rem (18px) | InterDisplay display font is too heavy at larger sizes |
| font-weight | 400 (explicit) | Prevent inheritance; display fonts render heavier than text faces |
| line-height | 170% | Comfortable for long-form reading at this font size |
| margin | 1.5rem 0 | Paragraphs need breathing room |
| color | $neutral-700 (#364152) | Sufficient contrast without being pure black |
| strong weight | 600 (SemiBold) | 800 (Bold) is excessive for inline emphasis with display fonts |
| list item weight | 400 | Must match paragraph weight for consistency |