On this page
- Build the audit worksheet
- 1. Inventory the actual published content
- 2. Define what success means
- 3. Find search opportunities
- 4. Fact-check the important claims
- 5. Check the current product workflow
- 6. Improve the answer and search presentation
- 7. Review links, structure, and images
- 8. Test the mobile experience
- 9. Interpret performance evidence correctly
- 10. Publish with a rollback and verify
- 11. Measure and schedule the next review
A website content audit turns your page inventory into decisions: keep, correct, improve, consolidate, or retire. Combine search and business data with a direct review of the content. Do not delete a page solely because it has few organic visits or a low word count.
Use the checklist below to prioritize useful changes, verify the release, and measure what happened afterward.
Build the audit worksheet
| Column | Record |
|---|---|
| Identity | URL, title, content type, owner, publication and modification dates |
| Purpose | Audience, task, intended next step, relevant product |
| Search evidence | Impressions, clicks, CTR, average position, queries, date range |
| Business evidence | Qualified enquiries, customer use, referral value, conversions |
| Content findings | Outdated claims, missing steps, unsupported statistics, useful existing material |
| Technical findings | Status, canonical, indexing directives, links, media, mobile issues |
| Action | Decision, reason, owner, priority, backup, release and review dates |
Swipe the table to see all columns.
1. Inventory the actual published content
Export the CMS inventory and compare it with the sitemap and crawl results. A crawler may miss unlinked pages; a sitemap may contain outdated URLs. Keep canonical URLs and variants distinct until you understand their relationship.
Separate evergreen guides, product pages, historical announcements, and case studies. Historical material should be labeled with its original context, not automatically rewritten to sound current.
2. Define what success means
A support article may save customers time without producing sales enquiries. A pricing page should help buyers compare the actual offer. A statistical reference should provide traceable numbers. Give each page a purpose before judging its metrics.
3. Find search opportunities
In Search Console, review pages with substantial impressions, falling relevant clicks, or useful queries that the current page answers poorly. Filter the page and inspect its queries rather than relying only on a sitewide average.
Use consistent date ranges and account for seasonality, country, device, and query mix. Google’s performance metric definitions explain the reporting scope. Low CTR can reflect ranking position or result features as well as wording.
4. Fact-check the important claims
Open the source behind each important statistic or instruction. Confirm its date, population, methodology, and whether it supports the sentence. Distinguish estimates, company disclosures, measured results, and illustrative examples.
Check arithmetic and units. Visits are not users, monthly totals are not daily counts, and an old price is not the current offer. If a number cannot be verified, remove it or clearly explain the limitation.
5. Check the current product workflow
Follow the actual steps in the product. Replace obsolete navigation, unavailable controls, and unsupported promises. Label screenshots with the context needed to understand them, and avoid presenting demo data as a customer result.
For BrandWell content planning, use Visibility > Keywords > Research, then RankWell > Articles > Plan before you write > Check opportunity. Prepare the brief from the audit findings and review the draft’s sources, examples, and search preview.
6. Improve the answer and search presentation
Put the direct answer near the beginning. Add missing practical steps, examples, and decision criteria. Preserve valuable original material instead of making every article the same length.
Write a title and description that accurately describe the page. Do not use fixed character counts as proof of correctness or repeat a keyword to reach a density target. See our title guide.
7. Review links, structure, and images
Check internal links, source links, heading hierarchy, image alternatives, and the social-sharing image. Confirm that calls to action lead to a relevant current destination. Remove obsolete embeds that no longer help the reader.
Where pages overlap, compare their intent and unique value before combining them. Preserve important information and use a relevant redirect if a URL is retired. Do not redirect every removed article to the homepage.
8. Test the mobile experience
Inspect the page on a phone-sized viewport and, where possible, a real device. Check menus, forms, sticky elements, tables, image sizing, and readability. A desktop window resize checks responsive layout but does not reproduce every phone behavior.
Google’s Mobile-Friendly Test was retired in December 2023. Use current browser tools and PageSpeed Insights for diagnostics, alongside real interaction checks.
9. Interpret performance evidence correctly
The current Core Web Vitals are LCP, INP, and CLS. Use their current definitions and distinguish field data from individual lab runs. Do not assume every one-second delay causes the same conversion loss on every site.
Structured data should describe visible, accurate content and meet the relevant feature requirements. Valid markup does not guarantee a rich result or a higher ranking.
10. Publish with a rollback and verify
Save the original content and metadata or create a CMS revision. Check for concurrent changes before overwriting a page. After publication, verify the public title, canonical, image, links, content, and mobile presentation.
Track full editorial reviews separately from targeted corrections and automated checks. Finding no flagged phrase is not the same as verifying every fact in an article.
11. Measure and schedule the next review
Record the release date, then compare equivalent periods after recrawling. Review qualified actions alongside search visibility. Avoid claiming that one edit caused all subsequent change.
Choose the next review based on how quickly the subject changes. Product instructions and pricing may need more frequent checks than an evergreen writing example. There is no universal two-week audit duration or fixed waiting period for every website.
For crawl-specific instructions, use our content crawl workflow.
Reviewed and updated October 2, 2026.


Julia McCoy
