Try this skill in Strawberry
An SEO audit can produce hundreds of findings and still avoid the decision: what should the team do next? The useful work is connecting search demand, site performance, content, technical constraints, competitors, product fit, and conversion value into a credible priority.
Strawberry can inspect the live site and search results in the browser while working with approved Search Console, analytics, crawl, rank, and research tools. Your companion can keep links and screenshots beside important findings and make sampled, estimated, stale, or conflicting data visible.
Define the site and decision
Clarify the site, audience, market, priority products or pages, competitors, timeframe, and decision the audit should support. Choose a focused question, first-pass audit, recurring review, or redesign of an existing process rather than assuming every property and page needs equal depth.
Align the evidence before diagnosing
Use the approved sources most likely to change the decision: Search Console, analytics, rank or crawl tools, previous audits, keyword research, the live site, competitor sites, and current search results. None is an automatic prerequisite.
Align properties, periods, markets, devices, attribution windows, query definitions, and tool methods before comparing them. A platform estimate and an observed site outcome should not carry the same confidence.
Look for problems and opportunities that matter
- Queries and pages with meaningful impressions but weak position or click-through.
- Pages or templates losing visibility, traffic, conversion contribution, or index coverage.
- Search needs and competitor formats the site does not credibly serve.
- Overlapping, stale, thin, or unsupported content.
- Technical, rendering, crawl, structured-data, internal-linking, or page-experience issues.
- Material differences by brand, market, device, page type, funnel stage, or audience.
Do not infer opportunity from search volume alone. Consider intent, authority, product fit, competition, conversion value, effort, and whether the team can create something genuinely useful.
Prioritize the underlying issues
Group related symptoms into the underlying issue when the evidence supports it. Prioritize by likely impact, confidence, effort, dependency, risk, and time to learn rather than presenting an inflated checklist.
| For each priority | Make clear |
|---|---|
| Evidence | The source, date, scope, and what was actually observed. |
| Why it matters | The audience, search, product, or conversion consequence. |
| Next action | The concrete owner, dependency, and smallest useful change or investigation. |
| How to learn | The baseline, expected signal, review window, and uncertainty that remains. |
Deliver a report that leads to action
Lead with the decision-relevant findings and action plan. Include scope and source limits, the current baseline where available, supporting links or screenshots, owners, dependencies, and a sensible review point.
A report does not approve changes to site copy, technical settings, publishing, tracking, paid search, or spend. Keep those actions separately scoped and verify completed work.