Onsite SEO

Site audits and tasks

Crawl the client site, turn findings into prioritised tasks with AI-written fixes, and deploy the approved ones.

Tasks is where site problems are found and fixed. Three panels sit in the left rail and the workflow runs left to right through them.

Panel	What it is for
Audit	Run the crawl and read the findings, scores and issues.
Tasks	The prioritised work queue with AI-written fixes, review and approval.
Script	How approved fixes reach the live site, and the state of the script on it.

Running an audit

Start an audit from Onsite SEO → Tasks. The crawler walks the site, collects page metadata and technical signals, and writes a report you can revisit. Large sites are crawled in batches by a background worker, so you can leave the page and come back once it finishes.

What gets checked

Titles, meta descriptions, heading structure and duplicate or missing metadata.
Indexability: status codes, redirects, canonical tags, robots directives and sitemap coverage.
Content quality signals: thin pages, keyword coverage, internal linking.
Images: missing alt text and oversized assets.
Structured data presence and validity.
Core page performance signals.

Tasks

Findings become tasks with a category, a priority and a status. For most on-page tasks the platform also generates the replacement copy, a rewritten title, meta description, heading or paragraph, grounded in the client's AI Training context and target keywords.

1
Review
Read the finding, the affected URL and the proposed rewrite.
2
Edit
Adjust the copy if it needs a human touch. Nothing publishes without approval.
3
Approve
Approve individually, or bulk-approve a filtered set once you trust the pattern, for example every "missing meta description" task on a low-risk page type.
4
Deploy
Approved changes are pushed through your connected integration, WordPress, the SEO script, or exported for a developer.

Deployment paths

Connect WordPress once with an application password under Integrations. Approved title, meta description and content-block changes are pushed through the WordPress REST API directly to the matching post or page. Best when the client already manages the site in WordPress and you want changes to appear in their own editor history too.

Bulk approval is powerful

Filter to one task type and spot-check several rewrites before bulk-approving. Reverting many live page changes is slower than reviewing them.

Recurring audits

Scheduled audits re-crawl on a cadence and open new tasks only for new findings, so the list stays a to-do list rather than a report you reread. A deeper weekly scan covers slower checks such as URL inspection and structured-data validation.

Common problems

Symptom	Likely cause	What to do
Audit stalls partway through	Very large site or the crawler hit a rate limit / bot protection.	Let the background job continue, large sites batch over longer windows. Check for a firewall rule blocking the crawler if it never resumes.
Same finding reopens every audit	A fix was approved in the platform but never actually deployed, or a template regenerates the issue on every publish.	Confirm the deployment integration is connected and check the task's deploy status, not just its approval status.
AI rewrite looks generic	The client profile or AI Training knowledge base is thin on that topic.	Add more source material (service pages, brochures, FAQs) to AI Training, then regenerate the task.
Bulk-approved change broke formatting	A rewrite assumed a page structure that this template does not use.	Revert the task, fix the template mismatch, and approve remaining tasks individually for that page type.