Open the project, go to Settings, and click Delete Project in the Danger Zone. A dialog names the project and warns that all tracking data, audits, and keywords will be permanently removed. Confirm to delete.
You’re returned to the Projects list.
Who can delete
Deleting requires the owner or admin role. A member sees the button, but the request is rejected. See Roles and permissions.
What gets removed
Everything belonging to the project cascades from the delete, so nothing is left behind:
- Tracked keywords and their full position history
- Backlinks, referring domains, anchors, and new/lost history
- Every site audit and all crawled page data
- Domain overview metrics and detected tech stack
- AI search, GEO, local SEO, and web vitals history
- Saved keywords and research results
- Reports built on the project, and their shared links
- Its four collection schedules, and any report automations
Shared report links stop working immediately. Anyone holding one gets a not-found page.
What survives
- The organization, its other projects, and its members
- Your plan and billing history
- API keys — they’re organization-scoped, so they keep working for other projects
Deleting a project frees a slot against your plan’s project limit right away.
Deletion cannot be undone and there is no archive or trash. Ranking and backlink history is accumulated day by day — creating a new project for the same domain starts from zero, with no back-fill. A year of position history is gone permanently.
Before you delete
If you might want the data later, export what you need first. Reports are the practical way to preserve a snapshot: build one covering the period you care about and share or download it before deleting.
Consider whether you actually need to delete. A project you stop looking at costs you a project slot, but the alternatives are worse if you’re wrong:
