What is Content Auditing?

What is content auditing?

A content audit is a systematic, end-to-end inventory and quality assessment of every piece of content on a website. The output is a spreadsheet (or database) listing each URL with verdicts: keep as-is, update, consolidate with another page, noindex, or delete. Done well, a content audit is the foundation of major SEO recoveries, accessibility compliance work, brand voice consistency projects, and migrations between CMSs.

The standard scope includes: URL, page title, meta description, word count, last-updated date, organic traffic (last 90 days), conversions, internal link count in/out, target keyword, and a freshness score. The deliverable is the verdict column — what action to take per page.

Why content audits matter (especially after Google's HCU)

Google's Helpful Content Update (HCU) of August 2022 introduced site-wide quality classification: pages with thin or unhelpful content can demote the entire site, not just themselves. After HCU, sites that had accumulated thousands of mediocre auto-generated pages saw catastrophic ranking drops. The fix is auditing — identifying which pages drag the site quality signal down, then removing or improving them.

Beyond SEO recovery, content audits drive: site migrations (which pages move?), template redesigns (which pages need different layouts?), accessibility remediation (which pages fail WCAG?), and brand voice projects (which pages drift from current tone of voice?).

How to run a content audit (5 steps)

1. Crawl the site. Screaming Frog, Sitebulb, or DeepCrawl all work. Output: a list of every reachable URL with title, meta, status code, content-length, internal links.
2. Layer in performance data. Pull 90-day organic clicks/impressions from Google Search Console per URL. Pull conversions from analytics. Now each URL has both editorial metadata and traffic/business signal.
3. Score quality. A simple rubric: word count below 200 = thin; not updated in 24+ months = stale; zero clicks AND zero impressions in 90 days = invisible. Composite score per URL.
4. Decide actions. Standard verdicts: KEEP (high-traffic, recent, on-brand), UPDATE (good topic, stale execution), CONSOLIDATE (multiple weak pages on same topic merge into one strong page), NOINDEX (low-value but worth keeping accessible), DELETE (no traffic, no conversions, low quality).
5. Execute and measure. Apply the actions in waves. Measure CrUX/GSC after 30/60/90 days. Iterate.

What to look for: red flags during audits

• Cannibalization. Multiple URLs targeting the same keyword. Google can't decide which to rank, so nothing ranks well. Consolidate.
• Orphan pages. Pages with zero internal links pointing to them. Crawlers can find them via sitemap but they get no PageRank flow. Either link them in or noindex.
• Duplicate content. Two pages with 80%+ identical text. Pick one as canonical or merge. Common cause: faceted navigation creating thousands of near-duplicates.
• Auto-generated thin content. The classic HCU trigger. Templated pages with one-paragraph descriptions. If they don't earn organic traffic, noindex or delete in bulk.
• Broken internal links. Links to deleted pages, 404s discovered during the crawl. Fix or redirect.
• Stale content. Articles with 2020 dates that don't reflect current best practice. Either rewrite with new date or update in place.

Tools for content auditing

• Crawlers: Screaming Frog (desktop, free up to 500 URLs), Sitebulb (paid, polished UI), DeepCrawl/Lumar (enterprise SaaS).
• Analytics integration: Google Search Console for organic clicks; GA4 for conversions; Ahrefs/Semrush for external link data and keyword rankings.
• Quality scoring: Custom spreadsheet with formulas, or specialized tools like ContentKing (Conductor) for ongoing quality monitoring.
• Performance check: Audit pages that survive should also be performant — run them through PageSpeed Insights or LoadFocus to flag slow/broken templates.

FAQ: Content Auditing

How often should I run a content audit?

Full site audit: annually for most sites, quarterly for fast-moving content sites (news, e-commerce). Targeted audits (e.g. just blog content, just product pages) every 6 months. After major Google algorithm updates, ad-hoc audits are usually worth doing.

How long does a typical content audit take?

Small site (under 500 URLs): 1-2 weeks for one person. Medium site (500-5,000): 4-6 weeks. Enterprise (50,000+): 3-6 months and a dedicated team. The crawling and data-pulling is fast (days); the editorial verdicts and execution take the time.

What's the difference between a content audit and a technical SEO audit?

A content audit evaluates the editorial quality and traffic of each page. A technical SEO audit evaluates infrastructure: crawlability, indexability, site speed, schema markup, redirects. Run both — they complement each other but answer different questions.

Should I delete or noindex underperforming pages?

Generally noindex first, watch for 60 days, then delete only if there's no negative impact. Deleting causes 410/404s which lose any external links the page had. Noindex preserves those links while removing the page from search.

Do content audits help with Core Web Vitals?

Indirectly. The audit identifies pages worth keeping; you then ensure those pages meet CWV thresholds. Audits also catch slow templates that affect many URLs — fixing one template may improve CWV across thousands of pages.

Can content audits be automated?

The data collection (crawl, GSC pulls, GA4 pulls) automates well. The verdicts (keep/update/delete) require human judgment — automated quality scoring is decent but misses brand voice, topical relevance, and strategic context.

How LoadFocus relates to content auditing

After identifying which pages survive your audit, validate they perform well. Run scheduled LoadFocus speed tests on the surviving URLs to confirm Core Web Vitals are passing across all locales and regions. Pages that pass the editorial bar but fail CWV need template fixes — content audits and performance audits work together.