Skip to main content
Open a project and go to Settings in the project sidebar. The page has three sections: General, Schedules, and Danger Zone. The subtitle under the heading shows the project’s domain, so you can confirm which project you’re editing. On the sample project, every setting is shown with its controls switched off; only deleting it works.

General

Project Name

Edit the field and click Save Changes. The name updates everywhere immediately — the project card, the sidebar switcher, and reports that reference it. Nothing that’s been collected is affected.

Domain

Shown read-only. A project’s domain is fixed for the project’s life, because every ranking, backlink and audit is keyed to it. The API doesn’t accept a domain change either: a project update takes its name, its schedules, and — over the API — the markets its forms and pages start on. To track a different domain, create a second project. That’s also the better outcome if you’re migrating — you keep the old site’s history for comparison instead of losing it.

Where markets are chosen

There’s no market setting here. Each tracked keyword and each AI prompt has its own search engine, location and language, chosen when you add it, and the pages that search — Keyword Research, Trends and the AI searches — have a country and language picker of their own. What you chose when you created the project is only where those start.

Schedules

When each of the project’s four recurring jobs runs — Rank tracking, Backlinks, AI visibility and Local SEO — each daily, every 3 days or weekly, at an hour in a timezone you choose, and each can be paused. Owners and admins can change them; members see them read-only. A job your plan doesn’t include — Local SEO on Starter, which has no local locations — is listed as Not on the Starter plan with an Upgrade link, and has no Runs or Edit. The API refuses to change its schedule too. Scheduled runs don’t use your monthly allowances. They’re covered by what the project holds — tracked keywords, AI prompts, local locations — so how often they run changes nothing on your usage. The sample project runs none. Each schedule also shows where it stands:
  • Next run — when it runs next, in the schedule’s timezone. Overdue means it came due and hasn’t started; Paused means it won’t run until it’s switched back on.
  • Last run — the newest run of that job, whether its schedule started it or someone did (On demand, which includes a new project’s first run): its status, when, and how long it took. A failed run says why.
  • Skipped — shown when the schedule came due while the organization had no active plan. Nothing runs then, and a skipped run isn’t made up later.
Runs opens the run history: every run of the job, newest first, ten at a time, with the same details. Switch the filter to see another job, or all four together. Anyone in the organization can see it. Through the API, schedules are part of the project record. Where they stand is GET /v1/projects/{projectId}/schedules, and the run history is GET /v1/projects/{projectId}/schedules/runs, paged, with an optional job_type.

Danger Zone

Delete this project

Click Delete Project and confirm in the dialog, which names the project you’re about to remove. See Delete a project for exactly what’s removed. Deleting requires the owner or admin role. Members don’t see this section.

What isn’t here