Content audit without spreadsheets: a visual approach

A content audit does not need a spreadsheet.

That's a controversial statement in SEO circles, where the spreadsheet-based audit has been the default methodology for 15 years. Export your crawl data to CSV. Import into Google Sheets. Add columns for scoring, status, action items. Share with the team. Watch it slowly rot as tabs proliferate, formulas break, and the follow-through collapses the moment someone rage-quits at row 847.

The spreadsheet isn't the problem. The problem is that spreadsheets reward data collection over action. It's easy to add another column, another tab, another formula. It's hard to answer the question that actually matters: "What should I work on next?"

This guide walks through a visual approach to content auditing that replaces the spreadsheet with a sortable, filterable audit surface — one that updates as your site changes and tells you what to fix instead of just documenting what exists.

If you're a content strategist or agency operator who has started and abandoned at least one spreadsheet-based audit, this is for you.

The five ways spreadsheet audits fail

Spreadsheet audits don't fail because the people doing them are lazy. They fail because the tool is wrong for the job. Here are the five failure modes:

1. The data goes stale immediately

A spreadsheet is a snapshot. The moment you finish populating it, the site changes. Pages get published, redirects get added, metadata gets updated. Within a month, your audit data diverges from reality. Within a quarter, it's fiction.

2. The scope creeps through columns

Every stakeholder wants "just one more column." SEO wants keyword data. Product wants conversion rates. Leadership wants a status column. The person running the audit wants scoring. By the time everyone has their column, the sheet has 30 columns and no one can parse it at a glance.

3. The scoring is inconsistent

Manual scoring (rating pages 1–5 on quality, relevance, performance) requires judgment calls. When one person scores the first 200 pages and another person scores the next 200, the scores drift. What counts as a "3" on Tuesday is different from a "3" on Friday.

4. The handoff breaks the chain

The person who builds the audit spreadsheet rarely executes the actions. The handoff — from auditor to writer to developer to reviewer — requires everyone to navigate the same spreadsheet. Most don't. The audit sits in a shared drive, technically complete, practically abandoned.

5. The repeat audit starts from scratch

When it's time to re-audit (quarterly, annually, after a migration), the spreadsheet can't diff itself. You can't easily compare this quarter's audit to last quarter's. You export fresh data, build a new sheet, and start over. The institutional memory of the previous audit is locked in a tab nobody opens.

What a visual audit surface looks like

A visual content audit replaces the spreadsheet with two things: an audit table and a visual sitemap.

The audit table

An audit table looks like a spreadsheet at first glance — rows of URLs, columns of data. The difference is that it's connected to a live crawl, not a static export. When the site changes, the table changes. The data includes:

• Page URL, title, H1
• Meta description (present, missing, duplicate, truncated)
• Word count
• Internal link count (inbound and outbound)
• Indexability status (indexable, noindex, canonicalized elsewhere)
• HTTP status code
• Lighthouse performance score
• Organic traffic (if GA4 is connected)
• Search impressions and clicks (if GSC is connected)

The columns are sortable and filterable. Instead of scrolling through 800 rows looking for problems, you filter to "meta description = missing" and see only the 47 pages that need attention. Filter to "word count < 300" and see your thin content. Sort by "traffic descending" and focus your effort on the pages that matter most.

The visual sitemap overlay

The visual sitemap shows your site structure as a hierarchy — homepage at the top, sections branching down, individual pages as leaf nodes. Each node is color-coded by a health metric: content quality, performance score, indexability status, or traffic level.

This is where the spreadsheet can't compete. A spreadsheet can tell you that /blog/old-post-from-2019 has thin content and zero traffic. A visual sitemap shows you that the entire /blog/2019/ branch is a dead zone — 40 pages, none with meaningful traffic, all dragging down the average content quality of the blog section. That's a different insight. It changes the action from "fix this one page" to "consider pruning this entire section."

How to run a visual content audit

The methodology is similar to a spreadsheet audit. The difference is in the tooling and the speed of each step.

Step 1: Crawl the site

Start with a full crawl. Every page the crawler can reach gets ingested into the audit table with its metadata, content metrics, and technical attributes. This replaces the "export to CSV and import to Sheets" step.

A crawl of a 500-page site typically takes under five minutes. The result is a complete inventory — the equivalent of the spreadsheet's first tab, but already filterable and connected to the live site.

Step 2: Connect analytics data

If you have GA4 and Google Search Console connected, the audit table automatically blends traffic and search data into each row. This replaces the "VLOOKUP from GA4 export" step — the step where most spreadsheet audits lose an afternoon to URL-matching problems.

The combined view shows you, for every page: what it is (metadata), how it performs (Lighthouse), whether people find it (GSC impressions), and what they do when they arrive (GA4 sessions and engagement).

Step 3: Filter to problems

Instead of scoring every page manually, use filters to surface the pages that need attention:

• Missing metadata: Filter to pages with empty title tags or meta descriptions. These are quick wins.
• Thin content: Filter to pages below your word count threshold. Evaluate whether they need expansion, consolidation, or removal.
• Low-traffic pages: Sort by traffic ascending to find pages that exist but nobody visits. Cross-reference with indexability — are they indexed but not ranking, or not indexed at all?
• Performance outliers: Sort by Lighthouse score to find the slowest pages. These may need template-level fixes rather than content changes.
• Orphan pages: Filter to pages with zero inbound internal links. These are invisible to both users and search engines.

Step 4: Decide actions per page

For each page surfaced by your filters, assign one of four actions:

• Keep — the page is performing well. No changes needed.
• Improve — the page has potential but needs updating: fresh content, better metadata, more internal links, performance fixes.
• Consolidate — the page overlaps with another page. Merge the content into the stronger page and redirect.
• Remove — the page is thin, outdated, and receives no traffic. Redirect to the most relevant surviving page or return a 410.

Step 5: Review the visual sitemap

After filtering and assigning actions in the audit table, switch to the visual sitemap view. Look for patterns that individual page analysis misses:

• Entire sections that are underperforming (a red branch on the sitemap)
• Deep pages that are buried too far from the homepage
• Content clusters that lack internal linking connections
• Sections with high traffic but poor content quality scores

Step 6: Act and re-crawl

Execute the actions. Then re-crawl the site to verify the changes took effect. The audit table updates automatically — no new spreadsheet needed. Over time, you build a history: each crawl is a version of the audit, comparable to the previous one.

When spreadsheets still win

Intellectual honesty requires acknowledging the cases where a spreadsheet is the right tool:

• One-time audits for a site you'll never touch again. If you're auditing a single site as a one-off project with no ongoing relationship, a spreadsheet is fine. The data doesn't need to stay fresh because there's no "next time."
• Custom scoring models with complex business logic. If your scoring model requires weighted formulas involving revenue data, pipeline attribution, or other data sources outside the crawl, a spreadsheet's formula engine is hard to beat. (Though at that point, you probably want a database, not a spreadsheet.)
• Stakeholders who refuse to leave Google Sheets. Organizational reality sometimes trumps tool superiority. If the marketing VP reviews content in Sheets and won't change, export the data for them while you use the visual tool for your own work.

For everything else — ongoing audits, multi-site audits, team-based audits, audits that need to result in action — the visual approach produces better outcomes faster.

How Evergreen handles content audits

Evergreen's content audit table is built for the workflow described in this guide. Crawl a site, and every page appears in the audit table with its metadata, content metrics, indexability status, and Lighthouse performance score. Connect GA4 and Search Console, and traffic and search data blend into each row automatically.

The table is sortable by any column and filterable by any attribute. "Show me pages with missing meta descriptions, sorted by traffic" is two clicks, not a VLOOKUP.

The visual sitemap overlays content health data onto your site structure. Sections are color-coded by the metric you choose — performance, content quality, traffic level, indexability status. Patterns that take an hour to find in a spreadsheet are visible in seconds.

Shareable report URLs let you send the audit to clients or teammates without exporting a CSV. They see the same filterable, sortable view — not a static snapshot.

On the free plan, you can audit one site with up to 500 pages. That's enough to try the workflow on your own site or a client's before committing.

Ditch the spreadsheet. Audit visually → Start free

Frequently asked questions

Can I export audit data to a spreadsheet if I need to?

Yes. Most audit tools, including Evergreen, support CSV export. The visual audit doesn't replace the spreadsheet — it replaces the spreadsheet as the primary working surface. Export when you need to share with someone who insists on Sheets, or when you need to run custom formulas the tool doesn't support natively.

How do I track audit progress if I'm not using a spreadsheet?

The audit table itself tracks status. Filter to pages you've already addressed (metadata updated, content refreshed) and pages that still need action. Re-crawling the site updates the data, so pages where the fix has been deployed automatically reflect their new state.

What about content scoring? Spreadsheets let me score pages manually.

Manual scoring is where most spreadsheet audits slow down. The visual approach replaces manual scoring with metric-based filtering — instead of rating every page 1–5 on "quality," you filter to pages that objectively have issues (thin content, missing metadata, no traffic, poor performance). The remaining pages, by definition, don't need immediate attention.

Is this approach suitable for large sites (10,000+ pages)?

Yes, and it's actually where the visual approach pulls furthest ahead. Manually scoring 10,000 pages in a spreadsheet is a multi-week project. Filtering 10,000 pages to the 200 that need attention is a 10-minute task. The visual sitemap makes section-level patterns visible at scale in a way that scrolling through thousands of rows cannot.

Your next step: crawl your site in 60 seconds → Create free account