## **📌 What this article covers**

Some customers see an unwanted brand or project, such as ShieldPan, come back after they delete it. Audits and alerts may start again and credits can drop. This article explains common causes and the steps to stop the activity.

## **🔍 Why a deleted project can come back**

Deleting a project removes it from your current view, but it can return if something still has permission to create or run it. Common causes include:

- **Shared access:** Another user, agency seat, or connected account still has access and recreates the project.
- Scheduled recrawls and monitoring only run for active (non-archived) projects. A deleted project returns only if the domain is added again, for example by another user, a connected GSC/OTTO property, or an invite or integration that re-creates it. Schedules and alerts on other projects are a separate source of credit use.
- **More than one workspace:** The same brand exists in another project or client folder you can still open.
- Signing in does not bring a deleted project back. It returns only if the domain is re-added (manually, via GSC/OTTO connection, or by another user), which restores the archived audit and starts a new crawl.

This is usually a permissions or automation issue, not proof that someone else controls your login. Still treat unexpected projects seriously and review who can access the account.

## **🛠️ Remove the project and stop new audits**

1. Open the project list and confirm the exact project name, such as ShieldPan.
2. Open that project and turn off scheduled audits, alerts, and any other recurring jobs before you delete it.
3. Check team or client access and remove users who should not manage this brand.
4. Delete the project, then sign out and sign back in to confirm it stays gone.
5. Review other workspaces so a copy of the same brand is not still active.

If the project returns after these steps, do not delete it repeatedly without noting the time it reappears. That timing helps support find the job or user that is recreating it.

## **📊 How credits are used**

Credits are used when the platform runs work such as audits. A project that keeps running those jobs can lower your balance even if you did not start them manually. Alerts themselves are notices about that work. They do not replace the credit charge for the audit.

- Check recent activity for the project name and the time of each audit.
- Pause or delete only the jobs tied to the unwanted brand.
- Leave unrelated projects running so you do not interrupt other client work.

Search Atlas cannot add credits automatically from a help article. If charges came from an unwanted project that you could not stop, support can review the activity and advise on your balance.

## **🔐 Check account access**

While you wait, protect the workspace:

- Review every user who can open the account and remove anyone you do not recognize.
- Sign out of unused sessions if your account settings allow it.
- Do not share your password in chat. Support will never ask for it.
- Avoid creating a new project with the same brand name until the old one is confirmed removed.

## **💬 When to contact support**

Contact support if the project returns after you remove access and turn off jobs, if audits continue, or if you want a credit review. Include the project name, when it reappeared, and a short note of which audits ran.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.