Content Audit That Delivers: Update Plan, Matrix & Templates

Systematic content revision shows what to keep as-is, what to update, what to merge and what can be removed safely. Below is a practical guide: checklists, a decision matrix, a working spreadsheet template, a 30/60/90 plan and rules for safe redirects.

What a content audit is and why you need one

In short: it’s an inventory and assessment of pages using business and search data to grow organic, relevant traffic and conversions. An audit reveals thin content, duplicates, query cannibalization, content gaps and outdated materials that hurt E‑E‑A‑T (Experience, Expertise, Authoritativeness, Trustworthiness).

What a content audit delivers in B2B and IT:

• Growth of targeted organic traffic by removing duplicates and strengthening leaders.
• Better visibility for important clusters where content gaps exist today.
• Higher conversions by updating articles, offers and CTA blocks.
• Reduced marketing debt: fewer pages means easier governance and more efficient crawl budget.

When and how often to run an audit (scenarios and cadence)

• Regularly: every 3–6 months for active blogs and media, and every 6–12 months for corporate B2B sites.
• Event-driven: migration/redesign, organic drop, strategy shift, new product line launch, regional expansion.
• Russian context (Yandex): account for regionality. Check region tags in Yandex.Webmaster and separate city queries (e.g., “outsourced development Moscow/SPb/Kazan”). Note recalculation happens in waves; observation window after release is 4–8 weeks.
• International context: when working with logs and user data comply with GDPR/CCPA and consider differences in available tools (Yandex may be unavailable in some regions).

Preparation: collecting the URL inventory (sitemap, crawler, logs, GSC/Webmaster)

The goal of this stage is to get a complete, clean list of URLs with technical and business fields.

What to collect:

• sitemap.xml: primary list of indexable URLs and lastmod dates.
• Site crawl: Screaming Frog (or equivalent) — status codes, canonical, H1–H2 headings, meta, depth.
• Server logs: actual bot crawling, crawl frequency, non-indexable sections that consume budget.
• Google Search Console and Yandex.Webmaster: impressions, clicks, CTR, positions, pages with indexing issues.
• GA4 and Yandex.Metrica: sessions, landing pages, micro- and macro-conversions (CV), user paths.
• Backlinks: Ahrefs/Semrush — incoming links and anchor lists.

How to avoid traps:

• Deduplication: respect canonical and parameter variations, but don’t hide problematic duplicates.
• Split content by roles: blog, service landing pages, help/knowledge base, product sections, local pages.

Which metrics to collect per URL (traffic, CTR, conversions, backlinks, update date)

The minimal column set for analysis and later conversion assessment:

• URL, H1, page type, role (traffic generator, converter, supporting).
• Search metrics: impressions, clicks, CTR, average positions (by main queries and separately branded).
• Traffic and behavior: sessions (organic), new user share, time on page, bounce/return rates.
• Business: conversions (CV), CVR, revenue/lead cost (where applicable in B2B — equivalent cost per lead/meeting).
• Links: number of referring domains, key anchors.
• Content: publish/last update date, text length, presence of FAQ/How‑to, media.
• Technical: status code, canonical, noindex, speed, Core Web Vitals.
• E‑E‑A‑T risk: author/expert presence, last update, data sources (no open links), topic coverage completeness.

Tip: separate metrics into tabs “Search”, “Behavior”, “Business”, “Links” to avoid overloaded filters.

Decision matrix: keep / update / merge / delete / noindex — criteria and examples

Below is a practical decision matrix. Base decisions on data, not feelings.

A condensed criteria table:

Decision	When to choose	What to do	Risks
Keep	Stable clicks/conversions, good positions	Minor fixes: date, micro‑updates, internal linking	Don’t break the leader — avoid changing URL or radically altering title
Update	Has impressions, low CTR/outdated content, cannibalization	Rewrite lead, add facts, E‑E‑A‑T, new sections, improve offer	Shift intent, over‑optimize
Merge	Intent/key duplication, split link equity	Merge pages: choose canonical, migrate content and links	Lose relevance if topics differ
Delete	Thin content, zero metrics, irrelevant	Delete pages with 301 to the nearest relevant page or noindex	Lose rare long tails, cause 404s
Noindex	Utility/filters, low quality not useful to search	Add noindex and block crawling if needed	Nested pages may drop out if overused

Examples:

• A 2019 blog post with traffic but low CTR — Update: add current data, a diagram, FAQ.
• Two articles “what is X” and “X in simple terms” — Merge: combine and set 301 redirect.
• Page “promo 2021” — Delete: redirect to evergreen “discounts” section or noindex.

How to compute scoring: example formula and weights for blogs/landings/docs

Scoring is needed to prioritize bulk URL decisions without debates. General scheme:

Score = w1·Traffic_Potential + w2·CTR_Gap + w3·CVR + w4·Links + w5·Freshness + w6·Cannibalization_Risk (negative)

Suggested weights (0–1) and normalization by page types:

Type	Traffic potential (impressions) w1	CTR gap w2	CVR w3	Links w4	Freshness w5	Cannibalization w6
Blog	0.35	0.20	0.10	0.15	0.15	-0.05
Service landing	0.25	0.20	0.30	0.10	0.10	-0.05
Product/knowledge	0.30	0.20	0.15	0.20	0.10	-0.05

How to calculate in practice:

• Traffic_Potential = normalized impressions for the main cluster (0–1).
• CTR_Gap = difference between current CTR and industry CTR at the same position (normalize 0–1).
• CVR = conversion rate to lead/target action from GA4/Yandex.Metrica (0–1).
• Links = log‑normalized number of referring domains (0–1).
• Freshness = 1 if no updates >12 months; 0.5 if 6–12 months; 0 if <6 months.
• Cannibalization_Risk = 1 if >50% query overlap with another page; otherwise 0.

Record results in a matrix: example thresholds, e.g., Score ≥ 0.6 — Update/Merge; 0.4–0.59 — Update; < 0.4 — Delete/Noindex (if no business value).

Step-by-step: 30/60/90 days to implement the audit

This plan helps avoid getting stuck in spreadsheets and makes changes safely production‑ready.

• Days 1–30: inventory and pilot

  • Collect URL inventory, build working sheet, calculate scoring for 50–100 pages.
  • Audit content in a priority topic, choose 10–15 URLs for a pilot.
  • Prepare texts: update articles, fix structure, visualize.
  • Set up monitoring in GSC/Webmaster + GA4/Yandex.Metrica, prepare redirect map.

• Days 31–60: scale

  • Launch pilot, measure initial results over 2–4 weeks.
  • Expand to 100–200 high‑scoring URLs; improve internal linking.
  • For duplicates — merge; for noise — delete with 301 redirect.

• Days 61–90: steady rhythm

  • Automate exports, formalize an editorial cadence for updates.
  • Finalize the decision matrix for your site, allocate roles in the team.

How to safely merge and delete pages (redirects, transfer map, control group)

The main rule — don’t break intent. Start with a control group of 5–10 URLs, then scale.

Stepwise: merging pages

1. Choose the target page (best positions/links, relevant URL).
2. Compare structures: collect sections to keep; remove duplicates and weak blocks.
3. Move strong fragments, diagrams, tables into the target; update date and E‑E‑A‑T (author, facts).
4. Set 301 redirects from all sources to the target.
5. Update internal links and menus.
6. Monitor GSC/Webmaster: positions, CTR, errors.

Stepwise: deleting pages with redirect

1. Classify candidates: thin content, outdated promos, duplicates, filters.
2. Find the closest intent match target.
3. Apply 301 redirect (no redirect chains), verify with logs and crawler.
4. If there’s no relevant target — use noindex and remove from sitemap.
5. Update internal links to point to targets.

Technical nuances:

• canonical: don’t confuse with redirects; canonical is a soft signal, 301 is a hard transfer.
• Regionality for Yandex: ensure redirects don’t route users to a different regional section without reason.
• Multi‑domains/directories: for ru/site and com/site maintain a redirect map and avoid cross 301s.

Example redirect map (fragment):

from_url,to_url,reason
/bitrix-24-obzor,/crm-obzor,merge: дубли тематики
/aktsiya-2021,/skidki,expired: акция завершена
/blog/kak-vybrat-erp,/erp-vybor,merge: каннибализация

Templates and checklists (downloadable files): working sheet, redirect map, pre‑release checklist

Below are printable template versions. Copy to Google Sheets or export as CSV.

Working sheet template (CSV) — basic structure

URL,H1,Type,Role,Clusters,Impressions,Clicks,CTR,Positions,Sessions_org,Conversions,CVR,Donors,Last_update,Status,Canonical,Noindex,Score,Decision,Priority,Owner,Sprint
https://site.ru/blog/kontent-audit,Контент-аудит,Blog,Traffic,content-audit;update,12000,600,5.0,12.3,1500,25,1.7,15,2023-05-12,200,https://site.ru/blog/kontent-audit,,0.72,Update,1,Editor,Sp1
https://site.ru/blog/audit-kontenta,Аудит контента,Blog,Traffic,content-audit,8000,280,3.5,17.1,900,10,1.1,8,2021-11-07,200,https://site.ru/blog/kontent-audit,,0.65,Merge,2,SEO,Sp2
https://site.ru/aktsii/2021,Акции 2021,Service,N/A,promotions,,0,0,–,0,0,0,0,2021-01-10,200,,,0.10,Delete,3,SEO,Sp3

Pre‑release checklist (for Update/Merge/Delete)

• Content: facts and data updated, E‑E‑A‑T blocks added, intent and structure verified.
• Search: titles/descriptions/headings free of over‑optimization, duplicate H1s fixed.
• Technical: target returns 200, redirects are 301 without chains, canonical is correct.
• Navigation: internal links, breadcrumbs and sitemap updated.
• Indexing: removed from sitemap.xml if deleted; utility pages set to noindex.
• Monitoring: annotations added in GA4/Yandex.Metrica, segments and reports set up in GSC/Webmaster.

Content audit daily operational checklist

• Reconcile inventory with sitemap.xml and logs.
• Check cannibalization by keys and intent.
• Review positions/CTR by clusters.
• Evaluate page conversions via GA4/Yandex.Metrica.
• Update status and priority in the sheet, re‑score if needed.

Tools and automation: which tools at each stage and script ideas

Tool comparison (when to use what):

Tool	Strengths	When to use	Limitations
Screaming Frog (crawler)	Full URL audit, statuses, meta, canonical	Inventory, check redirects and noindex, find duplicates	Paid for large sites, needs configuration
Ahrefs/Semrush	Links, visibility, clustering, competitors	Assess link profile, market topics, queries	Data may differ for Runet and regionality
Google Search Console	CTR, impressions, clicks, positions	Demand analysis, CTR‑gap, cannibalization	Not all traffic visible; sampling
Yandex.Webmaster	Indexing, regions, queries	RF regionality, correctness of regional sections	Logic differs from Google
Server logs	Crawl facts, errors, budget	Verify whether bots visit target URLs	Requires access, privacy care (GDPR/CCPA)
GA4/Yandex.Metrica	Behavior and conversions	Measure business impact, segment sources	Tracking schemes, attribution, privacy

Automation ideas (no code):

• Automated exports from GSC/GA4/Metric via API into Google Sheets daily.
• Conditional formatting to highlight rows by Score thresholds.
• Partial log collection with IP/UID masking to comply with GDPR/CCPA.

Examples and cases: before/after with numbers and action analysis

Case 1: B2B services blog (50 URLs)

• Actions: updated articles, unified offer and CTA, merged duplicate topics, internal linking.
• Result after 8 weeks: organic traffic +35%, CTR +1.2 pp, leads +28%.
• Contribution: 70% of the uplift came from 15 URLs in the “data analytics” topic.

Case 2: service landings (regional sections)

• Actions: revised regional content, correct regional markup for Yandex, deleted with redirects to current clusters, added city anchors and examples.
• Result after 6 weeks: positions for “service + city” improved by ~6 positions on average, calls/leads +22%.

Case 3: knowledge base (120 URLs)

• Actions: decision matrix, scoring, cleaning thin content, moved strong sections into 12 evergreen guides, set canonical on archives.
• Result after 12 weeks: pages in index −18%, organic traffic +19%, demo conversion +15%.

Example before/after (report fragment):

URL	Before (CTR/position/sessions/conversions)	After (CTR/position/sessions/conversions)	Action
/blog/kontent-audit	2.9% / 17.2 / 600 / 8	4.5% / 12.6 / 910 / 14	Update
/blog/audit-kontenta	3.1% / 19.0 / 420 / 4	4.1% / 13.8 / 720 / 7	Merge
/aktsii/2021	0% / – / 0 / 0	—	Delete (301 → /skidki)

KPIs and reporting: how to measure audit success (metrics and cadence)

• Global KPIs: organic traffic for non‑brand clusters, leads/applications, cost per lead, share of targeted traffic.
• Tactical KPIs: CTR on target queries, average positions, number of pages in index, crawl speed (from logs), depth of view.
• Operational KPIs: checklist items closed, share of URLs in Done status, adherence to deadlines.

Reporting cadence:

• Weekly: release status, indexing errors, CTR/position dynamics for the pilot.
• Biweekly: pages’ contribution by Score (Pareto 20/80), page conversion assessment.
• Monthly: traffic/leads summary, ROI calculation (if revenue from organic is available).

Common mistakes and how to avoid them

• Accidentally over‑optimizing for Google and ignoring Yandex: check regionality, mirrors, noindex and canonicals.
• Mass redirects without a map: always build a redirect map, avoid chains and loops.
• Updating for the sake of volume: updates must strengthen intent and E‑E‑A‑T, not bloat text.
• No result control: without annotations/segments in GA4/Yandex.Metrica it’s harder to prove impact.
• No scoring: without a numerical priority matrix decisions become subjective and releases random.

FAQ — answers to frequent questions

See short answers at the top of the article.

• When to perform a content audit — regularly or after events? See the cadence section: a regular cycle 3–12 months plus event audits after migrations, drops or strategy changes. In Russia account for Yandex recalculation waves and regionality.

• How to decide: update, merge or delete a page? Use the decision matrix and scoring. Update when there is demand potential and a CTR gap; merge when intent duplicates exist; delete with 301 for thin content/promotions; noindex for utility pages.

• Which metrics are essential for decisions? Impressions/clicks/CTR/positions, GA4 and Yandex.Metrica for conversions, backlinks, last update date, cannibalization and technical fields (status, canonical, noindex).

• How to set redirects when deleting/merging to avoid traffic loss? Create a map, set 301s, migrate strong blocks to the target, fix internal linking, and monitor errors and CTR/position dynamics in GSC/Webmaster.

• Which tools are best for a large audit (500+ pages)? Crawler + logs for technical state; Ahrefs/Semrush for links/topics; search consoles for CTR/positions; GA4/Metric for business metrics. Combine tools and automate exports.

---

Tips on “how to update old content” to finish:

• Don’t change the URL of well‑ranking pages unless absolutely necessary.
• Start with the lead paragraph, structure H2/H3, add concise answers and tables.
• Add/update the last updated date and assign author/editor responsibility.
• Verify intent against the SERP: informational vs commercial.
• Test the new version in staging and run the pre‑release checklist.

The material covers auditing and updating content, article refreshing, material revision, decision matrix and page conversion assessment, deletion with redirects and merging articles, working on content gaps and shaping a content strategy.