Content cannot fix a broken technical base. Run this checklist before you invest in a blog sprint.
Crawl and index
- `robots.txt` allows important paths
- XML sitemap submitted and only includes live URLs
- No accidental `noindex` on service pages
- HTTPS everywhere; redirect HTTP → HTTPS
Page essentials
- Unique title and meta description per URL
- One H1 that matches the offer
- Canonical tags when duplicates exist
- Fast mobile LCP on homepage and key services
Structure
- Logical URL paths (`/services/ai-automation`)
- Internal links from home and services index
- 404s that help people recover
- Redirects when you rename services (keep equity)
Schema worth having
- Organization
- WebSite
- Service (for each pillar)
- Article (for blog posts)
Keep schema accurate. Fake reviews or inflated offers backfire.
Then content
Only after the base is clean should you scale articles for SEO and GEO. Otherwise you publish into a leaky bucket.