A SaaS content audit checks whether existing pages still answer buyer questions accurately, then assigns a justified action: keep, refresh, rewrite, investigate consolidation, or retire with an approved plan. Use the worksheet and worked examples below to choose the next page to improve.
Copyable SaaS content-audit worksheet
Make one row per page. Link the evidence rather than replacing it with a single score. The examples in this section are fictional editorial exercises, not measured customer results.
| URL or page | Buyer task | Observed gap and evidence to attach | Decision | Owner and acceptance check |
|---|---|---|---|---|
| Pricing page | Check whether the plan fits | Public copy disagrees with the approved current plan sheet | Refresh | Product owner confirms limits; editor checks live copy and next step |
| Integration guide | Understand setup prerequisites | Setup steps describe a retired permission screen | Rewrite affected instructions | Integration owner verifies the current path and prerequisites |
| Comparison guide | Choose between two approaches | Intro never states criteria; useful comparison appears much later | Refresh structure | Reviewer can find criteria and qualified conclusion near the start |
| Two brief-template posts | Prepare the same writer assignment | Both answer the same question; distinct value not established | Investigate overlap | Compare evidence, links, queries, and reader tasks before any URL decision |
| Onboarding checklist | Prepare implementation | Accurate checklist; no evidenced missing answer | Keep | Owner records the next product-change trigger |
To create your own worksheet, copy these columns and replace every example with a real URL, observation, and evidence link. An empty analytics field means unknown; it is not proof of zero demand.
How to use Search Console in a content audit
Export queries and pages for a stated date range. Group wording variations that represent the same reader task and compare them with the page's title, opening answer, and useful supporting material. Search Console impressions describe when your site appeared; they are not total keyword search volume.
A relevant query with impressions and no clicks is an investigation lead. Check the actual results and whether the page promise matches the task. A low average position may limit exposure; a zero-click result does not, by itself, prove the title is the problem. Search Console also omits some queries, so query-table totals can differ from page totals.
Record the baseline before editing. Compare equal date ranges after enough time has passed to observe the revised page, and keep product launches, indexing changes, seasonality, and small samples visible. Do not attribute a later improvement to the copy alone without stronger evidence.
A practical order for the first audit pass
- Correct a misleading product or availability claim, and reproduce any broken contact or signup path.
- Review a commercially important page with a concrete missing answer and an available evidence owner.
- Improve an existing page receiving relevant queries before commissioning another page for the same task.
- Investigate overlap only after comparing both pages; preserve URLs until a consolidation decision is approved.
- Leave accurate, useful pages alone when you cannot name a reader benefit from rewriting them.
Turn the selected finding into one assignment with scope, evidence, owner, and a live acceptance check. For SaaS-specific page types and query examples, use the SaaS content playbook. For planning new coverage after the audit, see the keyword clustering example.
A content audit should produce decisions: keep, refresh, rewrite, investigate consolidation, or retire with an approved plan. A list of URLs is the inventory; the audit adds a reason and a verifiable next action.
Build an Inventory That Supports a Decision
Combine your current sitemap or CMS inventory with important historical URLs. Include pages used in sales conversations and support, even when they receive little search traffic. Group page types so a pricing page is not judged by the same expectations as a definition article.
Use the following copyable audit structure:
| Field group | Information to record |
|---|---|
| Identity | URL, title, page type, owner, and live status |
| Purpose | Intended reader, main question, search intent, and next step |
| Product accuracy | Current features, availability, setup, limits, and evidence owner |
| Search | Available queries, impressions, clicks, and comparable date ranges |
| Visitor behavior | Available visits, useful actions, and attribution limits |
| Content quality | Direct answer, clear scope, useful examples, supporting sources |
| Technical state | Access, indexability evidence, canonical, redirects, links |
| Decision | Action, reason, dependency, owner, and verification method |
Keep facts separate from interpretations. “The page describes an integration as available” is an observation. “This claim causes weak conversion” is a hypothesis unless you have evidence that establishes the relationship.
Use Consistent Prioritization Criteria
Assess five dimensions together: business role, current opportunity, severity of the gap, effort, and risk. Use a consistent qualitative rubric or a clearly documented scoring method. A score is a prioritization aid, not a prediction of traffic or revenue.
Business role asks whether the page helps a relevant buyer understand, compare, or use the product. Opportunity considers the search and audience evidence you actually have. Gap severity identifies the missing or inaccurate answer. Effort includes research, product review, design, and technical dependencies. Risk considers the cost of leaving misleading or harmful information in place.
Avoid turning absent data into zeros. If conversion tracking is incomplete, record that limitation. If a keyword metric is unavailable, do not label it a measured lack of demand.
A Worked SaaS Audit Decision Table
The following is an illustrative editorial scenario, not a measured customer audit or a claim about specific live pages.
| Observation | Likely work | What must be checked before acting |
|---|---|---|
| A feature page describes a retired workflow | Product-accuracy refresh | Confirm the current workflow with its owner |
| An integration page promises a connection that is not released | Correct availability language | Verify release evidence and setup requirements |
| A guide receives relevant impressions but few clicks | Review query fit, title, and answer | Compare the actual queries and page promise |
| Two template articles answer the same question | Define distinct intent or investigate consolidation | Review both pages' useful material, links, and performance |
| The main CTA leads to an error | Technical fix | Reproduce the failed journey and verify the corrected destination |
| An accurate article serves an existing audience | Keep and monitor | Confirm that a rewrite has a useful purpose |
The table does not prescribe a rewrite for every weak metric. A broken route is not fixed by a better introduction. A release dependency is not solved by changing “planned” to “available.” Two similar titles do not automatically justify a redirect.
Separate Refreshes From Strategic Rewrites
A refresh changes specific outdated or missing information while preserving the page's purpose. It might update the setup requirements for an integration or replace an inaccurate product description.
A strategic rewrite changes the answer's structure, audience, or angle because the existing page no longer serves its intended role. It requires a new brief, evidence plan, and review standard.
Consolidation is a separate decision. Preserve the useful material and establish which URL should own the intent before approving content moves, redirects, or deletion. A canonical tag is not a substitute for making a clear editorial decision.
Turn the Finding Into a Useful Assignment
For each selected page, write a compact assignment: who it should help, what is wrong now, which evidence supports the finding, what should change, and how you will verify the result.
Suppose the feature explanation is missing keyword clustering and Content Kits. The assignment should name those capabilities and their actual boundaries. It should not ask for “more modern copy” without explaining how the visitor's decision changes.
In RoboWrite, keyword strategy and a reviewed topic can inform the next brief. A Content Kit can then organize the required coverage, facts, sources, and selected elements. Existing imported-content refresh or rewrite actions follow their supported workflow; they should not be described as automatically using the new-item kit pipeline.
Preserve Evidence and Review After Publication
Record the old URL, the observed problem, the relevant date range, the approved change, and the live verification. Keep the original evidence so a later reviewer can distinguish a resolved issue from a changed measurement.
After publication, check that links and metadata work and that the page reflects the approved facts. Later, review relevant queries, clicks, and useful product actions. At low traffic levels, use individual observations and counts rather than claiming a reliable conversion lift.
Revisit priority as the product changes. A page that was accurate last month may need attention after a release. A recurring missing-source problem may be a brief or product-information problem rather than a writing problem.
Next Step
Choose one important page and complete the audit table before requesting a rewrite. Use the SaaS founder content workflow to connect the chosen decision to an appropriate research, brief, and review process.
Sources and Further Reading
- Google's SEO Starter Guide: a reference for foundational search checks.
- Google Search Console Performance documentation: context for search-performance observations.
- RoboWrite Public API guide: current generation, refresh, rewrite, and Content Kit scope.
