Begin with a page-level review that has clear boundaries. A useful first pass can improve content clarity and identify issues worth investigating further.
Define the scope
Prepare the public website URLs, target audience, business goal, and the language or market to review. Choose a small page set before asking for a full-site assessment.
Give the task to the agent
In a research project or focused conversation, use a brief such as:
Review these five public pages for content clarity and basic on-page SEO: [URLs]. Record each page’s visible title and headings where available, likely reader intent, content gaps, and useful internal-link opportunities. Return a prioritized action list with URLs and evidence. State what you could not inspect. Do not change the website.
If a page requires sign-in or cannot be reached, keep that gap visible. Do not substitute an assumption for an observation.
Evaluate the findings
- Open a sample of cited pages.
- Confirm that the observation matches the live page.
- Separate visible content facts from interpretations about user intent.
- Group recommendations by likely usefulness and effort.
- Identify technical questions that need a separate measurement or tool.
For a recommendation to change a title, ask for the proposed text and the reason. For a claimed technical defect, ask how it was tested.
Understand the limits of the review
A few inspected pages do not establish a full crawl, ranking history, backlink analysis, search-console access, or measured performance results. Supply authorized data or a suitable tool if the question requires those inputs.
Do not promise traffic or ranking improvements from an untested change. Treat the result as a prioritized review for a human owner to evaluate.
Turn findings into work
Ask for a separate implementation brief for the accepted changes. Include the affected URL, current issue, proposed revision, evidence, and a way to verify completion. Keep website editing or publishing as a distinct request.