A project groups jobs for one client or site. Jobs do not need a project; anything you submit without one still works exactly as before.
Create a project
-
Open Projects in the sidebar and choose New project, or pick New project from the project field when you submit URLs.
-
Give it a name, such as the client or the site. You can rename it later from the project page.
-
When you submit URLs, choose the project in the Project field. Opening Index URLs from a project page preselects it.
What a project shows
The project page lists its sitemaps and its most recent jobs, and counts every URL in the project by status, in the same way as a job page: indexed, in progress, not indexed yet, refunded, failed, skipped and any that need your review or credits.
Index rate
Once a project has finished results, the page shows its index rate next to the URL count, for example “72% indexed”. The rate is the share of indexed URLs among URLs from completed batches only. Pending URLs are excluded, even if some of them are already indexed, so the rate only moves when a batch finishes. Failed URLs are also excluded. Hover over the rate to see the counts behind it. Credits return only after a failed indexing result is confirmed, usually after 14 days.
Large projects list the 100 most recent jobs on the project page. The counts still cover every URL in the project.
Watch a sitemap
A project can watch up to 10 sitemaps, so new pages are found as they are published without pasting URLs.
-
On Index URLs, choose From a sitemap and pick the project, or on the project page choose Add sitemap. Enter the address of your sitemap or sitemap index. Compressed
.xml.gzsitemaps and plain-text lists work too. Sitemaps and pages must be on the same site as the address you enter;www.and the bare domain count as one site. -
Choose what happens to URLs already in the sitemap. You can pick the ones you never submitted and send them yourself (the default on Index URLs), or skip them and only watch for new URLs (the default on the project page).
-
Optionally limit which pages are sent, for example only
/blog/, and never/tag/. A path covers every page under it;*matches any characters.
We read each sitemap every six hours. To read one now, open its menu and choose Check now. Settings in the same menu shows what the last read found and lets you change the filters. A URL that was not there before is new. A new URL is offered only if it matches your filters and you have never submitted it from your account, so a page that is indexed, in progress, or was refunded is not sent again. A page the checks skipped earlier, such as one that redirected, can be sent once it appears again.
New URLs wait for you. The project page shows how many are waiting. Submit sends them all. Review lists them so you can tick the pages to send and submit only those, or dismiss the ones you never want sent. Pages you leave unticked keep waiting.
To skip the review, turn on Submit new URLs automatically in the sitemap’s settings. New URLs are then submitted as a job after each read, up to your limit (100 by default), and use credits without asking you first. If one read finds more than your limit, for example after a site move, those URLs wait for you instead.
Every submitted URL goes through the usual checks before sending and uses a credit only if it is sent.
If the first read cannot open every file in a sitemap index, nothing counts as new until a later read finishes, so pages that were missed are not sent by mistake.
Projects from your tools
- CLI:
indexmysite project list,indexmysite project create <name>,indexmysite project show <project-id>, andindexmysite submit --project <project-id> <urls...>. See the CLI. - API:
GET,POST, andPATCHunder/api/indexing/projects, plus an optionalprojectIdwhen you create a job. Sitemap watches are under/api/indexing/projects/:id/sitemapsand/api/indexing/sitemaps/:id. See the API.