Content checks
Review your website's writing with source text, suggested corrections and clear coverage.
Content checks review the text on your public pages for spelling, grammar, unfinished copy and contradictions between metadata, headings and page content. They provide specific suggestions with the original text and an explanation.
Start a review
- Confirm the Project environment and website URL.
- Open Site Audit and choose Review content. Review the available SEO credits before starting.
- Follow progress and open ready findings in Issues → Content, or keep All selected to see technical and content issues together.
A content review is independent of Run audit. It can run before, during or after a technical audit. Starting a technical audit does not start an AI review.
The review discovers public pages through sitemaps and links, respecting robots rules and excluded paths. Coverage is shown separately from the technical audit. A partial scan does not establish that all pages were checked.
Read a suggestion
Open an affected page to see the original quotation, the suggested replacement or removal, and the reason. Confirmed corrections and findings marked Needs review have different certainty; check the context before applying either.
Copy suggestion copies the proposed text. Open page lets you inspect the source. Neither action changes your website. Edit through your normal workflow, review the change and publish when ready. AI can make mistakes, particularly with names, deliberate phrasing and incomplete context.
Short bold text and inline code, such as a button label, a product name or a command, are treated as names. Spelling and grammar suggestions do not change them, and a sentence such as "Changes keeps every version" is not reported for using a singular verb.
The current review supports confidently identified English, Spanish and Russian content. Unsupported or mixed-language passages and unavailable text remain unverified. A scan with no confirmed findings is not a guarantee of error-free writing.
Progress, history and pauses
Ready findings appear as the scan progresses. You can leave the page and follow the run through background activity. Saved results retain their own check time, including when a newer scan is still running or a recheck fails.
A scan can pause because it reaches a processing limit, available credits are insufficient or a provider is temporarily unavailable. Read its specific reason. Continue review resumes eligible pending work; it does not turn failed or unchecked pages into successful checks. Use a new explicit scan when you need fresh evidence for changed content.
Unchanged, previously validated results may be reused. Reused evidence retains its observation date. The report's coverage tells you what was checked, reused or unavailable.
When the page changes
Later site audits and rechecks of the same pages, and the page fetches of a newer review, compare saved findings with the current text without AI or credits. When a finding's text is no longer on the page, it leaves the open findings, counts, exports and repair briefs, and the review shows how many findings are no longer on the current page. In a content issue's affected pages, choose … no longer on the current page to read them, marked Not on the current page and without copy or repair actions.
This means only that the saved text changed, not that the new copy is correct; run a new review to check it. If the text returns, the finding is open again. A page that could not be fetched completely never marks a finding as gone.
Credits and exports
AI content checks share the Organization's monthly SEO credits with external research and AI action plans. They are included in free access within that allowance; there is no separate paid-plan requirement. Technical audits remain available independently of the research balance.
Site Audit's Export includes available content results as a separate section of the PDF, Excel, CSV (ZIP) or JSON report, and so does the Dashboard export. When no finished technical audit is available, for example while one is running, the button becomes Export review and downloads the selected review on its own. A running or paused scan exports its current evidence with that status. The PDF shows up to 100 prioritized findings; the data formats keep every exported finding.
The CLI can start, continue or cancel a review and read its findings with siteos seo content. MCP reads saved results; it does not start a paid review.
For checks before publication and corrections inside your editor, use SiteOS for Sanity Studio.