On this page
SEO content analysis is a structured review of whether a page answers the right question, supports its claims and works for the reader. Combine a full editorial read with page-level search data, technical checks and business purpose. A low score or a missing analytics row does not tell you whether the page should be deleted.
Build a page-level audit record
Start with the canonical URL and read the whole page, including tables, captions, links and calls to action. Record the evidence and decision in one place.
| Audit field | What to record |
|---|---|
| Purpose and audience | The task the page completes and its relevance to the current business. |
| Search baseline | Date range, property, search type, impressions, clicks, CTR and position. |
| Data status | Observed zero, available result or unavailable/incomplete data. |
| Editorial findings | Missing answers, unsupported claims, obsolete products and confusing examples. |
| Experience | Mobile layout, image quality, links, forms and measured loading issues. |
| Decision and owner | Retain, improve, merge or propose retirement, with reasons and approval. |
Swipe the table to see all columns.
Work through six analysis steps
1. Verify the search task
Review the page’s actual queries and the current results for relevant searches. Does the reader want instructions, a comparison, a definition or a purchase page? A high-volume phrase is not automatically the right target. Keep distinct tasks separate, but do not create a page for every synonym.
2. Check completeness and original value
Write down the questions a reader still cannot answer. Look for a useful example, verified screenshot, clear decision process or first-hand evidence. Add what helps complete the task rather than expanding the page to reach a word count.
3. Verify evidence and product fit
Open the original sources behind statistics and technical claims. Record their date and scope. Distinguish a historical customer result from a current product capability. Remove retired features, unavailable offers and claims that the evidence does not support.
4. Review structure and next actions
Inspect the title, opening answer, headings and link labels. Remove duplicate introductions and unrelated sections. Check that the promised template or example is actually present. Follow the call to action to confirm it leads to the relevant current product.
5. Test the published experience
Check tables, screenshots, captions, forms and navigation on a small viewport. Confirm image dimensions, sensible responsive sizes and lazy loading below the initial viewport. Measure loading performance separately; a layout screenshot is not a speed test.
6. Choose and document the action
Explain why a page should remain separate, be improved, be merged with equivalent coverage or be proposed for retirement. Preserve useful historical evidence and existing search demand when deciding. Before any removal, review links, conversions and a genuinely relevant replacement.
Interpret search metrics without overclaiming
CTR is clicks divided by impressions. Average position is an aggregate, so inspect query and device differences rather than treating it as one fixed rank. Compare equivalent periods and note campaigns, seasonality or site changes that could affect results.
The Search Analytics API documentation explains that results are limited to top rows and are not guaranteed to include every row. Preserve unavailable data as unavailable. Do not turn an omitted URL or query into a claim of zero demand.
| Observed situation | Next investigation |
|---|---|
| Many impressions, low CTR and low position | Review query fit, coverage and competing page types before blaming the title. |
| First-page visibility with a vague promise | Check whether the title and opening accurately describe a useful answer. |
| Clicks but few relevant actions | Inspect the audience, offer, form and handoff rather than adding more keywords. |
| No row in an export | Check filters, property, dates and reporting limits before proposing removal. |
Swipe the table to see all columns.
A worked audit decision
Suppose a fictional payroll site has three articles repeating the same provider-switching checklist. One has a useful handover table, another has current expert review and the third contains obsolete screenshots. The audit decision could be to combine their useful material into the most appropriate destination.
Record which sections and evidence will move, which URLs have existing links and whether the remaining pages serve any distinct task. Approve the consolidation and redirect plan before changing URLs. Do not send all retired pages to the homepage merely because it is convenient.
Carry the decision into RankWell
- Review existing coverage and drafts in RankWell.
- Use Visibility research as an input, with the market, date and limitations recorded.
- Prepare a brief that names the audit decision, missing answers and approved sources.
- Supply current product facts and original examples. Have AIMEE flag unknowns instead of filling them with assumptions.
- Review and approve the draft, publish through the available configured destination and inspect the live page.
Common questions
Should you delete every low-traffic article?
No. Check product relevance, distinct purpose, conversion value, links and the completeness of the evidence. A low-traffic support resource may still help customers.
Does a content score prove the page is good?
No. Read the page, verify its claims and test the task. Scores cannot replace subject expertise or a working reader journey.
How do you assess the update?
Save the release date and compare equivalent periods after recrawling. Report search changes and meaningful actions separately, with any concurrent changes that limit attribution.
Reviewed and updated October 7, 2026.
Written by
