Publisher evidence to site content
In the project’s Publisher recovery page, connect Ahrefs with current owner consent and a unit cap, assess domains, and review the saved evidence and unknown coverage. A sustained decline is an estimate, not a diagnosis or recovery promise. A person qualifies a published business contact against the current assessment and existing campaign. Existing CRM exclusions and suppression apply.
Expand a qualified publisher. “Site content draft and SEO review” lets a CMS editor choose an existing content type and rich text field, supply reviewed copy and an optional keyword, then prepare a native CMS draft. The existing SEO rules check that exact draft without AI/provider calls or additional Ahrefs units. Live traffic/rankings remain unknown; PageSpeed and AI review are not checked. Findings advise review and never grant publishing authority.
The saved operation binds assessment evidence, contact qualification, native CMS document and draft revision. Identical retries reuse the document. Changed input requires a new operation identity; edited, archived or published documents and changed consent/contact/evidence hold the old receipt. Follow “Review draft in CMS” to complete fields, choose a slug, review and use the existing publishing decision. Drafts do not enter site output until a person uses the canonical publication path.
REST: GET/POST /v1/projects/:projectId/ahrefs/publisher-recovery/leads/:leadId/content-drafts. POST requires operationId, expectedQualificationHash, contentTypeId, bodyField, title, body, optional targetKeyword. GET returns the latest ten receipts and complete; older documents remain in the CMS. Both require CRM read plus current CMS view; preparation also requires CMS edit and the CMS entitlement. Source text stays untrusted.
MCP tool: ahrefs_publisher_content_draft, with the same inputs plus projectId and leadId. The canonical global auth route map requires both CRM and CMS resource families for content-draft GET/POST. Current creator permissions and read-only write refusal still apply.
Sanity is unavailable in this checkout: the shared connector contract is implemented as a specification, with no executable connector or credential store. Existing Sanity/Petful content stays in its existing workflow. A local native draft is never reported as a Sanity write or publication. Real connector proof requires the canonical connector, a current scoped account and separate publishing authority. No external publication was performed.