
Site audit in Claude: choose and verify three fixes
What the assistant reads, what it writes, and where you decide. An illustrative audit with its limits stated.
Your SEO assistant, inside Claude and ChatGPT
Checks your site, plans the content, and publishes to WordPress after your review. Nothing goes live until you say so.
Continues on app.advisorseo.ai. Nothing on your site is changed.
You
Check peakplumbing.co.uk/boiler-repairs and tell me what to fix first.
AdvisorSEO
The page has no heading that names the service and the city, the title repeats the home page title, and two images have no alt text. Fix the heading first. It is the line search and answer engines read to learn what the page is about.
Checked the public page only. Rankings, traffic and AI citations are not part of this check.
You
Plan an article from the boiler pressure keyword in my shortlist.
AdvisorSEO
Plan: "Why your boiler keeps losing pressure". Three sections: the three usual causes, what you can check yourself, when to call someone. Audience: homeowners in Sheffield. Source keyword: boiler losing pressure. Monthly searches: Not provided.
Preview shown. Saved only after you confirm.
You
Write the boiler pressure article from the plan, and hold it for me.
AdvisorSEO
Drafted against the Peak Plumbing profile. It answers the three questions people ask before they call, names Sheffield once in the heading and once in the body, and links the boiler repairs page.
Ready for your reviewWhy your boiler keeps losing pressure
1,240 words · drafted against the Peak Plumbing profile.
Nothing reaches peakplumbing.co.uk until you approve.
AdvisorSEO
Publishedpeakplumbing.co.uk/boiler-losing-pressure
approved by you at 14:02 · WordPress draft or live post, your choice at approval.
The preview, your confirmation and the publication record are kept together.
Illustrative example, not customer results. Approval actions shown are an example.
Before anything goes live
Read the whole piece in the conversation or in your account. Change it, or send it back.
The site, the address and the post type are shown before you decide.
One explicit yes per publication. Your WordPress application password can be revoked in WordPress at any time.
Capabilities
Context, plan, check, prepare, publish, follow up. Every family reads the same business profile and ends in something you can approve.

Keep the facts about your business close to every SEO task: services, area, audience, voice. Set once, used by every plan and draft.

Turn research into a ranked writing plan.

Findings with evidence, and a clear next step.

Access rules, passage clarity, structured data. AI-answer tracking is planned, not live.

Draft, preview, one yes, then WordPress.

Enquiries with the page they came from, stages, follow-up notes, and one overview of sites, drafts and leads. A source page shows where a form was filled in. It is not proof that SEO caused the enquiry.
See all 85 capabilities registered in the server source, with setup and approval limits.
Worked example
Every task reads the same profile: what you do, where, for whom, and how you sound. Set it once, change it any time, and every plan and draft leans on it.
Peak Plumbing, Sheffield. Boiler repair, emergency call-outs, radiator work. Homeowners, landlords, letting agents. Plain, direct, no jargon.
Supplied by the owner, not verified by AdvisorSEO. Illustrative example, not customer results.
A bounded crawl of your own site, findings with evidence, an audit history, and a checklist that says plainly when a person has to decide.
Illustrative example, not customer results.
Preview, your confirmation, and the publication record are kept together. Draft or live post, your call at approval.
Illustrative example, not customer results.
Compare
Choose AdvisorSEO for a focused workflow from site checks to reviewed content and captured leads. Consider Semrush for broad research data, backlinks and live AI-visibility measurement.
Scroll across to compare every column. With a keyboard, focus the table and use the arrow keys.
| The job | AdvisorSEO | Semrush | Verdict |
|---|---|---|---|
| Publishing approved content from inside the connector | yes, with a preview and your confirmation | data and read-only methods in its connector; publishing lives elsewhere | AdvisorSEO, for connector scope |
| Updating lead stages in the same workspace | yes | not in its documented connector surface | AdvisorSEO, for this workflow |
| Keyword and competitor research data | stores your research | its own datasets | Semrush |
| Backlink research | none | dedicated analysis | Semrush |
| AI-answer mentions | planned | offered | Semrush |
Planned pricing
Published for review, not yet available to purchase. No card is taken on this site. US dollars, tax excluded.
From the blog

What the assistant reads, what it writes, and where you decide. An illustrative audit with its limits stated.
Finish one small, reviewable piece of SEO work.
Understand what a connection can read and change.
Access, passages and structured data, with the limits stated.
Questions
A Claude or ChatGPT account where connectors can be added, and a website you own or are authorized to manage. A WordPress site is needed only for publishing.
No. Every publication shows the content, the destination and the action first, and runs only on your confirmation. A page-speed measurement, when configured, is stored without a separate confirmation because it changes nothing on your site.
From research you or your assistant bring in. AdvisorSEO stores keywords with their source. It does not measure search volume or difficulty, and a stored field is not a ranking.
Not yet. AI-answer and citation tracking are planned. Today's readiness checks read your pages; they do not watch any answer engine.
Publishing uses WordPress application passwords, which you create and can revoke in WordPress. The lead snippet works on any site where you can add one line before the closing body tag.
It stays in the workspace you chose at consent. We do not sell it or use it to train models. Removing the connector, revoking the WordPress password, deleting the snippet and deleting retained records are four separate steps, each described in the privacy policy. Several sites in one workspace share that workspace's access. Client-level permission separation is a workspace design question; ask us before relying on it.
Not yet. Plans are planned and shown for review. Write to us and we will tell you what is available for your account.

Continues on app.advisorseo.ai. Nothing on your site is changed.