The Content Audit: Find More Value Before You Create More Content

A new blog post or website page costs time and money. Before you create one, check whether your website already has a page that can do the job.

That older page might be out of date, hard to find, or too weak to turn a visitor into a customer. It may only need better information, clearer wording, or an easier next step.

Starting over can also throw away search history, links, and trust the page has already earned.

Sometimes the right move is to improve an existing page.

Sometimes two pages should become one.

Sometimes a page no longer serves a useful purpose.

A new page is only the answer when nothing you already have can fill the gap.

What is a content audit?

You do not need a content calendar, a large marketing team, or a complicated spreadsheet.

If your website has collected pages you rarely think about, this guide will help you decide what deserves your attention first. Treat those pages as marketing assets your business already owns, then decide which ones still earn their place.

Run our FREE Content Audit Tool to turn a public website crawl into a prioritized first-pass queue. It can also combine browser-only GA4 and Google Search Console exports for stronger evidence. It never changes your site.

---

Why Should You Check Existing Content Before Creating More?

A new page starts with no search history, links, or proof that your customer needs it. An existing page may already appear in search, answer a common question, support a sale, or help someone choose your business. Improving that page gives you a head start.

Age does not make a page bad. Low traffic does not make it disposable. A page can earn its place by converting visitors, attracting links, answering a support question, helping a salesperson, documenting a policy, or serving a narrow customer need.

A drop in clicks needs a diagnosis. It can come from a technical problem, lower demand, changed search intent, or a weaker page. Google’s guide to debugging search traffic drops recommends comparing periods, queries, pages, countries, devices, search appearance, technical issues, and demand before a major edit.

---

What Should You Protect Before Changing Anything?

Protect the homepage, contact pages, service and product pages, checkout and account pages, support content, and legal or accessibility pages at the start.

Their business role outweighs a simple traffic count.

For every page that may change, save the current copy and record five things:

1. The URL and its current business job
2. The visits, search demand, leads or sales, links, and support use you can verify
3. A copy of the current page
4. The proposed action and the reason for it
5. The person who will confirm the decision and the condition that would reverse it

Before a merge, redirect, noindex, or removal, have the person implementing it record the current HTTP status, canonical, indexability, sitemap membership, internal links, redirect destination, and technical rollback steps.

For a redirect, record the exact relevant destination before approval. Never use the homepage as a catchall for unrelated deletions.

Google Search Console’s Removals tool can temporarily block a URL from Search, generally for about six months. It does not replace a redirect, noindex, authentication, or a correct 404 or 410.

Define rollback before implementation.

Save the old content and redirect map, then name the traffic, conversion, or revenue loss that would justify restoring them.

---

How Do You Run a Fast Content Audit?

Start with a work queue, not a perfect spreadsheet.

1. Enter your domain in the FREE Content Audit Tool.
2. Read the coverage note, then confirm that your homepage, contact, service, support, and legal pages are protected.
3. Start with three pages: one valuable page, one declining page, and one page you suspect should be merged or removed.
4. Open Manual Review first. Conflicting evidence deserves attention before easy wins.
5. Add GA4 and Search Console page exports in your browser only when the public evidence cannot support a safe decision.
6. Export the queue with each URL’s recommendation, reason, confidence, missing evidence, and next step.

The tool tells you when it reviewed only part of a larger site.

Uploaded analytics stay in your browser, and the audit never changes the website.

---

Why Did the imFORZA Pilot Stop at Manual Review?

We ran the browser tool against imforza.com to test one important safeguard: it should refuse to delete a page when the evidence conflicts.

The full-domain run found 149 public URLs and reviewed a balanced sample of 75. Then we aimed it directly at two older articles. It recommended Manual Review, Low confidence for both.

Using Evergreen Content for Long-Term Results had 36,987 sessions, a 55.6 percent engagement rate, zero key events, and two live referring domains in the current 12-month GA4 and link pull collected August 22, 2026. It also contained stale advice about hiding a publication date.

Nine sessions did not make the page disposable. The links and stale advice did not automatically make it a merge candidate either. Shared subject matter is not shared intent. We still need its Search Console queries, internal links, and evergreen-specific value before choosing Refresh, Merge, or another action.

The Comprehensive Website Analysis Guide had 84,254 sessions, a 10.7 percent engagement rate, zero key events, and one live referring domain in the same evidence window. It also referred to renamed or retired platforms.

The page still attracts visits, while engagement is weak and parts of the guidance are stale. That mix does not justify a deletion or redirect. It tells us exactly what to inspect next: queries, landing paths, internal links, and the page’s distinct job.

No page was rewritten, removed, noindexed, merged, or redirected during the pilot.

---

What Data Should You Collect for a Content Audit?

The first pass sorts the work.

A useful SEO content audit goes beyond rankings. These reports strengthen the decision when a page carries traffic, links, revenue, or technical risk.

Whether you use the browser tool, a crawler, or a content audit template, keep one row per URL and keep the evidence separate from the recommendation.

Google Analytics 4

For the beginner pass:

1. Open Reports > Engagement > Landing page.
2. Set a full trailing-year date range so seasonal changes do not distort a short window.
3. Find one URL.
4. Read Sessions as visits that started on the page.
5. Read Key events and Total revenue as evidence that those visits led to a tracked business action.
6. Write one conclusion in plain language, such as: “This page still attracts visits, but it has not produced a tracked lead or sale.”

Use Share this report > Download file > Download CSV for the browser tool. Do not rename the export columns.

Optional advanced checks: Open Pages and screens for page activity beyond entrances. Use Path exploration to see where visitors go next, and Funnel exploration when the page belongs to a defined inquiry, booking, signup, or checkout path. Use Realtime and Admin > Data display > DebugView to verify tracking after an approved change.

See GA4’s Landing page report, Pages and screens report, and Path exploration.

Google Search Console

For the beginner pass:

1. Open Performance > Search results.
2. Set the same review period used in GA4.
3. Open the Pages tab and select one URL.
4. Read Clicks as visits from Google and Impressions as appearances in search results.
5. Switch to Queries to see what job Google currently assigns to the page.
6. Write one conclusion, such as: “Google shows this page for the right questions, but few searchers choose it.”

The Search Console Performance report supports these page and query checks.

Use Export > CSV from the Pages tab for the browser tool. Keep the original headers:

• GA4: Landing page or Landing page + query string
• Search Console Pages: Top pages or Page, plus Clicks, Impressions, CTR, and Position
• Search Console Queries: use this export during manual review because query rows do not identify a page by themselves

Optional advanced checks: Use Indexing > Pages for index status, URL Inspection for the selected URL, Links for internal and external link evidence, Core Web Vitals for page-experience issues, Sitemaps for submitted URL coverage, and Settings > Crawl stats for crawl patterns.

Ahrefs and a Crawler

In Ahrefs, open Site Explorer > Top pages, filter for declining traffic, then open each selected page’s Content Changes timeline. Use Organic keywords to review ranking changes, Keywords Explorer > SERP overview > Identify intents to compare intent, and Site Audit for crawl evidence. Ahrefs’ guide to content decay is useful for diagnosis, but vendor metrics do not override your sales, support, or legal evidence.

Export the relevant rows for the URLs under review, then add backlinks, referring domains, keywords, and traffic change to your work queue. Ahrefs data is manual evidence in this version of the browser tool, not an upload.

For a full crawl, export status codes, canonicals, indexability, sitemap inclusion, redirect chains, titles, H1s, internal links, broken links, structured data, and similarity signals from Screaming Frog or Sitebulb. A fixed word count cannot decide quality.

The Four Separate Decision Lenses

Use four questions on the same page:

• SEO: Can search systems crawl, index, understand, and match this page to the right query? Check status, canonical, sitemap, links, queries, clicks, impressions, CTR, position, and backlinks. Our guide to showing up on Google explains the broader search foundation.
• Answer visibility: Does the page give a clear, supported answer that search features and AI assistants can quote accurately? Google says its AI features use the existing Search index. Its guidance for AI features and websites does not require special AI schema, a fixed word count, or text chunking. The AI-Ready Website Playbook covers the wider technical and content foundation.
• User experience: Can one reader understand the purpose, scan the answer, use the page on a phone, complete forms, and find the next step?
• Conversion: Does the page support the right action for its job? A generic button is not evidence. Check key events, revenue, inquiry or checkout paths, and sales or support use. An informational page may assist a later decision.

Run the URL through PageSpeed Insights for mobile field and lab data, then use WAVE or axe for an accessibility pass. Test the page yourself with a phone-sized viewport and a keyboard. A score can point to a problem, but it cannot tell you whether the answer or next step makes sense.

Use GA4 Path exploration or Funnel exploration for the on-site path. Then check the CRM, form inbox, call tracking, or ecommerce platform for the quality and value of the action. A tracked button click is not the same as a qualified lead or completed sale.

---

What Is the Content Audit Decision Tree?

Use this order for every URL:

1. Does the page serve a real customer or business job?
2. Does that job still fit the business?
3. Is the page available, crawlable, and indexable as intended?
4. Does another URL serve substantially the same intent?
5. Is the problem stale information, missing coverage, weak structure, or a broken next step?
6. Is there enough evidence for a safe action?
7. Assign Keep, Refresh, Expand, Merge, Redirect, Noindex, Remove, or Manual Review.
8. Create a new URL only when no existing page can own the verified gap.

Here is the short version:

• Keep when the page is accurate, useful, technically sound, and clear about its job.
• Refresh when the purpose still fits but facts, links, examples, structure, or the next step are stale.
• Expand when the right page owns the intent but misses a verified question or needed step.
• Merge when several pages satisfy substantially the same intent and one survivor can do the combined job.
• Redirect when a moved or retired URL has a clearly relevant permanent replacement.
• Noindex when a non-sensitive page must remain public but has no search role.
• Remove after you evaluate business value, links, conversions, demand, legal or support use, and replacement options.
• Manual Review when the signals conflict or a risky decision is missing evidence.

---

How Do You Apply Each Content Audit Action?

Keep, Refresh, Expand, and Manual Review are planning decisions you can make without changing how a URL works. Merge, Redirect, Noindex, and Remove change what visitors or search systems receive. Stop before implementation unless you or your technical partner can test the response, indexing signals, internal links, sitemap, and rollback.

When Should You Keep a Page?

Keep a page when it is accurate, useful, technically sound, and still serves a clear job. Record that job, fix only clear defects, and set a trigger for the next review. This protects valuable pages from calendar-driven rewrites.

1. Write the page’s job in one sentence.
2. Save its baseline search, conversion, and link evidence.
3. Fix genuine defects without rewriting the page to satisfy the calendar.
4. Name the event that should trigger another review.

When Should You Refresh a Page?

Refresh when the URL and purpose still fit, but the facts, sources, examples, screenshots, links, structure, or next step need meaningful work.

Keep the useful parts and update the weak ones. Google’s people-first content guidance supports changes that make a page more useful, not cosmetic date changes.

A content refresh should solve named problems, not make the page look busy.

1. Preserve the current copy and performance baseline.
2. Mark the exact claims, sources, examples, screenshots, links, and steps that are stale.
3. Compare the page’s current query intent with the job it should keep.
4. Replace weak material while preserving useful sections, earned links, and the existing URL.
5. Update the title and description only when they no longer match intent.
6. Recheck structured data, internal links, and the conversion path.
7. Add a modified date only after a meaningful revision, then test the CTA and links.

After a useful refresh, plan how the updated page will be seen again. Our content distribution strategy covers the channels, repurposing moves, and settings that matter before and after publication.

When Should You Expand a Page?

Expand when the page owns the right intent but leaves a verified question unanswered. Use Search Console Queries, sales questions, support tickets, on-page search, and the current search results to find the gap.

1. List the unanswered queries or customer questions.
2. Confirm that this URL, not a neighboring page, should own each answer.
3. Add the missing answer, evidence, example, or next step under a descriptive heading.
4. Link to a separate page when the question belongs to another stage or intent.
5. Recheck the page’s flow and CTA. Do not pad it to reach a word count.

A concise answer under a descriptive heading can improve comprehension without forcing artificial content chunking.

When Should You Merge Pages?

Merge when two or more pages satisfy substantially the same intent and one strong page can do the combined job. Choose the survivor by intent fit, links, traffic, conversions, URL clarity, and long-term role.

1. Build a query-to-page comparison for every candidate.
2. Confirm that the pages satisfy the same need, not just that they mention the same topic.
3. Choose the survivor by intent fit, links, traffic, conversions, URL clarity, and long-term role.
4. Move only the material that improves the survivor.
5. Create a source-to-destination redirect map with one final destination per retired URL.
6. Update internal links, navigation, canonicals, structured data, and the XML sitemap.
7. Apply a server-side 301 or 308 redirect directly to the survivor.
8. Crawl the old and surviving URLs, then compare search and conversion baselines.

Google’s guidance covers both redirects and site moves with URL changes.

When Should You Redirect a Page?

Redirect when a moved or retired URL has a clearly relevant permanent replacement. Point the old URL directly to the final destination with a server-side 301 or 308. Remove redirect chains and update internal links so visitors and crawlers do not rely on the redirect.

1. Confirm that the old and new pages serve equivalent intent.
2. Verify that the destination returns 200, is indexable, and contains the promised information.
3. Record the source, final destination, reason, baseline, and rollback condition.
4. Add a server-side 301 or 308 with no intermediate hop.
5. Replace internal links to the old URL with the final URL.
6. Remove the old URL from the sitemap and confirm the destination’s canonical.
7. Test the source in a browser and crawler. Inspect the source and final destination separately in Search Console URL Inspection.
8. Monitor destination traffic, conversions, and indexing alongside requests for the old URL.

A canonical is different. rel="canonical" leaves both URLs accessible and signals a preferred version. It is a strong hint, not a guaranteed instruction. Use it when duplicate variants must remain available. Use a redirect when the old URL is no longer needed. Google’s canonicalization guide explains the distinction.

When Should You Noindex a Page?

Noindex a non-sensitive page when it must remain publicly accessible but has no search role. Use authentication for private content, rel="canonical" for duplicate variants with a preferred version, and a dedicated crawl-control plan for large filter or faceted spaces.

1. Write down why the page must remain available but should not appear in search.
2. Add a noindex robots meta tag or x-robots-tag response header.
3. Allow crawlers to access the page so they can read the directive.
4. Remove the URL from the XML sitemap.
5. Confirm that the page is not a duplicate that should consolidate into a preferred canonical URL.
6. Use URL Inspection to confirm that Google can see the directive.

Blocking the URL in robots.txt can prevent Google from reading noindex. Google’s noindex documentation covers the requirement.

When Should You Remove a Page?

Content pruning should follow this test. Remove a page only after evaluating its business role, conversions, links, search demand, legal or support use, and replacement options. Low traffic alone never earns this action. Redirect when a close replacement exists. A 404 or 410 can be correct when no useful role or relevant replacement remains.

1. Confirm that business, search, link, conversion, legal, sales, and support checks are all clear.
2. Confirm that no relevant replacement serves the same intent.
3. Save the content, baseline, inbound-link list, and rollback condition.
4. Remove normal internal links and the sitemap entry.
5. Return a real 404 or 410.
6. Test the HTTP status. Do not return 200 with an empty message.
7. Monitor referral requests, crawl reports, and customer reports.

Do not send an unrelated deletion to the homepage. Keep a useful custom error page while preserving the correct status. Google documents how it handles HTTP status codes and crawl errors.

When Should You Use Manual Review?

Use Manual Review when signals conflict, the page’s job is unclear, coverage is partial, or a risky action lacks evidence. Protect the page and name the next check, such as queries, internal links, landing paths, or sales use.

1. Keep the current URL and index state unchanged.
2. Write the conflict as one decision question.
3. Name the missing report, person, or live check that can answer it.
4. Assign an owner and review date.
5. Return the page to the queue with the new evidence.

---

How Often Should You Review Your Content Audit Queue?

You do not need to re-audit the entire website every month. Keep one small batch active, finish it, and recheck the result before opening another.

At Publication

Record the audience, intent, business job, CTA, owner, sources, canonical URL, and review trigger. Link the page into its topic cluster so it does not launch as an orphan.

Monthly

Review priority commercial and conversion pages. Investigate the largest verified declines, choose one to three pages, and check completed changes against their monitoring conditions.

Quarterly

Audit one topic cluster. Check query-to-page overlap, orphaned pages, internal links, stale claims, conversion paths, and redirect chains. Choose one controlled batch, then measure it before starting the next one.

Annually

Run the full website content audit. Review old redirects, utility pages, structured data, legal pages, support content, sitemaps, and content ownership. Reconfirm that every surviving URL has a job.

This schedule turns maintenance into normal publishing work. A content calendar can contain a refresh, a merge, and an internal-link cleanup without pretending that three new articles are the only useful output.

---

Content Audit FAQs

---

Choose the Next Page Decision

Pick three URLs: one valuable page, one declining page, and one page you suspect should be merged or removed. Record the evidence and assign one action to each. If an existing page can own the need, improve the asset you already have. Create a new URL only when the gap is real and no current page can fill it.

Run our FREE Content Audit Tool for the first pass. You can run it yourself, ask us to review the queue, or have us implement and monitor the changes you approve.

---